CMMC 2.0
Security Assessment

CMMC 2.0 CA.L2-3.12.4: System Security Plan

Develop, document and periodically update a system security plan describing system boundaries, the operating environment, how each requirement is implemented, and connections to other systems.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 72 controls across 29 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 14 controls

  • 1.1.1 1.1.1 Requirement 1 policies and procedures governed
  • 1.2.3 1.2.3 Accurate network diagram of CDE connections
  • 11.1.1 11.1.1 Requirement 11 policies and procedures managed
  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 12.10.2 12.10.2 Annual review and testing of the incident response plan
  • 12.5.1 12.5.1 Inventory of in-scope system components
  • 12.5.2 12.5.2 Annual and change-driven scope confirmation
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
  • 7.1.1 7.1.1 Requirement 7 policies and procedures maintained
  • 9.1.1 9.1.1 Requirement 9 policies and procedures maintained
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 8.1.1 8.1.1 Requirement 8 policies and procedures maintained

ISO 27701:2019 · 6 controls

  • 5.1 General
  • 5.2.3 Determining the scope of the information security management system
  • 5.3.2 Policy
  • 5.5.5 Documented information
  • 6.1 General
  • 6.15.1 Compliance with legal and contractual requirements

ISO 22301:2019 · 5 controls

  • 4.3.2 Scope of the business continuity management system
  • 7.5.1 General
  • 7.5.3 Control of documented information
  • 8.1 Operational planning and control
  • 8.4.4 Business continuity plans

HIPAA Security Rule · 4 controls

ISO 27002:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.37 Documented operating procedures
  • 8.26 Application security requirements

SOC 2 · 4 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC3.1 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

ISO 27001:2022 · 3 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.37 Documented operating procedures

NIS2 Directive · 3 controls

  • Art.21.1 Take proportionate all-hazards measures calibrated to the entity's own risk exposure
  • Art.21.2.a Policies on risk analysis and on information system security
  • Art.32 Cooperate with supervision: inspections, security audits, scans and requests for information and evidence

APRA CPS 234 · 2 controls

  • CPS234-19 Information Security Policy Framework
  • CPS234-21 Implementation of Information Security Controls

AWS Well-Architected Security Pillar · 2 controls

  • SEC01-BP03 Identify and validate control objectives
  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model

Australia Consumer Data Right - Banking (CDR) · 2 controls

  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

C5 (Germany) · 2 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram

APRA CPS 220 Risk Management · 1 control

  • CPS220-P35 Required Content of Risk Management Policies and Procedures

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-24 Design and Embedding of Internal Controls

APRA SPS 220 Risk Management (Superannuation) · 1 control

  • SPS220-P28 Annual Review in Non Comprehensive Review Years

Azure Security Benchmark · 1 control

  • ASBv3-GS-5 Define and implement security posture management strategy

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-1 Program of Risk Analysis and Oversight

CIS Controls v8 · 1 control

  • CIS-12.4 Establish and Maintain Architecture Diagram(s)

FedRAMP High · 1 control

  • PL-2 System Security and Privacy Plans

FedRAMP Moderate · 1 control

  • PL-2 System Security and Privacy Plans

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.11.4e Security Solution Rationale Document

UK Cyber Essentials · 1 control

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.

Other controls in Security Assessment

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 CA.L2-3.12.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gapsIf you hold NIST SP 800-171 Rev 394.5% covered · 6 gapsIf you hold NIST SP 800-53 Rev 585.5% covered · 16 gapsIf you hold ISO 27001:202279.1% covered · 23 gapsIf you hold ISO 27002:202267.3% covered · 36 gapsIf you hold CIS Controls v864.5% covered · 39 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 1 were rejected on the FedRAMP Moderate pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 72 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CMMC 2.0 controls