800-53 · PL Planning
PL-2
System Security and Privacy Plans
frameworkNIST SP 800-53 Rev 5.2
sectionPL Planning
csf 2.0ID.AM-03 ID.AM-08 ID.IM-01 ID.IM-02 ID.IM-03 ID.IM-04
topics—
frameworks3 0 0
Official texta. Develop security and privacy plans for the system that:
1. Are consistent with the organization’s enterprise architecture;
2. Explicitly define the constituent system components;
3. Describe the operational context of the system in terms of mission and business processes;
4. Identify the individuals that fulfill system roles and responsibilities;
5. Identify the information types processed, stored, and transmitted by the system;
6. Provide the security categorization of the system, including supporting rationale;
7. Describe any specific threats to the system that are of concern to the organization;
8. Provide the results of a privacy risk assessment for systems processing personally identifiable information;
9. Describe the operational environment for the system and any dependencies on or connections to other systems or system components;
10. Provide an overview of the security and privacy requirements for the system;
11. Identify any relevant control baselines or overlays, if applicable;
12. Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions;
13. Include risk determinations for security and privacy architecture and design decisions;
14. Include security- and privacy-related activities affecting the system that require planning and coordination with [Assignment: organization-defined individuals or groups]; and
15. Are reviewed and approved by the authorizing official or designated representative prior to plan implementation.
b. Distribute copies of the plans and communicate subsequent changes to the plans to [Assignment: organization-defined personnel or roles];
c. Review the plans [Assignment: organization-defined frequency];
d. Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and
e. Protect the plans from unauthorized disclosure and modification.NIST SP 800-53 Rev 5.2 control statement (public domain)
1. Are consistent with the organization’s enterprise architecture;
2. Explicitly define the constituent system components;
3. Describe the operational context of the system in terms of mission and business processes;
4. Identify the individuals that fulfill system roles and responsibilities;
5. Identify the information types processed, stored, and transmitted by the system;
6. Provide the security categorization of the system, including supporting rationale;
7. Describe any specific threats to the system that are of concern to the organization;
8. Provide the results of a privacy risk assessment for systems processing personally identifiable information;
9. Describe the operational environment for the system and any dependencies on or connections to other systems or system components;
10. Provide an overview of the security and privacy requirements for the system;
11. Identify any relevant control baselines or overlays, if applicable;
12. Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions;
13. Include risk determinations for security and privacy architecture and design decisions;
14. Include security- and privacy-related activities affecting the system that require planning and coordination with [Assignment: organization-defined individuals or groups]; and
15. Are reviewed and approved by the authorizing official or designated representative prior to plan implementation.
b. Distribute copies of the plans and communicate subsequent changes to the plans to [Assignment: organization-defined personnel or roles];
c. Review the plans [Assignment: organization-defined frequency];
d. Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and
e. Protect the plans from unauthorized disclosure and modification.NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | ID.AM-03ID.AM-08 | Representations of the organization's authorized network communication and internal and external network data flows are maintained; Systems, hardware, software, services, and data are managed throughout their life cycles | No mapping. Only shares CSF ID.AM-03, ID.AM-08: related, not a mapping | |
| ISO 27001 | A.5.8A.5.34Clause 7.5.1Clause 7.5.2Clause 7.5.3Clause 10.2 | Information security in project management; Privacy and protection of PII… | Crosswalk | NIST SP 800-53 → ISO 27001 mapping13 loosely related (not mappings)A.5.19 Information security in supplier relationships Only shares CSF ID.AM-08, ID.IM-02: related, not a mapping A.5.9 Inventory of information and other associated assets Only shares CSF ID.AM-08: related, not a mapping A.5.22 Monitoring, review and change management of supplier services Only shares CSF ID.AM-08: related, not a mapping …and 5 more in the downloads |
| CIS v8.1 | CIS 1.1CIS 3.5CIS 3.8CIS 1.2 | Establish and Maintain Detailed Enterprise Asset Inventory; Securely Dispose of Data… | No mapping. Only shares CSF ID.AM-08, ID.AM-03: related, not a mapping+13 more loosely related (not mappings)CIS 1.4 Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory Only shares CSF ID.AM-08: related, not a mapping …and 9 more in the downloads | |
| SOC 2 | CC6.1CC6.6 | Logical access security over information assets; Protection against threats from outside system boundaries | No mapping. Only shares CSF ID.AM-08, ID.AM-03: related, not a mapping | |
| PCI DSS | 6.3.312.3.41.2.31.2.4 | Security patches installed promptly; Hardware and software technologies reviewed annually… | No mapping. Only shares CSF ID.AM-08, ID.IM-03, ID.IM-01, ID.AM-03: related, not a mapping+11 more loosely related (not mappings)6.2.1 Bespoke and custom software developed securely Only shares CSF ID.AM-08: related, not a mapping 6.2.2 Developers trained in secure software development Only shares CSF ID.AM-08: related, not a mapping 6.2.3.1 Manual code reviews approved by someone else Only shares CSF ID.AM-08: related, not a mapping …and 7 more in the downloads | |
| CMMC | CA.L2-3.12.1CA.L2-3.12.2CA.L2-3.12.3CA.L2-3.12.4 | Security Control Assessment; Plan of Action… | Crosswalk | NIST SP 800-171r2 Appendix D; NIST SP 800-171r3 03.15.02 → SP 800-533 loosely related (not mappings)SC.L2-3.13.2 Security Engineering Only shares CSF ID.AM-08, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping |
| HIPAA | §164.308(a)(1)(ii)(B)§164.310(a)(2)(ii)§164.314(b)§164.314(b)(2)(i)§164.314(b)(2)(ii)§164.316(a)§164.316(b)§164.316(b)(2)(iii) | Risk Management; Facility Security Plan… | Crosswalk | NIST HIPAA → SP 800-53 crosswalk12 loosely related (not mappings)§164.308(a)(3)(ii)(A) Authorization and/or Supervision Only shares CSF ID.AM-03, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping §164.308(a)(4)(ii)(B) Access Authorization Only shares CSF ID.AM-03, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping §164.310(a)(2)(iv) Maintenance Records Only shares CSF ID.AM-08, ID.IM-01, ID.IM-02, ID.IM-03: related, not a mapping §164.308(b)(4) Written Contract or Other Arrangement Only shares CSF ID.AM-03, ID.AM-08, ID.IM-03: related, not a mapping §164.314(a) Business Associate Contracts or Other Arrangements Only shares CSF ID.AM-08, ID.IM-03: related, not a mapping §164.314(a)(2)(i) Business Associate Contracts Only shares CSF ID.AM-08, ID.IM-03: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF ID.AM-08, ID.IM-03: related, not a mapping §164.308(a)(4)(ii)(A) Isolating Health care Clearinghouse Function Only shares CSF ID.AM-03: related, not a mapping …and 4 more in the downloads |
| GDPR | Art.30(1) | Records of processing activities | No mapping. Only shares CSF ID.AM-08: related, not a mapping | |
| NIS2 | 12.44.36.2 | Asset inventory; Crisis management… | No mapping. Only shares CSF ID.AM-03, ID.AM-08: related, not a mapping | |
| Essential Eight | ISM-1807 | An automated method of asset discovery is used at least fortnightly to support the… | No mapping. Only shares CSF ID.AM-08: related, not a mapping | |
| DORA | Art.8(1)Art.8(4)Art.8(6)Art.9(4)(b) | Identification; Identification… | No mapping. Only shares CSF ID.AM-08, ID.AM-03: related, not a mapping | |
| CPS 234 | Para 20 | Classify information assets by criticality and sensitivity | No mapping. Only shares CSF ID.AM-08: related, not a mapping | |
| Cyber Essentials | CE 1CE 3 | Firewalls; Security Update Management | No mapping. Only shares CSF ID.AM-03, ID.AM-08: related, not a mapping |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.