800-53 · PL Planning
PL-8
Security and Privacy Architectures
Official texta. Develop security and privacy architectures for the system that:
1. Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;
2. Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;
3. Describe how the architectures are integrated into and support the enterprise architecture; and
4. Describe any assumptions about, and dependencies on, external systems and services;
b. Review and update the architectures [Assignment: organization-defined frequency] to reflect changes in the enterprise architecture; and
c. Reflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitions.NIST SP 800-53 Rev 5.2 control statement (public domain)
1. Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;
2. Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;
3. Describe how the architectures are integrated into and support the enterprise architecture; and
4. Describe any assumptions about, and dependencies on, external systems and services;
b. Review and update the architectures [Assignment: organization-defined frequency] to reflect changes in the enterprise architecture; and
c. Reflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitions.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-03 | Representations of the organization's authorized network communication and internal and external network data flows are maintained | No mapping. Only shares CSF ID.AM-03: related, not a mapping | |
| ISO 27001 | A.5.8 | Information security in project management | Crosswalk | NIST SP 800-53 → ISO 27001 mapping4 loosely related (not mappings) |
| CIS v8.1 | CIS 3.8CIS 4.4CIS 4.5CIS 12.3 | Document Data Flows; Implement and Manage a Firewall on Servers… | No mapping. Only shares CSF ID.AM-03: related, not a mapping+4 more loosely related (not mappings)CIS 12.4 Establish and Maintain Architecture Diagram(s) Only shares CSF ID.AM-03: related, not a mapping CIS 12.6 Use of Secure Network Management and Communication Protocols Only shares CSF ID.AM-03: related, not a mapping CIS 13.4 Perform Traffic Filtering Between Network Segments Only shares CSF ID.AM-03: related, not a mapping | |
| SOC 2 | CC6.6 | Protection against threats from outside system boundaries | No mapping. Only shares CSF ID.AM-03: related, not a mapping | |
| PCI DSS | 1.2.31.2.412.5.21.2.1 | Accurate network diagram maintained; Accurate account-data flow diagram maintained… | No mapping. Only shares CSF ID.AM-03: related, not a mapping | |
| CMMC | CA.L2-3.12.4 | System Security Plan | No mapping. Only shares CSF ID.AM-03: related, not a mapping | |
| HIPAA | §164.308(a)(1)(ii)(B)§164.308(a)(3)(ii)(A)§164.308(a)(4)(ii)(A)§164.308(a)(4)(ii)(B) | Risk Management; Authorization and/or Supervision… | No mapping. Only shares CSF ID.AM-03: related, not a mapping+11 more loosely related (not mappings)§164.308(b)(1) Business Associate Contracts and Other Arrangements Only shares CSF ID.AM-03: related, not a mapping §164.308(b)(4) Written Contract or Other Arrangement Only shares CSF ID.AM-03: related, not a mapping …and 7 more in the downloads | |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | 4.312.4 | Crisis management; Asset inventory | No mapping. Only shares CSF ID.AM-03: related, not a mapping | |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | Art.9(4)(b) | Protection and prevention | No mapping. Only shares CSF ID.AM-03: related, not a mapping | |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | CE 1 | Firewalls | No mapping. Only shares CSF ID.AM-03: 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.