Focus area · Pentesting

Penetration Testing

How authorised security testing is scoped, governed and reported, and how findings feed risk decisions.

Penetration testing is authorised, simulated attack against systems to find exploitable weaknesses before adversaries do. Its value depends far more on scoping, rules of engagement and reporting than on any single tool or technique.

For GRC teams, a penetration test is also evidence. PCI DSS requires regular internal, external and segmentation testing. FedRAMP and many customer contracts expect independent testing. Knowing what a good test plan and report look like makes those obligations useful rather than ceremonial.

What does this area cover?

Scoping and rules of engagement
Written authorisation, in-scope and out-of-scope assets, permitted techniques and stop conditions.
Testing methods
Network, web application, API and cloud configuration testing approaches and methodologies.
Severity rating and reporting
Findings that engineers can reproduce and leaders can prioritise.
Remediation and retesting
Tracking findings to verified closure through vulnerability management.

Related frameworks

Where does Pentesting show up in the rules?

Reading

Guides and explainers