Security Frameworks
Table of Contents
- Introduction to Security Frameworks
- NIST Cybersecurity Framework (CSF 2.0)
- NIST SP 800-53
- ISO/IEC 27001
- CIS Critical Security Controls v8
- PCI DSS v4.0
- Other Frameworks and Regulations
- OSCP Exam Relevance
- Practical Examples
- Lab Exercises
- Key Tools
- Exam Tips
- Cross-References
Introduction to Security Frameworks
Security frameworks provide structured, standardized approaches to managing cybersecurity risk. For penetration testers, understanding these frameworks is essential for:
- Structuring remediation recommendations that align with industry standards
- Communicating findings to stakeholders who think in framework terms
- Prioritizing vulnerabilities based on compliance impact
- Writing professional reports that map to recognized control sets
Why Frameworks Matter in Penetration Testing
| Stakeholder | Framework Value |
|---|---|
| CISO / Executive | Risk posture visibility, compliance status, investment justification |
| IT / Engineering | Actionable remediation steps, prioritized controls |
| Auditors | Evidence of control implementation, gap identification |
| Penetration Tester | Structured reporting, standardized language, defensible recommendations |
Framework Taxonomy
Security Frameworks
├── Risk Management Frameworks
│ ├── NIST CSF (Cybersecurity Framework)
│ └── ISO 31000 (Risk Management)
├── Control Frameworks
│ ├── NIST SP 800-53 (Security Controls)
│ ├── ISO 27001 / 27002 (ISMS Controls)
│ ├── CIS Critical Security Controls
│ └── COBIT (IT Governance)
├── Compliance Frameworks
│ ├── PCI DSS (Payment Card)
│ ├── HIPAA (Healthcare)
│ ├── SOC 2 (Service Organizations)
│ └── GDPR (Data Protection)
└── Industry-Specific
├── FedRAMP (Government Cloud)
├── FFIEC (Financial)
└── NERC CIP (Energy)
NIST Cybersecurity Framework (CSF 2.0)
Overview
The NIST Cybersecurity Framework (CSF) 2.0, released in February 2024, is the most widely adopted cybersecurity framework in the United States and globally. Version 2.0 added a sixth function — GOVERN — reflecting the increasing need for board-level and executive oversight of cyber risk.
Core Purpose: Provide a common language and structured approach for managing cybersecurity risk across organizations of all sizes and sectors.
The Six Functions
┌─────────────────────────────────────────────────────────────────┐
│ NIST CSF 2.0 Core Functions │
├──────────┬──────────┬──────────┬──────────┬──────────┬──────────┤
│ GOVERN │ IDENTIFY │ PROTECT │ DETECT │ RESPOND │ RECOVER │
│ (GV) │ (ID) │ (PR) │ (DE) │ (RS) │ (RC) │
└──────────┴──────────┴──────────┴──────────┴──────────┴──────────┘
Function 1: GOVERN (GV) — New in CSF 2.0
The GOVERN function establishes organizational cybersecurity risk management strategy, expectations, and oversight.
| Category | ID | Description | Penetration Testing Relevance |
|---|---|---|---|
| Context | GV.RM | Organizational context, roles, and responsibilities for cybersecurity risk | Defines scope and rules of engagement |
| Risk Management Strategy | GV.RM | Establish risk management strategy, appetite, and tolerance | Determines testing depth and acceptance criteria |
| Oversight | GV.RO | Monitor, review, and communicate cybersecurity risk exposure | Report delivery and executive briefing alignment |
| Policy | GV.PO | Establish and communicate cybersecurity policy | Baseline for compliance testing |
| Cybersecurity Supply Chain Risk | GV.SC | Manage cybersecurity supply chain risk | Third-party and vendor assessment scope |
Subcategories for GV.RM (Risk Management)
GV.RM-01: An organizational strategy, policy, and standards for managing
cybersecurity risk are established and communicated
GV.RM-02: Roles and accountabilities for managing cybersecurity risk are
established and communicated
GV.RM-03: Cybersecurity risk management is integrated with organizational
risk management
GV.RM-04: Cybersecurity risk management considers relevant cybersecurity
supply chain risks
GV.RM-05: An organizational risk appetite is established and communicated
Function 2: IDENTIFY (ID)
Asset management, governance, and risk assessment activities.
| Category | ID | Description | Key Subcategories |
|---|---|---|---|
| Assets | ID.AM | Physical and digital assets inventoried | Hardware, software, data, services |
| Environment | ID.BE | Cybersecurity activities, supply chain, agreements | Third-party risk, cloud services |
| Governance | ID.GV | Internal risk management policies | Roles, compliance obligations |
| Risk Assessment | ID.RA | Cybersecurity risks to operations and assets | Vulnerability identification, threat analysis |
| Risk Management | ID.RM | Cybersecurity risks addressed per strategy | Risk acceptance, mitigation planning |
| Business Understanding | ID.BU | Mission, objectives, stakeholders | Critical functions, impact analysis |
ID.RA — Risk Assessment (Most Relevant to Pen Testing)
ID.RA-01: Vulnerabilities in owned or operated assets are identified and
recorded on a recurring basis and when changes occur
ID.RA-02: Cybersecurity risks to people, entities, and information are
identified, taking into account threats, vulnerabilities, and
likelihoods of occurrence
ID.RA-03: Cybersecurity risks are prioritized based on likelihood and
potential impact
ID.RA-04: Identified cybersecurity risks are communicated to relevant
stakeholders
ID.RA-05: Cybersecurity risks to the organization are considered within
the context of supply chain risks
Function 3: PROTECT (PR)
Safeguards to ensure delivery of critical services and limit cyber incident impact.
| Category | ID | Description | Pen Testing Focus |
|---|---|---|---|
| Identity Mgmt & Auth | PR.AC | Identity management, authentication, access control | Auth bypass, weak credentials, MFA gaps |
| Awareness & Training | PR.AT | Security awareness and training | Social engineering susceptibility |
| Data Protection | PR.DS | Data security, loss prevention, encryption | Data exposure, weak crypto, DLP gaps |
| Platform Protection | PR.PS | Platform security, hardening, maintenance | Misconfigurations, patch gaps |
| Asset Management | PR.IP | Information protection processes | Asset exposure, shadow IT |
| Maintenance | PR.MA | Cybersecurity maintenance, vulnerability remediation | Patch levels, config drift |
| Protective Technology | PR.PT | Technical safeguards, architecture, monitoring | Firewall rules, WAF, segmentation |
PR.AC — Access Control (High-Frequency Finding Area)
PR.AC-01: Identities and credentials for users, services, and hardware
tokens are managed
PR.AC-02: User and non-user accounts are provisioned, managed, and
deprovisioned
PR.AC-03: Authentication is performed for user and non-user access
(including multi-factor)
PR.AC-04: Authorization and access control mechanisms are implemented
PR.AC-05: Network and device access is managed and enforced
PR.AC-06: Mechanisms are implemented to restrict the ability to input,
output, store, and process data
PR.AC-07: Remote access is managed
PR.AC-08: Access privileges and authorizations are reviewed
PR.AC-09: Authentication credentials are protected from unauthorized
access and compromise
Function 4: DETECT (DE)
Activities to identify cybersecurity incidents.
| Category | ID | Description | Pen Testing Relevance |
|---|---|---|---|
| Continuous Monitoring | DE.CM | Networked and cloud environments monitored | Detection of test activities |
| Anomalies & Events | DE.AE | Anomalies and potential indicators identified | Alert generation during testing |
| Detection Processes | DE.DP | Detection processes implemented and tested | Blue team exercise coordination |
DE.CM — Continuous Monitoring
DE.CM-01: Networked and cloud environments are monitored to detect
potential cybersecurity events
DE.CM-02: Notifications of potential cybersecurity events are correlated
with external sources of information
DE.CM-03: Assets and user activity are monitored for unusual and
unauthorized activities
DE.CM-04: Traffic at external and strategically important internal
interfaces is monitored
DE.CM-05: Traffic within the environment is monitored at strategically
important points
DE.CM-06: The environment is monitored to detect malware
DE.CM-07: The effectiveness of detection processes is evaluated
Function 5: RESPOND (RS)
Activities taken regarding a detected cybersecurity incident.
| Category | ID | Description |
|---|---|---|
| Response Planning | RS.RP | Response plan executed and communicated |
| Communication | RS.CO | Internal and external incident communication |
| Analysis | RS.AN | Incident analysis performed to maintain containment |
| Mitigation | RS.MI | Mitigation activities implemented |
| Improvement | RS.IM | Response plan improved based on lessons learned |
Function 6: RECOVER (RC)
Activities to maintain plans for resilience and restore capabilities.
| Category | ID | Description |
|---|---|---|
| Recovery Planning | RC.RP | Recovery plan executed and communicated |
| Improvement | RC.IM | Recovery plan improved based on lessons learned |
| Communication | RC.CO | Internal and external recovery communication |
Mapping Penetration Testing Findings to NIST CSF
Every vulnerability discovered during a penetration test can be mapped to one or more NIST CSF subcategories. This mapping provides structure for remediation recommendations.
Mapping Methodology
Step 1: Identify the vulnerability type
Step 2: Determine which CSF function is most impacted
Step 3: Map to the specific category and subcategory
Step 4: Use the mapping to structure remediation guidance
Step 5: Reference the mapping in the executive summary for alignment
Finding-to-Framework Mapping Table
| Finding Type | Primary Function | Category | Subcategory Example |
|---|---|---|---|
| SQL Injection | PROTECT | PR.PS / PR.DS | PR.PS-03, PR.DS-01 |
| Weak Passwords | PROTECT | PR.AC | PR.AC-03, PR.AC-09 |
| Missing Patches | PROTECT | PR.MA | PR.MA-03, PR.MA-05 |
| Unencrypted Data | PROTECT | PR.DS | PR.DS-01, PR.DS-02 |
| No MFA | PROTECT | PR.AC | PR.AC-03 |
| Exposed Admin Panel | PROTECT | PR.AC / PR.PT | PR.AC-05, PR.PT-03 |
| No Logging | DETECT | DE.CM | DE.CM-01, DE.CM-03 |
| No Segmentation | PROTECT | PR.PT | PR.PT-03, PR.PT-04 |
| Phishing Susceptibility | PROTECT | PR.AT | PR.AT-01, PR.AT-02 |
| Privilege Escalation | PROTECT | PR.AC | PR.AC-04, PR.AC-08 |
| Missing WAF | PROTECT | PR.PT | PR.PT-05 |
| No Backup | RECOVER | RC.RP | RC.RP-01, RC.RP-02 |
| Default Credentials | PROTECT | PR.AC / PR.MA | PR.AC-01, PR.MA-03 |
| Insecure Config | PROTECT | PR.PS | PR.PS-03, PR.PS-04 |
| No Incident Response Plan | RESPOND | RS.RP | RS.RP-01 |
Example: Mapping SQL Injection to NIST CSF
Finding: SQL Injection in Login Form
CVSS: 8.6 (High)
NIST CSF Mapping:
Primary:
Function: PROTECT
Category: PR.PS (Platform Protection)
Subcategory: PR.PS-03 "Software and firmware are maintained and configured"
Secondary:
Function: PROTECT
Category: PR.DS (Data Protection)
Subcategory: PR.DS-01 "Data-at-rest is protected"
Function: DETECT
Category: DE.CM (Continuous Monitoring)
Subcategory: DE.CM-01 "Networked environments are monitored"
Tertiary:
Function: IDENTIFY
Category: ID.RA (Risk Assessment)
Subcategory: ID.RA-01 "Vulnerabilities in assets are identified"
Using NIST CSF for Executive Reporting
The NIST CSF provides a Tier-based maturity model that executives can understand:
| Tier | Name | Characteristics |
|---|---|---|
| Tier 1 | Partial | Risk management is ad-hoc, reactive, no common understanding |
| Tier 2 | Risk-Informed | Cyber risk management informed by past practice, no formal policy |
| Tier 3 | Repeatable | Formal policy adopted, consistently implemented, may vary by mission |
| Tier 4 | Adaptive | Agile, continuous improvement, advanced analytics, proactive threat intel |
Executive Summary Template Using NIST CSF
## Executive Summary — NIST CSF Alignment
### Current Posture Assessment
The penetration test identified [X] vulnerabilities across the following
NIST CSF functions:
| Function | Findings | Severity Distribution | Current Tier |
|----------------|----------|----------------------|--------------|
| GOVERN | 0 | — | Tier 2 |
| IDENTIFY | 2 | 1 Med, 1 Low | Tier 2 |
| PROTECT | 12 | 3 High, 5 Med, 4 Low | Tier 1-2 |
| DETECT | 3 | 1 High, 2 Med | Tier 1 |
| RESPOND | 1 | 1 Med | Tier 1 |
| RECOVER | 1 | 1 Low | Tier 1 |
### Key Gaps
1. **PROTECT (PR.AC)**: Access control weaknesses represent the largest
finding category, indicating a need for identity and access management
program improvement.
2. **DETECT (DE.CM)**: Limited monitoring capabilities mean that even
successful exploitation may go undetected for extended periods.
### Recommended Investment Priorities
Based on NIST CSF alignment, the following areas should receive immediate
attention:
1. Implement multi-factor authentication (PR.AC-03)
2. Deploy centralized logging and SIEM (DE.CM-01)
3. Establish vulnerability management program (ID.RA-01, PR.MA-03)
NIST SP 800-53
Overview
NIST Special Publication 800-53, “Security and Privacy Controls for Information Systems and Organizations,” provides a comprehensive catalog of security and privacy controls for federal information systems. While originally designed for federal systems, it is widely adopted by private sector organizations, especially those handling sensitive data.
Current Version: Rev. 5 (2020), with ongoing updates.
Control Structure
NIST SP 800-53 Rev. 5 organizes controls into 18 families with over 1,000 individual controls:
| Family | Abbreviation | Controls | Description |
|---|---|---|---|
| Access Control | AC | 53 | Regulate access to information systems |
| Awareness and Training | AT | 7 | Security awareness programs |
| Audit and Accountability | AU | 34 | Audit trail generation and review |
| Configuration Management | CM | 23 | System configuration baselines |
| Contingency Planning | CP | 20 | Backup, recovery, and resilience |
| Identification and Authentication | IA | 23 | User and system identification |
| Incident Response | IR | 17 | Incident handling and response |
| Maintenance | MA | 9 | System maintenance procedures |
| Media Protection | MP | 11 | Media handling and protection |
| Personnel Security | PS | 13 | Personnel risk mitigation |
| Physical and Environmental Protection | PE | 25 | Physical security controls |
| Planning | PL | 17 | Security planning processes |
| Program Management | PM | 17 | Organizational program management |
| Release Activities | RA | 12 | Risk assessment activities |
| System and Communications Protection | SC | 64 | Technical system protections |
| System and Information Integrity | SI | 30 | System integrity and malware protection |
| Supply Chain Risk Management | SR | 15 | Supply chain controls |
| Operations | OP | 14 | Operational procedures |
Impact Levels
NIST SP 800-53 defines three impact levels based on FIPS 199:
| Impact Level | Data Sensitivity | Control Baseline | Approx. Controls |
|---|---|---|---|
| Low | Loss could be negligible | Low Baseline | ~170 controls |
| Moderate | Loss could be serious | Moderate Baseline | ~300 controls |
| High | Loss could be severe/catastrophic | High Baseline | ~500+ controls |
Controls Most Relevant to Penetration Testing
AC — Access Control
AC-2 Account Management
AC-3 Access Enforcement
AC-4 Information Flow Enforcement
AC-5 Separation of Duties
AC-6 Least Privilege
AC-7 Unsuccessful Logon Attempts
AC-8 System Use Notification
AC-11 Session Lock
AC-12 Session Termination
AC-17 Remote Access
AC-19 Access Control for Mobile Devices
AC-20 Use of External Information Systems
AC-21 Information Sharing
AC-22 Publicly Accessible Content
IA — Identification and Authentication
IA-2 Identification and Authentication (Organizational Users)
IA-2(1) Multi-factor authentication
IA-4 Identifier Management
IA-5 Authenticator Management
IA-5(1) Minimum password length (8+ characters)
IA-5(2) Password complexity
IA-5(4) Password history mechanism
IA-5(7) Password quality check
IA-6 Authenticator Feedback
IA-7 Unused Account Disablement
IA-8 System-Generated Passwords
IA-9 Authenticator Transfer Protection
IA-11 Re-authentication
AU — Audit and Accountability
AU-2 Audit Events
AU-3 Content of Audit Records
AU-6 Audit Review, Analysis, and Reporting
AU-7 Audit Reduction and Report Generation
AU-8 Time Stamps
AU-9 Protection of Audit Information
AU-11 Audit Record Retention
AU-12 Audit Generation
SC — System and Communications Protection
SC-7 Boundary Protection
SC-8 Transmission Confidentiality and Integrity
SC-8(1) Cryptographic protection
SC-12 Cryptographic Key Establishment and Management
SC-13 Cryptographic Protection
SC-28 Protection of Information at Rest
SC-39 Process Isolation
SC-40 Secure Name/Address Resolution Service
SC-47 Resource Isolation
SC-48 Virtualization/Containerization Protection
SC-50 DNS over HTTPS
SC-51 Denial of Service Protection
SC-52 Architecture, Provisioning, and Management of Trusted Path
SC-54 Remote Support Access
SC-55 External Telecommunications Services
SC-56 Resource Monitoring
SC-57 Platform-Independent Applications
SC-58 Network Segmentation
SC-59 Secure Access Control Policies for Public Websites
SC-60 Voice over Internet Protocol Security
SC-62 Memory Protection
SC-63 Stream Inspection
SC-64 Wireless Link Protection
SC-65 Embedded Component Security
SC-66 Cryptographic Module
SC-67 Secure Generation of Cryptographic Values
SC-68 Public Key Infrastructure Certificates
SC-69 Roles, Clearances, and Labels for Decryption
SC-70 Honeypots
SC-71 Security/Privacy Functional Isolation from Other Functions
SC-72 Security/Privacy Function Separation
SC-73 Firmware/Jirmware Integrity
SC-74 Security/Privacy Zero Trust
SI — System and Information Integrity
SI-2 Flaw Remediation
SI-2(1) Automated flaw remediation status
SI-2(8) Time to Remediate Flaws
SI-2(9) Automated Security Patch Installation
SI-3 Malicious Code Protection
SI-4 Information System Monitoring
SI-4(5) System-wide malware detection
SI-4(23) Network Intrusion Detection
SI-5 Security Alerts, Advisories, and Directives
SI-6 Security Function Verification
SI-11 Error Handling
SI-12 Information Handling and Retention
SI-16 Memory Protection
SI-17 Fail-Safe Procedures
SI-18 Predictable Failure Handling
SI-19 Public Access Protection
SI-20 Secure Capture/Processing/Storage/Display of PII
SI-21 Fixity Verification
SI-22 Architecture/Design/Implementation Reviews
SI-23 Data Integrity
SI-24 Non-Persistence
SI-25 Honeypots
SI-26 Memory Protection
SI-27 Remote Maintenance Monitoring
Penetration Testing Assessment Mapping
When conducting a penetration test, map findings to NIST SP 800-53 controls for precise remediation:
| Finding | NIST SP 800-53 Controls |
|---|---|
| SQL Injection | SI-11, SI-19, SC-28, CM-7 |
| XSS | SI-11, SI-19, SC-8 |
| Weak Passwords | IA-5, IA-5(1), IA-5(2), IA-5(4) |
| Missing MFA | IA-2(1) |
| Unpatched Software | SI-2, SI-2(8), SI-5 |
| Default Credentials | IA-5, AC-17 |
| No HTTPS | SC-8, SC-8(1), SC-13 |
| Excessive Permissions | AC-6, AC-5 |
| No Logging | AU-2, AU-3, AU-6, AU-12 |
| Open Ports | SC-7, SC-7(8) |
| Misconfigured Firewall | SC-7, SC-7(1), SC-7(8) |
| Privilege Escalation | AC-6, AC-5, CM-7 |
| Insecure Direct Object Ref. | AC-3, AC-6 |
| Security Misconfiguration | CM-1, CM-2, CM-3, CM-7 |
ISO/IEC 27001
Overview
ISO/IEC 27001 is the international standard for Information Security Management Systems (ISMS). It provides a systematic approach to managing sensitive company information, ensuring it remains secure.
Key Documents:
- ISO 27001: Requirements for establishing, implementing, maintaining, and continually improving an ISMS
- ISO 27002: Code of practice for information security controls (implementation guidance)
ISMS Lifecycle (PDCA Model)
┌─────────────────┐
│ PLAN │
│ ┌─────────────┐ │
│ │ Risk Assess │ │
│ │ Scope/Policy│ │
│ │ Objectives │ │
│ └─────────────┘ │
└────────┬────────┘
│
┌────────▼────────┐
│ DO │
│ ┌─────────────┐ │
│ │ Implement │ │
│ │ Controls │ │
│ │ Train Staff │ │
│ └─────────────┘ │
└────────┬────────┘
│
┌────────▼────────┐
│ CHECK │
│ ┌─────────────┐ │
│ │ Monitor │ │
│ │ Audit │ │
│ │ Pen Testing │ │
│ └─────────────┘ │
└────────┬────────┘
│
┌────────▼────────┐
│ ACT │
│ ┌─────────────┐ │
│ │ Improve │ │
│ │ Remediate │ │
│ │ Update ISMS │ │
│ └─────────────┘ │
└────────┬────────┘
│
└───► (back to PLAN)
ISO 27001:2022 Annex A Controls
The 2022 revision reorganized Annex A into 4 themes with 93 controls (down from 114 in the 2013 version):
Theme 1: Organizational Controls (A.5) — 37 Controls
| Control | Title | Pen Testing Relevance |
|---|---|---|
| A.5.1 | Policies for information security | Baseline for security testing scope |
| A.5.2 | Information security roles and responsibilities | Defines who owns remediation |
| A.5.3 | Segregation of duties | Privilege escalation testing |
| A.5.6 | Information security in project management | SDLC security integration |
| A.5.7 | Roles and responsibilities for using ICT | User access testing |
| A.5.9 | Threat intelligence | Threat modeling input |
| A.5.10 | Information security for cloud services | Cloud security assessment |
| A.5.12 | ICT readiness for business continuity | Recovery testing |
| A.5.14 | Monitoring | Detection capability assessment |
| A.5.15 | Evaluation of information security | Internal audit alignment |
| A.5.16 | Internal information security review | Pen test as evidence |
| A.5.17 | Compliance with policies and standards | Compliance gap analysis |
| A.5.18 | Documented operating procedures | Configuration baseline testing |
| A.5.21 | Inventory of information and assets | Asset discovery validation |
| A.5.22 | Acceptable use of information and assets | Policy enforcement testing |
| A.5.23 | Return of assets | Asset lifecycle security |
| A.5.24 | Classification of information | Data handling validation |
| A.5.25 | Labelling of information | Data classification testing |
| A.5.26 | Information transfer | Data in transit testing |
| A.5.27 | Access control | Core pen test focus area |
| A.5.28 | Identity management | Authentication testing |
| A.5.29 | Authentication information | Credential testing |
| A.5.30 | Access rights | Authorization testing |
| A.5.31 | Secure authentication | MFA, password policy testing |
| A.5.32 | Capacity management | DoS testing relevance |
| A.5.33 | Protection of tools against malicious code | Endpoint security testing |
| A.5.34 | Segregation in test environments | Test environment security |
| A.5.35 | Monitoring activities | SIEM/log review testing |
| A.5.36 | Logging | Log completeness testing |
| A.5.37 | Administrators’ activities | Privileged access testing |
| A.5.38 | Clock synchronization | Log correlation testing |
| A.5.39 | Use of privileged programs | Privilege abuse testing |
| A.5.40 | Wildcard characters and default parameters | Default config testing |
| A.5.41 | Changing minimum security parameters | Hardening validation |
| A.5.42 | Information security in teams developing/ supporting ICT | DevSecOps testing |
| A.5.43 | Secure development life cycle | Application security testing |
| A.5.44 | Application security requirements | AppSec assessment |
| A.5.45 | Secure system architecture and engineering | Architecture review |
| A.5.46 | Secure coding | Code review, SAST/DAST |
| A.5.47 | Protection of information development testing | Test data security |
| A.5.48 | Outsourced development | Third-party code security |
| A.5.49 | Separation of development, test, and production | Environment isolation testing |
| A.5.50 | Change management | Change control testing |
| A.5.51 | Test information | Test data protection |
| A.5.52 | Protected information processing facilities | Physical security |
| A.5.53 | Supporting utilities | Infrastructure security |
| A.5.54 | Protection against physical and environmental security | Physical pen test |
| A.5.55 | Secure disposal | Data destruction validation |
| A.5.56 | Secure wiping | Media sanitization testing |
| A.5.57 | Physical security monitoring | Physical access testing |
| A.5.58 | Clear desk and clear screen | Physical security |
| A.5.59 | Equipment siting and protection | Physical security |
| A.5.60 | Security of assets off-premises | Remote work security |
| A.5.61 | Infrastructure monitoring and control | Network security testing |
| A.5.62 | Utilities | Infrastructure resilience |
| A.5.63 | Supporting communications | Comms security |
| A.5.64 | Delivery procedures and agreements | Supply chain security |
| A.5.65 | Addressing information security in ICT procurement | Procurement security |
| A.5.66 | Information security for use of ICT supplier services | Vendor assessment |
| A.5.67 | Monitoring and review of ICT supplier services | Vendor monitoring |
| A.5.68 | Managing changes to ICT supplier services | Vendor change mgmt |
| A.5.69 | Information security for cloud services | Cloud security |
| A.5.70 | Information security incident management planning and preparation | IR plan testing |
| A.5.71 | Assessment and decision on information security incident | Incident response testing |
| A.5.72 | Response to information security incidents | IR execution testing |
| A.5.73 | Learning from information security incidents | Post-incident review |
| A.5.74 | Collection of evidence | Forensic readiness |
| A.5.75 | Improvement of information security | Continuous improvement |
| A.5.76 | Collection of requirements | Requirement gathering |
| A.5.77 | Minimisation of information | Data minimization |
| A.5.78 | Obfuscation of information | Data masking |
| A.5.79 | Anonymisation | PII protection |
| A.5.80 | pseudonymisation | Privacy protection |
| A.5.81 | Confidentiality | Encryption testing |
| A.5.82 | Availability | Availability testing |
| A.5.83 | Integrity | Integrity testing |
| A.5.84 | Information backup | Backup testing |
| A.5.85 | Redundancy of information processing facilities | Redundancy testing |
| A.5.86 | Timeliness of information processing | Performance testing |
| A.5.87 | Communication channels | Channel security |
| A.5.88 | Mobile devices | Mobile security testing |
| A.5.89 | Information security in the use of privileged access rights | Privileged access testing |
| A.5.90 | Information security for access by teleworkers | Remote access testing |
| A.5.91 | Access control | Access control testing |
| A.5.92 | Secure authentication | Authentication testing |
| A.5.93 | Configuration management | Config baseline testing |
Note: The 2022 revision consolidated and renumbered controls. The table above shows the restructured control set.
Corrected ISO 27001:2022 Annex A Control Structure
The 2022 version has exactly 93 controls organized into 4 themes:
| Theme | Controls | Count |
|---|---|---|
| A.5 Organizational | A.5.1 — A.5.37 | 37 |
| A.6 People | A.6.1 — A.6.7 | 7 |
| A.7 Physical | A.7.1 — A.7.9 | 9 |
| A.8 Technological | A.8.1 — A.8.39 | 39 |
| Total | 93 |
Theme 2: People Controls (A.6) — 7 Controls
| Control | Title |
|---|---|
| A.6.1 | Screening |
| A.6.2 | Terms and conditions of employment |
| A.6.3 | Information security awareness, education, and training |
| A.6.4 | Disciplinary process |
| A.6.5 | Responsibilities after change or termination of employment |
| A.6.6 | Confidentiality agreements |
| A.6.7 | Remote working |
Theme 3: Physical Controls (A.7) — 9 Controls
| Control | Title |
|---|---|
| A.7.1 | Physical security perimeters |
| A.7.2 | Physical entry |
| A.7.3 | Securing offices, rooms, and facilities |
| A.7.4 | Physical security monitoring |
| A.7.5 | Protecting against physical and environmental threats |
| A.7.6 | Working in secure areas |
| A.7.7 | Clear desk and clear screen |
| A.7.8 | Equipment siting and protection |
| A.7.9 | Unattended user equipment |
Theme 4: Technological Controls (A.8) — 39 Controls
| Control | Title | Pen Testing Relevance |
|---|---|---|
| A.8.1 | Inventory of information and associated assets | Asset discovery |
| A.8.2 | Acceptable use of information and associated assets | Policy enforcement |
| A.8.3 | Return of assets | Asset lifecycle |
| A.8.4 | Ownership of assets | Accountability |
| A.8.5 | Use of backup materials | Backup validation |
| A.8.6 | Transport | Data transport security |
| A.8.7 | Storage | Data at rest security |
| A.8.8 | Erasure | Data destruction |
| A.8.9 | Media transfer | Media handling |
| A.8.10 | Maintenance | System maintenance |
| A.8.11 | Configuration | Config management |
| A.8.12 | Information deletion | Data lifecycle |
| A.8.13 | Secure boot and integrity verification | Boot security |
| A.8.14 | Prevention of side-channel and jitter attacks | Hardware security |
| A.8.15 | Segregation of information in shared processing facilities | Multi-tenancy |
| A.8.16 | Information access restriction | Access control |
| A.8.17 | Access to source code | Code security |
| A.8.18 | Authentication information | Credential security |
| A.8.19 | Access control | Authorization |
| A.8.20 | Identity management | Identity lifecycle |
| A.8.21 | Authentication information management | Password policies |
| A.8.22 | Capacity management | Resource management |
| A.8.23 | Protection of logs | Log security |
| A.8.24 | Monitoring activities | Detection |
| A.8.25 | Clock synchronization | Time sync |
| A.8.26 | Use of privileged commands or tools | Privileged access |
| A.8.27 | Installation of software on operational systems | Software mgmt |
| A.8.28 | Management of configuration information | Config mgmt |
| A.8.29 | Protection of information systems in development and testing | Dev/test security |
| A.8.30 | Segregation of development, testing, and production environments | Env isolation |
| A.8.31 | Change management | Change control |
| A.8.32 | Test information | Test data protection |
| A.8.33 | Controlled testing environment | Test env security |
| A.8.34 | Protection of information systems from malicious software | Anti-malware |
| A.8.35 | Management of technical vulnerabilities | Vuln management |
| A.8.36 | Configuration management | Baseline config |
| A.8.37 | Control of operational software | Software control |
| A.8.38 | Network security and operations management | Network security |
| A.8.39 | Security of network services | Service security |
How ISO 27001 Relates to Penetration Testing
- Clause 10.1 (Continual Improvement): Pen test findings drive improvement actions
- Clause 9.1 (Evaluation): Pen testing is a form of security evaluation
- Annex A.8.35 (Management of Technical Vulnerabilities): Requires regular vulnerability assessment and penetration testing
- Certification Requirement: Many certification bodies require annual penetration testing for ISO 27001 certification
Using ISO Controls for Remediation Recommendations
## Remediation Recommendation
### Finding: Cross-Site Scripting (XSS) in Search Function
**ISO 27001:2022 Control Mapping:**
- A.8.35 Management of technical vulnerabilities
- A.8.29 Protection of information systems in development and testing
- A.8.30 Segregation of development, testing, and production environments
- A.5.43 Secure development life cycle
- A.5.46 Secure coding
**Recommended Actions:**
1. Implement output encoding for all user-supplied input (A.8.35)
2. Integrate SAST/DAST into CI/CD pipeline (A.5.43, A.5.46)
3. Establish secure coding standards and training (A.6.3, A.5.46)
4. Implement Content Security Policy headers (A.8.38)
CIS Critical Security Controls v8
Overview
The CIS (Center for Internet Security) Critical Security Controls provide actionable, prioritized cybersecurity safeguards. Version 8 (released 2023) reorganized the controls into a more implementation-friendly structure with explicit Implementation Groups.
Key Philosophy: “Do these things first” — prioritized, actionable, and measurable.
The 18 CIS Controls v8
Control 1: Inventory and Account Management of Enterprise Assets and Devices
| SAC | Safeguard | Description |
|---|---|---|
| 1.1 | Maintain an up-to-date asset management process | Track all hardware and software assets |
| 1.2 | Maintain an up-to-date inventory of enterprise assets and devices | Current inventory of all devices |
| 1.3 | Define and maintain an inventory of Internet-facing assets | External-facing asset inventory |
| 1.4 | Establish and maintain an inventory of authorized and unauthorized devices | Allow/deny device lists |
| 1.5 | Establish and maintain an inventory of authorized and unauthorized software | Software allow/deny lists |
| 1.6 | Establish and maintain an accurate account management process | Account lifecycle management |
| 1.7 | Maintain an inventory of enterprise and system accounts | All accounts documented |
| 1.8 | Establish and maintain an inventory of SaaS, PaaS, and IaaS accounts | Cloud account inventory |
| 1.9 | Conduct periodic review of human accounts | Access review process |
| 1.10 | Conduct periodic review of non-human accounts | Service account review |
| 1.11 | Conduct periodic review of privileged accounts | Privileged access review |
| 1.12 | Perform enterprise asset and device due diligence prior to onboarding | Pre-onboarding assessment |
OSCP Relevance: Every penetration test begins with asset discovery. CIS Control 1 validates that the organization knows what it has.
Control 2: Inventory and Account Management of Software Assets
| SAC | Safeguard | Description |
|---|---|---|
| 2.1 | Establish and maintain an inventory of authorized and unauthorized software | Software inventory |
| 2.2 | Establish and maintain an inventory of software vulnerabilities | Known vuln tracking |
| 2.3 | Perform software due diligence prior to onboarding | Pre-deployment review |
| 2.4 | Deploy anti-exploit technologies | EMET, exploit protection |
| 2.5 | Utilize software asset information to support vulnerability management | Vuln mgmt integration |
OSCP Relevance: Identifying unauthorized software (shadow IT) and known vulnerabilities during testing.
Control 3: Data Protection
| SAC | Safeguard | Description |
|---|---|---|
| 3.1 | Establish and maintain an inventory of critical information | Data classification |
| 3.2 | Establish and maintain a process to protect critical information | Data protection process |
| 3.3 | Detect and prevent data exfiltration | DLP implementation |
| 3.4 | Encrypt critical information at rest | Encryption at rest |
| 3.5 | Encrypt critical information in transit | Encryption in transit |
| 3.6 | Implement and maintain a data retention process | Data lifecycle mgmt |
| 3.7 | Establish and maintain a process to protect PII | PII protection |
| 3.8 | Establish and maintain a process to protect PHI | PHI protection |
OSCP Relevance: Testing for unencrypted data, data exfiltration paths, and improper data handling.
Control 4: Secure Configuration of Enterprise Assets and Software
| SAC | Safeguard | Description |
|---|---|---|
| 4.1 | Develop and maintain secure configuration guidelines | Hardening standards |
| 4.2 | Implement and maintain secure configurations for all assets | Config enforcement |
| 4.3 | Implement and maintain secure configurations for software | App hardening |
| 4.4 | Implement and maintain secure configurations for network infrastructure | Network hardening |
| 4.5 | Implement and maintain secure configurations for cloud services | Cloud hardening |
| 4.6 | Implement and maintain secure configurations for mobile devices | Mobile hardening |
| 4.7 | Implement and maintain secure configurations for IoT devices | IoT hardening |
| 4.8 | Implement and maintain secure configurations for OT devices | OT hardening |
| 4.9 | Implement and maintain secure configurations for AI/ML systems | AI security |
| 4.10 | Validate secure configurations | Config auditing |
OSCP Relevance: Security misconfiguration is the #1 finding category in most penetration tests.
Control 5: Account Management
| SAC | Safeguard | Description |
|---|---|---|
| 5.1 | Establish and maintain an account management process | Account lifecycle |
| 5.2 | Establish and maintain a process for privileged account management | PAM implementation |
| 5.3 | Establish and maintain a process for non-human account management | Service account mgmt |
| 5.4 | Establish and maintain a process for guest and temporary account management | Temp account mgmt |
| 5.5 | Establish and maintain a process for account provisioning and deprovisioning | Joiner/mover/leaver |
| 5.6 | Establish and maintain a process for account access reviews | Periodic review |
| 5.7 | Establish and maintain a process for account password management | Password policies |
| 5.8 | Establish and maintain a process for multi-factor authentication | MFA deployment |
OSCP Relevance: Privilege escalation, credential attacks, and access control testing directly relate to this control.
Control 6: Access Control Management
| SAC | Safeguard | Description |
|---|---|---|
| 6.1 | Establish and maintain an access control management process | Access control framework |
| 6.2 | Implement and maintain role-based access control | RBAC implementation |
| 6.3 | Implement and maintain least privilege access | Least privilege |
| 6.4 | Implement and maintain network access control | NAC implementation |
| 6.5 | Implement and maintain remote access control | Remote access security |
| 6.6 | Implement and maintain cloud access control | Cloud IAM |
| 6.7 | Implement and maintain API access control | API security |
| 6.8 | Implement and maintain data access control | Data-level access |
OSCP Relevance: Authorization testing, horizontal/vertical privilege escalation, and access control bypass.
Control 7: Continuous Vulnerability Management
| SAC | Safeguard | Description |
|---|---|---|
| 7.1 | Establish and maintain a vulnerability management process | Vuln mgmt program |
| 7.2 | Scan for vulnerabilities on a recurring basis | Regular scanning |
| 7.3 | Scan for vulnerabilities prior to new deployments | Pre-deployment scanning |
| 7.4 | Scan for vulnerabilities after changes | Post-change scanning |
| 7.5 | Remediate vulnerabilities based on risk | Risk-based remediation |
| 7.6 | Perform penetration testing on a recurring basis | Regular pen testing |
| 7.7 | Perform penetration testing prior to new deployments | Pre-deployment pen test |
| 7.8 | Perform penetration testing after significant changes | Post-change pen test |
OSCP Relevance: CIS Control 7.6-7.8 explicitly require penetration testing.
Control 8: Audit Log Management
| SAC | Safeguard | Description |
|---|---|---|
| 8.1 | Establish and maintain an audit log management process | Log management program |
| 8.2 | Collect audit logs from all enterprise assets | Centralized logging |
| 8.3 | Collect audit logs from all software assets | App logging |
| 8.4 | Collect audit logs from all network infrastructure | Network logging |
| 8.5 | Collect audit logs from all cloud services | Cloud logging |
| 8.6 | Synchronize time across all assets | Time synchronization |
| 8.7 | Protect audit logs from unauthorized access | Log integrity |
| 8.8 | Retain audit logs for a defined period | Log retention |
| 8.9 | Review audit logs on a recurring basis | Log review process |
| 8.10 | Alert on significant audit log events | Log alerting |
OSCP Relevance: Testing whether attacker activities would be detected through logging.
Control 9: Email and Web Browser Protections
| SAC | Safeguard | Description |
|---|---|---|
| 9.1 | Establish and maintain email and web browser protection policies | Security policies |
| 9.2 | Implement email security protections | Email security |
| 9.3 | Implement web browser security protections | Browser hardening |
| 9.4 | Implement anti-phishing protections | Phishing defense |
| 9.5 | Implement web filtering | URL filtering |
| 9.6 | Implement email filtering | Email filtering |
OSCP Relevance: Web application testing and social engineering assessment.
Control 10: Maintenance and Vulnerability Management for Software and Applications
| SAC | Safeguard | Description |
|---|---|---|
| 10.1 | Establish and maintain a software maintenance process | Patch management |
| 10.2 | Apply security patches in a timely manner | Timely patching |
| 10.3 | Apply non-security updates | General updates |
| 10.4 | Validate patch effectiveness | Patch verification |
| 10.5 | Manage end-of-life software | EOL management |
OSCP Relevance: Identifying unpatched systems and end-of-life software during testing.
Control 11: Data Recovery
| SAC | Safeguard | Description |
|---|---|---|
| 11.1 | Establish and maintain a data recovery process | Backup strategy |
| 11.2 | Back up critical information regularly | Regular backups |
| 11.3 | Test data recovery processes regularly | Backup testing |
| 11.4 | Protect backup data | Backup security |
| 11.5 | Maintain offline backups | Air-gapped backups |
OSCP Relevance: Ransomware resilience and backup security testing.
Control 12: Network Infrastructure Management
| SAC | Safeguard | Description |
|---|---|---|
| 12.1 | Establish and maintain network infrastructure management processes | Network mgmt |
| 12.2 | Implement network segmentation | Segmentation |
| 12.3 | Implement network access control | NAC |
| 12.4 | Implement firewall management | Firewall rules |
| 12.5 | Implement DNS security | DNS hardening |
| 12.6 | Implement network monitoring | Network monitoring |
| 12.7 | Implement wireless security | WiFi security |
| 12.8 | Implement cloud network security | Cloud networking |
OSCP Relevance: Network segmentation testing, firewall rule review, and lateral movement assessment.
Control 13: Network Monitoring and Defense
| SAC | Safeguard | Description |
|---|---|---|
| 13.1 | Establish and maintain network monitoring processes | Monitoring program |
| 13.2 | Monitor network traffic at external interfaces | Perimeter monitoring |
| 13.3 | Monitor network traffic at internal interfaces | Internal monitoring |
| 13.4 | Implement intrusion detection/prevention | IDS/IPS |
| 13.5 | Implement network detection and response | NDR |
| 13.6 | Implement threat intelligence integration | Threat intel |
| 13.7 | Implement automated response capabilities | SOAR |
OSCP Relevance: Testing detection capabilities and alert generation during engagement.
Control 14: Incident Response Management
| SAC | Safeguard | Description |
|---|---|---|
| 14.1 | Establish and maintain an incident response plan | IR plan |
| 14.2 | Establish and maintain an incident response team | IR team |
| 14.3 | Test the incident response plan regularly | IR testing |
| 14.4 | Update the incident response plan based on lessons learned | IR improvement |
| 14.5 | Establish and maintain communication procedures | IR comms |
| 14.6 | Establish and maintain evidence collection procedures | Forensics |
OSCP Relevance: Coordinating with blue teams during red team exercises.
Control 15: Security Awareness and Skills Training
| SAC | Safeguard | Description |
|---|---|---|
| 15.1 | Establish and maintain a security awareness program | Awareness program |
| 15.2 | Provide security awareness training to all personnel | General training |
| 15.3 | Provide role-based security training | Role-specific training |
| 15.4 | Provide security skills training for technical staff | Technical training |
| 15.5 | Test security awareness effectiveness | Phishing tests |
| 15.6 | Provide AI/ML security training | AI security awareness |
OSCP Relevance: Social engineering susceptibility and human-factor vulnerabilities.
Control 16: Service Provider Management
| SAC | Safeguard | Description |
|---|---|---|
| 16.1 | Establish and maintain a service provider management process | Vendor mgmt |
| 16.2 | Assess service provider security practices | Vendor assessment |
| 16.3 | Monitor service provider security posture | Vendor monitoring |
| 16.4 | Establish and maintain contractual security requirements | Contractual security |
| 16.5 | Assess cloud service provider security | Cloud vendor assessment |
OSCP Relevance: Third-party risk and supply chain security testing.
Control 17: Application Software Security
| SAC | Safeguard | Description |
|---|---|---|
| 17.1 | Establish and maintain an application security program | AppSec program |
| 17.2 | Implement secure software development lifecycle | SSDLC |
| 17.3 | Perform security testing of applications | App security testing |
| 17.4 | Implement application security controls | App controls |
| 17.5 | Implement API security | API security |
| 17.6 | Implement container security | Container security |
| 17.7 | Implement AI/ML application security | AI app security |
OSCP Relevance: Web application penetration testing and API security assessment.
Control 18: Endpoint Detection and Response
| SAC | Safeguard | Description |
|---|---|---|
| 18.1 | Establish and maintain an EDR program | EDR deployment |
| 18.2 | Deploy EDR solutions on all endpoints | EDR coverage |
| 18.3 | Configure EDR solutions effectively | EDR tuning |
| 18.4 | Monitor EDR alerts and respond | EDR response |
| 18.5 | Integrate EDR with other security tools | EDR integration |
OSCP Relevance: Testing whether endpoint activities are detected by EDR solutions.
Implementation Groups (IG1, IG2, IG3)
CIS Controls are organized into three Implementation Groups based on organizational size and risk profile:
| Implementation Group | Target Organization | Approx. Safeguards | Description |
|---|---|---|---|
| IG1 | Small organizations, basic protection | ~60 safeguards | Minimum baseline for any organization |
| IG2 | Medium organizations, moderate risk | ~150 safeguards | Adds depth for organizations with significant digital footprint |
| IG3 | Large organizations, high risk | ~200+ safeguards | Comprehensive for organizations handling sensitive data or facing advanced threats |
IG1 vs IG2 vs IG3 — Key Differences
| Control | IG1 | IG2 | IG3 |
|---|---|---|---|
| Control 1 (Asset Mgmt) | Basic inventory | + Internet-facing inventory | + Full due diligence |
| Control 4 (Config) | Enterprise assets | + Software + Network | + Cloud + Mobile + IoT + OT |
| Control 5 (Accounts) | Basic account mgmt | + Privileged accounts | + Non-human + Guest accounts |
| Control 7 (Vuln Mgmt) | Scanning | + Pen testing recurring | + Pre/post deployment pen testing |
| Control 13 (Network Mon) | External monitoring | + Internal monitoring | + IDS/IPS + NDR + Threat Intel |
Most Relevant CIS Controls for OSCP Findings
| OSCP Finding Type | Primary CIS Control | Secondary CIS Control |
|---|---|---|
| SQL Injection | Control 17 (App Security) | Control 4 (Config) |
| XSS | Control 17 (App Security) | Control 9 (Web Browser) |
| Weak Credentials | Control 5 (Account Mgmt) | Control 15 (Awareness) |
| Privilege Escalation | Control 6 (Access Control) | Control 5 (Account Mgmt) |
| Unpatched Systems | Control 10 (Maintenance) | Control 7 (Vuln Mgmt) |
| Default Credentials | Control 4 (Config) | Control 5 (Account Mgmt) |
| Missing MFA | Control 5 (Account Mgmt) | Control 6 (Access Control) |
| No Encryption | Control 3 (Data Protection) | Control 12 (Network) |
| Open Ports/Services | Control 12 (Network) | Control 4 (Config) |
| No Logging | Control 8 (Audit Logs) | Control 13 (Network Mon) |
| Lateral Movement | Control 12 (Network) | Control 6 (Access Control) |
| Phishing Success | Control 15 (Awareness) | Control 9 (Email/Web) |
| Misconfiguration | Control 4 (Config) | Control 1 (Asset Mgmt) |
| Insecure API | Control 17 (App Security) | Control 6 (Access Control) |
| Ransomware Risk | Control 11 (Recovery) | Control 18 (EDR) |
PCI DSS v4.0
Overview
The Payment Card Industry Data Security Standard (PCI DSS) v4.0, released in March 2022, is a compliance standard for organizations that handle credit card data. It is one of the most strictly enforced security standards with mandatory penetration testing requirements.
Scope: Any organization that stores, processes, or transmits cardholder data (CHD) or sensitive authentication data (SAD).
The 12 Requirements
| Requirement | Title | Key Controls |
|---|---|---|
| Req 1 | Install and maintain a network security controls | Firewalls, segmentation, secure configs |
| Req 2 | Apply secure configurations to all system components | Hardening, remove defaults, unique IDs |
| Req 3 | Protect stored account data | Encryption, truncation, secure storage |
| Req 4 | Protect cardholder data with strong cryptography during transmission | TLS, encryption in transit |
| Req 5 | Protect all systems and networks from malware | Anti-malware, endpoint protection |
| Req 6 | Develop and maintain secure systems and software | Secure SDLC, patching, vulnerability mgmt |
| Req 7 | Restrict access to system components and cardholder data by business need to know | Access control, least privilege |
| Req 8 | Identify users and authenticate access to system components | Unique IDs, MFA, password policies |
| Req 9 | Restrict physical access to cardholder data | Physical security, media control |
| Req 10 | Log and monitor all access to system components and cardholder data | Logging, monitoring, alerting |
| Req 11 | Regularly test security of systems and networks | Pen testing, vulnerability scanning, wireless testing |
| Req 12 | Support information security with organizational policies and procedures | Security policy, training, incident response |
PCI DSS Penetration Testing Requirements (Requirement 11.3)
PCI DSS v4.0 has specific, mandatory penetration testing requirements:
Internal Penetration Testing (11.3.1)
| Requirement | Detail |
|---|---|
| Frequency | At least annually and after significant changes |
| Scope | All internal systems in the CDE (Cardholder Data Environment) |
| Tester | Internal resources or approved external tester |
| Depth | Include all systems that store, process, or transmit CHD |
External Penetration Testing (11.3.2)
| Requirement | Detail |
|---|---|
| Frequency | At least annually and after significant changes |
| Scope | All external-facing systems |
| Tester | Approved Scanning Vendor (ASV) or qualified security assessor (QSA) |
| Depth | Internet-facing systems, DMZ, public-facing applications |
Penetration Testing Methodology Requirements
PCI DSS v4.0 Penetration Testing Requirements:
1. Testing must be performed by qualified personnel
- Internal testers: Must have relevant certifications and experience
- External testers: Must be PTES-certified or equivalent
2. Testing must follow a recognized methodology
- PTES (Penetration Testing Execution Standard)
- OWASP Testing Guide
- NIST SP 800-115
- Custom methodology (must be documented and approved)
3. Testing must include:
a. Network infrastructure testing
b. Web application testing
c. Wireless testing (if applicable)
d. Custom application testing
e. Social engineering (optional but recommended)
4. Testing must be documented:
- Scope and methodology
- Tools and techniques used
- Findings and evidence
- Risk ratings
- Remediation recommendations
- Retest results
5. Retesting required:
- All High and Medium findings must be retested
- Retest must be performed by the same or equivalent tester
- Retest results must be documented
When PCI DSS Applies to Penetration Testing
| Scenario | PCI DSS Applies? | Notes |
|---|---|---|
| Testing payment processing systems | Yes | Full Req 11.3 compliance |
| Testing systems connected to CDE | Yes | In scope if in DMZ or connected |
| Testing corporate network (no CHD) | Maybe | Depends on segmentation effectiveness |
| Testing third-party payment processor | No | Their responsibility (but validate) |
| Testing mobile payment app | Yes | If it handles CHD |
| Testing IoT payment devices | Yes | P2PE and PIN scope considerations |
PCI DSS v4.0 Key Changes from v3.2.1
| Area | v3.2.1 | v4.0 |
|---|---|---|
| MFA | Required for remote access | Required for all access to CDE |
| Pen Testing | Annual | Annual + after significant changes |
| Vuln Scanning | Quarterly internal/external | Continuous or at least quarterly |
| Secure SDLC | Recommended | Required (Req 6.4) |
| Custom Controls | Not supported | Compensating controls framework |
| Risk-Based Approach | Limited | More flexible, risk-based options |
| Logging | Basic requirements | Enhanced, more specific requirements |
Other Frameworks and Regulations
SOC 2 (Service Organization Control 2)
Overview
SOC 2 is an auditing procedure established by the AICPA (American Institute of Certified Public Accountants) that focuses on non-financial reporting based on Trust Service Criteria (TSC).
Trust Service Criteria
| Criterion | Description | Pen Testing Relevance |
|---|---|---|
| Security (Common Criteria) | System security against threats | Core pen test scope |
| Availability | System availability for operation and use | DoS testing, uptime validation |
| Processing Integrity | System processing is complete, accurate, timely | Data integrity testing |
| Confidentiality | Information designated as confidential is protected | Data exposure testing |
| Privacy | Personal information is collected, used, retained, disclosed, disposed | PII handling testing |
SOC 2 Types
| Type | Description | Pen Testing Role |
|---|---|---|
| Type I | Point-in-time assessment of design | Baseline assessment |
| Type II | Assessment of operating effectiveness over time (6-12 months) | Ongoing validation |
HIPAA (Health Insurance Portability and Accountability Act)
Overview
HIPAA protects Protected Health Information (PHI) in the United States. The Security Rule specifically addresses electronic PHI (ePHI).
HIPAA Security Rule Components
| Component | Requirements | Pen Testing Relevance |
|---|---|---|
| Administrative Safeguards | Security management, workforce security, information access management | Policy review, access testing |
| Physical Safeguards | Facility access, workstation security, device security | Physical security testing |
| Technical Safeguards | Access control, audit controls, integrity controls, transmission security | Technical pen testing |
HIPAA Technical Safeguards Mapping
HIPAA Technical Safeguard -> Pen Testing Activity
─────────────────────────────────────────────────────────────
Access Control (164.312(a)(1)) -> Authentication/authorization testing
Audit Controls (164.312(b)) -> Log review, audit trail testing
Integrity (164.312(c)(1)) -> Data integrity testing
Person or Entity Authentication -> MFA, credential testing
Transmission Security -> Encryption in transit testing
(164.312(e)(1))
GDPR (General Data Protection Regulation)
Overview
GDPR is the European Union’s data protection regulation that applies to any organization processing personal data of EU residents, regardless of the organization’s location.
Key GDPR Principles Relevant to Pen Testing
| Principle | Article | Pen Testing Relevance |
|---|---|---|
| Lawfulness, fairness, transparency | Art. 5(1)(a) | Testing must have legal basis |
| Purpose limitation | Art. 5(1)(b) | Scope definition |
| Data minimization | Art. 5(1)(c) | Data handling assessment |
| Accuracy | Art. 5(1)(d) | Data integrity testing |
| Storage limitation | Art. 5(1)(e) | Data retention testing |
| Integrity and confidentiality | Art. 5(1)(f) | Core security testing |
| Accountability | Art. 5(2) | Documentation and reporting |
GDPR Security Requirements (Article 32)
Article 32 — Security of Processing:
Taking into account the state of the art, the costs of implementation and
the nature, scope, context and purposes of processing as well as the risk
of varying likelihood and severity for the rights and freedoms of natural
persons, the controller and the processor shall implement appropriate
technical and organizational measures to ensure a level of security
appropriate to the risk:
(a) The pseudonymisation and encryption of personal data
(b) The ability to ensure the ongoing confidentiality, integrity,
availability and resilience of processing systems and services
(c) The ability to restore the availability and access to personal data
in a timely manner in the event of a physical or technical incident
(d) A process for regularly testing, assessing and evaluating the
effectiveness of technical and organizational measures
Key Point: Article 32(d) explicitly requires regular security testing, making penetration testing a de facto requirement for GDPR compliance.
GDPR Breach Notification Requirements
| Requirement | Timeline |
|---|---|
| Notify supervisory authority | Within 72 hours of becoming aware |
| Notify data subjects | Without undue delay (if high risk) |
| Document all breaches | Maintain breach register |
OSCP Exam Relevance
How Frameworks Appear in OSCP Reporting
The OSCP exam requires a professional penetration testing report. While the exam does not test framework knowledge directly, framework-aligned reporting significantly improves report quality:
| Report Section | Framework Application |
|---|---|
| Executive Summary | NIST CSF function mapping for executive understanding |
| Findings | CIS Controls for specific remediation guidance |
| Risk Ratings | CVSS scoring aligned with framework severity |
| Remediation | ISO 27001 / CIS Controls for actionable steps |
| Appendix | Framework mapping tables for compliance teams |
Using Frameworks to Structure Remediation Recommendations
Framework-Aligned Remediation Template
## Finding: [Vulnerability Name]
### Risk Rating
- **CVSS v3.1 Score:** [Score] ([Severity])
- **Vector String:** [Vector]
- **Business Impact:** [Description]
### Description
[Technical description of the vulnerability]
### Proof of Concept
[Steps to reproduce]
### Impact
[What an attacker can achieve]
### Remediation
#### Immediate Actions (Short-Term)
1. [Specific technical fix]
- **CIS Control:** Control 4.2 — Implement secure configurations
- **NIST CSF:** PR.PS-03 — Software and firmware are maintained
#### Strategic Actions (Long-Term)
1. [Process improvement]
- **ISO 27001:** A.8.35 — Management of technical vulnerabilities
- **NIST CSF:** ID.RA-01 — Vulnerabilities are identified on recurring basis
#### Verification Steps
1. [How to verify the fix is effective]
CVSS Scoring and Framework Alignment
CVSS v3.1 Metric Groups
CVSS v3.1 Score Components:
┌─────────────────────────────────────────────────────────────┐
│ BASE METRICS │
├──────────────────┬──────────────────┬────────────────────────┤
│ EXPLOITABILITY │ IMPACT │ METRIC │
│ (Weight: 0.822) │ (Weight: 0.178) │ VALUES │
├──────────────────┼──────────────────┼────────────────────────┤
│ Attack Vector │ Confidentiality │ Network (N) │
│ (AV) │ Impact (C) │ Adjacent (A) │
│ │ │ Local (L) │
│ Attack Complexity │ Integrity │ Physical (P) │
│ (AC) │ Impact (I) │ │
│ │ │ High (H) │
│ Attack │ Availability │ Medium (L) │
│ Requirements (PR)│ Impact (A) │ Low (L) │
│ │ │ None (N) │
│ User Interaction │ │ │
│ (UI) │ │ │
│ │ │ │
│ Privilege │ │ │
│ Level (RL) │ │ │
└──────────────────┴──────────────────┴────────────────────────┘
CVSS Vector Examples for Common OSCP Findings
| Finding | CVSS Vector | Score | Severity |
|---|---|---|---|
| Remote Code Execution (no auth) | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
9.8 | Critical |
| SQL Injection (authenticated) | AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
8.6 | High |
| XSS (reflected) | AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
6.1 | Medium |
| Privilege Escalation (local) | AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
7.8 | High |
| Information Disclosure | AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
5.3 | Medium |
| Default Credentials | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
9.8 | Critical |
| Directory Traversal | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
7.5 | High |
| CSRF | AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
5.4 | Medium |
| Open Redirect | AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N |
4.3 | Medium |
| Weak SSL/TLS | AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
5.9 | Medium |
What Level of Framework Knowledge Is Needed for OSCP
| Knowledge Area | Required Level | Reason |
|---|---|---|
| CVSS Scoring | Required | Must score findings accurately in the report |
| NIST CSF | Helpful | Structures executive summary and remediation |
| CIS Controls | Helpful | Provides specific remediation references |
| ISO 27001 | Nice to Have | Adds credibility to remediation recommendations |
| PCI DSS | Contextual | Relevant if testing payment systems |
| Framework Mapping | Helpful | Shows professionalism in reporting |
Bottom Line: The OSCP exam primarily tests technical exploitation skills. Framework knowledge enhances the report quality, which accounts for a significant portion of the exam grade. A well-structured, framework-aligned report demonstrates professionalism and can be the difference between passing and failing.
Practical Examples
Example 1: Mapping a Finding to NIST CSF Categories
Scenario: Remote Code Execution via Deserialization
## Finding: Insecure Deserialization Leading to Remote Code Execution
### Technical Details
- **Target:** /api/v2/user/profile
- **Parameter:** serialized_data (POST body)
- **Language:** Java
- **Library:** Apache Commons Collections 3.2.1
- **CVSS v3.1:** 9.8 (Critical)
- **Vector:** AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
### NIST CSF 2.0 Mapping
| Function | Category | Subcategory | Relevance |
|---|---|---|---|
| PROTECT | PR.PS | PR.PS-03 | Software and firmware are maintained and configured |
| PROTECT | PR.PS | PR.PS-04 | Code development and testing processes |
| PROTECT | PR.DS | PR.DS-01 | Data-at-rest is protected |
| DETECT | DE.CM | DE.CM-01 | Networked environments are monitored |
| IDENTIFY | ID.RA | ID.RA-01 | Vulnerabilities in assets are identified |
| PROTECT | PR.PT | PR.PT-05 | Protective technology is implemented |
### CIS Controls Mapping
| Control | Safeguard | Description |
|---|---|---|
| Control 17 | 17.3 | Perform security testing of applications |
| Control 4 | 4.3 | Implement secure configurations for software |
| Control 7 | 7.6 | Perform penetration testing on a recurring basis |
| Control 10 | 10.2 | Apply security patches in a timely manner |
### ISO 27001:2022 Mapping
| Control | Title |
|---|---|
| A.8.35 | Management of technical vulnerabilities |
| A.5.43 | Secure development life cycle |
| A.5.46 | Secure coding |
| A.8.29 | Protection of information systems in development and testing |
### Remediation Recommendations
#### Immediate (0-7 days)
1. Update Apache Commons Collections to version 4.4+ or apply the
specific patch for the deserialization vulnerability
2. Implement input validation to reject unexpected serialized objects
3. Deploy WAF rule to block known deserialization attack patterns
#### Short-Term (1-4 weeks)
1. Implement object allowlisting for deserialization
2. Add runtime application self-protection (RASP) to detect
deserialization attacks
3. Conduct organization-wide scan for other uses of vulnerable libraries
#### Long-Term (1-3 months)
1. Implement Software Composition Analysis (SCA) in CI/CD pipeline
2. Establish secure coding standards for serialization/deserialization
3. Conduct developer training on insecure deserialization risks
Example 2: Writing Remediation Using CIS Controls
Scenario: Weak Password Policy
## Finding: Weak Password Policy Allows Brute Force Attacks
### Technical Details
- **Minimum Length:** 6 characters
- **Complexity:** Not enforced
- **History:** Not enforced
- **Lockout:** Not configured
- **MFA:** Not enabled
- **CVSS v3.1:** 7.5 (High)
- **Vector:** AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
### CIS Controls Mapping
| Control | Safeguard | Current State | Required State |
|---|---|---|---|
| 5.7 | Password management | 6 chars, no complexity | 12+ chars, complexity required |
| 5.8 | Multi-factor authentication | Not enabled | Enabled for all accounts |
| 5.2 | Privileged account management | Same policy as users | Enhanced policy for privileged |
| 1.9 | Periodic review of human accounts | Not performed | Quarterly review |
### CIS-Aligned Remediation
#### CIS Control 5.7 — Password Management
**Current State Assessment:**
- Minimum password length: 6 characters (CIS requires 8+ for IG1, 12+ for IG2)
- No complexity requirements (CIS requires uppercase, lowercase, numbers, special)
- No password history (CIS requires 24 passwords remembered)
- No account lockout (CIS requires lockout after 6 failed attempts)
**Remediation Steps:**
```powershell
# Windows Group Policy — Password Policy
# Run as Domain Administrator
# Set minimum password length to 12
net accounts /minpwlen:12
# Set password complexity requirement
# (Enable via Group Policy: Computer Configuration ->
# Policies -> Windows Settings -> Security Settings ->
# Account Policies -> Password Policy ->
# Password must meet complexity requirements)
# Set maximum password age to 90 days
net accounts /maxpwage:90
# Set minimum password age to 1 day
net accounts /minpwage:1
# Set password history to 24 passwords
net accounts /uniquepw:24
# Set account lockout threshold to 6 attempts
net accounts /lockoutthreshold:6
# Set account lockout duration to 30 minutes
net accounts /lockoutduration:30
# Set lockout observation window to 30 minutes
net accounts /lockoutwindow:30
# Linux — /etc/login.defs
# Edit as root
PASS_MIN_LEN 12
PASS_MAX_DAYS 90
PASS_MIN_DAYS 1
PASS_MIN_LEN 12
PASS_WARN_AGE 14
UMASK 077
# /etc/pam.d/system-auth
# Add password quality module
password requisite pam_pwquality.so try_first_pass local_users_only
retry=3 minlen=12 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1
# Set password history
password sufficient pam_pwhistory.so remember=24 use_authtok
CIS Control 5.8 — Multi-Factor Authentication
Remediation Steps:
- Deploy MFA solution (e.g., Azure MFA, Duo, Okta Verify)
- Enable MFA for all user accounts
- Enable MFA for all administrative accounts (mandatory for CIS IG1)
- Configure MFA for remote access (VPN, RDP, SSH)
- Implement conditional access policies based on risk
Verification Testing
# Verify password policy on Windows
net accounts
# Verify password policy on Linux
pam-auth-update --help
grep -E "PASS_MIN|PASS_MAX" /etc/login.defs
# Test brute force resistance
# (After remediation, attempt brute force and verify lockout)
hydra -l admin -P wordlist.txt ssh://target_ip
# Expected: Account locked after 6 attempts
### Example 3: CVSS Scoring Examples
#### Example 3a: SQL Injection with Authentication
Vulnerability: SQL Injection in User Search Function
- Requires authentication (low privilege)
- No user interaction needed
- Attacker gains full database access
- Can read, modify, and delete data
- Does not affect system availability
CVSS v3.1 Calculation:
Exploitability Metrics: Attack Vector (AV): Network (N) — Exploitable remotely Attack Complexity (AC): Low (L) — Straightforward exploitation Attack Requirements (PR): Low (L) — Requires authenticated account User Interaction (UI): None (N) — No victim interaction needed
Impact Metrics: Scope (S): Unchanged (U) — Impact limited to vulnerable component Confidentiality (C): High (H) — Full database access Integrity (I): High (H) — Can modify/delete data Availability (A): None (N) — Does not affect availability
Vector String: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Base Score: 8.6 (High)
#### Example 3b: Local Privilege Escalation
Vulnerability: Kernel Privilege Escalation (CVE-2021-4034)
- Requires local access
- Low complexity exploitation
- Starts with low privilege user
- Escalates to root/System
- Full system compromise
CVSS v3.1 Calculation:
Exploitability Metrics: Attack Vector (AV): Local (L) — Requires local access Attack Complexity (AC): Low (L) — Simple exploitation Attack Requirements (PR): Low (L) — Standard user account User Interaction (UI): None (N) — No interaction needed
Impact Metrics: Scope (S): Changed (C) — Impact affects beyond vulnerable component Confidentiality (C): High (H) — Full system access Integrity (I): High (H) — Full system control Availability (A): High (H) — Can disrupt system
Vector String: AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Base Score: 7.8 (High)
#### Example 3c: Reflected XSS
Vulnerability: Reflected Cross-Site Scripting in Search Parameter
- Exploitable via network
- Low complexity
- No authentication required
- Requires victim to click malicious link
- Limited to victim’s browser session
- Can steal session cookies
CVSS v3.1 Calculation:
Exploitability Metrics: Attack Vector (AV): Network (N) — Remote exploitation Attack Complexity (AC): Low (L) — Simple payload Attack Requirements (PR): None (N) — No authentication User Interaction (UI): Required (R) — Victim must click link
Impact Metrics: Scope (S): Changed (C) — Impact affects user agent (browser) Confidentiality (C): Low (L) — Limited data exposure Integrity (I): Low (L) — Limited integrity impact Availability (A): None (N) — No availability impact
Vector String: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Base Score: 6.1 (Medium)
---
## Lab Exercises
### Exercise 1: Framework Mapping Practice
**Objective:** Map common penetration testing findings to multiple frameworks.
**Instructions:**
1. For each finding below, identify:
- Primary NIST CSF function and subcategory
- Relevant CIS Control(s)
- Applicable ISO 27001:2022 control(s)
- CVSS v3.1 score and vector string
2. Findings to map:
| # | Finding | Difficulty |
|---|---|---|
| 1 | Unpatched Apache Struts (CVE-2017-5638) | Medium |
| 2 | Default admin/admin credentials on router | Easy |
| 3 | Stored XSS in blog comment form | Medium |
| 4 | Missing TLS on internal API | Easy |
| 5 | Linux kernel privilege escalation (Dirty Cow) | Hard |
| 6 | Exposed Elasticsearch cluster | Medium |
| 7 | Insecure JWT implementation | Hard |
| 8 | No account lockout policy | Easy |
| 9 | Server-Side Request Forgery (SSRF) | Hard |
| 10 | Unencrypted backup files on shared drive | Medium |
**Deliverable:** Create a mapping table with all framework references for each finding.
### Exercise 2: Writing a Framework-Aligned Report
**Objective:** Write a professional penetration testing finding using framework references.
**Scenario:** You discovered the following during a penetration test:
Target: webapp.example.com Vulnerability: SQL Injection in login form Endpoint: POST /api/login Parameter: username Payload: admin’ OR ‘1’=‘1’ – Impact: Full database access, all user credentials exposed Database: MySQL 5.7 Data exposed: 15,000 user records with passwords (MD5 hashed)
**Instructions:**
1. Write a complete finding section including:
- Executive summary (1-2 paragraphs, non-technical)
- Technical details
- Proof of concept
- Impact analysis
- CVSS scoring with justification
- NIST CSF mapping
- CIS Controls mapping
- ISO 27001 control mapping
- Remediation recommendations (immediate, short-term, long-term)
- Verification steps
2. Write an executive summary paragraph that references NIST CSF functions.
**Deliverable:** Complete finding write-up following the template in Practical Examples.
### Exercise 3: CVSS Scoring Practice
**Objective:** Practice CVSS v3.1 scoring for various vulnerability scenarios.
**Instructions:** Score each scenario using CVSS v3.1 and provide the vector string:
| # | Scenario |
|---|---|
| 1 | Remote code execution via buffer overflow in internet-facing service, no authentication required |
| 2 | Cross-site scripting in admin panel (requires admin authentication), reflected, steals admin session |
| 3 | Local file inclusion on internal server, requires SSH access with valid credentials |
| 4 | Information disclosure via error messages on public API, no authentication, reveals internal IP addresses |
| 5 | Privilege escalation from www-data to root via SUID binary misconfiguration, requires web shell |
| 6 | CSRF token bypass on password change function, requires authenticated session |
| 7 | Directory traversal on file download feature, authenticated, reads /etc/passwd |
| 8 | Open redirect used in phishing campaign, no authentication, redirects to attacker-controlled site |
**Deliverable:** CVSS vector string and score for each scenario with brief justification.
### Exercise 4: Remediation Recommendation Writing
**Objective:** Write framework-aligned remediation recommendations for a set of findings.
**Instructions:** For each finding, write remediation recommendations that reference:
- At least one CIS Control
- At least one NIST CSF subcategory
- Specific technical steps
**Findings:**
1. Weak SSL/TLS configuration (TLS 1.0 enabled)
2. Missing HTTP security headers (X-Frame-Options, CSP, HSTS)
3. Excessive database permissions for web application account
4. No rate limiting on authentication endpoints
5. Sensitive data logged in plaintext
**Deliverable:** Remediation section for each finding with framework references.
---
## Key Tools
### CVSS Calculator
| Tool | URL | Description |
|---|---|---|
| **First.org CVSS Calculator** | `https://www.first.org/cvss/calculator/3.1` | Official CVSS v3.1 calculator |
| **NIST CVSS Calculator** | `https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator` | NIST-hosted calculator with NVD integration |
| **Snyk CVSS Calculator** | `https://snyk.io/vuln-calculator/` | Modern UI, export capabilities |
### NIST CSF Tools
| Tool | URL | Description |
|---|---|---|
| **NIST CSF Toolkit** | `https://www.nist.gov/cyberframework` | Official NIST CSF resources |
| **CSF Builder** | `https://www.nist.gov/itl/ssd/software-quality-group/cybersecurity-framework` | Interactive CSF mapping tool |
| **OpenCSF** | `https://opencsf.io` | Open-source CSF implementation framework |
| **CSF Lens Mapper** | Various | Map other frameworks to NIST CSF |
### CIS Tools
| Tool | URL | Description |
|---|---|---|
| **CIS-CAT Pro** | `https://www.cisecurity.org/cis-cat` | CIS Controls Assessment Tool |
| **CIS-CAT Lite** | `https://www.cisecurity.org/tools/workbench` | Free version of CIS-CAT |
| **CIS Benchmarks** | `https://www.cisecurity.org/benchmark` | Free hardening benchmarks |
| **CIS Controls Implementation Guide** | `https://www.cisecurity.org/controls` | Detailed implementation guidance |
### Framework Comparison Tools
| Tool | URL | Description |
|---|---|---|
| **MITRE ATT&CK Navigator** | `https://mitre-attack.github.io/attack-navigator` | Map findings to ATT&CK techniques |
| **OWASP ASVS** | `https://owasp.org/www-project-application-security-verification-standard` | Application security verification |
| **SecurityScorecard** | `https://securityscorecard.com` | External attack surface monitoring |
| **BitSight** | `https://www.bitsight.com` | Security rating and monitoring |
### Penetration Testing Framework Tools
| Tool | Purpose | Description |
|---|---|---|
| **PTES** | Methodology | Penetration Testing Execution Standard |
| **OSSTMM** | Methodology | Open Source Security Testing Methodology Manual |
| **ISSAF** | Methodology | Information Systems Security Assessment Framework |
| **WAPT** | Methodology | Web Application Penetration Testing standard |
---
## Exam Tips
### Framework Knowledge for the OSCP Report
#### Must-Know (Required for Passing)
1. **CVSS v3.1 Scoring**
- Know how to calculate CVSS scores manually
- Understand each metric and its values
- Be able to justify your score choices
- Practice with the official calculator
2. **Finding Structure**
- Every finding must have: Title, Risk Rating, Description, Proof of Concept, Impact, Remediation
- Risk ratings must be consistent and justified
- Remediation must be specific and actionable
3. **Executive Summary**
- Write for a non-technical audience
- Summarize key findings without technical jargon
- Provide overall risk assessment
- Include high-level recommendations
#### Should-Know (Improves Report Quality)
1. **NIST CSF Functions**
- Know the 6 functions and their purposes
- Be able to map findings to CSF categories
- Use CSF language in executive summaries
2. **CIS Controls**
- Know the most relevant controls (1-8, 12-14, 17)
- Reference CIS Controls in remediation sections
- Understand Implementation Groups
3. **Common Framework References**
- ISO 27001 Annex A controls for remediation
- PCI DSS requirements if applicable
- OWASP Top 10 for web application findings
#### Nice-to-Know (Bonus Points)
1. **Framework Mapping Tables**
- Include a mapping table in the appendix
- Map each finding to multiple frameworks
- Show compliance impact
2. **Risk Quantification**
- Use FAIR or similar methodology
- Estimate potential financial impact
- Provide ROI for remediation
3. **Industry-Specific Frameworks**
**
- Reference HIPAA for healthcare targets
- Reference PCI DSS for payment systems
- Reference GDPR for EU data processing
### Common Report Mistakes to Avoid
| Mistake | Impact | Fix |
|---|---|---|
| Inconsistent CVSS scores | Lowers credibility | Use calculator, justify each metric |
| Vague remediation | Unactionable | Provide specific steps and commands |
| Missing proof of concept | Finding not validated | Include screenshots and commands |
| Technical jargon in executive summary | Executives can't understand | Write plain-language summaries |
| No framework references | Missed compliance context | Add NIST CSF / CIS Control mappings |
| Inconsistent risk ratings | Confusing prioritization | Use CVSS consistently, document methodology |
| Missing impact analysis | Can't prioritize | Describe business impact for each finding |
| No verification steps | Can't confirm fix | Include testing steps for each remediation |
### Report Structure Checklist
[ ] Executive Summary [ ] Non-technical language [ ] Overall risk assessment [ ] Key findings summary [ ] High-level recommendations [ ] NIST CSF function mapping (optional but recommended)
[ ] Methodology [ ] Testing approach description [ ] Tools used [ ] Scope and limitations [ ] Rules of engagement
[ ] Findings [ ] Each finding has unique ID [ ] CVSS score with vector string [ ] Clear description [ ] Proof of concept with evidence [ ] Impact analysis [ ] Specific remediation steps [ ] Framework references (CIS, NIST CSF, ISO 27001) [ ] Verification steps
[ ] Appendix [ ] Network diagram [ ] Tool output samples [ ] Framework mapping table [ ] Glossary of terms [ ] References
---
## Cross-References
### Related Topics in This Study Guide
| Topic | Relationship | Reference |
|---|---|---|
| **Report Writing** | Frameworks structure professional reports | See Report Writing chapter |
| **Penetration Testing Methodology** | Frameworks inform testing phases | See Methodology chapter |
| **Ethical Hacking** | Frameworks define scope and boundaries | See Ethical Hacking chapter |
| **Vulnerability Assessment** | Frameworks prioritize vulnerabilities | See Vuln Assessment chapter |
| **Risk Management** | Frameworks quantify and manage risk | See Risk Management chapter |
| **Compliance Testing** | Frameworks are compliance baselines | See Compliance chapter |
| **CVSS Scoring** | CVSS aligns with framework severity | See CVSS chapter |
| **Remediation Strategies** | Frameworks guide remediation prioritization | See Remediation chapter |
### External Resources
| Resource | URL | Description |
|---|---|---|
| **NIST CSF 2.0** | `https://www.nist.gov/cyberframework` | Official NIST Cybersecurity Framework |
| **NIST SP 800-53 Rev. 5** | `https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final` | Security Controls Catalog |
| **ISO 27001:2022** | `https://www.iso.org/standard/27001` | ISMS Standard |
| **CIS Controls v8** | `https://www.cisecurity.org/controls` | Critical Security Controls |
| **PCI DSS v4.0** | `https://docs.prpcips.org/pcidssv4_0` | Payment Card Security Standard |
| **CVSS v3.1 Specification** | `https://www.first.org/cvss/specification-document` | CVSS Specification |
| **OWASP Top 10** | `https://owasp.org/www-project-top-ten` | Web Application Risks |
| **MITRE ATT&CK** | `https://attack.mitre.org` | Adversary Tactics and Techniques |
| **PTES** | `https://www.pentest-standard.org` | Penetration Testing Execution Standard |
### Framework Comparison Quick Reference
| Framework | Best For | Pen Testing Role | Complexity |
|---|---|---|---|
| **NIST CSF** | Executive reporting, risk management | Finding mapping, executive summary | Medium |
| **NIST SP 800-53** | Federal compliance, detailed controls | Precise control mapping | High |
| **ISO 27001** | International compliance, ISMS | Remediation recommendations | High |
| **CIS Controls** | Actionable remediation, prioritization | Specific safeguard references | Medium |
| **PCI DSS** | Payment card compliance | Mandatory testing requirements | High |
| **SOC 2** | Service organization trust | Trust criteria validation | Medium |
| **HIPAA** | Healthcare compliance | PHI protection testing | Medium |
| **GDPR** | EU data protection | PII handling assessment | Medium |
---
## Summary
Security frameworks provide the structured language and standardized approach that bridges the gap between technical penetration testing findings and organizational risk management. For OSCP candidates, understanding these frameworks is not about memorizing every control — it is about:
1. **Knowing how to reference frameworks** in your report to add credibility and compliance context
2. **Using CVSS scoring correctly** to provide consistent, defensible risk ratings
3. **Structuring remediation recommendations** that IT teams can act on using familiar control language
4. **Writing executive summaries** that resonate with stakeholders who think in framework terms
The most valuable frameworks for OSCP reporting are:
- **NIST CSF 2.0** — For executive-level communication and risk mapping
- **CIS Critical Security Controls** — For specific, actionable remediation guidance
- **CVSS v3.1** — For consistent vulnerability scoring
- **ISO 27001** — For international compliance context
Master these four, and your OSCP report will stand out for its professionalism, clarity, and actionable value.
---
*Last Updated: 2026-09-01*
*Next Review: 2027-03-01*
*Related: Report Writing, Penetration Testing Methodology, CVSS Scoring, Risk Management*