Update 2-4-3-Pentest.md

Author: julio-cfa

current-version/2-Process/2-4-Operation/2-4-3-Pentest.md

@@ -1,6 +1,6 @@
 ### Penetration Test
 
-A penetration test, or pen test, is a simulated attack on systems and applications to identify exploitable vulnerabilities. It involves attempting to breach web and mobile applications, APIs, network devices, workstations, servers, and more, uncovering issues like SQL injection, code injection, XSS, and privilege escalation.
+A penetration test, or pen test, is a simulated attack on systems and applications to identify exploitable vulnerabilities. It involves attempting to breach web and mobile applications, APIs, network devices, workstations, servers and more, uncovering issues like SQL injection, code injection, XSS and privilege escalation.
 
 While penetration testers use automated tools for scanning and information gathering, most testing is conducted manually. Manual testing is crucial for detecting vulnerabilities related to business logic and other issues that automated scans might miss.
 
@@ -16,11 +16,11 @@ A penetration test can be approached in three ways: black-box, gray-box, or whit
 
 Regardless of the approach, penetration testers will generally follow publicly-available and/or internal checklists and testing guides. The most popular ones are:
 
-- [OWASP Web Security Testing Guide (WSTG)](https://owasp.org/www-project-web-security-testing-guide/) -  a comprehensive guide to testing the security of web applications and web services.
-- [OWASP Mobile Application Security Testing Guide (MASTG)](https://mas.owasp.org/MASTG/) - similar to the OWASP WSTG, it is a comprehensive guide to testing mobile applications.
-- [OWASP Top 10](https://owasp.org/www-project-top-ten/) - most common and impactful web application security vulnerabilities.
-- [OWASP Top 10 API](https://owasp.org/API-Security/editions/2023/en/0x11-t10/) - most common security risks and vulnerabilities for APIs.
-- [OWASP Mobile Top 10](https://owasp.org/www-project-mobile-top-10/) - a list containing the most common and impactful mobile application security vulnerabilities.
+- [OWASP Web Security Testing Guide (WSTG)](https://owasp.org/www-project-web-security-testing-guide/) - A comprehensive guide to testing the security of web applications and web services.
+- [OWASP Mobile Application Security Testing Guide (MASTG)](https://mas.owasp.org/MASTG/) - Similar to the OWASP WSTG, it is a comprehensive guide to testing mobile applications.
+- [OWASP Top 10](https://owasp.org/www-project-top-ten/) - Most common and impactful web application security vulnerabilities.
+- [OWASP Top 10 API](https://owasp.org/API-Security/editions/2023/en/0x11-t10/) - Most common security risks and vulnerabilities for APIs.
+- [OWASP Mobile Top 10](https://owasp.org/www-project-mobile-top-10/) - A list containing the most common and impactful mobile application security vulnerabilities.
 
 ### Process Overview
 
@@ -38,20 +38,41 @@ After assembling the penetration testing team, the organization must meticulousl
 - Define the requirements - e.g. testing accounts, credentials, documentation, etc.
 
 #### Requirements
-Once the scope and dates are defined, the penetration testing team will communicate their requirements to the organization. These may include testing credentials, application documentation, source code access, and other necessary resources. It is crucial for the organization to promptly provide all requested information and access before testing begins to ensure a smooth and effective penetration testing process.
+Once the scope and dates are defined, the penetration testing team will communicate their requirements to the organization. These may include testing credentials, application documentation, source code access and other necessary resources. It is crucial for the organization to promptly provide all requested information and access before testing begins to ensure a smooth and effective penetration testing process.
 
 #### Execution
+After receiving the necessary requirements, such as credentials and documentation, the penetration testing team will begin assessing the system or application. It is crucial for the penetration testing team to:
 
+- Notify the organization immediately if their tests cause any disruption to a system, especially if it is in production, to mitigate potential impacts on business operations.
+- Report any critical vulnerabilities discovered promptly to the organization, as these could have significant financial and/or reputational consequences, allowing for swift remediation and risk management.
+- If the penetration testing team finds any indicators of compromise (IoC) that an incident may have happened, they must notify the organizatio immediately.
 
-#### Reporting
 
+#### Reporting
+Upon completing all tests, the penetration testing team will begin compiling a comprehensive report. This report should be structured as follows:
+
+- Cover
+- Table of Contents
+- General Information
+  - Penetration Testing Team
+  - Methodology
+  - Scope 
+- Executive Summary
+- Vulnerabilities
+  - Title
+  - Severity
+  - Description
+  - Impact
+  - Mitigation
+  - References
+- Conclusion
 
 ### Tools
 There are several tools that can help while performing penetration test against applications. The most common are:
-- [BurpSuite](https://portswigger.net/burp) - a comprehensive software tool used for web application security testing. Key features include a proxy for intercepting and modifying web traffic, a scanner for automated vulnerability detection, and tools for performing manual testing, such as repeater, intruder, and so forth.
-- [OWASP ZAP](https://www.zaproxy.org) - an open-source tool similar to BurpSuite.
-- [Postman](https://www.postman.com/) - API testing tool that allows sending various HTTP requests, manipulating headers, and automating tests. It helps identify vulnerabilities like authentication issues and data exposure, integrating with other security tools for comprehensive analysis.
-- [MobSF](https://github.com/MobSF/Mobile-Security-Framework-MobSF) - automated, open-source tool for security testing and analyzing mobile applications, supporting both Android and iOS platforms.
+- [BurpSuite](https://portswigger.net/burp) - A comprehensive software tool used for web application security testing. Key features include a proxy for intercepting and modifying web traffic, a scanner for automated vulnerability detection and tools for performing manual testing, such as repeater, intruder and so forth.
+- [OWASP ZAP](https://www.zaproxy.org) - An open-source web proxy similar that has features similar to BurpSuite's.
+- [Postman](https://www.postman.com/) - API testing tool that allows sending various HTTP requests, manipulating headers and automating tests. It helps identify vulnerabilities like authentication issues and data exposure, integrating with other security tools for comprehensive analysis.
+- [MobSF](https://github.com/MobSF/Mobile-Security-Framework-MobSF) - Automated, open-source tool for security testing and analyzing mobile applications, supporting both Android and iOS platforms.
 
 ### References
 - [OWASP Penetration Testing Methodologies](https://owasp.org/www-project-web-security-testing-guide/latest/3-The_OWASP_Testing_Framework/1-Penetration_Testing_Methodologies)