Frameworks / PTES / PTESPHASE-4 PTES
Vulnerability Analysis
PTES PTESPHASE-4: Vulnerability Analysis Per PTES Vulnerability Analysis phase: identify weaknesses. Requirements include (a) conduct vulnerability scanning + manual review + (b) validate findings + remove false positives + (c) prioritise by exploitability + impact + business context + (d) cross-reference threat intelligence + CVE + ATT&CK + (e) document validated vulnerabilities + (f) integrate with exploitation.
What else in your programme already covers this This control maps to 76 controls across 37 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
ASD37-20 Multi-factor authentication (Essential) ASD37-22 Network segmentation (Excellent) ASD37-25 Software firewall - inbound (Very Good) CPG-1.D Revoking Credentials for Departing Employees CPG-5.A Vulnerability Disclosure Program CPG-8.A Network Segmentation OWASPSAMM-4 Verification: Architecture Assessment, Requirements-Driven Testing, Security Testing OWASPSAMM-5 Operations: Incident Management, Environment Management, Operational Management BSI-14 Vulnerability scanning and management FFIEC-06 Network security and segmentation 29134-9.2 Report findings and recommendations PSDTWO-1 Strong Customer Authentication (SCA) Core Requirements UNGPBHR-2 Pillar II: Corporate Responsibility to Respect Human Rights CPSC-CS.1 Network Security for Connected Products USSDWA-2 Cybersecurity Practices (Assessment, Access, Network, IR) Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected .
Query this from an agent The graph holds this control, the 76 it maps to, and the evidence behind each claim, over MCP and REST.