FedRAMP High
PL - Planning

FedRAMP High PL-2: System Security and Privacy Plans

Develop SSP that aligns with FedRAMP template; review and update annually.

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

What else in your programme already covers this

This control maps to 60 controls across 31 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 · 6 controls

  • 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.5.2 12.5.2 Annual and change-driven scope confirmation
  • 12.5.2.1 12.5.2.1 Six-monthly scope confirmation for service providers
  • 12.8.5 12.8.5 Responsibility allocation between entity and TPSPs
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed

ISO 27001:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.35 Independent review of information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 5.8 Information security in project management

ISO 27002:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.35 Independent review of information security
  • 5.37 Documented operating procedures
  • 5.8 Information security in project management

HIPAA Security Rule · 4 controls

SOC 2 · 4 controls

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC3.1 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

C5 (Germany) · 3 controls

  • C5-COM-01 Identification of applicable legal, regulatory, self-imposed or contractual requirements
  • C5-OIS-01 Information Security Management System (ISMS)
  • C5-OIS-02 Information Security Policy
  • 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

GDPR · 2 controls

ISO 27701:2019 · 2 controls

  • 5.1 General
  • 5.2.3 Determining the scope of the information security management system

NIS2 Directive · 2 controls

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation
  • Art.21.2.a Policies on risk analysis and on information system security

NIST SP 800-66 Rev 2 · 2 controls

  • CPS230-P27 Comprehensive Assessment of the Operational Risk Profile
  • SEC01-BP03 Identify and validate control objectives
  • APP-1 APP 1 - Open and transparent management of personal information
  • CFTC-SS-1 Program of Risk Analysis and Oversight

CMMC 2.0 · 1 control

DORA · 1 control

ISO 22301:2019 · 1 control

  • 4.3.2 Scope of the business continuity management system

ISO/IEC 42001:2023 · 1 control

  • A.6.2.3 Documentation of AI system design and development
  • NIST-CSF-GV.OC-01 The organizational mission is understood and informs cybersecurity risk management

NIST SP 800-172 · 1 control

  • 3.11.4e Security Solution Rationale Document
  • PL-2 PL-2 System Security and Privacy Plans
  • PL-2 PL-2 System Security and Privacy Plans
  • PL-2 PL-2 System Security and Privacy Plans

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 PL - Planning

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High PL-2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

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. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

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