{"bundle":{"id":"bundle--ogrl-library","name":"OGRL Control Library","version":"0.3.0","spec_version":"0.1.0","modified":"2026-11-21T00:00:00Z","digest":"sha-256:5f96dd185fd5dd879fd3b5577fe9c93acfe2fe805882fcfe88e65a2de6c74e0b","commit":"8d0e512","repo_url":"https://github.com/adversitydotdev/ogrl-library","tools_repo_url":"https://github.com/adversitydotdev/ogrl-rs"},"counts":{"objects":2338,"frameworks":4,"controls":113,"baselines":4,"tests":12,"requirements":1395,"active_requirements":1180,"withdrawn_requirements":215,"objectives":3203,"mappings":810,"reviewed_mappings":413,"draft_mappings":397},"frameworks":[{"id":"framework--iso-iec-27001-2022","slug":"iso-iec-27001-2022","name":"ISO/IEC 27001:2022","publisher":"ISO/IEC","version":"2022","reproduction":"citation-only","source":null,"requirement_count":8,"active_count":8,"withdrawn_count":0,"objective_count":0,"mapping_count":8},{"id":"framework--nist-sp-800-171-r3","slug":"nist-sp-800-171-r3","name":"NIST SP 800-171 Revision 3","publisher":"NIST","version":"1.1.0","reproduction":"permitted","source":{"commit":"f0de6d8d8c059d374f15e0ae07508d82e370fc1d","format":"oscal-catalog","path":"nist.gov/SP800-171/rev3/json/NIST_SP800-171_rev3_catalog.json","uri":"https://github.com/usnistgov/oscal-content"},"requirement_count":130,"active_count":97,"withdrawn_count":33,"objective_count":422,"mapping_count":207},{"id":"framework--nist-sp-800-53-r5","slug":"nist-sp-800-53-r5","name":"NIST SP 800-53 Revision 5","publisher":"NIST","version":"5.2.0","reproduction":"permitted","source":{"commit":"f0de6d8d8c059d374f15e0ae07508d82e370fc1d","format":"oscal-catalog","path":"nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json","uri":"https://github.com/usnistgov/oscal-content"},"requirement_count":1196,"active_count":1014,"withdrawn_count":182,"objective_count":2781,"mapping_count":406},{"id":"framework--soc2-tsc-2017","slug":"soc2-tsc-2017","name":"AICPA SOC 2 Trust Services Criteria","publisher":"AICPA","version":"2017 (with 2022 Points of Focus)","reproduction":"citation-only","source":null,"requirement_count":61,"active_count":61,"withdrawn_count":0,"objective_count":0,"mapping_count":189}],"baselines":[{"id":"baseline--ogrl-core","slug":"ogrl-core","name":"OGRL Core Security Baseline","framework_refs":["framework--nist-sp-800-53-r5","framework--nist-sp-800-171-r3","framework--soc2-tsc-2017","framework--iso-iec-27001-2022"],"control_refs":["control--ogrl-ac-01","control--ogrl-ac-02","control--ogrl-ac-03","control--ogrl-ac-04","control--ogrl-ac-05","control--ogrl-ac-06","control--ogrl-lm-01","control--ogrl-lm-02","control--ogrl-cm-01","control--ogrl-cr-01","control--ogrl-ir-01","control--ogrl-vm-01"],"requirement_refs":[],"tags":["starter","multi-framework"],"yaml_path":"library/baseline/ogrl-core.yaml"},{"id":"baseline--ogrl-iso27001","slug":"ogrl-iso27001","name":"OGRL ISO/IEC 27001:2022 Starter Baseline","framework_refs":["framework--iso-iec-27001-2022"],"control_refs":["control--ogrl-ac-01","control--ogrl-ac-02","control--ogrl-ac-03","control--ogrl-ac-05","control--ogrl-ac-06","control--ogrl-lm-01","control--ogrl-cm-01","control--ogrl-cr-01"],"requirement_refs":["requirement--iso-iec-27001-2022-a-5-15","requirement--iso-iec-27001-2022-a-5-16","requirement--iso-iec-27001-2022-a-5-17","requirement--iso-iec-27001-2022-a-5-18","requirement--iso-iec-27001-2022-a-8-5","requirement--iso-iec-27001-2022-a-8-15","requirement--iso-iec-27001-2022-a-8-24","requirement--iso-iec-27001-2022-a-8-32"],"tags":["iso27001","starter"],"yaml_path":"library/baseline/ogrl-iso27001.yaml"},{"id":"baseline--ogrl-nist-800-171-r3","slug":"ogrl-nist-800-171-r3","name":"OGRL NIST SP 800-171 Rev 3 Core Baseline","framework_refs":["framework--nist-sp-800-171-r3"],"control_refs":["control--ogrl-ac-01","control--ogrl-ac-02","control--ogrl-ac-03","control--ogrl-ac-05","control--ogrl-lm-01","control--ogrl-cm-01","control--ogrl-cr-01","control--ogrl-ir-01","control--ogrl-vm-01"],"requirement_refs":["requirement--nist-sp-800-171-r3-03-01-01","requirement--nist-sp-800-171-r3-03-01-05","requirement--nist-sp-800-171-r3-03-03-01","requirement--nist-sp-800-171-r3-03-04-03","requirement--nist-sp-800-171-r3-03-05-03","requirement--nist-sp-800-171-r3-03-06-03","requirement--nist-sp-800-171-r3-03-11-02","requirement--nist-sp-800-171-r3-03-13-08"],"tags":["nist","cui","starter"],"yaml_path":"library/baseline/ogrl-nist-800-171-r3.yaml"},{"id":"baseline--ogrl-soc2","slug":"ogrl-soc2","name":"OGRL SOC 2 Baseline","framework_refs":["framework--soc2-tsc-2017"],"control_refs":["control--ogrl-ac-01","control--ogrl-ac-02","control--ogrl-ac-03","control--ogrl-ac-04","control--ogrl-ac-05","control--ogrl-ac-06","control--ogrl-ac-07","control--ogrl-ac-08","control--ogrl-ac-09","control--ogrl-ac-10","control--ogrl-ac-11","control--ogrl-ac-12","control--ogrl-ac-13","control--ogrl-ac-14","control--ogrl-ac-15","control--ogrl-am-01","control--ogrl-am-02","control--ogrl-bc-01","control--ogrl-bc-02","control--ogrl-bc-03","control--ogrl-bc-04","control--ogrl-bc-05","control--ogrl-bc-06","control--ogrl-bc-07","control--ogrl-bc-08","control--ogrl-bc-09","control--ogrl-cm-01","control--ogrl-cm-02","control--ogrl-cm-03","control--ogrl-cm-04","control--ogrl-cm-05","control--ogrl-cm-06","control--ogrl-cm-07","control--ogrl-cm-08","control--ogrl-cm-09","control--ogrl-cr-01","control--ogrl-cr-02","control--ogrl-cr-03","control--ogrl-cr-04","control--ogrl-cr-05","control--ogrl-gv-01","control--ogrl-gv-02","control--ogrl-gv-03","control--ogrl-gv-04","control--ogrl-gv-05","control--ogrl-gv-06","control--ogrl-gv-07","control--ogrl-gv-08","control--ogrl-gv-09","control--ogrl-gv-10","control--ogrl-gv-11","control--ogrl-gv-12","control--ogrl-hr-01","control--ogrl-hr-02","control--ogrl-hr-03","control--ogrl-hr-04","control--ogrl-hr-05","control--ogrl-hr-06","control--ogrl-hr-07","control--ogrl-hr-08","control--ogrl-ir-01","control--ogrl-ir-02","control--ogrl-ir-03","control--ogrl-ir-04","control--ogrl-ir-05","control--ogrl-ir-06","control--ogrl-lm-01","control--ogrl-lm-02","control--ogrl-lm-03","control--ogrl-lm-04","control--ogrl-lm-05","control--ogrl-pr-01","control--ogrl-pr-02","control--ogrl-pr-03","control--ogrl-pr-04","control--ogrl-pr-05","control--ogrl-pr-06","control--ogrl-pr-07","control--ogrl-pr-08","control--ogrl-pr-09","control--ogrl-pr-10","control--ogrl-pr-11","control--ogrl-ps-01","control--ogrl-ps-02","control--ogrl-ps-03","control--ogrl-ps-04","control--ogrl-ps-05","control--ogrl-ps-06","control--ogrl-ps-07","control--ogrl-rm-01","control--ogrl-rm-02","control--ogrl-rm-03","control--ogrl-rm-04","control--ogrl-rm-05","control--ogrl-rm-06","control--ogrl-sd-01","control--ogrl-sd-02","control--ogrl-sd-03","control--ogrl-sd-04","control--ogrl-sd-05","control--ogrl-sd-06","control--ogrl-sd-07","control--ogrl-sd-08","control--ogrl-tp-01","control--ogrl-tp-02","control--ogrl-tp-03","control--ogrl-tp-04","control--ogrl-vm-01","control--ogrl-vm-02","control--ogrl-vm-03","control--ogrl-vm-04","control--ogrl-vm-05","control--ogrl-vm-06"],"requirement_refs":["requirement--soc2-tsc-2017-cc1-1","requirement--soc2-tsc-2017-cc1-2","requirement--soc2-tsc-2017-cc1-3","requirement--soc2-tsc-2017-cc1-4","requirement--soc2-tsc-2017-cc1-5","requirement--soc2-tsc-2017-cc2-1","requirement--soc2-tsc-2017-cc2-2","requirement--soc2-tsc-2017-cc2-3","requirement--soc2-tsc-2017-cc3-1","requirement--soc2-tsc-2017-cc3-2","requirement--soc2-tsc-2017-cc3-3","requirement--soc2-tsc-2017-cc3-4","requirement--soc2-tsc-2017-cc4-1","requirement--soc2-tsc-2017-cc4-2","requirement--soc2-tsc-2017-cc5-1","requirement--soc2-tsc-2017-cc5-2","requirement--soc2-tsc-2017-cc5-3","requirement--soc2-tsc-2017-cc6-1","requirement--soc2-tsc-2017-cc6-2","requirement--soc2-tsc-2017-cc6-3","requirement--soc2-tsc-2017-cc6-4","requirement--soc2-tsc-2017-cc6-5","requirement--soc2-tsc-2017-cc6-6","requirement--soc2-tsc-2017-cc6-7","requirement--soc2-tsc-2017-cc6-8","requirement--soc2-tsc-2017-cc7-1","requirement--soc2-tsc-2017-cc7-2","requirement--soc2-tsc-2017-cc7-3","requirement--soc2-tsc-2017-cc7-4","requirement--soc2-tsc-2017-cc7-5","requirement--soc2-tsc-2017-cc8-1","requirement--soc2-tsc-2017-cc9-1","requirement--soc2-tsc-2017-cc9-2","requirement--soc2-tsc-2017-a1-1","requirement--soc2-tsc-2017-a1-2","requirement--soc2-tsc-2017-a1-3","requirement--soc2-tsc-2017-c1-1","requirement--soc2-tsc-2017-c1-2","requirement--soc2-tsc-2017-pi1-1","requirement--soc2-tsc-2017-pi1-2","requirement--soc2-tsc-2017-pi1-3","requirement--soc2-tsc-2017-pi1-4","requirement--soc2-tsc-2017-pi1-5","requirement--soc2-tsc-2017-p1-1","requirement--soc2-tsc-2017-p2-1","requirement--soc2-tsc-2017-p3-1","requirement--soc2-tsc-2017-p3-2","requirement--soc2-tsc-2017-p4-1","requirement--soc2-tsc-2017-p4-2","requirement--soc2-tsc-2017-p4-3","requirement--soc2-tsc-2017-p5-1","requirement--soc2-tsc-2017-p5-2","requirement--soc2-tsc-2017-p6-1","requirement--soc2-tsc-2017-p6-2","requirement--soc2-tsc-2017-p6-3","requirement--soc2-tsc-2017-p6-4","requirement--soc2-tsc-2017-p6-5","requirement--soc2-tsc-2017-p6-6","requirement--soc2-tsc-2017-p6-7","requirement--soc2-tsc-2017-p7-1","requirement--soc2-tsc-2017-p8-1"],"tags":["soc2","trust-services-criteria"],"yaml_path":"library/baseline/ogrl-soc2.yaml"}],"controls":[{"id":"control--ogrl-ac-01","slug":"ogrl-ac-01","display_id":"OGRL-AC-01","name":"Account Provisioning and Lifecycle Governance","family":"ac","control_type":"preventive","frequency":"event-driven","summary":"Require documented approval before provisioning user or service accounts and disable accounts promptly upon departure.\n","statement":"Approve every user and service account request through {{ approver_role }} prior to provisioning, and revoke or disable accounts within {{ deprovision_sla }} of personnel termination or role change.\n","objective":"Ensure only authorized personnel and services hold active accounts on in-scope systems.\n","guidance":"Integrate the identity provider with HR lifecycle events so terminations automatically trigger session revocation and account suspension within the defined SLA.\n","parameters":{"approver_role":{"label":"Account approval authority","value":"the system owner or manager"},"deprovision_sla":{"label":"Termination deprovisioning SLA","value":"24 hours"}},"tags":["identity","lifecycle","access-control"],"tests":[{"id":"test--ogrl-ac-01-lifecycle","slug":"ogrl-ac-01-lifecycle","name":"Verify Account Provisioning Approvals and Termination Revocation","method":"automated","interval":"daily","required":true,"description":"Confirm newly provisioned accounts have linked approval tickets and all terminated personnel accounts were disabled within the configured deprovisioning SLA.\n","objective_refs":["requirement--nist-sp-800-53-r5-ac-2#obj.e","requirement--nist-sp-800-53-r5-ac-2#obj.h.2"],"yaml_path":"library/test/ogrl-ac-01-lifecycle.yaml"}],"mappings":[{"id":"mapping--ogrl-ac-01-to-iso27001-a-5-16","source_ref":"control--ogrl-ac-01","target_ref":"requirement--iso-iec-27001-2022-a-5-16","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Approved identity provisioning and timely offboarding satisfy ISO/IEC 27001:2022 A.5.16.\n"},{"id":"mapping--ogrl-ac-01-to-800-171-03-01-01","source_ref":"control--ogrl-ac-01","target_ref":"requirement--nist-sp-800-171-r3-03-01-01","relationship":"subset-of","review_status":"reviewed","parameter_map":{"a_03_01_01_odp_01":"approver_role","a_03_01_01_odp_04":"deprovision_sla"},"summary":"Account provisioning approval and termination revocation contribute to SP 800-171 03.01.01 account management.\n"},{"id":"mapping--ogrl-ac-01-to-800-53-ac-2-e","source_ref":"control--ogrl-ac-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_odp_03":"approver_role"},"summary":"Pre-provisioning account approval directly satisfies NIST AC-2(e)."},{"id":"mapping--ogrl-ac-01-to-800-53-ac-2-h-2","source_ref":"control--ogrl-ac-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2#h.2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_odp_07":"deprovision_sla"},"summary":"Timely termination deprovisioning satisfies NIST AC-2(h.2) notification and suspension timing.\n"},{"id":"mapping--ogrl-ac-01-to-soc2-cc6-2","source_ref":"control--ogrl-ac-01","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Documented provisioning approval and prompt deprovisioning satisfy SOC 2 CC6.2."},{"id":"mapping--ogrl-ac-01-to-soc2-cc6-3","source_ref":"control--ogrl-ac-01","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Revoking or modifying access on termination and role change addresses the removal and modification aspects of CC6.3.\n"}],"yaml_path":"library/control/ogrl-ac-01.yaml"},{"id":"control--ogrl-ac-02","slug":"ogrl-ac-02","display_id":"OGRL-AC-02","name":"Periodic User Access Review","family":"ac","control_type":"detective","frequency":"quarterly","summary":"Review active user accounts and privileged group memberships on a defined cadence and revoke unapproved access.\n","statement":"Review all active user accounts, privileged roles, and service accounts {{ review_cadence }} and remediate unauthorized or unneeded entitlements within {{ remediation_window }}.\n","objective":"Detect and remove privilege creep, orphaned accounts, and stale entitlements before misuse.\n","guidance":"Generate account rosters directly from authoritative identity providers and production systems, require reviewer sign-off from managers or system owners, and retain ticketed removal evidence.\n","parameters":{"remediation_window":{"label":"Revocation remediation window","value":"5 business days"},"review_cadence":{"label":"Access review cadence","value":"at least quarterly"}},"tags":["access-review","governance","access-control"],"tests":[{"id":"test--ogrl-ac-02-access-review","slug":"ogrl-ac-02-access-review","name":"Verify Quarterly Access Review Completion","method":"manual","interval":"quarterly","required":true,"description":"Examine completed quarterly user access review records to confirm reviewer sign-off and timely removal of revoked entitlements.\n","objective_refs":["requirement--nist-sp-800-53-r5-ac-2#obj.j"],"yaml_path":"library/test/ogrl-ac-02-access-review.yaml"}],"mappings":[{"id":"mapping--ogrl-ac-02-to-iso27001-a-5-18","source_ref":"control--ogrl-ac-02","target_ref":"requirement--iso-iec-27001-2022-a-5-18","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Periodic user access reviews and revocation satisfy ISO/IEC 27001:2022 A.5.18."},{"id":"mapping--ogrl-ac-02-to-800-171-03-01-01","source_ref":"control--ogrl-ac-02","target_ref":"requirement--nist-sp-800-171-r3-03-01-01","relationship":"subset-of","review_status":"reviewed","parameter_map":{"a_03_01_01_odp_06":"review_cadence"},"summary":"Periodic user access reviews contribute to SP 800-171 03.01.01 account compliance reviews.\n"},{"id":"mapping--ogrl-ac-02-to-800-53-ac-2-j","source_ref":"control--ogrl-ac-02","target_ref":"requirement--nist-sp-800-53-r5-ac-2#j","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_odp_10":"review_cadence"},"summary":"Periodic user access review directly satisfies NIST AC-2(j) account compliance reviews.\n"},{"id":"mapping--ogrl-ac-02-to-soc2-cc6-2","source_ref":"control--ogrl-ac-02","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Periodic review confirms registered users remain authorized, supporting the credential lifecycle in CC6.2.\n"},{"id":"mapping--ogrl-ac-02-to-soc2-cc6-3","source_ref":"control--ogrl-ac-02","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Quarterly access reviews and timely entitlement removal satisfy SOC 2 CC6.3."}],"yaml_path":"library/control/ogrl-ac-02.yaml"},{"id":"control--ogrl-ac-03","slug":"ogrl-ac-03","display_id":"OGRL-AC-03","name":"Least Privilege and Role-Based Access Enforcement","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Enforce least-privilege role-based access control so users and services receive only permissions required for their job function.\n","statement":"Restrict logical access to systems, administrative interfaces, and sensitive data using role-based access control scoped to least privilege, requiring {{ privileged_elevation }} for administrative actions.\n","objective":"Limit blast radius by preventing unauthorized read, write, or administrative operations.\n","guidance":"Avoid standing administrative privileges on production environments; use scoped IAM roles, just-in-time elevation, and separation between developer and production-deployment permissions.\n","parameters":{"privileged_elevation":{"label":"Privileged elevation mechanism","value":"time-bound just-in-time elevation"}},"tags":["rbac","least-privilege","access-control"],"tests":[{"id":"test--ogrl-ac-03-least-privilege","slug":"ogrl-ac-03-least-privilege","name":"Verify Least-Privilege Role Assignments","method":"automated","interval":"daily","required":true,"description":"Check IAM role bindings and administrative group memberships to verify no unauthorized wildcard permissions or standing administrative privileges exist.\n","objective_refs":[],"yaml_path":"library/test/ogrl-ac-03-least-privilege.yaml"}],"mappings":[{"id":"mapping--ogrl-ac-03-to-iso27001-a-5-15","source_ref":"control--ogrl-ac-03","target_ref":"requirement--iso-iec-27001-2022-a-5-15","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege RBAC policies directly satisfy ISO/IEC 27001:2022 A.5.15."},{"id":"mapping--ogrl-ac-03-to-800-171-03-01-05","source_ref":"control--ogrl-ac-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-05","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege role enforcement directly satisfies SP 800-171 03.01.05."},{"id":"mapping--ogrl-ac-03-to-800-53-ac-3","source_ref":"control--ogrl-ac-03","target_ref":"requirement--nist-sp-800-53-r5-ac-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Role-based access control enforces approved logical access authorizations per AC-3.\n"},{"id":"mapping--ogrl-ac-03-to-800-53-ac-6","source_ref":"control--ogrl-ac-03","target_ref":"requirement--nist-sp-800-53-r5-ac-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege role scoping and just-in-time elevation satisfy NIST AC-6."},{"id":"mapping--ogrl-ac-03-to-soc2-cc6-1","source_ref":"control--ogrl-ac-03","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege RBAC and access enforcement satisfy SOC 2 CC6.1 logical access security.\n"},{"id":"mapping--ogrl-ac-03-to-soc2-cc6-3","source_ref":"control--ogrl-ac-03","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Role-based least privilege governs how access is granted and modified under CC6.3.\n"}],"yaml_path":"library/control/ogrl-ac-03.yaml"},{"id":"control--ogrl-ac-04","slug":"ogrl-ac-04","display_id":"OGRL-AC-04","name":"Network Boundary and Logical Access Restriction","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Segment network boundaries with default-deny ingress controls and restrict administrative ports from the public internet.\n","statement":"Enforce default-deny network ingress policies at system boundaries, allowing only explicitly documented service ports and restricting administrative access to {{ admin_access_path }}.\n","objective":"Prevent unauthorized network traffic and direct internet exposure of internal or administrative services.\n","guidance":"Manage security groups, firewall rules, and private network peering via infrastructure-as-code with automated drift detection.\n","parameters":{"admin_access_path":{"label":"Authorized administrative network path","value":"authenticated VPN or zero-trust bastion endpoints"}},"tags":["network","segmentation","access-control"],"tests":[{"id":"test--ogrl-ac-04-network-boundary","slug":"ogrl-ac-04-network-boundary","name":"Verify Default-Deny Network Ingress Policies","method":"automated","interval":"daily","required":true,"description":"Inspect cloud security groups and firewall rules to confirm administrative ports (SSH, RDP, database ports) are not exposed to 0.0.0.0/0.\n","objective_refs":[],"yaml_path":"library/test/ogrl-ac-04-network-boundary.yaml"}],"mappings":[{"id":"mapping--ogrl-ac-04-to-soc2-cc6-1","source_ref":"control--ogrl-ac-04","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Default-deny network restrictions form part of the logical access security architecture in CC6.1.\n"},{"id":"mapping--ogrl-ac-04-to-soc2-cc6-6","source_ref":"control--ogrl-ac-04","target_ref":"requirement--soc2-tsc-2017-cc6-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Default-deny network boundaries and restricted admin paths satisfy SOC 2 CC6.6."}],"yaml_path":"library/control/ogrl-ac-04.yaml"},{"id":"control--ogrl-ac-05","slug":"ogrl-ac-05","display_id":"OGRL-AC-05","name":"Multi-Factor Authentication Enforcement","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Require phishing-resistant or hardware-backed multi-factor authentication for all interactive user and privileged logins.\n","statement":"Enforce {{ mfa_standard }} multi-factor authentication on all interactive workforce, remote, and privileged accounts across identity providers and in-scope systems.\n","objective":"Prevent account compromise from stolen, reused, or phished single-factor credentials.\n","guidance":"Prefer FIDO2/WebAuthn security keys or platform authenticators for privileged accounts, and block legacy single-factor protocols.\n","parameters":{"mfa_standard":{"label":"Required MFA factor strength","value":"phishing-resistant (FIDO2/WebAuthn or TOTP)"}},"tags":["mfa","authentication","identity"],"tests":[{"id":"test--ogrl-ac-05-mfa-enforcement","slug":"ogrl-ac-05-mfa-enforcement","name":"Verify MFA Enforcement on All Active Accounts","method":"automated","interval":"daily","required":true,"description":"Query the identity provider and cloud IAM directories to confirm MFA is enrolled and enforced for 100% of active interactive accounts.\n","objective_refs":[],"yaml_path":"library/test/ogrl-ac-05-mfa-enforcement.yaml"}],"mappings":[{"id":"mapping--ogrl-ac-05-to-iso27001-a-8-5","source_ref":"control--ogrl-ac-05","target_ref":"requirement--iso-iec-27001-2022-a-8-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Phishing-resistant MFA enforcement satisfies ISO/IEC 27001:2022 A.8.5 secure authentication.\n"},{"id":"mapping--ogrl-ac-05-to-800-171-03-05-03","source_ref":"control--ogrl-ac-05","target_ref":"requirement--nist-sp-800-171-r3-03-05-03","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"MFA enforcement across interactive and privileged logins satisfies SP 800-171 03.05.03.\n"},{"id":"mapping--ogrl-ac-05-to-800-53-ia-2","source_ref":"control--ogrl-ac-05","target_ref":"requirement--nist-sp-800-53-r5-ia-2","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Universal MFA enforcement satisfies and strengthens organizational user authentication under IA-2.\n"},{"id":"mapping--ogrl-ac-05-to-soc2-cc6-1","source_ref":"control--ogrl-ac-05","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Universal MFA strengthens authentication required by SOC 2 CC6.1."}],"yaml_path":"library/control/ogrl-ac-05.yaml"},{"id":"control--ogrl-ac-06","slug":"ogrl-ac-06","display_id":"OGRL-AC-06","name":"Secret and Authenticator Lifecycle Management","family":"ac","control_type":"preventive","frequency":"quarterly","summary":"Store secrets in managed vaults, prohibit hardcoded credentials, and rotate keys on a defined cadence or upon compromise.\n","statement":"Manage passwords, API keys, and cryptographic credentials in an approved secrets vault, rotate non-ephemeral credentials at least every {{ rotation_period }}, and revoke immediately upon {{ revocation_triggers }}.\n","objective":"Protect authenticators from unauthorized disclosure and limit exposure windows if leaked.\n","guidance":"Prefer short-lived workload identities (OIDC/IAM roles) over static API keys, run secret scanning on source repositories, and replace default credentials prior to deployment.\n","parameters":{"revocation_triggers":{"label":"Immediate revocation events","value":"suspected exposure, personnel departure, or system decommission"},"rotation_period":{"label":"Maximum static credential lifetime","value":"90 days"}},"tags":["secrets","credentials","authentication"],"tests":[{"id":"test--ogrl-ac-06-secret-hygiene","slug":"ogrl-ac-06-secret-hygiene","name":"Verify Secret Vaulting and Credential Rotation Age","method":"automated","interval":"weekly","required":true,"description":"Confirm static API keys and service credentials do not exceed the configured rotation age and repository secret scanning reports zero unresolved leaks.\n","objective_refs":["requirement--nist-sp-800-53-r5-ia-5#obj.f","requirement--nist-sp-800-53-r5-ia-5#obj.g"],"yaml_path":"library/test/ogrl-ac-06-secret-hygiene.yaml"}],"mappings":[{"id":"mapping--ogrl-ac-06-to-iso27001-a-5-17","source_ref":"control--ogrl-ac-06","target_ref":"requirement--iso-iec-27001-2022-a-5-17","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Vaulted secret storage and rotation governance satisfy ISO/IEC 27001:2022 A.5.17.\n"},{"id":"mapping--ogrl-ac-06-to-800-53-ia-5-f","source_ref":"control--ogrl-ac-06","target_ref":"requirement--nist-sp-800-53-r5-ia-5#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ia_05_odp_01":"rotation_period","ia_05_odp_02":"revocation_triggers"},"summary":"Scheduled credential rotation and event-driven revocation directly satisfy NIST IA-5(f).\n"},{"id":"mapping--ogrl-ac-06-to-soc2-cc6-1","source_ref":"control--ogrl-ac-06","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Protecting secrets and credentials is part of the logical access safeguards in CC6.1.\n"}],"yaml_path":"library/control/ogrl-ac-06.yaml"},{"id":"control--ogrl-ac-07","slug":"ogrl-ac-07","display_id":"OGRL-AC-07","name":"Privileged Access Management","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Limit administrative access to an approved roster, separate it from everyday accounts, alert on changes, and reconcile it regularly.\n","statement":"Maintain an approved roster of individuals authorized to hold administrative access to {{ privileged_scope }}, limited to {{ privileged_roles }}; require those individuals to use dedicated privileged accounts or elevated roles that are not used for email, browsing, or other routine work; alert {{ privileged_alert_recipient }} on every grant of a privileged role and every change to a privileged role definition; and reconcile actual privileged assignments against the roster {{ privileged_review_frequency }}, removing any that are not approved.\n","objective":"Keep the set of people who can alter security configurations, production systems, or audit data small, known, and monitored.\n","guidance":"Define privileged roles in the identity provider and cloud IAM and treat cloud root, organization admin, IdP super-admin, database superuser, and security tooling admin as in scope. Use separate admin identities or just-in-time role elevation (see OGRL-AC-03) instead of permanently privileged daily accounts. Stream IAM and IdP role-change events to the SIEM for alerting, and export privileged group membership for the reconciliation. Break-glass accounts belong on the roster with sealed credentials and alerting on use.\n","parameters":{"privileged_alert_recipient":{"label":"Recipient of privileged change alerts","value":"the security team"},"privileged_review_frequency":{"label":"Privileged roster reconciliation frequency","value":"monthly"},"privileged_roles":{"label":"Personnel eligible for privileged access","value":"named members of the infrastructure and security teams"},"privileged_scope":{"label":"Systems and functions treated as privileged","value":"cloud provider organizations, identity provider administration, production databases, and security tooling\n"}},"tags":["privileged-access","least-privilege","access-control"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-07-to-800-53-ac-2-7","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-2-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Role-based privileged accounts, alerting on privileged assignments and role changes, and removal of unapproved privileges cover AC-2(7).\n"},{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-1","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_01_odp_01":"privileged_roles"},"summary":"The approved roster explicitly authorizes which individuals may access security functions and security-relevant systems.\n"},{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-2","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_02_odp":"privileged_scope"},"summary":"Dedicated privileged accounts or elevated roles are not used for routine, non-security work.\n"},{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-5","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_05_odp":"privileged_roles"},"summary":"Privileged accounts are restricted to the defined set of eligible personnel.\n"},{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-7","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_07_odp_01":"privileged_review_frequency","ac_06_07_odp_02":"privileged_roles"},"summary":"Periodic reconciliation of privileged assignments validates need and removes unapproved privileges; non-privileged access review is in OGRL-AC-02.\n"},{"id":"mapping--ogrl-ac-07-to-soc2-cc6-1","source_ref":"control--ogrl-ac-07","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Restricting and monitoring administrative access contributes to logical access protection under CC6.1.\n"},{"id":"mapping--ogrl-ac-07-to-soc2-cc6-3","source_ref":"control--ogrl-ac-07","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Limiting privileged roles to approved individuals applies least privilege to the most sensitive access under CC6.3.\n"}],"yaml_path":"library/control/ogrl-ac-07.yaml"},{"id":"control--ogrl-ac-08","slug":"ogrl-ac-08","display_id":"OGRL-AC-08","name":"Separation of Duties","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Document conflicting duties and configure access so no single person can complete a conflicting pair alone.\n","statement":"Document the duties that must be separated, including at minimum {{ separated_duties }}, configure system access so that no single individual can perform both duties in a conflicting pair without independent approval, and record any approved exception together with its compensating control.\n","objective":"Prevent a single individual from introducing and concealing unauthorized or erroneous changes.\n","guidance":"Enforce separation technically where possible: branch protection requiring a reviewer other than the author, access-request workflows that block self-approval, and audit log storage that system administrators cannot modify. Small teams that cannot fully separate duties should document compensating detective controls such as after-the-fact review of administrator activity.\n","parameters":{"separated_duties":{"label":"Duties that must be separated","value":"authoring and approving production code changes, requesting and approving access grants, and administering systems and reviewing their audit logs\n"}},"tags":["separation-of-duties","access-control","governance"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-08-to-800-53-ac-5","source_ref":"control--ogrl-ac-08","target_ref":"requirement--nist-sp-800-53-r5-ac-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_05_odp":"separated_duties"},"summary":"Documenting separated duties and configuring access authorizations to enforce them satisfies both parts of AC-5.\n"},{"id":"mapping--ogrl-ac-08-to-soc2-cc5-1","source_ref":"control--ogrl-ac-08","target_ref":"requirement--soc2-tsc-2017-cc5-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Segregating incompatible duties is a control activity that mitigates risk under CC5.1.\n"},{"id":"mapping--ogrl-ac-08-to-soc2-cc6-3","source_ref":"control--ogrl-ac-08","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Separation of duties is a consideration when authorizing and modifying role-based access under CC6.3.\n"}],"yaml_path":"library/control/ogrl-ac-08.yaml"},{"id":"control--ogrl-ac-09","slug":"ogrl-ac-09","display_id":"OGRL-AC-09","name":"Inactive and Temporary Account Disablement","family":"ac","control_type":"preventive","frequency":"daily","summary":"Automatically disable dormant, expired, orphaned, and temporary accounts.\n","statement":"Automatically disable user accounts that have been inactive for {{ inactivity_period }}; disable accounts that have expired, are no longer associated with an active individual, or violate policy within {{ disable_window }} of detection; and configure temporary and emergency accounts to be {{ temporary_account_action }} automatically after {{ temporary_account_lifetime }}.\n","objective":"Eliminate dormant and leftover accounts that could be used for unauthorized access.\n","guidance":"Use identity provider inactivity policies or a scheduled job that compares last-login data from the IdP and directly-managed systems against the threshold. Set expiration dates on contractor, vendor-support, and break-glass accounts at creation. Service accounts are excluded from the inactivity rule but must have an owner and appear in access reviews (OGRL-AC-02).\n","parameters":{"disable_window":{"label":"Time to disable expired, orphaned, or non-compliant accounts","value":"24 hours"},"inactivity_period":{"label":"Inactivity threshold","value":"90 days"},"temporary_account_action":{"label":"Automatic action for temporary accounts","value":"disabled or removed"},"temporary_account_lifetime":{"label":"Maximum temporary or emergency account lifetime","value":"the approved expiration date, not to exceed 30 days"}},"tags":["account-management","lifecycle","access-control"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-09-to-800-53-ac-2-2","source_ref":"control--ogrl-ac-09","target_ref":"requirement--nist-sp-800-53-r5-ac-2-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_02_odp_01":"temporary_account_action","ac_02_02_odp_02":"temporary_account_lifetime"},"summary":"Temporary and emergency accounts are automatically disabled or removed after a defined period.\n"},{"id":"mapping--ogrl-ac-09-to-800-53-ac-2-3","source_ref":"control--ogrl-ac-09","target_ref":"requirement--nist-sp-800-53-r5-ac-2-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_03_odp_01":"disable_window","ac_02_03_odp_02":"inactivity_period"},"summary":"Disabling expired, orphaned, non-compliant, and inactive accounts within a defined window covers all of AC-2(3).\n"},{"id":"mapping--ogrl-ac-09-to-soc2-cc6-2","source_ref":"control--ogrl-ac-09","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Removing dormant and temporary accounts supports deregistration of users who no longer need access under CC6.2.\n"}],"yaml_path":"library/control/ogrl-ac-09.yaml"},{"id":"control--ogrl-ac-10","slug":"ogrl-ac-10","display_id":"OGRL-AC-10","name":"Session Lock and Termination","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Lock idle workstations and terminate idle or long-lived sessions to in-scope systems.\n","statement":"Configure workforce endpoints to lock the screen after {{ device_lock_timeout }} of inactivity, requiring re-authentication to unlock, and configure in-scope applications, administrative consoles, and remote access sessions to terminate after {{ session_termination_conditions }}.\n","objective":"Prevent unattended or hijacked sessions from being used to access systems and data.\n","guidance":"Enforce screen lock through MDM configuration profiles and session lifetimes through identity provider and cloud console session policies. Apply shorter timeouts to production and administrative access than to collaboration tools. Evidence is typically the MDM profile, IdP session policy, and cloud console session settings.\n","parameters":{"device_lock_timeout":{"label":"Endpoint inactivity lock timeout","value":"15 minutes"},"session_termination_conditions":{"label":"Session termination conditions","value":"30 minutes of inactivity or 12 hours of total session duration"}},"tags":["session-management","endpoint","access-control"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-10-to-800-53-ac-11","source_ref":"control--ogrl-ac-10","target_ref":"requirement--nist-sp-800-53-r5-ac-11","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_11_odp_02":"device_lock_timeout"},"summary":"Inactivity-based screen lock that persists until re-authentication satisfies AC-11.\n"},{"id":"mapping--ogrl-ac-10-to-800-53-ac-12","source_ref":"control--ogrl-ac-10","target_ref":"requirement--nist-sp-800-53-r5-ac-12","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_12_odp":"session_termination_conditions"},"summary":"Sessions to in-scope systems are automatically terminated under defined conditions.\n"},{"id":"mapping--ogrl-ac-10-to-soc2-cc6-1","source_ref":"control--ogrl-ac-10","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Session lock and termination is one logical access safeguard within CC6.1.\n"}],"yaml_path":"library/control/ogrl-ac-10.yaml"},{"id":"control--ogrl-ac-11","slug":"ogrl-ac-11","display_id":"OGRL-AC-11","name":"Remote Access Security","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Document and authorize each remote access method and route production remote access through an approved, authenticated gateway.\n","statement":"Document each permitted remote access method to in-scope systems with its usage restrictions and configuration requirements, authorize each method before it is enabled, and require all remote access to production environments to pass through {{ remote_access_gateway }} that enforces single sign-on with multi-factor authentication, encrypted transport, and session logging; review the permitted methods {{ remote_access_review_frequency }}.\n","objective":"Ensure remote connections to production are made only through known, approved, and monitored paths.\n","guidance":"For cloud SaaS, remote access usually means administrative paths into production: cloud consoles and CLIs, SSH or database sessions via a bastion or identity-aware proxy, and Kubernetes API access. Prefer identity-aware proxies or SSM-style session managers over static SSH keys and public bastions. Network-level exposure restrictions are covered by OGRL-AC-04.\n","parameters":{"remote_access_gateway":{"label":"Approved remote access gateway","value":"an approved identity-aware proxy, session manager, or VPN"},"remote_access_review_frequency":{"label":"Remote access method review frequency","value":"annually"}},"tags":["remote-access","network","access-control"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-11-to-800-53-ac-17","source_ref":"control--ogrl-ac-11","target_ref":"requirement--nist-sp-800-53-r5-ac-17","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Documented restrictions and configuration requirements per remote access type, with authorization before enablement, satisfy AC-17.\n"},{"id":"mapping--ogrl-ac-11-to-soc2-cc6-1","source_ref":"control--ogrl-ac-11","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Authenticated, logged remote access gateways contribute to logical access security under CC6.1.\n"},{"id":"mapping--ogrl-ac-11-to-soc2-cc6-6","source_ref":"control--ogrl-ac-11","target_ref":"requirement--soc2-tsc-2017-cc6-6","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Controlling remote access paths into production protects against threats from outside system boundaries under CC6.6.\n"}],"yaml_path":"library/control/ogrl-ac-11.yaml"},{"id":"control--ogrl-ac-12","slug":"ogrl-ac-12","display_id":"OGRL-AC-12","name":"Information Flow Enforcement and Tenant Data Segregation","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Scope every data path to the requesting customer's tenant and test isolation on each release.\n","statement":"Enforce tenant isolation in every data path of the service so that each request, query, background job, and export is constrained to the authenticated customer's tenant at {{ isolation_enforcement_layer }}, and run automated cross-tenant access tests {{ isolation_test_trigger }}.\n","objective":"Prevent one customer's data from flowing to, or being accessed by, another customer.\n","guidance":"Enforce tenancy in a shared layer rather than in each handler: row-level security, tenant-scoped repository or ORM helpers, per-tenant encryption keys, or per-tenant databases. Derive the tenant from the authenticated session, never from client-supplied parameters alone. Include cross-tenant negative tests in CI and in periodic penetration tests.\n","parameters":{"isolation_enforcement_layer":{"label":"Layer where tenant isolation is enforced","value":"the data access layer through row-level security or mandatory tenant-scoped queries\n"},"isolation_test_trigger":{"label":"When cross-tenant isolation tests run","value":"on every release to production"}},"tags":["multi-tenancy","data-segregation","access-control"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-12-to-800-53-ac-4","source_ref":"control--ogrl-ac-12","target_ref":"requirement--nist-sp-800-53-r5-ac-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Tenant isolation enforces one information flow policy within the system; network and inter-system flow controls are outside this control.\n"},{"id":"mapping--ogrl-ac-12-to-soc2-c1-1","source_ref":"control--ogrl-ac-12","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Preventing cross-tenant exposure helps protect customers' confidential information under C1.1.\n"},{"id":"mapping--ogrl-ac-12-to-soc2-cc6-1","source_ref":"control--ogrl-ac-12","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Segregating customer data at the application layer is a logical access protection within CC6.1.\n"}],"yaml_path":"library/control/ogrl-ac-12.yaml"},{"id":"control--ogrl-ac-13","slug":"ogrl-ac-13","display_id":"OGRL-AC-13","name":"Unique Identification and Centralized SSO","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Give every workforce member one unique identity in a central identity provider and use it to sign in to in-scope systems.\n","statement":"Assign each workforce member a unique identifier in {{ identity_provider }}, authenticate access to in-scope systems through single sign-on from that provider wherever the system supports it, prohibit shared or generic user identifiers other than inventoried service and break-glass accounts, and do not reassign a retired identifier for {{ identifier_reuse_period }}.\n","objective":"Make every action on in-scope systems attributable to one individual and manageable from one place.\n","guidance":"Connect SaaS and cloud consoles to the IdP via SAML or OIDC and provision via SCIM where available. Maintain an inventory of in-scope systems that cannot use SSO, with compensating local account management. Do not recycle email addresses or usernames of departed personnel. MFA requirements are in OGRL-AC-05; account approval is in OGRL-AC-01.\n","parameters":{"identifier_reuse_period":{"label":"Minimum period before an identifier may be reused","value":"at least two years"},"identity_provider":{"label":"Central workforce identity provider","value":"the organization's designated workforce identity provider"}},"tags":["identity","sso","authentication"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-13-to-800-53-ia-2","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Unique workforce identities authenticated through central SSO provide unique identification and authentication of organizational users.\n"},{"id":"mapping--ogrl-ac-13-to-800-53-ia-4-b","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-4#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Each identifier is selected to identify one specific individual.\n"},{"id":"mapping--ogrl-ac-13-to-800-53-ia-4-c","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-4#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Each unique identifier is assigned to the intended individual in the central identity provider.\n"},{"id":"mapping--ogrl-ac-13-to-800-53-ia-4-d","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-4#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ia_04_odp_02":"identifier_reuse_period"},"summary":"Retired identifiers are not reused for a defined period.\n"},{"id":"mapping--ogrl-ac-13-to-soc2-cc6-1","source_ref":"control--ogrl-ac-13","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Unique identities and centralized authentication are foundational logical access measures under CC6.1.\n"},{"id":"mapping--ogrl-ac-13-to-soc2-cc6-2","source_ref":"control--ogrl-ac-13","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Central identity registration supports the user registration aspect of CC6.2; authorization and removal are other controls.\n"}],"yaml_path":"library/control/ogrl-ac-13.yaml"},{"id":"control--ogrl-ac-14","slug":"ogrl-ac-14","display_id":"OGRL-AC-14","name":"Authenticator Strength and Lockout","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Enforce modern password requirements and lock out repeated failed sign-in attempts on every system that accepts passwords.\n","statement":"Configure every in-scope system that accepts passwords, including the identity provider and customer-facing sign-in, to enforce {{ password_composition_rules }}, permit passphrases of at least 64 characters, reject passwords found on a list of breached or commonly used values that is updated {{ blocklist_update_frequency }}, transmit passwords only over encrypted channels, store them only with a salted adaptive key derivation function, require a new password after account recovery, and lock the account or impose increasing delays after {{ max_failed_attempts }} consecutive failed attempts within {{ failed_attempt_window }}.\n","objective":"Resist credential guessing, stuffing, and offline cracking attacks against password-based authentication.\n","guidance":"Follow NIST SP 800-63B: favor length and breached-password screening over composition rules and periodic forced rotation. Use a breached-password service (for example k-anonymity range queries) at creation and change. Use bcrypt, scrypt, or Argon2id for storage. Apply lockout or rate limiting per account and per source to blunt credential stuffing without enabling easy denial of service.\n","parameters":{"blocklist_update_frequency":{"label":"Breached-password list update frequency","value":"at least monthly"},"failed_attempt_window":{"label":"Failed-attempt counting window","value":"15 minutes"},"max_failed_attempts":{"label":"Consecutive failed attempts before lockout","value":"10"},"password_composition_rules":{"label":"Password composition rules","value":"a minimum length of 12 characters without arbitrary character-class requirements"}},"tags":["authentication","passwords","brute-force"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-14-to-800-53-ac-7","source_ref":"control--ogrl-ac-14","target_ref":"requirement--nist-sp-800-53-r5-ac-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_07_odp_01":"max_failed_attempts","ac_07_odp_02":"failed_attempt_window"},"summary":"A limit on consecutive failed attempts within a window with automatic lockout or delay satisfies AC-7.\n"},{"id":"mapping--ogrl-ac-14-to-800-53-ia-5-1","source_ref":"control--ogrl-ac-14","target_ref":"requirement--nist-sp-800-53-r5-ia-5-1","relationship":"subset-of","review_status":"reviewed","parameter_map":{"ia_05_01_odp_01":"blocklist_update_frequency","ia_05_01_odp_02":"password_composition_rules"},"summary":"Covers blocklist maintenance and checking, protected transmission and storage, reset on recovery, long passphrases, and composition rules; automated strength-assistance tooling is not required.\n"},{"id":"mapping--ogrl-ac-14-to-soc2-cc6-1","source_ref":"control--ogrl-ac-14","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Password strength and lockout settings are authentication safeguards within CC6.1.\n"}],"yaml_path":"library/control/ogrl-ac-14.yaml"},{"id":"control--ogrl-ac-15","slug":"ogrl-ac-15","display_id":"OGRL-AC-15","name":"Customer Authentication","family":"ac","control_type":"preventive","frequency":"continuous","summary":"Authenticate every customer user uniquely and offer strong authentication options in the product.\n","statement":"Require every customer user of the service to authenticate with an individual account, offer {{ customer_mfa_options }} to all customer users and SAML or OIDC single sign-on to {{ sso_eligible_customers }}, verify the requester through a previously registered channel before completing account recovery, and invalidate active sessions on logout, password change, and account recovery.\n","objective":"Ensure only the intended customer users can access customer accounts and data in the service.\n","guidance":"Use a mature authentication library or customer identity platform rather than custom code. Allow customer administrators to enforce MFA or SSO for their organization. Issue short-lived, server-revocable session tokens. API keys issued to customers should be scoped, revocable, and attributable to a customer account.\n","parameters":{"customer_mfa_options":{"label":"MFA options offered to customers","value":"TOTP authenticator apps and WebAuthn passkeys"},"sso_eligible_customers":{"label":"Customers offered SSO","value":"all business-tier customers"}},"tags":["authentication","customer-identity","mfa"],"tests":[],"mappings":[{"id":"mapping--ogrl-ac-15-to-800-53-ia-8","source_ref":"control--ogrl-ac-15","target_ref":"requirement--nist-sp-800-53-r5-ia-8","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Individual customer accounts uniquely identify and authenticate non-organizational users, with added MFA, SSO, and recovery safeguards.\n"},{"id":"mapping--ogrl-ac-15-to-soc2-cc6-1","source_ref":"control--ogrl-ac-15","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Customer authentication safeguards protect the service's logical access boundary under CC6.1.\n"}],"yaml_path":"library/control/ogrl-ac-15.yaml"},{"id":"control--ogrl-am-01","slug":"ogrl-am-01","display_id":"OGRL-AM-01","name":"System Component Inventory","family":"am","control_type":"detective","frequency":"continuous","summary":"Maintain an accurate, owner-assigned inventory of in-scope system components, generated automatically where possible.\n","statement":"Maintain an inventory of in-scope system components, including cloud accounts, compute, data stores, network entry points, workforce endpoints, and production SaaS services, that records {{ inventory_attributes }} for each component and assigns each component to exactly one system and environment. Populate the inventory from provider APIs and device management where available, and reconcile it against those sources {{ inventory_review_frequency }}.\n","objective":"Every component in scope is known, owned, and accounted for once, so that it can be secured, monitored, and assessed.\n","guidance":"Use cloud provider resource inventories, infrastructure-as-code state, MDM enrollment, and the SaaS management or SSO catalog as sources. Required tags (owner, environment, data classification) enforced by policy keep the inventory accurate. Reconciliation means investigating untagged or unknown resources and unenrolled devices. Evidence: an inventory export and reconciliation records.\n","parameters":{"inventory_attributes":{"label":"Inventory attributes","value":"unique identifier, type, owner, environment, location or region, and data classification\n"},"inventory_review_frequency":{"label":"Inventory reconciliation frequency","value":"at least quarterly"}},"tags":["asset-management","inventory"],"tests":[],"mappings":[{"id":"mapping--ogrl-am-01-to-800-53-cm-8","source_ref":"control--ogrl-am-01","target_ref":"requirement--nist-sp-800-53-r5-cm-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_08_odp_01":"inventory_attributes","cm_08_odp_02":"inventory_review_frequency"},"summary":"An accurate, non-duplicated inventory with defined attributes, reconciled on a fixed cadence, covers both parts of the requirement.\n"},{"id":"mapping--ogrl-am-01-to-soc2-cc3-2","source_ref":"control--ogrl-am-01","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The inventory identifies the assets whose risks are assessed."},{"id":"mapping--ogrl-am-01-to-soc2-cc6-1","source_ref":"control--ogrl-am-01","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Knowing which components exist is a precondition for applying logical access protections to them.\n"}],"yaml_path":"library/control/ogrl-am-01.yaml"},{"id":"control--ogrl-am-02","slug":"ogrl-am-02","display_id":"OGRL-AM-02","name":"Data Classification","family":"am","control_type":"preventive","frequency":"annual","summary":"Classify data by sensitivity under a defined scheme with handling rules, and record the classification of each data store.\n","statement":"Maintain a data classification scheme defining {{ classification_levels }} and the handling requirements for each level, including storage, sharing, encryption, and retention. Record the classification of each in-scope data store in the component inventory, have {{ classification_approver }} approve classifications, and review the scheme and recorded classifications {{ classification_review_frequency }}.\n","objective":"Confidential and customer data can be located and is handled according to its sensitivity.\n","guidance":"Three or four levels are typical, such as public, internal, confidential, and restricted, with customer data classified confidential or higher. Tag cloud data stores and buckets with their level so automated checks can enforce encryption and access rules. Evidence: the scheme, the inventory showing classifications, and the review record.\n","parameters":{"classification_approver":{"label":"Classification approver","value":"the data owner"},"classification_levels":{"label":"Classification levels","value":"public, internal, confidential, and restricted"},"classification_review_frequency":{"label":"Classification review frequency","value":"at least annually"}},"tags":["asset-management","data-classification","confidentiality"],"tests":[],"mappings":[{"id":"mapping--ogrl-am-02-to-800-53-ra-2","source_ref":"control--ogrl-am-02","target_ref":"requirement--nist-sp-800-53-r5-ra-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Classifying information and data stores overlaps with system and information categorization; impact-level categorization and authorizing official approval are not provided.\n"},{"id":"mapping--ogrl-am-02-to-soc2-c1-1","source_ref":"control--ogrl-am-02","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Classification identifies confidential information so it can be protected."},{"id":"mapping--ogrl-am-02-to-soc2-cc6-1","source_ref":"control--ogrl-am-02","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Classification informs which protections apply to each data store."}],"yaml_path":"library/control/ogrl-am-02.yaml"},{"id":"control--ogrl-bc-01","slug":"ogrl-bc-01","display_id":"OGRL-BC-01","name":"Business Continuity and Disaster Recovery Plan","family":"bc","control_type":"corrective","frequency":"annual","summary":"Maintain an approved business continuity and disaster recovery plan that defines recovery objectives, priorities, roles, and procedures, and keep it current.\n","statement":"Maintain a documented business continuity and disaster recovery plan, approved by {{ plan_approver }}, that identifies critical services with their recovery time and recovery point objectives, recovery priorities, contingency roles with current contact information, and procedures for continuing operations during a disruption and fully restoring systems afterward; review and update the plan {{ plan_review_cadence }} and after significant changes or tests, and communicate changes to {{ plan_recipients }}.\n","objective":"Ensure the organization can sustain critical services and restore systems to normal operation within committed timeframes after a disruption.\n","guidance":"Cover cloud-relevant scenarios such as availability zone and region outages, cloud account compromise or ransomware, loss of a critical SaaS dependency (identity provider, code hosting, payment processor), and loss of key personnel. Derive recovery objectives from the business impact analysis (OGRL-BC-07) and customer SLAs. Keep a copy accessible outside the primary environment in case SSO or the main workspace is unavailable, and restrict edit access. Align with the incident response plan (OGRL-IR-01) and fold in lessons from plan tests (OGRL-BC-02).\n","parameters":{"plan_approver":{"label":"Plan approval authority","value":"executive leadership"},"plan_recipients":{"label":"Recipients of plan changes","value":"key contingency personnel and critical service owners"},"plan_review_cadence":{"label":"Plan review frequency","value":"at least annually"}},"tags":["business-continuity","disaster-recovery","resilience"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-a","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#a","relationship":"subset-of","review_status":"reviewed","parameter_map":{"cp_2_prm_1":"plan_approver"},"summary":"The plan identifies critical functions, recovery objectives and priorities, roles, continuity and restoration procedures, and approval, but does not address sharing of contingency information.\n"},{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-d","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_02_odp_05":"plan_review_cadence"},"summary":"Periodic plan review satisfies CP-2(d)."},{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-e","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Updating the plan after significant changes and tests satisfies CP-2(e)."},{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-f","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_2_prm_4":"plan_recipients"},"summary":"Communicating plan changes to key contingency personnel satisfies CP-2(f)."},{"id":"mapping--ogrl-bc-01-to-soc2-a1-2","source_ref":"control--ogrl-bc-01","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The plan defines the recovery objectives and procedures that recovery infrastructure is designed to meet.\n"},{"id":"mapping--ogrl-bc-01-to-soc2-cc7-5","source_ref":"control--ogrl-bc-01","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented recovery procedures and priorities guide restoration after incidents."},{"id":"mapping--ogrl-bc-01-to-soc2-cc9-1","source_ref":"control--ogrl-bc-01","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A continuity plan is a primary risk mitigation activity for potential business disruptions.\n"}],"yaml_path":"library/control/ogrl-bc-01.yaml"},{"id":"control--ogrl-bc-02","slug":"ogrl-bc-02","display_id":"OGRL-BC-02","name":"Continuity and Recovery Plan Testing","family":"bc","control_type":"detective","frequency":"annual","summary":"Exercise the business continuity and disaster recovery plan on a schedule, review results against recovery objectives, and remediate gaps.\n","statement":"Test the business continuity and disaster recovery plan {{ dr_test_cadence }} using {{ dr_test_methods }}, document results against recovery time and recovery point objectives, have results reviewed by {{ dr_test_reviewer }}, and track identified gaps to remediation.\n","objective":"Demonstrate that recovery procedures work and objectives are achievable, and correct weaknesses before a real disruption.\n","guidance":"Combine a tabletop walkthrough with a technical exercise such as promoting a database replica in another region or rebuilding an environment from infrastructure as code into a clean account. Measure actual recovery time and data loss and compare them with stated objectives. Tests may share a session with incident response tabletops (OGRL-IR-01) but keep separate results records. Feed findings back into the plan (OGRL-BC-01).\n","parameters":{"dr_test_cadence":{"label":"Plan test frequency","value":"at least annually"},"dr_test_methods":{"label":"Plan test methods","value":"a tabletop walkthrough and a technical failover or restoration exercise for at least one critical service\n"},"dr_test_reviewer":{"label":"Test results reviewer","value":"the business continuity plan owner"}},"tags":["business-continuity","disaster-recovery","testing"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-02-to-800-53-cp-4","source_ref":"control--ogrl-bc-02","target_ref":"requirement--nist-sp-800-53-r5-cp-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_04_odp_01":"dr_test_cadence","cp_4_prm_2":"dr_test_methods"},"summary":"Scheduled plan testing with defined methods, results review, and gap remediation satisfies CP-4 in full.\n"},{"id":"mapping--ogrl-bc-02-to-soc2-a1-3","source_ref":"control--ogrl-bc-02","target_ref":"requirement--soc2-tsc-2017-a1-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Exercising the continuity and recovery plan is the plan-level portion of recovery testing; backup restoration testing is a separate control.\n"}],"yaml_path":"library/control/ogrl-bc-02.yaml"},{"id":"control--ogrl-bc-03","slug":"ogrl-bc-03","display_id":"OGRL-BC-03","name":"Data Backup","family":"bc","control_type":"corrective","frequency":"daily","summary":"Back up production data and system state automatically, protect backups from tampering and loss, and alert on failures.\n","statement":"Back up {{ backup_scope }} {{ backup_frequency }} using automated backup jobs, encrypt backups, keep at least one copy in {{ backup_storage_location }} that production credentials cannot modify or delete, retain backups for {{ backup_retention }}, and alert {{ backup_alert_recipients }} when a backup job fails.\n","objective":"Ensure data and system state can be recovered after accidental deletion, corruption, ransomware, or infrastructure loss.\n","guidance":"Use managed snapshots and point-in-time recovery for databases and a central backup service with vault lock or object lock for immutability. Copy backups to a separate cloud account to isolate them from a compromised production account. Infrastructure as code and application source held in a hosted version control system count as system-level backups if the provider retains history. Periodically compare the backup inventory against the data store inventory to catch unprotected stores, and consider backups of critical SaaS data such as the document workspace.\n","parameters":{"backup_alert_recipients":{"label":"Backup failure alert recipients","value":"the on-call engineering team"},"backup_frequency":{"label":"Backup frequency","value":"at least daily"},"backup_retention":{"label":"Backup retention period","value":"at least 30 days"},"backup_scope":{"label":"Data and system state to back up","value":"production databases, object storage, and system configuration not reproducible from version control\n"},"backup_storage_location":{"label":"Isolated backup location","value":"a separate cloud account or region"}},"tags":["backup","data-protection","resilience"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-03-to-800-53-cp-9-a","source_ref":"control--ogrl-bc-03","target_ref":"requirement--nist-sp-800-53-r5-cp-9#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_09_odp_01":"backup_scope","cp_09_odp_02":"backup_frequency"},"summary":"Automated backups of production data stores at a defined frequency satisfy CP-9(a).\n"},{"id":"mapping--ogrl-bc-03-to-800-53-cp-9-b","source_ref":"control--ogrl-bc-03","target_ref":"requirement--nist-sp-800-53-r5-cp-9#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_09_odp_03":"backup_frequency"},"summary":"Backing up system configuration and state not held in version control at the same frequency satisfies CP-9(b).\n"},{"id":"mapping--ogrl-bc-03-to-800-53-cp-9-d","source_ref":"control--ogrl-bc-03","target_ref":"requirement--nist-sp-800-53-r5-cp-9#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Encryption, immutable isolated copies, and failure alerting protect the confidentiality, integrity, and availability of backups per CP-9(d).\n"},{"id":"mapping--ogrl-bc-03-to-soc2-a1-2","source_ref":"control--ogrl-bc-03","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated, protected backups are a core element of the data backup processes this criterion addresses.\n"},{"id":"mapping--ogrl-bc-03-to-soc2-cc7-5","source_ref":"control--ogrl-bc-03","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Backups provide the data needed to restore systems when recovering from incidents.\n"}],"yaml_path":"library/control/ogrl-bc-03.yaml"},{"id":"control--ogrl-bc-04","slug":"ogrl-bc-04","display_id":"OGRL-BC-04","name":"Backup Restoration Testing","family":"bc","control_type":"detective","frequency":"quarterly","summary":"Periodically restore backups of critical data stores to confirm they are usable, complete, and recoverable within objectives.\n","statement":"Restore backups of each critical data store {{ restore_test_cadence }} into an isolated environment, verify data completeness and integrity against defined checks, record the restore duration and data recency against recovery time and recovery point objectives, and remediate failed tests.\n","objective":"Confirm that backups are reliable and can be restored within committed recovery objectives before they are needed.\n","guidance":"Automate restore tests where possible, for example a scheduled job that restores the latest snapshot to a temporary instance, runs row-count and checksum queries, records timing, and tears down the instance. Rotate which data stores are tested if full coverage each period is impractical, but test every critical store at least annually. Keep the job output or a ticket per test as evidence.\n","parameters":{"restore_test_cadence":{"label":"Restoration test frequency","value":"at least quarterly"}},"tags":["backup","restore-testing","resilience"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-04-to-800-53-cp-9-1","source_ref":"control--ogrl-bc-04","target_ref":"requirement--nist-sp-800-53-r5-cp-9-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_9_1_prm_1":"restore_test_cadence"},"summary":"Scheduled restore tests with completeness and integrity checks verify backup reliability and integrity per CP-9(1).\n"},{"id":"mapping--ogrl-bc-04-to-soc2-a1-2","source_ref":"control--ogrl-bc-04","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Restore testing confirms that backup processes actually support recovery."},{"id":"mapping--ogrl-bc-04-to-soc2-a1-3","source_ref":"control--ogrl-bc-04","target_ref":"requirement--soc2-tsc-2017-a1-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Backup restoration tests are one part of testing recovery procedures."}],"yaml_path":"library/control/ogrl-bc-04.yaml"},{"id":"control--ogrl-bc-05","slug":"ogrl-bc-05","display_id":"OGRL-BC-05","name":"Redundant Processing and Storage Sites","family":"bc","control_type":"preventive","frequency":"continuous","summary":"Run critical services across redundant locations, keep backups in a separate region, and secure alternate locations to the same baseline as primary.\n","statement":"Run critical production services across {{ processing_redundancy }} with the ability to resume them at an alternate processing location within {{ failover_time_limit }}, keep backup copies in {{ alternate_storage_location }}, and apply the same security baseline to alternate locations as to the primary environment.\n","objective":"Ensure the loss of a single facility, zone, or region does not cause prolonged unavailability or loss of data.\n","guidance":"In cloud environments, alternate sites are additional availability zones and regions rather than separate data centers, and provider agreements cover the facilities. Deploy stateless tiers across zones behind load balancers and use multi-zone managed databases. For regional failover, keep infrastructure as code and container images deployable to a secondary region and replicate backups there. Apply identical IaC modules, IAM guardrails, logging, and encryption settings to every region so the secondary environment is not a weaker target.\n","parameters":{"alternate_storage_location":{"label":"Alternate storage location","value":"a region geographically separate from the primary data"},"failover_time_limit":{"label":"Alternate processing resumption time","value":"the recovery time objective defined in the business continuity plan"},"processing_redundancy":{"label":"Processing redundancy","value":"at least two availability zones"}},"tags":["redundancy","high-availability","disaster-recovery"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-05-to-800-53-cp-6","source_ref":"control--ogrl-bc-05","target_ref":"requirement--nist-sp-800-53-r5-cp-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Storing backups in a separate region with an equivalent security baseline establishes an alternate storage site per CP-6.\n"},{"id":"mapping--ogrl-bc-05-to-800-53-cp-7-a","source_ref":"control--ogrl-bc-05","target_ref":"requirement--nist-sp-800-53-r5-cp-7#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_07_odp_02":"failover_time_limit"},"summary":"Multi-zone deployment with the ability to resume at an alternate location within a defined time establishes an alternate processing capability per CP-7(a).\n"},{"id":"mapping--ogrl-bc-05-to-800-53-cp-7-c","source_ref":"control--ogrl-bc-05","target_ref":"requirement--nist-sp-800-53-r5-cp-7#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Applying the same security baseline to alternate locations satisfies CP-7(c)."},{"id":"mapping--ogrl-bc-05-to-soc2-a1-2","source_ref":"control--ogrl-bc-05","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Redundant processing and storage locations are recovery infrastructure within this criterion.\n"}],"yaml_path":"library/control/ogrl-bc-05.yaml"},{"id":"control--ogrl-bc-06","slug":"ogrl-bc-06","display_id":"OGRL-BC-06","name":"System Recovery and Reconstitution","family":"bc","control_type":"corrective","frequency":"event-driven","summary":"Restore affected systems to a known-good, secure state within defined recovery time and recovery point objectives after a disruption.\n","statement":"After a disruption, compromise, or failure, recover affected systems to a known-good state within {{ recovery_time_objective }} and with data loss no greater than {{ recovery_point_objective }} using documented recovery runbooks and infrastructure as code, and verify that security configurations and controls are restored and functioning before returning systems to service.\n","objective":"Return systems to normal, secure operation within committed timeframes and without degrading the controls that protect them.\n","guidance":"Rebuild from infrastructure as code and trusted images rather than patching compromised hosts in place. Restore data from the most recent clean backup, which may predate the latest backup after ransomware or corruption. Use a recovery checklist that confirms logging, encryption, access policies, and monitoring are active before reopening traffic. Tighten the default objectives per service based on the business impact analysis (OGRL-BC-07). Evidence is the recovery record showing timing and the completed checklist.\n","parameters":{"recovery_point_objective":{"label":"Recovery point objective","value":"24 hours"},"recovery_time_objective":{"label":"Recovery time objective","value":"24 hours"}},"tags":["disaster-recovery","reconstitution","resilience"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-06-to-800-53-cp-10","source_ref":"control--ogrl-bc-06","target_ref":"requirement--nist-sp-800-53-r5-cp-10","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_10_prm_1":"recovery_time_objective"},"summary":"Recovering to a known-good state within defined recovery objectives satisfies CP-10.\n"},{"id":"mapping--ogrl-bc-06-to-soc2-a1-2","source_ref":"control--ogrl-bc-06","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Runbook-driven restoration within objectives relies on and exercises the recovery infrastructure.\n"},{"id":"mapping--ogrl-bc-06-to-soc2-cc7-5","source_ref":"control--ogrl-bc-06","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Restoring systems to a secure state is the recovery activity following an incident.\n"}],"yaml_path":"library/control/ogrl-bc-06.yaml"},{"id":"control--ogrl-bc-07","slug":"ogrl-bc-07","display_id":"OGRL-BC-07","name":"Business Impact Analysis","family":"bc","control_type":"preventive","frequency":"annual","summary":"Analyze the impact of disruption to critical business functions and the systems and dependencies that support them to set recovery objectives.\n","statement":"Perform a business impact analysis {{ bia_cadence }} and upon significant changes to services or infrastructure that identifies critical business functions and the systems, data, personnel, and third-party dependencies supporting them, rates their criticality, and determines the maximum tolerable downtime and data loss used to set recovery objectives.\n","objective":"Ensure recovery priorities and objectives reflect the actual impact of disruption on customers and the business.\n","guidance":"Keep the analysis lightweight: a table of customer-facing services and internal functions with their supporting cloud resources, data stores, and SaaS vendors, a criticality tier, impact over time (for example at 1 hour, 1 day, 1 week), and the resulting recovery objectives. Draw dependencies from the system inventory (OGRL-AM-01) and vendor inventory (OGRL-TP-01). Feed results into the continuity plan (OGRL-BC-01).\n","parameters":{"bia_cadence":{"label":"Business impact analysis frequency","value":"at least annually"}},"tags":["business-continuity","business-impact-analysis","risk-assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-07-to-800-53-cp-2-8","source_ref":"control--ogrl-bc-07","target_ref":"requirement--nist-sp-800-53-r5-cp-2-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The analysis identifies the critical system assets supporting essential business functions as CP-2(8) requires.\n"},{"id":"mapping--ogrl-bc-07-to-800-53-ra-9","source_ref":"control--ogrl-bc-07","target_ref":"requirement--nist-sp-800-53-r5-ra-9","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Rating the criticality of supporting systems and dependencies overlaps criticality analysis, though not performed at system development decision points.\n"},{"id":"mapping--ogrl-bc-07-to-soc2-a1-2","source_ref":"control--ogrl-bc-07","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Impact analysis sets the recovery objectives that backup and recovery infrastructure must support.\n"},{"id":"mapping--ogrl-bc-07-to-soc2-cc9-1","source_ref":"control--ogrl-bc-07","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Understanding the impact of disruption informs selection of business disruption risk mitigation activities.\n"}],"yaml_path":"library/control/ogrl-bc-07.yaml"},{"id":"control--ogrl-bc-08","slug":"ogrl-bc-08","display_id":"OGRL-BC-08","name":"Capacity Planning and Monitoring","family":"bc","control_type":"detective","frequency":"continuous","summary":"Monitor resource utilization and quotas against thresholds and periodically forecast capacity needs, including for contingency operations.\n","statement":"Monitor utilization of critical compute, storage, database, and network resources and cloud service quotas, alert {{ capacity_alert_recipients }} when utilization exceeds {{ capacity_alert_threshold }}, and review capacity forecasts {{ capacity_review_cadence }} to provision additional capacity, including the capacity needed to operate from alternate locations during contingency operations.\n","objective":"Maintain sufficient capacity to meet availability commitments as demand grows and during failover.\n","guidance":"Use cloud-native metrics and alarms for CPU, memory, disk, connection counts, queue depth, and service quota usage, and enable autoscaling with sensible maximums. Confirm that quotas and reserved capacity in the failover region can absorb production load. Record capacity reviews in a recurring ticket or meeting notes with resulting actions.\n","parameters":{"capacity_alert_recipients":{"label":"Capacity alert recipients","value":"the on-call engineering team"},"capacity_alert_threshold":{"label":"Capacity alert threshold","value":"80 percent of provisioned capacity or quota"},"capacity_review_cadence":{"label":"Capacity review frequency","value":"quarterly"}},"tags":["capacity","availability","monitoring"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-08-to-800-53-cp-2-2","source_ref":"control--ogrl-bc-08","target_ref":"requirement--nist-sp-800-53-r5-cp-2-2","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Capacity forecasting explicitly includes contingency operations, covering CP-2(2), and adds ongoing utilization monitoring and alerting.\n"},{"id":"mapping--ogrl-bc-08-to-soc2-a1-1","source_ref":"control--ogrl-bc-08","target_ref":"requirement--soc2-tsc-2017-a1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Utilization monitoring and capacity forecasting are central to managing processing capacity for availability.\n"}],"yaml_path":"library/control/ogrl-bc-08.yaml"},{"id":"control--ogrl-bc-09","slug":"ogrl-bc-09","display_id":"OGRL-BC-09","name":"Denial-of-Service Protection","family":"bc","control_type":"preventive","frequency":"continuous","summary":"Protect internet-facing services against denial-of-service attacks with layered mitigations and alerting.\n","statement":"Protect internet-facing services against the effects of {{ dos_event_types }} by employing {{ dos_protections }} in front of all public endpoints, and alert {{ dos_alert_recipients }} when attack traffic or rate-limit thresholds are exceeded.\n","objective":"Keep services available to legitimate users during denial-of-service attacks.","guidance":"Place public endpoints behind a CDN or cloud load balancer with provider DDoS protection, add WAF rate-based rules for login, signup, and expensive API routes, and apply per-tenant or per-key API quotas. Avoid exposing origin servers directly. Keep a runbook for engaging the provider's DDoS response team during large attacks.\n","parameters":{"dos_alert_recipients":{"label":"Denial-of-service alert recipients","value":"the on-call engineering team"},"dos_event_types":{"label":"Denial-of-service event types","value":"volumetric network floods, protocol attacks, and application-layer request floods\n"},"dos_protections":{"label":"Denial-of-service protections","value":"cloud DDoS mitigation, web application firewall rate limiting, and API request quotas\n"}},"tags":["ddos","availability","network-security"],"tests":[],"mappings":[{"id":"mapping--ogrl-bc-09-to-800-53-sc-5","source_ref":"control--ogrl-bc-09","target_ref":"requirement--nist-sp-800-53-r5-sc-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sc_05_odp_01":"dos_event_types","sc_05_odp_03":"dos_protections"},"summary":"Layered denial-of-service mitigations for defined attack types satisfy SC-5."},{"id":"mapping--ogrl-bc-09-to-soc2-a1-1","source_ref":"control--ogrl-bc-09","target_ref":"requirement--soc2-tsc-2017-a1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"DoS protection preserves usable capacity under attack traffic, complementing capacity management.\n"},{"id":"mapping--ogrl-bc-09-to-soc2-cc6-6","source_ref":"control--ogrl-bc-09","target_ref":"requirement--soc2-tsc-2017-cc6-6","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"DoS mitigation at public endpoints is a boundary protection against threats from outside the system.\n"}],"yaml_path":"library/control/ogrl-bc-09.yaml"},{"id":"control--ogrl-cm-01","slug":"ogrl-cm-01","display_id":"OGRL-CM-01","name":"Peer-Reviewed Production Change Control","family":"cm","control_type":"preventive","frequency":"event-driven","summary":"Require independent peer review, automated testing, and traceable approval before deploying production code or infrastructure changes.\n","statement":"Require independent peer review, automated verification checks, and documented approval overseen by {{ change_authority }} before merging or deploying changes to production, retaining change records for {{ change_record_retention }}.\n","objective":"Prevent unauthorized, untested, or unreviewed modifications to production code and infrastructure.\n","guidance":"Enforce branch protection rules that prevent self-approval, require passing CI checks, and link deployments to immutable commit hashes and review tickets.\n","parameters":{"change_authority":{"label":"Change oversight authority","value":"designated code owners and the change advisory workflow"},"change_record_retention":{"label":"Change record retention period","value":"365 days"}},"tags":["change-management","sdlc","ci-cd"],"tests":[{"id":"test--ogrl-cm-01-change-control","slug":"ogrl-cm-01-change-control","name":"Verify Branch Protection and Peer-Reviewed Deployments","method":"automated","interval":"daily","required":true,"description":"Confirm production repositories enforce required independent pull-request reviews and passing CI status checks with no bypassed merges.\n","objective_refs":["requirement--nist-sp-800-53-r5-cm-3#obj.b-1","requirement--nist-sp-800-53-r5-cm-3#obj.e"],"yaml_path":"library/test/ogrl-cm-01-change-control.yaml"}],"mappings":[{"id":"mapping--ogrl-cm-01-to-iso27001-a-8-32","source_ref":"control--ogrl-cm-01","target_ref":"requirement--iso-iec-27001-2022-a-8-32","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Peer-reviewed production change control satisfies ISO/IEC 27001:2022 A.8.32."},{"id":"mapping--ogrl-cm-01-to-800-171-03-04-03","source_ref":"control--ogrl-cm-01","target_ref":"requirement--nist-sp-800-171-r3-03-04-03","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Peer-reviewed change authorization and tracking satisfy SP 800-171 03.04.03."},{"id":"mapping--ogrl-cm-01-to-800-53-cm-3-e","source_ref":"control--ogrl-cm-01","target_ref":"requirement--nist-sp-800-53-r5-cm-3#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_03_odp_01":"change_record_retention"},"summary":"Retaining pull-request review and deployment audit trails satisfies NIST CM-3(e).\n"},{"id":"mapping--ogrl-cm-01-to-800-53-cm-3-g","source_ref":"control--ogrl-cm-01","target_ref":"requirement--nist-sp-800-53-r5-cm-3#g","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_03_odp_02":"change_authority"},"summary":"Change oversight through code owners and change advisory workflows satisfies NIST CM-3(g).\n"},{"id":"mapping--ogrl-cm-01-to-soc2-cc8-1","source_ref":"control--ogrl-cm-01","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Peer-reviewed and CI-verified production change control directly satisfies SOC 2 CC8.1.\n"}],"yaml_path":"library/control/ogrl-cm-01.yaml"},{"id":"control--ogrl-cm-02","slug":"ogrl-cm-02","display_id":"OGRL-CM-02","name":"Baseline Configuration and Hardening Standards","family":"cm","control_type":"preventive","frequency":"annual","summary":"Define hardened, version-controlled configuration baselines for in-scope components and build new components only from them.\n","statement":"Define hardened baseline configurations for {{ baseline_scope }} derived from {{ hardening_benchmark }}, maintain them as version-controlled code or templates, provision new components only from an approved baseline, require documented approval by {{ deviation_approver }} for any deviation, and review and update each baseline {{ baseline_review_frequency }} and whenever covered components are introduced or upgraded.\n","objective":"Ensure in-scope components start from, and remain traceable to, an approved secure configuration rather than ad hoc vendor defaults.\n","guidance":"Express baselines as infrastructure-as-code modules, golden machine images, hardened container base images, and organization-level cloud policies (for example AWS SCPs, Azure Policy, or GCP organization policies). Keep a short deviation register linked to the baseline repository. Use CIS Benchmarks or provider security best-practice guides as the starting point and record which settings were tailored and why. Drift detection against these baselines is covered by OGRL-CM-03.\n","parameters":{"baseline_review_frequency":{"label":"Baseline review frequency","value":"annually"},"baseline_scope":{"label":"Components covered by hardened baselines","value":"cloud accounts and projects, compute images, container base images, managed databases, and network configurations\n"},"deviation_approver":{"label":"Baseline deviation approver","value":"the security lead"},"hardening_benchmark":{"label":"Hardening benchmark source","value":"CIS Benchmarks or the cloud provider's security best-practice guidance"}},"tags":["configuration-management","hardening","infrastructure-as-code"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-02-to-800-53-cm-2-a","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-2#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Version-controlled hardened baselines satisfy the CM-2(a) obligation to develop, document, and maintain a baseline under configuration control.\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-2-b-1","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-2#b.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_02_odp_01":"baseline_review_frequency"},"summary":"The periodic baseline review supplies the CM-2(b)(1) review frequency."},{"id":"mapping--ogrl-cm-02-to-800-53-cm-2-b-3","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-2#b.3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Baselines are reviewed and updated whenever covered components are introduced or upgraded, as CM-2(b)(3) requires.\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-6-a","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_06_odp_01":"hardening_benchmark"},"summary":"Baselines derived from a named hardening benchmark establish restrictive configuration settings per CM-6(a).\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-6-b","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Provisioning only from approved baselines implements the documented configuration settings per CM-6(b).\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-6-c","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_06_odp_02":"baseline_scope"},"summary":"Documented, approved baseline deviations for in-scope components address CM-6(c).\n"},{"id":"mapping--ogrl-cm-02-to-soc2-cc5-2","source_ref":"control--ogrl-cm-02","target_ref":"requirement--soc2-tsc-2017-cc5-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Hardened baselines are a technology general control contributing to CC5.2."},{"id":"mapping--ogrl-cm-02-to-soc2-cc7-1","source_ref":"control--ogrl-cm-02","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Defined secure configuration standards are one input to the configuration and vulnerability monitoring expected under CC7.1.\n"}],"yaml_path":"library/control/ogrl-cm-02.yaml"},{"id":"control--ogrl-cm-03","slug":"ogrl-cm-03","display_id":"OGRL-CM-03","name":"Configuration Drift Detection","family":"cm","control_type":"detective","frequency":"continuous","summary":"Automatically detect production configuration that diverges from the approved baseline and resolve each drift.\n","statement":"Continuously compare the running configuration of {{ drift_scope }} against its approved baseline using {{ drift_detection_tooling }}, alert {{ drift_alert_recipients }} on unapproved deviations, and revert or formally approve each detected drift within {{ drift_remediation_sla }}.\n","objective":"Detect unauthorized or accidental configuration changes quickly so production does not silently diverge from its approved secure state.\n","guidance":"Run scheduled infrastructure-as-code plan or drift checks (for example terraform plan in CI, AWS Config, or Azure Policy compliance) and a CSPM tool against production accounts. Route findings to the owning team's queue with the SLA as a due date. Evidence is the drift tool configuration plus a sample of alerts showing revert or approval within SLA.\n","parameters":{"drift_alert_recipients":{"label":"Drift alert recipients","value":"the owning engineering team and the security team"},"drift_detection_tooling":{"label":"Drift detection mechanisms","value":"automated infrastructure-as-code drift checks and cloud security posture management (CSPM) rules\n"},"drift_remediation_sla":{"label":"Drift resolution SLA","value":"7 days for security-relevant settings and 30 days for all other settings"},"drift_scope":{"label":"Components monitored for drift","value":"production cloud resources and infrastructure-as-code managed components"}},"tags":["configuration-management","drift-detection","monitoring"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-03-to-800-53-cm-2-2","source_ref":"control--ogrl-cm-03","target_ref":"requirement--nist-sp-800-53-r5-cm-2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"cm_02_02_odp":"drift_detection_tooling"},"summary":"Automated drift checks keep the recorded baseline and actual state aligned, partly supporting CM-2(2) accuracy and currency.\n"},{"id":"mapping--ogrl-cm-03-to-800-53-cm-6-1","source_ref":"control--ogrl-cm-03","target_ref":"requirement--nist-sp-800-53-r5-cm-6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":{"cm_6_1_prm_2":"drift_detection_tooling"},"summary":"Drift tooling provides the automated verification element of CM-6(1); central management and application are covered elsewhere.\n"},{"id":"mapping--ogrl-cm-03-to-800-53-cm-6-d","source_ref":"control--ogrl-cm-03","target_ref":"requirement--nist-sp-800-53-r5-cm-6#d","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated drift detection and resolution monitors and controls changes to configuration settings under CM-6(d).\n"},{"id":"mapping--ogrl-cm-03-to-soc2-cc7-1","source_ref":"control--ogrl-cm-03","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Detecting configuration changes that depart from approved baselines is a monitoring activity within CC7.1.\n"},{"id":"mapping--ogrl-cm-03-to-soc2-cc8-1","source_ref":"control--ogrl-cm-03","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Drift detection surfaces changes made outside the authorized change process, supporting CC8.1.\n"}],"yaml_path":"library/control/ogrl-cm-03.yaml"},{"id":"control--ogrl-cm-04","slug":"ogrl-cm-04","display_id":"OGRL-CM-04","name":"Security Impact Analysis of Changes","family":"cm","control_type":"preventive","frequency":"event-driven","summary":"Analyze and sign off on the security and privacy impact of significant changes before they are deployed.\n","statement":"Before implementing {{ significant_change_types }}, document an analysis of the change's potential security and privacy impact, covering affected data, trust boundaries, access paths, and existing controls, and obtain sign-off from {{ impact_reviewer }} prior to deployment.\n","objective":"Ensure significant changes do not introduce unassessed security or privacy risk into production.\n","guidance":"Add a security-impact section to the design document or pull-request template that is required when a change matches a significant-change label. Lightweight threat modeling (for example STRIDE on a data-flow diagram) is sufficient for most changes. Organization-level risk re-evaluation for significant business changes is covered by the risk family.\n","parameters":{"impact_reviewer":{"label":"Security impact sign-off authority","value":"the security lead or a designated security reviewer"},"significant_change_types":{"label":"Changes requiring security impact analysis","value":"significant changes, including new external integrations, changes to authentication or authorization, new data stores holding customer data, and network boundary changes\n"}},"tags":["change-management","threat-modeling","risk"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-04-to-800-53-cm-4","source_ref":"control--ogrl-cm-04","target_ref":"requirement--nist-sp-800-53-r5-cm-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Pre-deployment security and privacy impact analysis for significant changes covers CM-4 for that subset of changes.\n"},{"id":"mapping--ogrl-cm-04-to-soc2-cc3-4","source_ref":"control--ogrl-cm-04","target_ref":"requirement--soc2-tsc-2017-cc3-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Analyzing the security impact of significant system changes partly addresses identifying risks from change under CC3.4.\n"},{"id":"mapping--ogrl-cm-04-to-soc2-cc8-1","source_ref":"control--ogrl-cm-04","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Security impact analysis of significant changes is part of designing and authorizing changes under CC8.1.\n"}],"yaml_path":"library/control/ogrl-cm-04.yaml"},{"id":"control--ogrl-cm-05","slug":"ogrl-cm-05","display_id":"OGRL-CM-05","name":"Production Change Access Restrictions","family":"cm","control_type":"preventive","frequency":"continuous","summary":"Limit who and what can change production to the deployment pipeline and a small reviewed set of identities.\n","statement":"Restrict permissions to deploy to or modify production systems to {{ deploy_authorized_identities }} acting through the CI/CD pipeline or infrastructure-as-code workflow, prohibit direct manual changes outside that path except under the emergency change procedure, and review the identities holding production change permissions {{ change_access_review_frequency }}.\n","objective":"Ensure production can only be changed through the controlled, reviewable delivery path.\n","guidance":"Grant production write access to the pipeline's workload identity (for example GitHub Actions OIDC roles) rather than to humans. Keep human production access read-only by default with just-in-time elevation. Use GitHub environments with required reviewers and restrict who can modify pipeline definitions. Evidence is the IAM policy export and the quarterly review record.\n","parameters":{"change_access_review_frequency":{"label":"Production change access review frequency","value":"quarterly"},"deploy_authorized_identities":{"label":"Identities permitted to change production","value":"the automated deployment pipeline and a named set of platform engineers"}},"tags":["change-management","least-privilege","ci-cd"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-05-to-800-53-cm-5","source_ref":"control--ogrl-cm-05","target_ref":"requirement--nist-sp-800-53-r5-cm-5","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Defines and enforces logical access restrictions for changing production; physical change restrictions are out of scope.\n"},{"id":"mapping--ogrl-cm-05-to-soc2-cc6-1","source_ref":"control--ogrl-cm-05","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Limiting production change permissions is a logical access restriction over protected assets under CC6.1.\n"},{"id":"mapping--ogrl-cm-05-to-soc2-cc8-1","source_ref":"control--ogrl-cm-05","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting who can implement production changes supports the authorized change process under CC8.1.\n"}],"yaml_path":"library/control/ogrl-cm-05.yaml"},{"id":"control--ogrl-cm-06","slug":"ogrl-cm-06","display_id":"OGRL-CM-06","name":"Emergency Change Procedure","family":"cm","control_type":"corrective","frequency":"event-driven","summary":"Allow expedited production changes during incidents while preserving authorization, records, and after-the-fact review.\n","statement":"Permit changes that bypass standard pre-deployment approval only when authorized by {{ emergency_authorizer }} to resolve an active incident or critical vulnerability, record each emergency change with its justification and linked incident or ticket, and complete retrospective peer review and approval of the change within {{ retro_review_window }}.\n","objective":"Allow rapid remediation without creating an unreviewed path into production.\n","guidance":"Use a dedicated emergency label or break-glass deployment workflow that records who invoked it and requires an incident ID. A weekly query for merges that bypassed branch protection or deployments without an approved review gives auditors a complete population to sample.\n","parameters":{"emergency_authorizer":{"label":"Emergency change authorizer","value":"the incident commander or on-call engineering lead"},"retro_review_window":{"label":"Retrospective review deadline","value":"2 business days"}},"tags":["change-management","emergency-change","incident-response"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-06-to-800-53-cm-3-b","source_ref":"control--ogrl-cm-06","target_ref":"requirement--nist-sp-800-53-r5-cm-3#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Emergency changes receive authorization and retrospective review, a variant of CM-3(b) approval for the expedited path.\n"},{"id":"mapping--ogrl-cm-06-to-800-53-cm-3-c","source_ref":"control--ogrl-cm-06","target_ref":"requirement--nist-sp-800-53-r5-cm-3#c","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Recording each emergency change with its justification documents change decisions for that class of change under CM-3(c).\n"},{"id":"mapping--ogrl-cm-06-to-soc2-cc8-1","source_ref":"control--ogrl-cm-06","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"An authorized, documented, and retrospectively reviewed emergency path is part of change management under CC8.1.\n"}],"yaml_path":"library/control/ogrl-cm-06.yaml"},{"id":"control--ogrl-cm-07","slug":"ogrl-cm-07","display_id":"OGRL-CM-07","name":"Change Testing and Environment Separation","family":"cm","control_type":"preventive","frequency":"event-driven","summary":"Test changes in separated non-production environments with automated gates before production deployment.\n","statement":"Test and validate each change in {{ test_environment }} that is logically separated from production before deployment, require automated test suites to pass as a merge or deployment gate, retain test results with the change record, and prohibit unmasked production customer data in non-production environments unless approved by {{ prod_data_exception_approver }}.\n","objective":"Catch defects and unintended effects before they reach production without exposing customer data in lower environments.\n","guidance":"Run staging in a separate cloud account or project with distinct credentials. Configure required status checks in branch protection so merges are blocked on failing tests, and keep CI run links on the pull request. Use synthetic or masked data sets for testing.\n","parameters":{"prod_data_exception_approver":{"label":"Production data in test exception approver","value":"the security lead"},"test_environment":{"label":"Pre-production test environment","value":"a staging environment in a separate cloud account or project"}},"tags":["change-management","testing","environment-separation"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-07-to-800-53-cm-3-2","source_ref":"control--ogrl-cm-07","target_ref":"requirement--nist-sp-800-53-r5-cm-3-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Gated testing, validation, and retained results before deployment meet CM-3(2)."},{"id":"mapping--ogrl-cm-07-to-800-53-cm-4-1","source_ref":"control--ogrl-cm-07","target_ref":"requirement--nist-sp-800-53-r5-cm-4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Changes are exercised in a separate test environment, though analysis is not necessarily focused on security and privacy impact as CM-4(1) expects.\n"},{"id":"mapping--ogrl-cm-07-to-soc2-cc8-1","source_ref":"control--ogrl-cm-07","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Pre-production testing in separated environments is part of the change process under CC8.1.\n"}],"yaml_path":"library/control/ogrl-cm-07.yaml"},{"id":"control--ogrl-cm-08","slug":"ogrl-cm-08","display_id":"OGRL-CM-08","name":"Least Functionality and Software Restriction","family":"cm","control_type":"preventive","frequency":"continuous","summary":"Run only required services and ports on production, and restrict software installation to approved sources.\n","statement":"Configure production hosts and container images to run only the services, ports, and protocols required for their function with all others disabled or blocked by default, restrict software installation on production systems and workforce endpoints to {{ approved_software_sources }} enforced through {{ software_enforcement_methods }}, and review compliance {{ software_compliance_review_frequency }}.\n","objective":"Reduce attack surface and prevent unauthorized or malicious software from being introduced.\n","guidance":"Use minimal or distroless base images, default-deny security groups, and read-only root filesystems. On endpoints, remove local administrator rights and use MDM-managed application catalogs or allow-listing. A quarterly export of listening ports, image package lists, and MDM installed-software reports provides evidence.\n","parameters":{"approved_software_sources":{"label":"Approved software sources","value":"approved package repositories, the internal container registry, and the MDM-managed software catalog\n"},"software_compliance_review_frequency":{"label":"Software compliance review frequency","value":"quarterly"},"software_enforcement_methods":{"label":"Software restriction enforcement methods","value":"immutable container images, removal of local administrator rights, and MDM application allow-listing\n"}},"tags":["hardening","least-functionality","endpoint-security"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-08-to-800-53-cm-11-b","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-11#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_11_odp_02":"software_enforcement_methods"},"summary":"Named enforcement methods for software installation satisfy CM-11(b)."},{"id":"mapping--ogrl-cm-08-to-800-53-cm-11-c","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-11#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_11_odp_03":"software_compliance_review_frequency"},"summary":"Periodic compliance review supplies the CM-11(c) monitoring frequency."},{"id":"mapping--ogrl-cm-08-to-800-53-cm-7-a","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-7#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Running only required services, ports, and protocols provides only essential capabilities per CM-7(a).\n"},{"id":"mapping--ogrl-cm-08-to-800-53-cm-7-b","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-7#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Default-deny of unneeded services and restricted software sources overlap with the CM-7(b) prohibitions, which the organization still enumerates.\n"},{"id":"mapping--ogrl-cm-08-to-soc2-cc6-8","source_ref":"control--ogrl-cm-08","target_ref":"requirement--soc2-tsc-2017-cc6-8","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting software installation and unneeded functionality helps prevent unauthorized software under CC6.8.\n"}],"yaml_path":"library/control/ogrl-cm-08.yaml"},{"id":"control--ogrl-cm-09","slug":"ogrl-cm-09","display_id":"OGRL-CM-09","name":"Software and Data Integrity Verification","family":"cm","control_type":"detective","frequency":"continuous","summary":"Verify the integrity of build artifacts and critical system files and act on unauthorized changes.\n","statement":"Verify the integrity of {{ integrity_protected_assets }} using {{ integrity_mechanisms }} before deployment and while running, and when verification fails or an unauthorized change is detected, {{ integrity_response_actions }}.\n","objective":"Detect and stop tampered or unauthorized software and configuration before it can affect production.\n","guidance":"Sign build artifacts and container images in CI (for example Sigstore cosign), pin deployments to image digests, and enforce signature verification with an admission controller or deployment policy. Use file integrity monitoring or immutable infrastructure for hosts. Integrity of customer data stores is addressed by the data integrity control in the cryptography family.\n","parameters":{"integrity_mechanisms":{"label":"Integrity verification mechanisms","value":"cryptographic signing and digest pinning of artifacts and images, plus file integrity monitoring on hosts\n"},"integrity_protected_assets":{"label":"Assets subject to integrity verification","value":"build artifacts, container images, infrastructure-as-code templates, and critical system binaries and configuration files\n"},"integrity_response_actions":{"label":"Actions on integrity failure","value":"block the deployment or isolate the affected host, alert the security on-call team, and open a security incident\n"}},"tags":["integrity","supply-chain","file-integrity-monitoring"],"tests":[],"mappings":[{"id":"mapping--ogrl-cm-09-to-800-53-si-7-a","source_ref":"control--ogrl-cm-09","target_ref":"requirement--nist-sp-800-53-r5-si-7#a","relationship":"subset-of","review_status":"reviewed","parameter_map":{"si_7_prm_1":"integrity_protected_assets"},"summary":"Integrity verification covers software and critical configuration; firmware and general information are out of scope for SI-7(a).\n"},{"id":"mapping--ogrl-cm-09-to-800-53-si-7-b","source_ref":"control--ogrl-cm-09","target_ref":"requirement--nist-sp-800-53-r5-si-7#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_7_prm_2":"integrity_response_actions"},"summary":"Defined response actions on integrity failure satisfy SI-7(b)."},{"id":"mapping--ogrl-cm-09-to-soc2-cc6-8","source_ref":"control--ogrl-cm-09","target_ref":"requirement--soc2-tsc-2017-cc6-8","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Blocking unsigned or tampered software helps prevent unauthorized or malicious software under CC6.8.\n"}],"yaml_path":"library/control/ogrl-cm-09.yaml"},{"id":"control--ogrl-cr-01","slug":"ogrl-cr-01","display_id":"OGRL-CR-01","name":"Encryption in Transit and at Rest","family":"cr","control_type":"preventive","frequency":"continuous","summary":"Encrypt sensitive data in transit using modern TLS and at rest using strong managed cryptographic keys.\n","statement":"Protect {{ protected_data_scope }} in transit using {{ transit_cipher_suite }} and at rest using {{ rest_cipher_suite }} with centrally managed keys.\n","objective":"Preserve confidentiality and integrity of sensitive data across networks and storage media.\n","guidance":"Disable TLS versions below 1.2, enforce HSTS on public web endpoints, and enable cloud KMS encryption on all databases, object stores, and block volumes.\n","parameters":{"protected_data_scope":{"label":"Protected data scope","value":"all customer, authentication, and confidential organizational data"},"rest_cipher_suite":{"label":"Minimum storage encryption","value":"AES-256"},"transit_cipher_suite":{"label":"Minimum transport encryption","value":"TLS 1.2 or higher"}},"tags":["cryptography","tls","encryption"],"tests":[{"id":"test--ogrl-cr-01-encryption","slug":"ogrl-cr-01-encryption","name":"Verify TLS in Transit and Storage Encryption at Rest","method":"automated","interval":"daily","required":true,"description":"Verify public endpoints enforce TLS 1.2+ and all production databases, object buckets, and volumes have encryption at rest enabled.\n","objective_refs":[],"yaml_path":"library/test/ogrl-cr-01-encryption.yaml"}],"mappings":[{"id":"mapping--ogrl-cr-01-to-iso27001-a-8-24","source_ref":"control--ogrl-cr-01","target_ref":"requirement--iso-iec-27001-2022-a-8-24","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Modern TLS and managed AES-256 storage encryption satisfy ISO/IEC 27001:2022 A.8.24.\n"},{"id":"mapping--ogrl-cr-01-to-800-171-03-13-08","source_ref":"control--ogrl-cr-01","target_ref":"requirement--nist-sp-800-171-r3-03-13-08","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Modern TLS and storage encryption satisfy SP 800-171 03.13.08 data protection."},{"id":"mapping--ogrl-cr-01-to-800-53-sc-28","source_ref":"control--ogrl-cr-01","target_ref":"requirement--nist-sp-800-53-r5-sc-28","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sc_28_odp_02":"protected_data_scope"},"summary":"Enforcing AES-256 encryption at rest with managed keys protects stored data per SC-28.\n"},{"id":"mapping--ogrl-cr-01-to-800-53-sc-8","source_ref":"control--ogrl-cr-01","target_ref":"requirement--nist-sp-800-53-r5-sc-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Enforcing modern TLS protects confidentiality and integrity of transmitted information per SC-8.\n"},{"id":"mapping--ogrl-cr-01-to-soc2-cc6-1","source_ref":"control--ogrl-cr-01","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Encryption at rest protects information assets as part of the logical access safeguards in CC6.1.\n"},{"id":"mapping--ogrl-cr-01-to-soc2-cc6-7","source_ref":"control--ogrl-cr-01","target_ref":"requirement--soc2-tsc-2017-cc6-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"TLS in transit and encryption at rest satisfy SOC 2 CC6.7 transmission and data protection.\n"}],"yaml_path":"library/control/ogrl-cr-01.yaml"},{"id":"control--ogrl-cr-02","slug":"ogrl-cr-02","display_id":"OGRL-CR-02","name":"Cryptographic Key Management","family":"cr","control_type":"preventive","frequency":"continuous","summary":"Manage encryption keys in a dedicated key management service with restricted access, periodic rotation, and logged administration.\n","statement":"Generate, store, and use cryptographic keys protecting {{ key_scope }} within {{ key_management_system }}, restrict key administration and key use to authorized roles through least-privilege policies, rotate keys {{ key_rotation_period }} and upon suspected compromise, and log all key administration actions.\n","objective":"Keep cryptographic keys confidential, available, and under authorized control throughout their lifecycle so that encryption remains effective.\n","guidance":"Use a cloud KMS (AWS KMS, Google Cloud KMS, Azure Key Vault) with HSM-backed keys and enable automatic rotation for customer-managed keys. Separate key administrators from key users in IAM policy, require a waiting period before key deletion, and send KMS audit events to the central log store. Manage TLS certificates through a managed certificate service with automated renewal. Keep a key inventory recording owner and purpose, and never embed key material in source code or images (see OGRL-AC-06).\n","parameters":{"key_management_system":{"label":"Key management system","value":"a FIPS 140-validated cloud key management service or HSM"},"key_rotation_period":{"label":"Key rotation frequency","value":"at least annually"},"key_scope":{"label":"Data and services protected by managed keys","value":"production data stores, backups, and TLS endpoints"}},"tags":["cryptography","key-management","kms"],"tests":[],"mappings":[{"id":"mapping--ogrl-cr-02-to-800-53-sc-12","source_ref":"control--ogrl-cr-02","target_ref":"requirement--nist-sp-800-53-r5-sc-12","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Centralized key generation, storage, access restriction, rotation, and logging establish and manage keys as SC-12 requires.\n"},{"id":"mapping--ogrl-cr-02-to-soc2-cc6-1","source_ref":"control--ogrl-cr-02","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Protecting encryption keys is one element of the logical access security measures this criterion covers.\n"}],"yaml_path":"library/control/ogrl-cr-02.yaml"},{"id":"control--ogrl-cr-03","slug":"ogrl-cr-03","display_id":"OGRL-CR-03","name":"Data Retention and Disposal","family":"cr","control_type":"preventive","frequency":"quarterly","summary":"Define retention periods for each data category, enforce them, and dispose of data that has expired or that customers ask to delete.\n","statement":"Define retention periods for each category of customer, personal, and confidential data in a documented retention schedule; enforce them through automated deletion or lifecycle rules where technically feasible; delete customer data within {{ customer_deletion_window }} of contract termination or a verified deletion request; and verify {{ retention_review_cadence }} that data past its retention period has been disposed of.\n","objective":"Retain information only as long as required for business, legal, and contractual purposes and dispose of it securely afterward.\n","guidance":"Implement retention with object storage lifecycle policies, database TTL or scheduled purge jobs, and log-group retention settings. Document that deleted data persists in backups until they age out under OGRL-BC-03. Provide a legal-hold process that suspends deletion when required. Per-tenant encryption keys enable cryptographic erasure of a customer's data at offboarding. Keep deletion job output or tickets as evidence and provide deletion confirmations to customers on request.\n","parameters":{"customer_deletion_window":{"label":"Customer data deletion deadline","value":"30 days"},"retention_review_cadence":{"label":"Retention enforcement review frequency","value":"quarterly"}},"tags":["data-retention","data-disposal","privacy"],"tests":[],"mappings":[{"id":"mapping--ogrl-cr-03-to-800-53-si-12","source_ref":"control--ogrl-cr-03","target_ref":"requirement--nist-sp-800-53-r5-si-12","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"A documented and enforced retention schedule manages and retains information in line with legal, contractual, and operational requirements per SI-12.\n"},{"id":"mapping--ogrl-cr-03-to-soc2-c1-2","source_ref":"control--ogrl-cr-03","target_ref":"requirement--soc2-tsc-2017-c1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Scheduled and request-driven deletion disposes of confidential information when it is no longer needed.\n"},{"id":"mapping--ogrl-cr-03-to-soc2-cc6-5","source_ref":"control--ogrl-cr-03","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Logical data disposal contributes to removing the ability to recover data before assets are retired, though physical media handling is addressed elsewhere.\n"},{"id":"mapping--ogrl-cr-03-to-soc2-p4-2","source_ref":"control--ogrl-cr-03","target_ref":"requirement--soc2-tsc-2017-p4-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The retention schedule governs how long personal information is kept."}],"yaml_path":"library/control/ogrl-cr-03.yaml"},{"id":"control--ogrl-cr-04","slug":"ogrl-cr-04","display_id":"OGRL-CR-04","name":"Media Sanitization and Secure Disposal","family":"cr","control_type":"preventive","frequency":"event-driven","summary":"Sanitize storage media before disposal or reuse and keep a record of each sanitized asset.\n","statement":"Sanitize {{ media_scope }} prior to disposal, reuse, or release outside organizational control using {{ sanitization_methods }}, and retain a record of each sanitized asset including its identifier, method used, date, and the person or vendor performing the sanitization.\n","objective":"Prevent recovery of confidential and personal information from retired, reassigned, or returned storage media.\n","guidance":"For laptops, rely on full-disk encryption plus an MDM-initiated wipe or cryptographic erase before reassignment, and use a certified IT asset disposition vendor that issues certificates of destruction for retired hardware. Data center media is usually sanitized by the cloud provider; treat it as a subservice organization responsibility and confirm it in their SOC 2 report. For cloud volumes and tenant data, deleting the encryption key renders data unrecoverable. Reconcile disposal records against the asset inventory (OGRL-AM-01).\n","parameters":{"media_scope":{"label":"Media requiring sanitization","value":"laptops, workstations, removable media, and other devices that store organizational data\n"},"sanitization_methods":{"label":"Sanitization techniques","value":"NIST SP 800-88 purge or destroy techniques, including cryptographic erase of encrypted devices\n"}},"tags":["media-sanitization","data-disposal","asset-management"],"tests":[],"mappings":[{"id":"mapping--ogrl-cr-04-to-800-53-mp-6-a","source_ref":"control--ogrl-cr-04","target_ref":"requirement--nist-sp-800-53-r5-mp-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"mp_6_prm_1":"media_scope","mp_6_prm_2":"sanitization_methods"},"summary":"Sanitizing defined media with defined techniques before disposal, reuse, or release satisfies MP-6(a).\n"},{"id":"mapping--ogrl-cr-04-to-800-53-mp-6-b","source_ref":"control--ogrl-cr-04","target_ref":"requirement--nist-sp-800-53-r5-mp-6#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Using purge or destroy techniques aligned to SP 800-88 supports sanitization strength commensurate with data sensitivity, without formal categorization-based selection.\n"},{"id":"mapping--ogrl-cr-04-to-soc2-c1-2","source_ref":"control--ogrl-cr-04","target_ref":"requirement--soc2-tsc-2017-c1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Media sanitization is one mechanism for disposing of confidential information."},{"id":"mapping--ogrl-cr-04-to-soc2-cc6-5","source_ref":"control--ogrl-cr-04","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Sanitizing media before disposal ensures data cannot be recovered from retired assets.\n"},{"id":"mapping--ogrl-cr-04-to-soc2-p4-3","source_ref":"control--ogrl-cr-04","target_ref":"requirement--soc2-tsc-2017-p4-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Media sanitization is one mechanism for securely disposing of personal information.\n"}],"yaml_path":"library/control/ogrl-cr-04.yaml"},{"id":"control--ogrl-cr-05","slug":"ogrl-cr-05","display_id":"OGRL-CR-05","name":"Data Store Integrity and Replication","family":"cr","control_type":"detective","frequency":"continuous","summary":"Protect production data stores with storage-level integrity checks and multi-zone replication, and alert on integrity or replication failures.\n","statement":"Configure production data stores holding {{ integrity_scope }} with storage-level integrity verification and replication across at least {{ replica_zone_count }} availability zones, and alert {{ integrity_alert_recipients }} when integrity errors, replication failures, or replication lag exceeding {{ replication_lag_threshold }} are detected.\n","objective":"Ensure stored data remains complete and accurate and survives the loss of a single storage component or zone without corruption or loss.\n","guidance":"Prefer managed data stores with built-in checksumming and synchronous replication (for example multi-AZ relational databases and object storage with checksums and versioning), enable page checksums where the engine supports them, and alert on replica lag and storage error metrics. Replication propagates logical corruption and accidental deletes, so it complements rather than replaces backups (OGRL-BC-03). Run periodic consistency checks or reconciliations on critical tables. Software and artifact integrity verification is covered by OGRL-CM-09.\n","parameters":{"integrity_alert_recipients":{"label":"Integrity and replication alert recipients","value":"the on-call engineering team"},"integrity_scope":{"label":"Data covered by integrity verification","value":"customer data and system-of-record data"},"replica_zone_count":{"label":"Minimum replication zones","value":"two"},"replication_lag_threshold":{"label":"Replication lag alert threshold","value":"5 minutes"}},"tags":["data-integrity","replication","availability"],"tests":[],"mappings":[{"id":"mapping--ogrl-cr-05-to-800-53-cp-9","source_ref":"control--ogrl-cr-05","target_ref":"requirement--nist-sp-800-53-r5-cp-9","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Replicated copies preserve data availability, overlapping with backup objectives, but replication is not a substitute for point-in-time backups.\n"},{"id":"mapping--ogrl-cr-05-to-800-53-si-7-a","source_ref":"control--ogrl-cr-05","target_ref":"requirement--nist-sp-800-53-r5-si-7#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Storage-level integrity verification covers the information portion of SI-7(a) but not software or firmware.\n"},{"id":"mapping--ogrl-cr-05-to-800-53-si-7-b","source_ref":"control--ogrl-cr-05","target_ref":"requirement--nist-sp-800-53-r5-si-7#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Alerting on detected data integrity errors is a response action for information integrity under SI-7(b).\n"},{"id":"mapping--ogrl-cr-05-to-soc2-pi1-5","source_ref":"control--ogrl-cr-05","target_ref":"requirement--soc2-tsc-2017-pi1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Integrity verification and replication help keep stored data complete and accurate over time.\n"}],"yaml_path":"library/control/ogrl-cr-05.yaml"},{"id":"control--ogrl-gv-01","slug":"ogrl-gv-01","display_id":"OGRL-GV-01","name":"Information Security Program and Policy Framework","family":"gv","control_type":"preventive","frequency":"annual","summary":"Maintain an approved, published set of information security policies that is reviewed on a fixed cadence and after significant change.\n","statement":"Maintain a documented information security policy set that defines the security program's scope, policy owners, and roles and responsibilities. The policy set is approved by {{ policy_approver }}, published to all workforce members, stored in a repository where only policy owners can modify it, and reviewed and updated {{ policy_review_frequency }} and following {{ policy_review_triggers }}.\n","objective":"Security expectations are formally defined, approved by accountable leadership, available to everyone they apply to, and kept current.\n","guidance":"A startup can start with a top-level information security policy plus topic policies (access control, change management, incident response, vendor management, data handling) kept in a wiki or Git repository with change history. Record each review and approval with a dated sign-off or merge approval; auditors typically sample the approval record, the publication location, and the version history. Map each policy to the controls that implement it so gaps are visible.\n","parameters":{"policy_approver":{"label":"Policy approval authority","value":"executive leadership (CEO or designated executive)"},"policy_review_frequency":{"label":"Policy review frequency","value":"at least annually"},"policy_review_triggers":{"label":"Events triggering out-of-cycle policy review","value":"significant organizational, regulatory, contractual, or system changes"}},"tags":["governance","policy","security-program"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-01-to-800-53-pm-1-a","source_ref":"control--ogrl-gv-01","target_ref":"requirement--nist-sp-800-53-r5-pm-1#a","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"The approved policy set serves as the program plan and assigns roles, but does not itself describe every program management and common control.\n"},{"id":"mapping--ogrl-gv-01-to-800-53-pm-1-b","source_ref":"control--ogrl-gv-01","target_ref":"requirement--nist-sp-800-53-r5-pm-1#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_01_odp_01":"policy_review_frequency","pm_01_odp_02":"policy_review_triggers"},"summary":"Scheduled and event-driven policy review and update fulfils the plan review requirement.\n"},{"id":"mapping--ogrl-gv-01-to-800-53-pm-1-c","source_ref":"control--ogrl-gv-01","target_ref":"requirement--nist-sp-800-53-r5-pm-1#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Restricting policy modification to owners in a controlled repository protects the plan from unauthorized change.\n"},{"id":"mapping--ogrl-gv-01-to-soc2-cc2-2","source_ref":"control--ogrl-gv-01","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Publishing policies to all workforce members is one form of internal communication of security responsibilities.\n"},{"id":"mapping--ogrl-gv-01-to-soc2-cc5-1","source_ref":"control--ogrl-gv-01","target_ref":"requirement--soc2-tsc-2017-cc5-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The policy framework establishes the control activities intended to reduce risk; selection against assessed risk is addressed by risk controls.\n"},{"id":"mapping--ogrl-gv-01-to-soc2-cc5-3","source_ref":"control--ogrl-gv-01","target_ref":"requirement--soc2-tsc-2017-cc5-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Approved and published policies are the vehicle through which control activities are deployed; implementing procedures sit in other controls.\n"}],"yaml_path":"library/control/ogrl-gv-01.yaml"},{"id":"control--ogrl-gv-02","slug":"ogrl-gv-02","display_id":"OGRL-GV-02","name":"Security Leadership and Organizational Structure","family":"gv","control_type":"preventive","frequency":"annual","summary":"Formally designate an accountable security leader and document security roles, reporting lines, and responsibilities.\n","statement":"Designate in writing a {{ security_leader_role }} who is accountable for the information security program and has the authority and resources to run it. Maintain an organizational chart showing reporting lines and a document of security roles and responsibilities, and review both {{ org_review_frequency }} and when leadership or structure changes.\n","objective":"Accountability for security is assigned to a named individual, and reporting lines and responsibilities are clear and current.\n","guidance":"In small companies the role is often held by the CTO or a head of security as a part-time responsibility; that is acceptable if the designation is written and the person has the authority to act. Keep the org chart in the HRIS so it stays current, and keep a RACI for security activities (policy ownership, access reviews, incident command, vendor reviews). Evidence: the designation memo or board resolution, the dated org chart, and the reviewed RACI.\n","parameters":{"org_review_frequency":{"label":"Org chart and responsibilities review frequency","value":"at least annually"},"security_leader_role":{"label":"Accountable security leader role","value":"security officer (for example CISO, head of security, or CTO)"}},"tags":["governance","roles-and-responsibilities","leadership"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-02-to-800-53-pm-2","source_ref":"control--ogrl-gv-02","target_ref":"requirement--nist-sp-800-53-r5-pm-2","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Written designation of an accountable security leader with authority and resources covers the appointment requirement; documented reporting lines add scope.\n"},{"id":"mapping--ogrl-gv-02-to-soc2-cc1-3","source_ref":"control--ogrl-gv-02","target_ref":"requirement--soc2-tsc-2017-cc1-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented reporting lines, security roles, and a designated leader address organizational structure and authority for security.\n"},{"id":"mapping--ogrl-gv-02-to-soc2-cc1-5","source_ref":"control--ogrl-gv-02","target_ref":"requirement--soc2-tsc-2017-cc1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Assigning named accountability for the security program supports holding individuals accountable; performance enforcement is elsewhere.\n"}],"yaml_path":"library/control/ogrl-gv-02.yaml"},{"id":"control--ogrl-gv-03","slug":"ogrl-gv-03","display_id":"OGRL-GV-03","name":"Board Oversight of Security and Risk","family":"gv","control_type":"detective","frequency":"annual","summary":"Security leadership briefs the board or its designated committee on security and risk on a fixed cadence, and oversight is recorded.\n","statement":"Security leadership briefs {{ oversight_body }} on the state of the security program {{ briefing_frequency }}, covering top risks and their treatment status, significant incidents, control assessment and audit results, and open deficiencies. The oversight body's review, questions, and decisions are recorded in meeting minutes.\n","objective":"Those charged with governance exercise informed, documented oversight of security and risk independently of the management that operates the controls.\n","guidance":"Pre-revenue companies with an informal board can use a board meeting agenda item with a short security deck; record attendance and decisions in minutes. Where the board includes outside or independent directors, note their participation. Auditors usually sample the deck and minutes for each briefing in the period.\n","parameters":{"briefing_frequency":{"label":"Security briefing frequency","value":"at least annually"},"oversight_body":{"label":"Governance body exercising oversight","value":"the board of directors or a designated board committee"}},"tags":["governance","board-oversight","risk"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-03-to-soc2-cc1-2","source_ref":"control--ogrl-gv-03","target_ref":"requirement--soc2-tsc-2017-cc1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Documented board briefings demonstrate oversight of security; board independence and composition are outside this control.\n"},{"id":"mapping--ogrl-gv-03-to-soc2-cc2-2","source_ref":"control--ogrl-gv-03","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Briefing the governing body is one channel of internal communication about security objectives and results.\n"}],"yaml_path":"library/control/ogrl-gv-03.yaml"},{"id":"control--ogrl-gv-04","slug":"ogrl-gv-04","display_id":"OGRL-GV-04","name":"Code of Conduct","family":"gv","control_type":"preventive","frequency":"annual","summary":"Maintain an approved code of conduct and obtain workforce acknowledgment at hire and periodically thereafter.\n","statement":"Maintain a code of conduct, approved by {{ conduct_approver }}, that sets expectations for integrity, ethical behavior, conflicts of interest, and protection of company and customer information, and states disciplinary consequences for violations. Require every employee and contractor to acknowledge the code within {{ acknowledgment_window }} of starting and {{ reacknowledgment_frequency }} thereafter.\n","objective":"Every workforce member has been informed of, and has agreed to, the organization's standards of conduct and the consequences of violating them.\n","guidance":"Collect acknowledgments through the HRIS or compliance platform during onboarding and annual policy attestations, and keep the signed record per person. Reference the whistleblower channel (OGRL-GV-05) in the code. Auditors typically sample new hires and existing staff for timely acknowledgment.\n","parameters":{"acknowledgment_window":{"label":"Deadline for new-hire acknowledgment","value":"30 days"},"conduct_approver":{"label":"Code of conduct approval authority","value":"executive leadership"},"reacknowledgment_frequency":{"label":"Re-acknowledgment frequency","value":"annually"}},"tags":["governance","ethics","workforce"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-04-to-soc2-cc1-1","source_ref":"control--ogrl-gv-04","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"An acknowledged code of conduct establishes standards of integrity and ethics; tone from leadership and evaluation of adherence go further.\n"},{"id":"mapping--ogrl-gv-04-to-soc2-cc1-5","source_ref":"control--ogrl-gv-04","target_ref":"requirement--soc2-tsc-2017-cc1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Stated disciplinary consequences and individual acknowledgment support accountability for conduct.\n"}],"yaml_path":"library/control/ogrl-gv-04.yaml"},{"id":"control--ogrl-gv-05","slug":"ogrl-gv-05","display_id":"OGRL-GV-05","name":"Whistleblower and Anonymous Reporting Channel","family":"gv","control_type":"detective","frequency":"event-driven","summary":"Provide a confidential, optionally anonymous channel for reporting ethics, fraud, and security concerns, and triage every report.\n","statement":"Provide a confidential reporting channel, with an anonymous option, through which workforce members and {{ external_reporters }} can report suspected misconduct, fraud, or security concerns. Route reports to {{ report_recipient }}, independent of the party reported on, triage each report within {{ triage_sla }}, record its disposition, and prohibit retaliation against good-faith reporters.\n","objective":"Concerns about misconduct or security can be raised safely and reach someone with authority to act, and every report is resolved.\n","guidance":"A third-party hotline or a web form that does not record identity satisfies the anonymous option; a shared inbox read only by the CEO does not provide independence if the CEO is the subject. Publish the channel in the code of conduct and employee handbook. Keep a case log (date, category, owner, outcome) as evidence; an empty log is acceptable if the channel's existence and communication are shown.\n","parameters":{"external_reporters":{"label":"External parties who may report","value":"contractors, customers, and vendors"},"report_recipient":{"label":"Report recipient","value":"a designated board member or the head of legal or people operations"},"triage_sla":{"label":"Report triage deadline","value":"5 business days"}},"tags":["governance","ethics","whistleblower"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-05-to-soc2-cc1-1","source_ref":"control--ogrl-gv-05","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Triaging reports of misconduct supports identifying and addressing deviations from expected conduct.\n"},{"id":"mapping--ogrl-gv-05-to-soc2-cc2-2","source_ref":"control--ogrl-gv-05","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A confidential reporting channel provides a separate internal communication path for raising concerns.\n"}],"yaml_path":"library/control/ogrl-gv-05.yaml"},{"id":"control--ogrl-gv-06","slug":"ogrl-gv-06","display_id":"OGRL-GV-06","name":"Security Objectives and Performance Measures","family":"gv","control_type":"detective","frequency":"quarterly","summary":"Define measurable security objectives and report performance against them to leadership on a fixed cadence.\n","statement":"Define security objectives for in-scope systems, each with at least one measurable performance metric and target, approved by {{ metrics_owner }}. Collect the metrics {{ metrics_collection_frequency }} and report results, trends, and missed targets to {{ metrics_audience }} {{ metrics_reporting_frequency }}.\n","objective":"Security objectives are specific enough to assess risk and performance against, and leadership sees measured results over time.\n","guidance":"Pick a small set of metrics tied to commitments: vulnerability SLA adherence, access review completion, training completion, MFA coverage, mean time to detect and resolve incidents, availability against SLA. Most can be pulled automatically from the compliance platform, ticketing, and monitoring. Evidence: the objectives document and dated metric reports.\n","parameters":{"metrics_audience":{"label":"Metric report audience","value":"executive leadership"},"metrics_collection_frequency":{"label":"Metric collection frequency","value":"monthly"},"metrics_owner":{"label":"Approver of objectives and metrics","value":"the security leader"},"metrics_reporting_frequency":{"label":"Metric reporting frequency","value":"quarterly"}},"tags":["governance","metrics","objectives"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-06-to-800-53-pm-6","source_ref":"control--ogrl-gv-06","target_ref":"requirement--nist-sp-800-53-r5-pm-6","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Developing, monitoring, and reporting security metrics meets the security half of this requirement; privacy measures are not covered.\n"},{"id":"mapping--ogrl-gv-06-to-soc2-cc3-1","source_ref":"control--ogrl-gv-06","target_ref":"requirement--soc2-tsc-2017-cc3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Measurable security objectives give a clear basis for identifying and assessing risks to achieving them.\n"},{"id":"mapping--ogrl-gv-06-to-soc2-cc4-1","source_ref":"control--ogrl-gv-06","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Periodic metric reporting is a form of ongoing evaluation of whether controls are performing.\n"}],"yaml_path":"library/control/ogrl-gv-06.yaml"},{"id":"control--ogrl-gv-07","slug":"ogrl-gv-07","display_id":"OGRL-GV-07","name":"External Commitments and Customer Communication","family":"gv","control_type":"preventive","frequency":"annual","summary":"Document security, availability, and confidentiality commitments made to customers, publish them, and give advance notice of material changes.\n","statement":"Maintain a register of the security, availability, and confidentiality commitments made to customers and users (for example in terms of service, data processing agreements, SLAs, and the trust center). Make current commitments and instructions for reporting security issues available through {{ customer_channel }}, notify affected customers at least {{ change_notice_period }} before a material reduction in commitments takes effect, and review the register {{ commitment_review_frequency }}.\n","objective":"Customers know what the organization has committed to and how to raise security concerns, and commitments do not change without notice.\n","guidance":"Legal or the commercial owner usually maintains the register; security confirms each commitment is backed by a control. A public trust center or security page with a security contact (for example security.txt) covers the publication channel. Evidence: the register, the published page, and notices sent for changes.\n","parameters":{"change_notice_period":{"label":"Advance notice for material commitment changes","value":"30 days"},"commitment_review_frequency":{"label":"Commitment register review frequency","value":"at least annually"},"customer_channel":{"label":"Customer communication channel","value":"the public trust center and customer contracts"}},"tags":["governance","customer-commitments","communication"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-07-to-soc2-cc2-3","source_ref":"control--ogrl-gv-07","target_ref":"requirement--soc2-tsc-2017-cc2-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Publishing commitments and a security contact covers communication with customers; communication with other external parties is outside this control.\n"}],"yaml_path":"library/control/ogrl-gv-07.yaml"},{"id":"control--ogrl-gv-08","slug":"ogrl-gv-08","display_id":"OGRL-GV-08","name":"System Description and Security Plan","family":"gv","control_type":"preventive","frequency":"annual","summary":"Maintain an approved description of each in-scope system covering its boundary, components, data, and controls, and keep it current.\n","statement":"Maintain a system description for each in-scope system that documents its boundary, infrastructure and software components, subservice organizations and other dependencies, data flows, information types handled, user roles, and the controls in place. The description is approved by {{ plan_approver }}, distributed to {{ plan_distribution }}, stored where only its owners can modify it, reviewed {{ plan_review_frequency }}, and updated when the system or its environment changes significantly or assessments identify problems.\n","objective":"An accurate, approved account of each system's scope and controls exists and is available to those who rely on it.\n","guidance":"This is the document a SOC 2 report's system description is drawn from. Keep the architecture and data-flow diagrams generated from or reconciled with the component inventory (OGRL-AM-01). Link controls to the OGRL control set rather than restating them. Evidence: the current version, its approval, and change history.\n","parameters":{"plan_approver":{"label":"System description approver","value":"the security leader and the system owner"},"plan_distribution":{"label":"Recipients of the system description and changes","value":"engineering leadership, the compliance team, and auditors"},"plan_review_frequency":{"label":"System description review frequency","value":"at least annually"}},"tags":["governance","system-description","security-plan"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-a","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#a","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Covers components, operational context, roles, information types, dependencies, and controls; security categorization, privacy risk results, and design risk determinations are not required.\n"},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-b","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pl_02_odp_02":"plan_distribution"},"summary":"Distribution of the description and its changes to named recipients meets the plan distribution requirement.\n"},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-c","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pl_02_odp_03":"plan_review_frequency"},"summary":"Periodic review of the system description meets the plan review requirement."},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-d","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Updating on significant change or assessment findings meets the plan update requirement.\n"},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-e","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Restricting modification to owners protects the plan from unauthorized change; disclosure protection relies on repository access controls.\n"},{"id":"mapping--ogrl-gv-08-to-soc2-cc2-1","source_ref":"control--ogrl-gv-08","target_ref":"requirement--soc2-tsc-2017-cc2-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A maintained system description is a key source of relevant, quality information about system scope and controls.\n"},{"id":"mapping--ogrl-gv-08-to-soc2-cc2-3","source_ref":"control--ogrl-gv-08","target_ref":"requirement--soc2-tsc-2017-cc2-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Sharing the system description with auditors and customers communicates system boundaries and controls externally.\n"}],"yaml_path":"library/control/ogrl-gv-08.yaml"},{"id":"control--ogrl-gv-09","slug":"ogrl-gv-09","display_id":"OGRL-GV-09","name":"Acceptable Use and Rules of Behavior","family":"gv","control_type":"preventive","frequency":"annual","summary":"Publish an acceptable use policy and obtain acknowledgment before access is granted and periodically thereafter.\n","statement":"Maintain an acceptable use policy that sets out workforce responsibilities and expected behavior when using company systems, devices, and data. Require each workforce member to acknowledge the policy before access to company systems is granted, and to re-acknowledge it {{ reacknowledgment_frequency }} and after material revisions. Review and update the policy {{ aup_review_frequency }}.\n","objective":"Everyone with system access has agreed to defined rules for using systems and data before receiving access, and the rules stay current.\n","guidance":"Cover device security, approved software and SaaS, handling of customer data, use of AI tools, personal use, and reporting of suspected incidents. Gate account provisioning (OGRL-AC-01) on a recorded acknowledgment in the HRIS or compliance platform. Evidence: the policy, its review history, and per-person acknowledgment timestamps compared with access grant dates.\n","parameters":{"aup_review_frequency":{"label":"Acceptable use policy review frequency","value":"at least annually"},"reacknowledgment_frequency":{"label":"Re-acknowledgment frequency","value":"annually"}},"tags":["governance","acceptable-use","workforce"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-09-to-800-53-pl-4","source_ref":"control--ogrl-gv-09","target_ref":"requirement--nist-sp-800-53-r5-pl-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pl_04_odp_01":"aup_review_frequency","pl_04_odp_03":"reacknowledgment_frequency"},"summary":"Published rules, acknowledgment before access, periodic review, and periodic or revision-driven re-acknowledgment together cover every part of rules of behavior.\n"},{"id":"mapping--ogrl-gv-09-to-soc2-cc1-1","source_ref":"control--ogrl-gv-09","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Acknowledged rules of behavior communicate expected conduct when using systems."},{"id":"mapping--ogrl-gv-09-to-soc2-cc2-2","source_ref":"control--ogrl-gv-09","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The policy and acknowledgment communicate security responsibilities to every user.\n"},{"id":"mapping--ogrl-gv-09-to-soc2-cc5-3","source_ref":"control--ogrl-gv-09","target_ref":"requirement--soc2-tsc-2017-cc5-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The acceptable use policy is one of the policies through which expected behavior is put into practice.\n"}],"yaml_path":"library/control/ogrl-gv-09.yaml"},{"id":"control--ogrl-gv-10","slug":"ogrl-gv-10","display_id":"OGRL-GV-10","name":"Periodic Control Assessment","family":"gv","control_type":"detective","frequency":"annual","summary":"Independently assess whether in-scope controls are designed and operating effectively on a fixed cadence, and report the results.\n","statement":"Assess the design and operating effectiveness of in-scope controls {{ assessment_frequency }} using {{ assessor }} independent of the people who operate the controls. Each assessment follows a written plan defining scope, controls, test procedures, and roles that {{ plan_approver }} approves before testing begins, produces a written report, and delivers results to {{ results_recipients }}.\n","objective":"Leadership has periodic, independent evidence of whether controls are implemented correctly and achieving their intended outcome.\n","guidance":"An external SOC 2 audit can serve as the assessment for the controls it covers; a readiness assessment or internal audit fills gaps in years without one. Retain the approved plan, workpapers or sample lists, and the final report. Findings flow to deficiency tracking (OGRL-GV-12).\n","parameters":{"assessment_frequency":{"label":"Control assessment frequency","value":"at least annually"},"assessor":{"label":"Assessor","value":"an internal audit function or a qualified third-party assessor"},"plan_approver":{"label":"Assessment plan approver","value":"the security leader"},"results_recipients":{"label":"Recipients of assessment results","value":"executive leadership and the board or its designated committee"}},"tags":["governance","control-assessment","audit"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-10-to-800-53-ca-2","source_ref":"control--ogrl-gv-10","target_ref":"requirement--nist-sp-800-53-r5-ca-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_02_odp_01":"assessment_frequency","ca_02_odp_02":"results_recipients"},"summary":"Covers assessor selection, an approved assessment plan, periodic assessment, reporting, and distribution of results.\n"},{"id":"mapping--ogrl-gv-10-to-soc2-cc4-1","source_ref":"control--ogrl-gv-10","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Periodic independent assessment is a separate evaluation; ongoing evaluations are addressed by continuous monitoring.\n"},{"id":"mapping--ogrl-gv-10-to-soc2-cc5-1","source_ref":"control--ogrl-gv-10","target_ref":"requirement--soc2-tsc-2017-cc5-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Assessment results inform whether selected control activities adequately mitigate risk.\n"}],"yaml_path":"library/control/ogrl-gv-10.yaml"},{"id":"control--ogrl-gv-11","slug":"ogrl-gv-11","display_id":"OGRL-GV-11","name":"Continuous Control Monitoring","family":"gv","control_type":"detective","frequency":"continuous","summary":"Automatically test in-scope controls on an ongoing basis, act on failures, and report control health to leadership.\n","statement":"Continuously monitor in-scope controls using automated checks that track {{ monitored_metrics }}, executed {{ monitoring_frequency }}. Assign an owner and a remediation ticket to each failing check within {{ triage_sla }}, and report control health and trends to {{ status_audience }} {{ status_reporting_frequency }}.\n","objective":"Control failures between periodic assessments are detected quickly, assigned, and resolved, and leadership sees current control health.\n","guidance":"Compliance automation platforms and cloud security posture tools provide most checks out of the box (MFA enforcement, encryption at rest, logging enabled, offboarding completed, background checks on file). Tune checks to the controls in scope, route failures to the owning team's queue, and retain the dashboard history. Persistent failures become deficiencies under OGRL-GV-12.\n","parameters":{"monitored_metrics":{"label":"Monitored control metrics","value":"pass or fail status of automated control tests and open failures by age and severity\n"},"monitoring_frequency":{"label":"Automated check frequency","value":"at least daily"},"status_audience":{"label":"Control health report audience","value":"the security leader and executive leadership"},"status_reporting_frequency":{"label":"Control health reporting frequency","value":"monthly"},"triage_sla":{"label":"Failing check triage deadline","value":"2 business days"}},"tags":["governance","continuous-monitoring","automation"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-a","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_07_odp_01":"monitored_metrics"},"summary":"Defines the control metrics that automated monitoring tracks."},{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-d","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Automated checks provide ongoing monitoring of the defined metrics."},{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-f","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Owner assignment and remediation tickets for failing checks are the response actions to monitoring results.\n"},{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-g","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#g","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_7_prm_4":"status_audience","ca_7_prm_5":"status_reporting_frequency"},"summary":"Regular control health reporting to named recipients meets the status reporting requirement.\n"},{"id":"mapping--ogrl-gv-11-to-soc2-cc4-1","source_ref":"control--ogrl-gv-11","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated checks are ongoing evaluations of control operation; separate evaluations are covered by periodic assessment.\n"},{"id":"mapping--ogrl-gv-11-to-soc2-cc7-1","source_ref":"control--ogrl-gv-11","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Automated configuration checks detect drift that could introduce vulnerabilities.\n"}],"yaml_path":"library/control/ogrl-gv-11.yaml"},{"id":"control--ogrl-gv-12","slug":"ogrl-gv-12","display_id":"OGRL-GV-12","name":"Deficiency Tracking and Remediation","family":"gv","control_type":"corrective","frequency":"monthly","summary":"Track every control deficiency to remediation with an owner and due date, and review open items with leadership.\n","statement":"Record every control deficiency identified by assessments, audits, continuous monitoring, penetration tests, or incidents in a deficiency register with an owner, severity, remediation plan, and due date. Remediate deficiencies within {{ remediation_sla }}, review open and overdue items with {{ review_audience }} {{ review_frequency }}, and escalate items past due to executive leadership.\n","objective":"Identified control weaknesses are communicated to those who can fix them and are corrected in a timely, tracked way.\n","guidance":"A dedicated project in the ticketing system or the compliance platform's findings module works as the register. Close items only with evidence of the fix and, for significant deficiencies, a retest. Evidence: the register with timestamps and the review meeting notes.\n","parameters":{"remediation_sla":{"label":"Deficiency remediation deadline","value":"30 days for high severity and 90 days for others, unless a documented risk acceptance applies\n"},"review_audience":{"label":"Deficiency review audience","value":"the security leader and responsible control owners"},"review_frequency":{"label":"Deficiency review frequency","value":"monthly"}},"tags":["governance","deficiency-management","remediation"],"tests":[],"mappings":[{"id":"mapping--ogrl-gv-12-to-800-53-ca-5","source_ref":"control--ogrl-gv-12","target_ref":"requirement--nist-sp-800-53-r5-ca-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_05_odp":"review_frequency"},"summary":"The deficiency register is the plan of action and milestones, updated on a fixed cadence from assessment, audit, and monitoring findings.\n"},{"id":"mapping--ogrl-gv-12-to-soc2-cc4-2","source_ref":"control--ogrl-gv-12","target_ref":"requirement--soc2-tsc-2017-cc4-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recording, reviewing, and escalating deficiencies communicates them to the parties responsible for corrective action.\n"}],"yaml_path":"library/control/ogrl-gv-12.yaml"},{"id":"control--ogrl-hr-01","slug":"ogrl-hr-01","display_id":"OGRL-HR-01","name":"Background Screening","family":"hr","control_type":"preventive","frequency":"event-driven","summary":"Screen employees and contractors before they receive access to production systems or customer data, and rescreen when risk changes.\n","statement":"Complete {{ screening_scope }} for every employee and contractor, to the extent permitted by applicable law, before granting access to production systems or customer data, and rescreen personnel {{ rescreening_conditions }}.\n","objective":"Reduce insider risk by confirming that individuals entrusted with systems and data have been vetted before access is granted.\n","guidance":"Use a background-check provider integrated with the HRIS or applicant tracking system so the check status gates the access-provisioning ticket. Calibrate check depth to the role and jurisdiction, document local-law exceptions, and retain completion records (not report contents) as audit evidence. Contractors supplied through an agency may be covered by the agency's screening if the contract requires it.\n","parameters":{"rescreening_conditions":{"label":"Conditions that trigger rescreening","value":"upon transfer into a privileged or high-risk role"},"screening_scope":{"label":"Required screening checks","value":"identity verification, criminal history, and employment history checks"}},"tags":["personnel-security","screening","onboarding"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-01-to-800-53-ps-3","source_ref":"control--ogrl-hr-01","target_ref":"requirement--nist-sp-800-53-r5-ps-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_03_odp_01":"rescreening_conditions"},"summary":"Screening before access plus condition-based rescreening covers both parts of PS-3.\n"},{"id":"mapping--ogrl-hr-01-to-soc2-cc1-1","source_ref":"control--ogrl-hr-01","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Vetting personnel supports the integrity expectations of CC1.1 but does not address the broader tone and conduct standards.\n"},{"id":"mapping--ogrl-hr-01-to-soc2-cc1-4","source_ref":"control--ogrl-hr-01","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Pre-access screening is one element of the workforce competence and trustworthiness expectations in CC1.4.\n"}],"yaml_path":"library/control/ogrl-hr-01.yaml"},{"id":"control--ogrl-hr-02","slug":"ogrl-hr-02","display_id":"OGRL-HR-02","name":"Personnel Offboarding","family":"hr","control_type":"preventive","frequency":"event-driven","summary":"Run a documented offboarding checklist for every departure and an access review for every internal transfer.\n","statement":"For every departing employee or contractor, complete a documented offboarding checklist that disables system access within {{ access_disable_sla }} of separation, revokes associated credentials, keys, and tokens, recovers company-issued devices and sanitizes them before reassignment, briefs the individual on {{ exit_briefing_topics }}, and transfers ownership of the individual's data and systems to a designated owner; when an individual transfers roles, review and adjust existing access to match the new role within {{ transfer_review_sla }}.\n","objective":"Ensure departing and transferring personnel retain no access, credentials, or company assets beyond what their current status requires.\n","guidance":"Trigger the checklist automatically from the HRIS termination or job-change event into the ticketing system. Use the identity provider to suspend SSO and revoke sessions, then sweep systems outside SSO (cloud root or break-glass credentials, SSH keys, personal access tokens, API keys). Track device return through the MDM inventory and remote-wipe unreturned devices. Account disablement itself is also governed by OGRL-AC-01; this control evidences the full offboarding workflow.\n","parameters":{"access_disable_sla":{"label":"Maximum time to disable access after separation","value":"24 hours"},"exit_briefing_topics":{"label":"Topics covered in the exit briefing","value":"continuing confidentiality obligations and return of company property"},"transfer_review_sla":{"label":"Time to review access after an internal transfer","value":"5 business days"}},"tags":["personnel-security","offboarding","access-revocation"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-02-to-800-53-ps-4","source_ref":"control--ogrl-hr-02","target_ref":"requirement--nist-sp-800-53-r5-ps-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_04_odp_01":"access_disable_sla","ps_04_odp_02":"exit_briefing_topics"},"summary":"The offboarding checklist covers access disablement, credential revocation, exit briefing, property recovery, and retained data access required by PS-4.\n"},{"id":"mapping--ogrl-hr-02-to-800-53-ps-5-a","source_ref":"control--ogrl-hr-02","target_ref":"requirement--nist-sp-800-53-r5-ps-5#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The transfer access review confirms continued need for existing access when personnel change roles.\n"},{"id":"mapping--ogrl-hr-02-to-800-53-ps-5-c","source_ref":"control--ogrl-hr-02","target_ref":"requirement--nist-sp-800-53-r5-ps-5#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Adjusting access to match the new role after a transfer is the modification PS-5(c) calls for.\n"},{"id":"mapping--ogrl-hr-02-to-soc2-cc6-2","source_ref":"control--ogrl-hr-02","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Removing credentials and access at separation and transfer contributes to CC6.2; account registration and authorization are covered elsewhere.\n"},{"id":"mapping--ogrl-hr-02-to-soc2-cc6-5","source_ref":"control--ogrl-hr-02","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recovering and sanitizing devices from departing personnel contributes to CC6.5 but does not cover general asset disposal.\n"}],"yaml_path":"library/control/ogrl-hr-02.yaml"},{"id":"control--ogrl-hr-03","slug":"ogrl-hr-03","display_id":"OGRL-HR-03","name":"Confidentiality and Access Agreements","family":"hr","control_type":"preventive","frequency":"event-driven","summary":"Require signed confidentiality and acceptable-use agreements before access, and refresh acknowledgements periodically.\n","statement":"Require every employee and contractor to sign a confidentiality agreement and acknowledge the acceptable use and information security policies before receiving access to systems or confidential information; review the agreement templates {{ agreement_review_frequency }} and obtain renewed acknowledgement {{ reacknowledgement_frequency }} and whenever the agreements materially change.\n","objective":"Establish enforceable, documented obligations for protecting organizational and customer information before anyone is given access to it.\n","guidance":"Collect signatures through the HRIS or e-signature tool during onboarding and gate access provisioning on completion. Track annual re-acknowledgement alongside awareness training to reduce friction. Legal should own the templates; security should own the policy content they reference.\n","parameters":{"agreement_review_frequency":{"label":"Agreement template review frequency","value":"annually"},"reacknowledgement_frequency":{"label":"Re-acknowledgement frequency","value":"annually"}},"tags":["personnel-security","confidentiality","onboarding"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-03-to-800-53-ps-6","source_ref":"control--ogrl-hr-03","target_ref":"requirement--nist-sp-800-53-r5-ps-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_06_odp_01":"agreement_review_frequency","ps_06_odp_02":"reacknowledgement_frequency"},"summary":"Documented agreements signed before access, periodically reviewed, and re-signed on change or cadence satisfy PS-6.\n"},{"id":"mapping--ogrl-hr-03-to-soc2-c1-1","source_ref":"control--ogrl-hr-03","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Binding personnel to confidentiality obligations contributes to protecting confidential information under C1.1.\n"},{"id":"mapping--ogrl-hr-03-to-soc2-cc1-1","source_ref":"control--ogrl-hr-03","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Signed policy acknowledgements help communicate and enforce expected conduct, one aspect of CC1.1.\n"}],"yaml_path":"library/control/ogrl-hr-03.yaml"},{"id":"control--ogrl-hr-04","slug":"ogrl-hr-04","display_id":"OGRL-HR-04","name":"Contractor and Third-Party Personnel Security","family":"hr","control_type":"preventive","frequency":"event-driven","summary":"Hold external personnel with system access to the organization's personnel security requirements and require timely notice of their departures.\n","statement":"Require providers whose personnel access organizational systems or confidential data to apply the organization's personnel security requirements, including screening, confidentiality agreements, and security training, with roles and responsibilities documented in the contract; require the provider to notify {{ notification_recipient }} of any transfer or termination of such personnel within {{ notification_window }}; and verify provider compliance {{ compliance_verification_frequency }}.\n","objective":"Ensure external personnel with access meet the same security expectations as employees and lose access promptly when their engagement ends.\n","guidance":"Sponsor every contractor account through an internal owner and give it an end date in the identity provider. Include personnel security clauses in staffing agreements and request attestation of screening and training completion. Reconcile active contractor accounts against the provider's roster as part of verification.\n","parameters":{"compliance_verification_frequency":{"label":"Provider compliance verification frequency","value":"annually"},"notification_recipient":{"label":"Recipient of provider personnel change notices","value":"the internal sponsor and the security team"},"notification_window":{"label":"Provider notification deadline","value":"1 business day"}},"tags":["personnel-security","contractors","third-party"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-04-to-800-53-ps-7","source_ref":"control--ogrl-hr-04","target_ref":"requirement--nist-sp-800-53-r5-ps-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_07_odp_01":"notification_recipient","ps_07_odp_02":"notification_window"},"summary":"Contractual personnel security requirements, change notifications, and compliance verification cover each part of PS-7.\n"},{"id":"mapping--ogrl-hr-04-to-soc2-cc1-4","source_ref":"control--ogrl-hr-04","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Extending screening and training expectations to external personnel supports the workforce expectations of CC1.4.\n"},{"id":"mapping--ogrl-hr-04-to-soc2-cc9-2","source_ref":"control--ogrl-hr-04","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Imposing personnel security obligations on providers addresses one dimension of vendor risk management under CC9.2.\n"}],"yaml_path":"library/control/ogrl-hr-04.yaml"},{"id":"control--ogrl-hr-05","slug":"ogrl-hr-05","display_id":"OGRL-HR-05","name":"Personnel Sanctions","family":"hr","control_type":"corrective","frequency":"event-driven","summary":"Apply a documented disciplinary process to security and privacy policy violations and notify designated roles when it is invoked.\n","statement":"Apply the documented disciplinary process to any employee or contractor who violates information security or privacy policies, record each case and its outcome, and notify {{ sanction_notification_recipient }} within {{ sanction_notification_window }} when a formal sanction is initiated, identifying the individual and the reason.\n","objective":"Hold personnel accountable for policy violations consistently and ensure security leadership is aware of sanctioned individuals.\n","guidance":"Reference the sanctions process in the code of conduct and acceptable use policy. HR owns case records; security receives notification so it can review the individual's access. Keep a log of cases (even if empty for the period) to evidence operation.\n","parameters":{"sanction_notification_recipient":{"label":"Roles notified when a sanction is initiated","value":"the security lead and the individual's manager"},"sanction_notification_window":{"label":"Sanction notification deadline","value":"2 business days"}},"tags":["personnel-security","accountability","discipline"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-05-to-800-53-ps-8","source_ref":"control--ogrl-hr-05","target_ref":"requirement--nist-sp-800-53-r5-ps-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_08_odp_01":"sanction_notification_recipient","ps_08_odp_02":"sanction_notification_window"},"summary":"A formal sanctions process with timely notification of designated roles satisfies both parts of PS-8.\n"},{"id":"mapping--ogrl-hr-05-to-soc2-cc1-1","source_ref":"control--ogrl-hr-05","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Consistently addressing deviations from expected conduct supports the integrity commitments of CC1.1.\n"},{"id":"mapping--ogrl-hr-05-to-soc2-cc1-5","source_ref":"control--ogrl-hr-05","target_ref":"requirement--soc2-tsc-2017-cc1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Disciplinary action for security violations is a mechanism for holding individuals accountable under CC1.5.\n"}],"yaml_path":"library/control/ogrl-hr-05.yaml"},{"id":"control--ogrl-hr-06","slug":"ogrl-hr-06","display_id":"OGRL-HR-06","name":"Position Descriptions and Security Responsibilities","family":"hr","control_type":"preventive","frequency":"annual","summary":"Document security and privacy responsibilities in every job description and keep them current.\n","statement":"Include security and privacy responsibilities in the documented description of every position, with role-specific duties for {{ elevated_roles }}, and review position descriptions {{ description_review_frequency }} and when roles materially change.\n","objective":"Make each individual's security and privacy obligations explicit so they can be communicated, trained, and enforced.\n","guidance":"Add a standard security-responsibilities clause to all job descriptions and role-specific clauses for engineering, operations, and leadership roles. Store current descriptions in the HRIS or a controlled document repository and record review dates.\n","parameters":{"description_review_frequency":{"label":"Position description review frequency","value":"annually"},"elevated_roles":{"label":"Roles requiring role-specific security duties","value":"engineers, administrators, and security and privacy personnel"}},"tags":["personnel-security","roles-and-responsibilities","governance"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-06-to-800-53-ps-9","source_ref":"control--ogrl-hr-06","target_ref":"requirement--nist-sp-800-53-r5-ps-9","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"The control incorporates security and privacy responsibilities into position descriptions as PS-9 requires and adds periodic review.\n"},{"id":"mapping--ogrl-hr-06-to-soc2-cc1-3","source_ref":"control--ogrl-hr-06","target_ref":"requirement--soc2-tsc-2017-cc1-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Defining security responsibilities per position supports the assignment of responsibilities addressed by CC1.3.\n"},{"id":"mapping--ogrl-hr-06-to-soc2-cc1-4","source_ref":"control--ogrl-hr-06","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented role expectations provide a basis for hiring and developing competent personnel under CC1.4.\n"}],"yaml_path":"library/control/ogrl-hr-06.yaml"},{"id":"control--ogrl-hr-07","slug":"ogrl-hr-07","display_id":"OGRL-HR-07","name":"Security and Privacy Awareness Training","family":"hr","control_type":"preventive","frequency":"annual","summary":"Train all personnel in security and privacy awareness at onboarding and on a recurring cadence, reinforced by phishing simulations.\n","statement":"Require every employee and contractor to complete security and privacy awareness training within {{ onboarding_training_window }} of starting and {{ training_frequency }} thereafter; conduct simulated phishing exercises {{ phishing_simulation_frequency }}; and update training content {{ content_review_frequency }} and after {{ content_update_events }}, incorporating lessons learned from security incidents.\n","objective":"Equip all personnel to recognize and report threats and to handle information in line with security and privacy policies.\n","guidance":"Use a training platform integrated with the HRIS so new hires are enrolled automatically and completion is tracked; escalate overdue training to managers and consider suspending access after a grace period. Cover phishing, credential hygiene, data handling, incident reporting, and privacy basics. Feed internal incidents and phishing simulation results into content updates.\n","parameters":{"content_review_frequency":{"label":"Training content review frequency","value":"annually"},"content_update_events":{"label":"Events that trigger content updates","value":"significant security incidents, policy changes, or emerging threats"},"onboarding_training_window":{"label":"Deadline for initial training after start date","value":"30 days"},"phishing_simulation_frequency":{"label":"Phishing simulation frequency","value":"at least quarterly"},"training_frequency":{"label":"Recurring training frequency","value":"annually"}},"tags":["training","awareness","phishing"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-07-to-800-53-at-2-1","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Simulated phishing exercises are practical exercises that simulate real attack events.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-a-1","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"at_02_odp_01":"training_frequency","at_02_odp_02":"training_frequency"},"summary":"Training at onboarding and on a recurring cadence covers initial and periodic literacy training.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-b","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Simulated phishing exercises are the awareness technique the control employs.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-c","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"at_02_odp_06":"content_review_frequency","at_02_odp_07":"content_update_events"},"summary":"Content is updated on a defined cadence and after defined events.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-d","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Lessons learned from security incidents are incorporated into training content.\n"},{"id":"mapping--ogrl-hr-07-to-soc2-cc1-4","source_ref":"control--ogrl-hr-07","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recurring security training develops personnel competence, one element of CC1.4.\n"},{"id":"mapping--ogrl-hr-07-to-soc2-cc2-2","source_ref":"control--ogrl-hr-07","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Awareness training is a primary channel for communicating security responsibilities internally under CC2.2.\n"}],"yaml_path":"library/control/ogrl-hr-07.yaml"},{"id":"control--ogrl-hr-08","slug":"ogrl-hr-08","display_id":"OGRL-HR-08","name":"Role-Based Security Training","family":"hr","control_type":"preventive","frequency":"annual","summary":"Provide additional security training tailored to roles with elevated access or security-relevant duties.\n","statement":"Provide role-specific security training to {{ trained_roles }} before they are granted access to perform those duties, {{ role_training_frequency }} thereafter, and when significant system changes alter their responsibilities; update the content {{ role_content_review_frequency }} and after {{ role_content_update_events }}, incorporating lessons learned from security incidents.\n","objective":"Ensure personnel with elevated access or security duties have the specific knowledge needed to perform them securely.\n","guidance":"Typical modules include secure coding and OWASP topics for engineers, cloud and IAM hygiene for infrastructure administrators, incident handling for on-call responders, and privacy obligations for staff handling personal data. Track completion per role in the training platform and gate production access requests on completion.\n","parameters":{"role_content_review_frequency":{"label":"Role-based content review frequency","value":"annually"},"role_content_update_events":{"label":"Events that trigger role-based content updates","value":"significant security incidents or major technology changes"},"role_training_frequency":{"label":"Recurring role-based training frequency","value":"annually"},"trained_roles":{"label":"Roles requiring role-based training","value":"engineers with production or source code access, on-call incident responders, and administrators of in-scope systems\n"}},"tags":["training","secure-development","roles-and-responsibilities"],"tests":[],"mappings":[{"id":"mapping--ogrl-hr-08-to-800-53-at-3","source_ref":"control--ogrl-hr-08","target_ref":"requirement--nist-sp-800-53-r5-at-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"at_03_odp_01":"trained_roles","at_03_odp_02":"trained_roles","at_03_odp_03":"role_training_frequency","at_03_odp_04":"role_content_review_frequency","at_03_odp_05":"role_content_update_events"},"summary":"Role-specific training before access, on a cadence, on system change, with content updates and lessons learned covers all parts of AT-3.\n"},{"id":"mapping--ogrl-hr-08-to-soc2-cc1-4","source_ref":"control--ogrl-hr-08","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Role-specific training develops the competence of personnel in security-relevant roles, part of CC1.4.\n"},{"id":"mapping--ogrl-hr-08-to-soc2-cc2-2","source_ref":"control--ogrl-hr-08","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Role-based training communicates role-specific security responsibilities, one aspect of CC2.2.\n"}],"yaml_path":"library/control/ogrl-hr-08.yaml"},{"id":"control--ogrl-ir-01","slug":"ogrl-ir-01","display_id":"OGRL-IR-01","name":"Incident Response Plan and Tabletop Testing","family":"ir","control_type":"corrective","frequency":"annual","summary":"Maintain a documented security incident response plan and exercise it regularly through tabletop or simulated drills.\n","statement":"Maintain a documented security incident response plan with defined roles and escalation paths, and test response effectiveness {{ ir_test_cadence }} using {{ ir_test_method }}.\n","objective":"Ensure personnel can rapidly detect, contain, eradicate, recover from, and report security incidents.\n","guidance":"Document post-incident lessons learned, track corrective action items to closure, and update contact trees whenever on-call rotations or regulatory notification obligations change.\n","parameters":{"ir_test_cadence":{"label":"Incident response test frequency","value":"at least annually"},"ir_test_method":{"label":"Incident response test method","value":"structured tabletop exercises and simulated incident drills"}},"tags":["incident-response","tabletop","resilience"],"tests":[{"id":"test--ogrl-ir-01-ir-testing","slug":"ogrl-ir-01-ir-testing","name":"Verify Annual Incident Response Tabletop Exercise","method":"manual","interval":"annual","required":true,"description":"Examine the current incident response plan, after-action report from the most recent tabletop exercise, and closure evidence for identified follow-up tasks.\n","objective_refs":[],"yaml_path":"library/test/ogrl-ir-01-ir-testing.yaml"}],"mappings":[{"id":"mapping--ogrl-ir-01-to-800-171-03-06-03","source_ref":"control--ogrl-ir-01","target_ref":"requirement--nist-sp-800-171-r3-03-06-03","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"a_03_06_03_odp_01":"ir_test_cadence"},"summary":"Periodic incident response tabletop drills satisfy SP 800-171 03.06.03."},{"id":"mapping--ogrl-ir-01-to-800-53-ir-3","source_ref":"control--ogrl-ir-01","target_ref":"requirement--nist-sp-800-53-r5-ir-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ir_03_odp_01":"ir_test_cadence","ir_03_odp_02":"ir_test_method"},"summary":"Scheduled tabletop exercises and drills directly satisfy NIST IR-3 incident response testing.\n"},{"id":"mapping--ogrl-ir-01-to-soc2-cc7-3","source_ref":"control--ogrl-ir-01","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Incident response playbooks and exercises support event evaluation and response under SOC 2 CC7.3.\n"},{"id":"mapping--ogrl-ir-01-to-soc2-cc7-4","source_ref":"control--ogrl-ir-01","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A documented, tested response plan defines how identified incidents are responded to under CC7.4.\n"}],"yaml_path":"library/control/ogrl-ir-01.yaml"},{"id":"control--ogrl-ir-02","slug":"ogrl-ir-02","display_id":"OGRL-IR-02","name":"Incident Handling and Triage","family":"ir","control_type":"corrective","frequency":"event-driven","summary":"Triage suspected security incidents promptly against a defined severity scale and drive confirmed incidents through containment, eradication, and recovery.\n","statement":"Triage each suspected security incident within {{ triage_sla }} of it being reported or detected, classify it using {{ severity_scale }}, assign an incident commander, and handle confirmed incidents through containment, eradication, and recovery as defined in the incident response plan, escalating high-severity incidents to {{ escalation_contacts }}.\n","objective":"Ensure suspected incidents are evaluated quickly and consistently and that confirmed incidents are contained and resolved before they cause further harm.\n","guidance":"Route monitoring alerts and employee or customer reports into a single on-call intake such as a paging tool or dedicated incident channel. Define a severity matrix (for example SEV1-SEV4) keyed on data exposure, customer impact, and blast radius. Keep runbooks for common cloud SaaS scenarios such as compromised credentials, leaked secrets, malicious dependencies, and cloud account takeover: revoke sessions and keys, isolate workloads with security groups or by scaling to zero, and snapshot volumes and preserve logs for forensics before rebuilding. Coordinate with the disaster recovery plan when recovery requires restoration from backup. Evidence is the incident ticket showing triage time, severity, commander, and response actions.\n","parameters":{"escalation_contacts":{"label":"High-severity escalation contacts","value":"the security lead and executive leadership"},"severity_scale":{"label":"Incident severity classification scheme","value":"the documented incident severity matrix"},"triage_sla":{"label":"Incident triage time limit","value":"1 hour"}},"tags":["incident-response","triage","containment"],"tests":[],"mappings":[{"id":"mapping--ogrl-ir-02-to-800-53-ir-4-a","source_ref":"control--ogrl-ir-02","target_ref":"requirement--nist-sp-800-53-r5-ir-4#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Severity-based triage and plan-driven containment, eradication, and recovery implement the incident handling capability in IR-4(a).\n"},{"id":"mapping--ogrl-ir-02-to-800-53-ir-4-d","source_ref":"control--ogrl-ir-02","target_ref":"requirement--nist-sp-800-53-r5-ir-4#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A shared severity matrix and runbooks make incident handling consistent, contributing to the predictability IR-4(d) expects across the organization.\n"},{"id":"mapping--ogrl-ir-02-to-soc2-cc7-3","source_ref":"control--ogrl-ir-02","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Triage and severity classification determine whether security events are incidents requiring response.\n"},{"id":"mapping--ogrl-ir-02-to-soc2-cc7-4","source_ref":"control--ogrl-ir-02","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Containment, eradication, and recovery steps form the core of the organization's incident response activity.\n"}],"yaml_path":"library/control/ogrl-ir-02.yaml"},{"id":"control--ogrl-ir-03","slug":"ogrl-ir-03","display_id":"OGRL-IR-03","name":"Incident Tracking and Documentation","family":"ir","control_type":"detective","frequency":"event-driven","summary":"Record every security incident in a tracking system from detection through closure with a consistent set of required details.\n","statement":"Record every security incident in {{ incident_tracking_system }} from detection through closure, capturing at minimum the detection source, timeline, severity, affected systems and data, actions taken, responsible owner, and resolution, and retain incident records for {{ incident_record_retention }}.\n","objective":"Maintain a complete and reliable history of incidents that supports coordinated response, trend analysis, and audit evidence.\n","guidance":"Use a dedicated ticket type or project with mandatory fields rather than free-form chat threads, and link alerts, incident channel exports, and post-incident reviews to the record. Restrict who can delete incident records. Report incident counts, time to detect, and time to resolve to leadership periodically. Auditors typically sample incidents for completeness, so keep the register even in periods with no incidents and document that none occurred.\n","parameters":{"incident_record_retention":{"label":"Incident record retention period","value":"at least 3 years"},"incident_tracking_system":{"label":"Incident tracking system","value":"a dedicated incident ticket queue with mandatory fields"}},"tags":["incident-response","documentation","tracking"],"tests":[],"mappings":[{"id":"mapping--ogrl-ir-03-to-800-53-ir-5","source_ref":"control--ogrl-ir-03","target_ref":"requirement--nist-sp-800-53-r5-ir-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Recording every incident with required details through closure satisfies IR-5 incident tracking and documentation.\n"},{"id":"mapping--ogrl-ir-03-to-soc2-cc7-3","source_ref":"control--ogrl-ir-03","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented incident records evidence how security events were evaluated and classified.\n"},{"id":"mapping--ogrl-ir-03-to-soc2-cc7-4","source_ref":"control--ogrl-ir-03","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Incident records capture the response actions taken, supporting a defined and evidenced response process.\n"}],"yaml_path":"library/control/ogrl-ir-03.yaml"},{"id":"control--ogrl-ir-04","slug":"ogrl-ir-04","display_id":"OGRL-IR-04","name":"Incident Reporting and Customer Notification","family":"ir","control_type":"corrective","frequency":"event-driven","summary":"Require prompt internal reporting of suspected incidents and notify affected customers and authorities of confirmed incidents within defined deadlines.\n","statement":"Require personnel to report suspected security incidents to the security team through a published reporting channel within {{ internal_report_window }} of discovery, and report confirmed incidents affecting customer data or services to {{ external_notification_recipients }} within {{ external_notification_deadline }} of confirmation, or sooner where contract or law requires.\n","objective":"Ensure incidents reach the response team quickly and that external parties who rely on the system learn of incidents affecting them in time to protect themselves.\n","guidance":"Publish a reporting channel such as a security@ alias or chat channel and cover it in onboarding and awareness training. Maintain a notification matrix of contractual (MSA, DPA) and regulatory deadlines, such as GDPR supervisory-authority notice within 72 hours or public-company disclosure rules, and have legal review external notices. Keep pre-approved notification templates and use the status page for availability incidents. Retain copies of sent notifications as evidence.\n","parameters":{"external_notification_deadline":{"label":"External notification deadline","value":"72 hours"},"external_notification_recipients":{"label":"External incident notification recipients","value":"affected customers, regulators, law enforcement, and other parties as required by contract or law\n"},"internal_report_window":{"label":"Internal reporting time limit","value":"24 hours"}},"tags":["incident-response","notification","communication"],"tests":[],"mappings":[{"id":"mapping--ogrl-ir-04-to-800-53-ir-6-a","source_ref":"control--ogrl-ir-04","target_ref":"requirement--nist-sp-800-53-r5-ir-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ir_06_odp_01":"internal_report_window"},"summary":"Mandatory internal reporting of suspected incidents within a set window satisfies IR-6(a).\n"},{"id":"mapping--ogrl-ir-04-to-800-53-ir-6-b","source_ref":"control--ogrl-ir-04","target_ref":"requirement--nist-sp-800-53-r5-ir-6#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ir_06_odp_02":"external_notification_recipients"},"summary":"Reporting confirmed incidents to customers, regulators, and other required parties satisfies IR-6(b).\n"},{"id":"mapping--ogrl-ir-04-to-soc2-cc2-3","source_ref":"control--ogrl-ir-04","target_ref":"requirement--soc2-tsc-2017-cc2-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Notifying customers and authorities of incidents is one form of communicating with external parties about matters affecting internal control.\n"},{"id":"mapping--ogrl-ir-04-to-soc2-cc7-4","source_ref":"control--ogrl-ir-04","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Internal escalation and external notification are part of responding to identified incidents.\n"}],"yaml_path":"library/control/ogrl-ir-04.yaml"},{"id":"control--ogrl-ir-05","slug":"ogrl-ir-05","display_id":"OGRL-IR-05","name":"Post-Incident Review","family":"ir","control_type":"corrective","frequency":"event-driven","summary":"Conduct a documented post-incident review for significant incidents and track the resulting improvements to closure.\n","statement":"Complete a documented post-incident review within {{ review_deadline }} of resolving each incident rated {{ review_severity_threshold }}, identifying root cause and contributing factors, and track the resulting corrective actions to closure, including updates to incident response procedures, training, and testing.\n","objective":"Prevent recurrence of incidents and continuously improve detection, response, and recovery capability.\n","guidance":"Use a blameless postmortem template covering timeline, impact, root cause, detection gaps, and what went well. File corrective actions in the engineering backlog with owners and due dates and review open items in a recurring security meeting. Feed real incident scenarios into the next tabletop exercise (OGRL-IR-01) and update runbooks and detection rules. Evidence is the completed review linked to the incident record and the closed corrective-action tickets.\n","parameters":{"review_deadline":{"label":"Post-incident review deadline","value":"10 business days"},"review_severity_threshold":{"label":"Severity requiring a post-incident review","value":"high or critical severity"}},"tags":["incident-response","lessons-learned","root-cause"],"tests":[],"mappings":[{"id":"mapping--ogrl-ir-05-to-800-53-ir-4-c","source_ref":"control--ogrl-ir-05","target_ref":"requirement--nist-sp-800-53-r5-ir-4#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Post-incident reviews with tracked corrective actions feed lessons learned into procedures, training, and testing as IR-4(c) requires.\n"},{"id":"mapping--ogrl-ir-05-to-soc2-cc7-5","source_ref":"control--ogrl-ir-05","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Root-cause analysis and tracked improvements after incidents support recovery and prevention of recurrence.\n"}],"yaml_path":"library/control/ogrl-ir-05.yaml"},{"id":"control--ogrl-ir-06","slug":"ogrl-ir-06","display_id":"OGRL-IR-06","name":"Privacy Breach Handling and Notification","family":"ir","control_type":"corrective","frequency":"event-driven","summary":"Assess incidents involving personal information for harm and notification obligations, notify affected individuals and regulators on time, and record each breach.\n","statement":"For each incident involving personal information, follow the breach-response procedure in the incident response plan to assess the data and individuals affected, the likely harm to them, and available mitigations; determine notification obligations under {{ applicable_privacy_requirements }}; notify affected individuals and regulators within {{ breach_notification_deadline }} when required; and record the breach, harm assessment, and notification decision in {{ breach_register }}.\n","objective":"Ensure breaches of personal information are evaluated for harm, mitigated, and reported to affected individuals and authorities as legally and contractually required.\n","guidance":"Maintain a jurisdiction matrix of breach notification rules (for example GDPR 72-hour supervisory-authority notice, US state breach laws, HIPAA, and customer DPAs) and involve privacy counsel in every assessment. Consider data sensitivity, encryption status, and likelihood of misuse when assessing harm, and offer mitigations such as forced credential resets or credit monitoring where appropriate. Record decisions not to notify with their rationale. Where the organization acts as a processor, notify the controlling customer rather than individuals directly.\n","parameters":{"applicable_privacy_requirements":{"label":"Applicable privacy and breach notification requirements","value":"applicable privacy and breach notification laws, regulations, and customer contracts\n"},"breach_notification_deadline":{"label":"Breach notification deadline","value":"the shortest applicable legal or contractual deadline"},"breach_register":{"label":"Breach record location","value":"the privacy breach register"}},"tags":["privacy","breach-notification","incident-response"],"tests":[],"mappings":[{"id":"mapping--ogrl-ir-06-to-800-53-ir-8-1","source_ref":"control--ogrl-ir-06","target_ref":"requirement--nist-sp-800-53-r5-ir-8-1","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"The documented breach procedure covers notification determination, harm assessment and mitigation, and applicable privacy requirements, and additionally requires executing notifications.\n"},{"id":"mapping--ogrl-ir-06-to-soc2-p6-3","source_ref":"control--ogrl-ir-06","target_ref":"requirement--soc2-tsc-2017-p6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The breach register keeps a record of detected or reported breaches of personal information.\n"},{"id":"mapping--ogrl-ir-06-to-soc2-p6-6","source_ref":"control--ogrl-ir-06","target_ref":"requirement--soc2-tsc-2017-p6-6","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Timely breach notification to affected individuals and regulators addresses the notification aspect of this criterion.\n"}],"yaml_path":"library/control/ogrl-ir-06.yaml"},{"id":"control--ogrl-lm-01","slug":"ogrl-lm-01","display_id":"OGRL-LM-01","name":"Centralized Security Audit Logging and Retention","family":"lm","control_type":"detective","frequency":"continuous","summary":"Capture security-relevant authentication, authorization, and administrative logs centrally with tamper-resistant retention.\n","statement":"Log {{ logged_events }} across all in-scope systems to a centralized, access-controlled log store, review logging coverage {{ logging_review_cadence }}, and retain audit records for at least {{ retention_period }}.\n","objective":"Maintain reliable, tamper-resistant audit trails sufficient for forensic investigation and accountability.\n","guidance":"Synchronize system clocks via NTP, enforce append-only or write-once storage policies on log buckets, and ensure log shippers alert on ingestion drops.\n","parameters":{"logged_events":{"label":"Auditable security event types","value":"authentication attempts, privilege changes, configuration mutations, and sensitive data access\n"},"logging_review_cadence":{"label":"Logging scope review cadence","value":"annually"},"retention_period":{"label":"Minimum audit log retention period","value":"365 days"}},"tags":["logging","audit","retention"],"tests":[{"id":"test--ogrl-lm-01-audit-logging","slug":"ogrl-lm-01-audit-logging","name":"Verify Centralized Audit Logging Ingestion and Retention","method":"automated","interval":"daily","required":true,"description":"Confirm audit logging is enabled across all production accounts, logs flow into the central store, and bucket retention policies meet or exceed the configured minimum.\n","objective_refs":["requirement--nist-sp-800-53-r5-au-2#obj.c-1","requirement--nist-sp-800-53-r5-au-2#obj.e"],"yaml_path":"library/test/ogrl-lm-01-audit-logging.yaml"}],"mappings":[{"id":"mapping--ogrl-lm-01-to-iso27001-a-8-15","source_ref":"control--ogrl-lm-01","target_ref":"requirement--iso-iec-27001-2022-a-8-15","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Centralized security logging and retention satisfy ISO/IEC 27001:2022 A.8.15."},{"id":"mapping--ogrl-lm-01-to-800-171-03-03-01","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-171-r3-03-03-01","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"a_03_03_01_odp_01":"logged_events","a_03_03_01_odp_02":"logging_review_cadence"},"summary":"Centralized security event logging and review directly satisfy SP 800-171 03.03.01.\n"},{"id":"mapping--ogrl-lm-01-to-800-53-au-11","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-53-r5-au-11","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_11_odp":"retention_period"},"summary":"Centralized tamper-resistant retention directly satisfies NIST AU-11 audit record retention.\n"},{"id":"mapping--ogrl-lm-01-to-800-53-au-2-a","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-53-r5-au-2#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_02_odp_01":"logged_events"},"summary":"Centralized logging defines and captures auditable security event types per AU-2(a).\n"},{"id":"mapping--ogrl-lm-01-to-800-53-au-2-e","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-53-r5-au-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_02_odp_04":"logging_review_cadence"},"summary":"Periodic review of logged event scope directly satisfies NIST AU-2(e)."},{"id":"mapping--ogrl-lm-01-to-soc2-cc7-2","source_ref":"control--ogrl-lm-01","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Centralized security audit logging supplies telemetry required for SOC 2 CC7.2 monitoring.\n"}],"yaml_path":"library/control/ogrl-lm-01.yaml"},{"id":"control--ogrl-lm-02","slug":"ogrl-lm-02","display_id":"OGRL-LM-02","name":"Continuous Security Monitoring and Alert Triage","family":"lm","control_type":"detective","frequency":"continuous","summary":"Monitor telemetry continuously for anomalous behavior and route high-severity security alerts for timely triage.\n","statement":"Continuously monitor system and security telemetry using {{ monitoring_methods }} to detect {{ monitoring_objectives }}, routing actionable alerts to {{ alert_recipients }} for triage within {{ triage_sla }}.\n","objective":"Detect unauthorized activity, intrusion attempts, and security anomalies quickly enough to contain impact.\n","guidance":"Tune SIEM/EDR rules to minimize alert fatigue, document escalation runbooks, and test alerting pipelines periodically.\n","parameters":{"alert_recipients":{"label":"Alert response recipients","value":"the on-call security operations team"},"monitoring_methods":{"label":"Detection techniques and tools","value":"automated SIEM correlation rules and cloud threat detection"},"monitoring_objectives":{"label":"Security monitoring objectives","value":"unauthorized access, privilege escalation, malware execution, and anomalous data egress\n"},"triage_sla":{"label":"High-severity alert triage SLA","value":"4 hours"}},"tags":["monitoring","siem","detection"],"tests":[{"id":"test--ogrl-lm-02-security-monitoring","slug":"ogrl-lm-02-security-monitoring","name":"Verify Active Threat Detection and Alert Routing","method":"automated","interval":"daily","required":true,"description":"Confirm threat detection rules are active, alert delivery channels are healthy, and open high-severity alerts are triaged within SLA.\n","objective_refs":["requirement--nist-sp-800-53-r5-si-4#obj.a.1","requirement--nist-sp-800-53-r5-si-4#obj.d-1"],"yaml_path":"library/test/ogrl-lm-02-security-monitoring.yaml"}],"mappings":[{"id":"mapping--ogrl-lm-02-to-800-53-si-4-a-1","source_ref":"control--ogrl-lm-02","target_ref":"requirement--nist-sp-800-53-r5-si-4#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_04_odp_01":"monitoring_objectives"},"summary":"Continuous telemetry monitoring against defined threat objectives satisfies NIST SI-4(a.1).\n"},{"id":"mapping--ogrl-lm-02-to-800-53-si-4-b","source_ref":"control--ogrl-lm-02","target_ref":"requirement--nist-sp-800-53-r5-si-4#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_04_odp_02":"monitoring_methods"},"summary":"SIEM correlation and cloud threat detection identify unauthorized system use per SI-4(b).\n"},{"id":"mapping--ogrl-lm-02-to-800-53-si-4-g","source_ref":"control--ogrl-lm-02","target_ref":"requirement--nist-sp-800-53-r5-si-4#g","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_04_odp_04":"alert_recipients"},"summary":"Routing actionable security alerts to on-call responders satisfies NIST SI-4(g)."},{"id":"mapping--ogrl-lm-02-to-soc2-cc7-2","source_ref":"control--ogrl-lm-02","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Continuous security monitoring and anomaly detection satisfy SOC 2 CC7.2."}],"yaml_path":"library/control/ogrl-lm-02.yaml"},{"id":"control--ogrl-lm-03","slug":"ogrl-lm-03","display_id":"OGRL-LM-03","name":"Audit Log Protection","family":"lm","control_type":"preventive","frequency":"continuous","summary":"Store audit logs immutably with restricted access and alert on attempts to tamper with logging.\n","statement":"Store audit logs in {{ log_store }} with immutable or write-once retention, restrict read access to {{ log_reader_roles }}, prevent modification or deletion by any user including administrators of the logged systems, and alert {{ log_tamper_alert_recipients }} on attempts to disable logging, change log configuration, or delete log data.\n","objective":"Preserve the integrity and confidentiality of audit trails so they remain trustworthy for investigations.\n","guidance":"Ship logs to a separate logging account or project with S3 Object Lock, GCS bucket lock, or equivalent retention locks. Deny log deletion and trail modification with organization policies. Alert on events such as StopLogging, DeleteTrail, or sink deletion. Log generation and retention periods are covered by OGRL-LM-01.\n","parameters":{"log_reader_roles":{"label":"Roles permitted to read audit logs","value":"security and designated on-call engineering roles"},"log_store":{"label":"Protected log storage location","value":"a dedicated logging account or project separate from production workloads"},"log_tamper_alert_recipients":{"label":"Log tampering alert recipients","value":"the security on-call team"}},"tags":["logging","integrity","audit"],"tests":[],"mappings":[{"id":"mapping--ogrl-lm-03-to-800-53-au-9-a","source_ref":"control--ogrl-lm-03","target_ref":"requirement--nist-sp-800-53-r5-au-9#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Immutable storage and restricted access protect audit information from unauthorized access, modification, and deletion per AU-9(a).\n"},{"id":"mapping--ogrl-lm-03-to-800-53-au-9-b","source_ref":"control--ogrl-lm-03","target_ref":"requirement--nist-sp-800-53-r5-au-9#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_09_odp":"log_tamper_alert_recipients"},"summary":"Tampering alerts to defined recipients satisfy AU-9(b)."},{"id":"mapping--ogrl-lm-03-to-soc2-cc6-1","source_ref":"control--ogrl-lm-03","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting access to audit logs is a logical access protection over an information asset under CC6.1.\n"},{"id":"mapping--ogrl-lm-03-to-soc2-cc7-2","source_ref":"control--ogrl-lm-03","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Trustworthy, tamper-resistant logs underpin the anomaly monitoring expected under CC7.2.\n"}],"yaml_path":"library/control/ogrl-lm-03.yaml"},{"id":"control--ogrl-lm-04","slug":"ogrl-lm-04","display_id":"OGRL-LM-04","name":"Audit Log Review and Analysis","family":"lm","control_type":"detective","frequency":"weekly","summary":"Periodically review high-risk audit logs, document findings, and escalate them.\n","statement":"Review and analyze {{ reviewed_log_sources }} {{ log_review_frequency }} for indications of {{ reviewed_activity }}, document each review with reviewer, date, and findings, report findings to {{ log_review_report_recipients }}, and increase review scope or frequency when incidents, threat intelligence, or significant system changes indicate elevated risk.\n","objective":"Identify inappropriate or unusual activity that automated alerting may not catch, and leave evidence that review occurred.\n","guidance":"Use saved SIEM queries or dashboards for each review so it is repeatable, and record the review as a ticket with the query output attached. Focus on privileged and administrative actions, break-glass usage, and changes to security tooling. Real-time automated alerting is covered by OGRL-LM-02.\n","parameters":{"log_review_frequency":{"label":"Log review frequency","value":"weekly"},"log_review_report_recipients":{"label":"Log review finding recipients","value":"the security lead and affected system owners"},"reviewed_activity":{"label":"Activity sought in log review","value":"unauthorized privileged actions, anomalous authentication patterns, and disabled or modified security controls\n"},"reviewed_log_sources":{"label":"Logs subject to periodic review","value":"privileged and administrative activity logs, authentication logs, and security tooling configuration changes\n"}},"tags":["logging","audit","monitoring"],"tests":[],"mappings":[{"id":"mapping--ogrl-lm-04-to-800-53-au-6-a","source_ref":"control--ogrl-lm-04","target_ref":"requirement--nist-sp-800-53-r5-au-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_06_odp_01":"log_review_frequency","au_06_odp_02":"reviewed_activity"},"summary":"Scheduled analysis of audit records for defined unusual activity satisfies AU-6(a).\n"},{"id":"mapping--ogrl-lm-04-to-800-53-au-6-b","source_ref":"control--ogrl-lm-04","target_ref":"requirement--nist-sp-800-53-r5-au-6#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_06_odp_03":"log_review_report_recipients"},"summary":"Findings are reported to defined recipients per AU-6(b)."},{"id":"mapping--ogrl-lm-04-to-800-53-au-6-c","source_ref":"control--ogrl-lm-04","target_ref":"requirement--nist-sp-800-53-r5-au-6#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Review scope is adjusted when credible information indicates a change in risk, as AU-6(c) requires.\n"},{"id":"mapping--ogrl-lm-04-to-soc2-cc4-1","source_ref":"control--ogrl-lm-04","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented recurring log reviews provide some ongoing evaluation evidence relevant to CC4.1.\n"},{"id":"mapping--ogrl-lm-04-to-soc2-cc7-2","source_ref":"control--ogrl-lm-04","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Periodic analysis of audit logs for anomalies is a monitoring activity under CC7.2.\n"},{"id":"mapping--ogrl-lm-04-to-soc2-cc7-3","source_ref":"control--ogrl-lm-04","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documenting and escalating log review findings feeds the evaluation of security events under CC7.3.\n"}],"yaml_path":"library/control/ogrl-lm-04.yaml"},{"id":"control--ogrl-lm-05","slug":"ogrl-lm-05","display_id":"OGRL-LM-05","name":"Processing Monitoring and Reconciliation","family":"lm","control_type":"detective","frequency":"daily","summary":"Monitor processing jobs for failures and reconcile inputs to outputs, correcting discrepancies promptly.\n","statement":"Monitor {{ monitored_processing_jobs }} for failures, delays, and incomplete runs, reconcile record counts or control totals between inputs and outputs {{ reconciliation_frequency }}, and route discrepancies to {{ processing_owner }} for investigation and correction within {{ discrepancy_resolution_sla }}.\n","objective":"Detect and correct incomplete or inaccurate processing before it affects customers or downstream systems.\n","guidance":"Emit job success, duration, and record-count metrics and alert on failures, missed schedules, and dead-letter queue depth. Automate reconciliation queries that compare source and destination counts or sums and open a ticket on mismatch. Evidence is the alert configuration plus a sample of reconciliation results and resolved discrepancy tickets.\n","parameters":{"discrepancy_resolution_sla":{"label":"Discrepancy resolution SLA","value":"2 business days"},"monitored_processing_jobs":{"label":"Processing monitored for completeness","value":"scheduled jobs, data pipelines, and queue consumers that process customer data"},"processing_owner":{"label":"Discrepancy owner","value":"the owning engineering team"},"reconciliation_frequency":{"label":"Reconciliation frequency","value":"daily"}},"tags":["processing-integrity","reconciliation","monitoring"],"tests":[],"mappings":[{"id":"mapping--ogrl-lm-05-to-soc2-pi1-3","source_ref":"control--ogrl-lm-05","target_ref":"requirement--soc2-tsc-2017-pi1-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Monitoring processing completion and reconciling volumes supports complete and accurate processing under PI1.3.\n"}],"yaml_path":"library/control/ogrl-lm-05.yaml"},{"id":"control--ogrl-pr-01","slug":"ogrl-pr-01","display_id":"OGRL-PR-01","name":"Privacy Notice","family":"pr","control_type":"preventive","frequency":"annual","summary":"Publish a plain-language privacy notice at the point of collection and keep it current.\n","statement":"Publish a plain-language privacy notice at {{ notice_locations }} that is available before or at first collection of personal information and that states the purposes and legal basis for processing and includes {{ notice_contents }}; review the notice {{ notice_review_cadence }} and before any material change in processing, and inform affected individuals of material changes {{ notice_change_lead_time }}.\n","objective":"Ensure individuals are informed about how their personal information is processed before and while it is processed.\n","guidance":"Link the notice from sign-up flows, the website footer, and mobile app settings; keep a version history with effective dates. Have legal or the privacy lead confirm the notice still matches the PII inventory at each review.\n","parameters":{"notice_change_lead_time":{"label":"Advance notice of material changes","value":"at least 30 days before they take effect"},"notice_contents":{"label":"Required privacy notice contents","value":"data categories, sources, recipients, retention, individual rights, and contacts"},"notice_locations":{"label":"Privacy notice locations","value":"the public website and every point where personal information is collected"},"notice_review_cadence":{"label":"Privacy notice review frequency","value":"annually"}},"tags":["privacy","privacy-notice","transparency"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-01-to-800-53-pt-5","source_ref":"control--ogrl-pr-01","target_ref":"requirement--nist-sp-800-53-r5-pt-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pt_05_odp_02":"notice_contents"},"summary":"A plain-language notice available at first collection stating purposes, legal basis, and defined contents covers PT-5.\n"},{"id":"mapping--ogrl-pr-01-to-soc2-p1-1","source_ref":"control--ogrl-pr-01","target_ref":"requirement--soc2-tsc-2017-p1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Publishing and maintaining a privacy notice addresses the notice obligations in P1.1.\n"}],"yaml_path":"library/control/ogrl-pr-01.yaml"},{"id":"control--ogrl-pr-02","slug":"ogrl-pr-02","display_id":"OGRL-PR-02","name":"Consent Management","family":"pr","control_type":"preventive","frequency":"event-driven","summary":"Obtain, record, and honor withdrawal of consent wherever consent is the basis for processing personal information.\n","statement":"Where consent is the basis for processing, obtain informed, affirmative consent through {{ consent_mechanism }} before collecting personal information, obtain separate explicit consent before collecting {{ sensitive_pii_categories }}, record each consent with the individual, scope, timestamp, and notice version, and give effect to consent withdrawals within {{ consent_withdrawal_sla }}.\n","objective":"Ensure personal information processed on the basis of consent is backed by a valid, provable, and revocable consent.\n","guidance":"Use unchecked opt-in boxes or a consent management platform; store consent records in a system queryable by user ID. Withdrawal should be as easy as giving consent and must propagate to downstream processors such as marketing tools.\n","parameters":{"consent_mechanism":{"label":"Consent collection mechanism","value":"unbundled opt-in controls presented with a link to the privacy notice"},"consent_withdrawal_sla":{"label":"Consent withdrawal processing SLA","value":"10 business days"},"sensitive_pii_categories":{"label":"Sensitive personal information categories","value":"health, biometric, financial, precise location, or government ID data"}},"tags":["privacy","consent"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-02-to-800-53-pt-4","source_ref":"control--ogrl-pr-02","target_ref":"requirement--nist-sp-800-53-r5-pt-4","relationship":"superset-of","review_status":"reviewed","parameter_map":{"pt_04_odp":"consent_mechanism"},"summary":"Pre-collection consent mechanisms satisfy PT-4; the control adds consent records and withdrawal handling.\n"},{"id":"mapping--ogrl-pr-02-to-soc2-p2-1","source_ref":"control--ogrl-pr-02","target_ref":"requirement--soc2-tsc-2017-p2-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Obtaining and recording consent addresses the choice and consent obligations in P2.1.\n"},{"id":"mapping--ogrl-pr-02-to-soc2-p3-2","source_ref":"control--ogrl-pr-02","target_ref":"requirement--soc2-tsc-2017-p3-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Separate explicit consent for sensitive categories addresses P3.2."}],"yaml_path":"library/control/ogrl-pr-02.yaml"},{"id":"control--ogrl-pr-03","slug":"ogrl-pr-03","display_id":"OGRL-PR-03","name":"Purpose Specification and Use Limitation","family":"pr","control_type":"preventive","frequency":"event-driven","summary":"Document the purpose and legal authority for each PII processing activity and restrict use to those purposes.\n","statement":"Document the purposes and legal authority for each personal information processing activity, reflect those purposes in the privacy notice, restrict collection and use of personal information to the documented purposes, and require {{ purpose_change_review }} before personal information is processed for a new or changed purpose.\n","objective":"Prevent personal information from being used for purposes individuals were not told about or that lack a legal basis.\n","guidance":"Record purposes and legal basis per processing activity in the PII inventory (pr-05). Add a privacy checkbox to product and data-pipeline design reviews so new uses (analytics, ML training, marketing) trigger review before launch.\n","parameters":{"purpose_change_review":{"label":"Review required for new or changed purposes","value":"a documented privacy review approved by the privacy lead"}},"tags":["privacy","purpose-limitation","data-governance"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-03-to-800-53-pt-2","source_ref":"control--ogrl-pr-03","target_ref":"requirement--nist-sp-800-53-r5-pt-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Documenting legal authority per activity and restricting processing to it addresses PT-2.\n"},{"id":"mapping--ogrl-pr-03-to-800-53-pt-3","source_ref":"control--ogrl-pr-03","target_ref":"requirement--nist-sp-800-53-r5-pt-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pt_03_odp_03":"purpose_change_review"},"summary":"Documenting purposes, reflecting them in the notice, restricting use, and reviewing changes covers PT-3.\n"},{"id":"mapping--ogrl-pr-03-to-soc2-p3-1","source_ref":"control--ogrl-pr-03","target_ref":"requirement--soc2-tsc-2017-p3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Limiting collection to documented purposes overlaps the collection objectives in P3.1.\n"},{"id":"mapping--ogrl-pr-03-to-soc2-p4-1","source_ref":"control--ogrl-pr-03","target_ref":"requirement--soc2-tsc-2017-p4-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting use to documented purposes addresses the use limitation in P4.1."}],"yaml_path":"library/control/ogrl-pr-03.yaml"},{"id":"control--ogrl-pr-04","slug":"ogrl-pr-04","display_id":"OGRL-PR-04","name":"PII Minimization","family":"pr","control_type":"preventive","frequency":"annual","summary":"Collect and retain only the personal information elements needed for each documented purpose.\n","statement":"Limit personal information collected and processed to {{ permitted_pii_elements }}, require {{ pii_element_approver }} to approve any new personal information element before collection begins, and review collection points and data stores {{ minimization_review_cadence }} to remove elements no longer needed.\n","objective":"Reduce privacy risk and breach impact by holding no more personal information than each purpose requires.\n","guidance":"Enforce minimization in form and API schemas, and use data discovery or schema diffs to spot unapproved fields. Prefer pseudonymized or aggregated data for analytics and testing.\n","parameters":{"minimization_review_cadence":{"label":"Minimization review frequency","value":"annually"},"permitted_pii_elements":{"label":"Permitted personal information elements","value":"the elements approved for each processing activity in the PII inventory"},"pii_element_approver":{"label":"Approver for new personal information elements","value":"the privacy lead"}},"tags":["privacy","data-minimization"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-04-to-800-53-si-12-1","source_ref":"control--ogrl-pr-04","target_ref":"requirement--nist-sp-800-53-r5-si-12-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_12_01_odp":"permitted_pii_elements"},"summary":"Limiting processing to approved PII elements satisfies SI-12(1)."},{"id":"mapping--ogrl-pr-04-to-soc2-p3-1","source_ref":"control--ogrl-pr-04","target_ref":"requirement--soc2-tsc-2017-p3-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Collecting only necessary PII elements addresses P3.1."},{"id":"mapping--ogrl-pr-04-to-soc2-p4-1","source_ref":"control--ogrl-pr-04","target_ref":"requirement--soc2-tsc-2017-p4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Minimizing processed elements supports limiting use of personal information under P4.1.\n"}],"yaml_path":"library/control/ogrl-pr-04.yaml"},{"id":"control--ogrl-pr-05","slug":"ogrl-pr-05","display_id":"OGRL-PR-05","name":"PII Inventory and Processing Records","family":"pr","control_type":"detective","frequency":"annual","summary":"Maintain an inventory of systems, vendors, and processing activities that handle personal information.\n","statement":"Maintain an inventory of systems, applications, vendors, and projects that process personal information, recording for each the personal information categories, data subjects, purposes, legal basis, storage locations, recipients, and retention period; update it when processing changes and review it in full {{ pii_inventory_review_cadence }}.\n","objective":"Provide an accurate record of where personal information lives and how it flows, enabling notice, rights requests, and risk management.\n","guidance":"A spreadsheet or data-map tool is sufficient; seed it from the system and vendor inventories and data-discovery scans. Make updates part of the change and vendor-onboarding workflows.\n","parameters":{"pii_inventory_review_cadence":{"label":"PII inventory review frequency","value":"annually"}},"tags":["privacy","data-inventory","data-mapping"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-05-to-800-53-pm-5-1","source_ref":"control--ogrl-pr-05","target_ref":"requirement--nist-sp-800-53-r5-pm-5-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_05_01_odp":"pii_inventory_review_cadence"},"summary":"A maintained and periodically reviewed inventory of PII-processing systems satisfies PM-5(1).\n"},{"id":"mapping--ogrl-pr-05-to-soc2-p4-1","source_ref":"control--ogrl-pr-05","target_ref":"requirement--soc2-tsc-2017-p4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recording purposes and recipients per activity enables but does not enforce use limitation under P4.1.\n"},{"id":"mapping--ogrl-pr-05-to-soc2-p6-7","source_ref":"control--ogrl-pr-05","target_ref":"requirement--soc2-tsc-2017-p6-7","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The inventory supplies the data needed to tell individuals what is held and shared, supporting P6.7.\n"}],"yaml_path":"library/control/ogrl-pr-05.yaml"},{"id":"control--ogrl-pr-06","slug":"ogrl-pr-06","display_id":"OGRL-PR-06","name":"Data Subject Access Requests","family":"pr","control_type":"corrective","frequency":"event-driven","summary":"Give individuals a way to request and receive the personal information held about them, within a defined timeline.\n","statement":"Provide {{ access_request_channels }} through which individuals can request access to their personal information, verify the requester's identity using {{ requester_verification_method }}, provide {{ access_request_elements }} within {{ access_request_sla }}, and log each request, its outcome, and the reason for any denial.\n","objective":"Enable individuals to learn what personal information the organization holds about them in a timely and secure manner.\n","guidance":"Track requests in a ticketing queue with due dates; use the PII inventory (pr-05) to locate data across systems and processors. Avoid over-collecting identity documents for verification; matching account login or a verified email is usually enough.\n","parameters":{"access_request_channels":{"label":"Access request channels","value":"a web form and a published privacy email address"},"access_request_elements":{"label":"Personal information disclosed in response","value":"a copy of their personal information and its categories, sources, and recipients"},"access_request_sla":{"label":"Access request response SLA","value":"30 days"},"requester_verification_method":{"label":"Requester identity verification method","value":"account authentication or confirmation via the email address on file"}},"tags":["privacy","data-subject-rights"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-06-to-800-53-ac-3-14","source_ref":"control--ogrl-pr-06","target_ref":"requirement--nist-sp-800-53-r5-ac-3-14","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_03_14_odp_01":"access_request_channels","ac_03_14_odp_02":"access_request_elements"},"summary":"Request channels and defined disclosed elements implement individual access under AC-3(14).\n"},{"id":"mapping--ogrl-pr-06-to-soc2-p5-1","source_ref":"control--ogrl-pr-06","target_ref":"requirement--soc2-tsc-2017-p5-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Verified, timely access-request fulfillment addresses individual access under P5.1.\n"}],"yaml_path":"library/control/ogrl-pr-06.yaml"},{"id":"control--ogrl-pr-07","slug":"ogrl-pr-07","display_id":"OGRL-PR-07","name":"Data Subject Correction Requests","family":"pr","control_type":"corrective","frequency":"event-driven","summary":"Correct or delete personal information on verified request and propagate the change to recipients.\n","statement":"Accept requests from individuals or their authorized representatives to correct or delete their personal information, verify the requester's identity, complete the correction or deletion within {{ correction_request_sla }} across all systems in the PII inventory, notify third parties that received the information, and record the reason when a request is denied and communicate it to the requester.\n","objective":"Ensure individuals can have inaccurate or unwanted personal information fixed or removed and that changes reach downstream recipients.\n","guidance":"Reuse the access-request intake and ticket queue (pr-06). Automate deletion through account-deletion workflows where possible and keep evidence of processor notifications. Legal holds and retention obligations are valid denial reasons when documented.\n","parameters":{"correction_request_sla":{"label":"Correction or deletion request SLA","value":"30 days"}},"tags":["privacy","data-subject-rights","data-quality"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-07-to-800-53-si-18-4","source_ref":"control--ogrl-pr-07","target_ref":"requirement--nist-sp-800-53-r5-si-18-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Correcting or deleting PII on verified request satisfies SI-18(4)."},{"id":"mapping--ogrl-pr-07-to-soc2-p5-2","source_ref":"control--ogrl-pr-07","target_ref":"requirement--soc2-tsc-2017-p5-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Correction handling with recipient notification and denial reasons addresses P5.2.\n"}],"yaml_path":"library/control/ogrl-pr-07.yaml"},{"id":"control--ogrl-pr-08","slug":"ogrl-pr-08","display_id":"OGRL-PR-08","name":"Third-Party Disclosure Authorization","family":"pr","control_type":"preventive","frequency":"event-driven","summary":"Approve each new third-party recipient of personal information against the permitted uses of that information.\n","statement":"Before disclosing personal information to a new third party or for a new purpose in {{ disclosure_circumstances }}, require {{ disclosure_approver }} to confirm that the disclosure is consistent with the privacy notice and any consent obtained and that a written agreement binds the recipient to equivalent privacy and confidentiality obligations.\n","objective":"Ensure personal information is shared only with recipients and for uses that individuals were informed of and that contracts restrict.\n","guidance":"Embed the privacy check in vendor onboarding and in data-sharing requests; maintain the approved recipient list as the public subprocessor list where applicable. A data processing agreement with standard privacy terms meets the written-agreement requirement.\n","parameters":{"disclosure_approver":{"label":"Disclosure approval authority","value":"the privacy lead"},"disclosure_circumstances":{"label":"Disclosure circumstances requiring authorization","value":"any sharing of personal information with a party outside the organization"}},"tags":["privacy","third-party","data-sharing"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-08-to-800-53-ac-21-a","source_ref":"control--ogrl-pr-08","target_ref":"requirement--nist-sp-800-53-r5-ac-21#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"ac_21_odp_01":"disclosure_circumstances"},"summary":"Approval of PII recipients against permitted uses overlaps the sharing-partner check in AC-21(a); automated aids in AC-21(b) are not covered.\n"},{"id":"mapping--ogrl-pr-08-to-soc2-p6-1","source_ref":"control--ogrl-pr-08","target_ref":"requirement--soc2-tsc-2017-p6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Authorizing third-party disclosures against notice, consent, and contract addresses P6.1.\n"}],"yaml_path":"library/control/ogrl-pr-08.yaml"},{"id":"control--ogrl-pr-09","slug":"ogrl-pr-09","display_id":"OGRL-PR-09","name":"Accounting of Disclosures","family":"pr","control_type":"detective","frequency":"event-driven","summary":"Record disclosures of personal information to third parties and make the record available to affected individuals on request.\n","statement":"Record each disclosure of personal information to a third party with the date, nature and purpose of the disclosure, and the recipient's name and contact information, retain each record for {{ disclosure_record_retention }}, and provide individuals with the record of disclosures of their personal information within {{ disclosure_accounting_sla }} of request.\n","objective":"Maintain a reliable history of who received personal information and why, supporting individual rights and investigations.\n","guidance":"Routine sharing with contracted processors can be recorded at category level via the subprocessor list and PII inventory; ad hoc disclosures (law enforcement requests, data transfers to partners, unauthorized disclosures found during incidents) should be logged individually in a ticket or register.\n","parameters":{"disclosure_accounting_sla":{"label":"Disclosure accounting response SLA","value":"30 days"},"disclosure_record_retention":{"label":"Disclosure record retention period","value":"the longer of the life of the information or five years after disclosure"}},"tags":["privacy","disclosure-tracking","data-sharing"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-09-to-800-53-pm-21","source_ref":"control--ogrl-pr-09","target_ref":"requirement--nist-sp-800-53-r5-pm-21","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Recording disclosure details, retaining them, and providing them on request covers PM-21.\n"},{"id":"mapping--ogrl-pr-09-to-soc2-p6-2","source_ref":"control--ogrl-pr-09","target_ref":"requirement--soc2-tsc-2017-p6-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Logging disclosures with date, purpose, and recipient addresses P6.2."},{"id":"mapping--ogrl-pr-09-to-soc2-p6-7","source_ref":"control--ogrl-pr-09","target_ref":"requirement--soc2-tsc-2017-p6-7","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Providing individuals their disclosure record covers the disclosure portion of P6.7.\n"}],"yaml_path":"library/control/ogrl-pr-09.yaml"},{"id":"control--ogrl-pr-10","slug":"ogrl-pr-10","display_id":"OGRL-PR-10","name":"PII Data Quality","family":"pr","control_type":"corrective","frequency":"annual","summary":"Periodically check personal information for accuracy and completeness and fix or remove bad data.\n","statement":"Validate personal information at collection, check the accuracy, completeness, relevance, and timeliness of stored personal information {{ pii_quality_check_cadence }}, and correct or delete inaccurate or outdated personal information within {{ pii_quality_remediation_sla }} of detection.\n","objective":"Ensure decisions and communications that rely on personal information are based on accurate and current data.\n","guidance":"Input validation, self-service profile editing, and bounce or undeliverable handling cover most needs. Periodic checks can be automated data-quality queries or stale-record reports reviewed by the data owner.\n","parameters":{"pii_quality_check_cadence":{"label":"PII quality check frequency","value":"annually"},"pii_quality_remediation_sla":{"label":"PII quality remediation SLA","value":"30 days"}},"tags":["privacy","data-quality"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-10-to-800-53-si-18-a","source_ref":"control--ogrl-pr-10","target_ref":"requirement--nist-sp-800-53-r5-si-18#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_18_prm_1":"pii_quality_check_cadence"},"summary":"Periodic accuracy, completeness, relevance, and timeliness checks satisfy SI-18(a).\n"},{"id":"mapping--ogrl-pr-10-to-800-53-si-18-b","source_ref":"control--ogrl-pr-10","target_ref":"requirement--nist-sp-800-53-r5-si-18#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Correcting or deleting inaccurate or outdated PII satisfies SI-18(b)."},{"id":"mapping--ogrl-pr-10-to-soc2-p7-1","source_ref":"control--ogrl-pr-10","target_ref":"requirement--soc2-tsc-2017-p7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Validating and correcting personal information addresses data quality under P7.1.\n"}],"yaml_path":"library/control/ogrl-pr-10.yaml"},{"id":"control--ogrl-pr-11","slug":"ogrl-pr-11","display_id":"OGRL-PR-11","name":"Privacy Inquiry and Complaint Management","family":"pr","control_type":"corrective","frequency":"event-driven","summary":"Receive, track, and respond to privacy inquiries and complaints within defined timelines under an accountable privacy lead.\n","statement":"Designate {{ privacy_lead_role }} as accountable for privacy inquiries and complaints, publish {{ complaint_channels }} together with the information needed to file a complaint, track each inquiry or complaint to closure, acknowledge it within {{ complaint_acknowledgement_sla }}, respond within {{ complaint_response_sla }}, and resolve or escalate it within {{ complaint_resolution_sla }}.\n","objective":"Ensure individuals' privacy concerns are heard, addressed in a timely way, and used to improve privacy practices.\n","guidance":"A shared privacy mailbox feeding a ticket queue with SLA timers is usually enough. Report complaint volume and themes to leadership periodically and feed recurring issues into the privacy risk assessment.\n","parameters":{"complaint_acknowledgement_sla":{"label":"Complaint acknowledgement SLA","value":"5 business days"},"complaint_channels":{"label":"Privacy complaint channels","value":"a privacy email address and web form linked from the privacy notice"},"complaint_resolution_sla":{"label":"Complaint resolution SLA","value":"60 days"},"complaint_response_sla":{"label":"Complaint response SLA","value":"30 days"},"privacy_lead_role":{"label":"Accountable privacy role","value":"the privacy lead"}},"tags":["privacy","complaint-management","accountability"],"tests":[],"mappings":[{"id":"mapping--ogrl-pr-11-to-800-53-pm-19","source_ref":"control--ogrl-pr-11","target_ref":"requirement--nist-sp-800-53-r5-pm-19","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Designating an accountable privacy lead for complaints is a narrow part of the privacy leadership role in PM-19.\n"},{"id":"mapping--ogrl-pr-11-to-800-53-pm-26","source_ref":"control--ogrl-pr-11","target_ref":"requirement--nist-sp-800-53-r5-pm-26","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_26_odp_03":"complaint_acknowledgement_sla","pm_26_odp_04":"complaint_response_sla","pm_26_prm_1":"complaint_resolution_sla"},"summary":"Published channels, filing information, tracking, and acknowledgement, response, and resolution timelines cover PM-26.\n"},{"id":"mapping--ogrl-pr-11-to-soc2-p8-1","source_ref":"control--ogrl-pr-11","target_ref":"requirement--soc2-tsc-2017-p8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Tracked intake and timely response to privacy inquiries and complaints addresses P8.1.\n"}],"yaml_path":"library/control/ogrl-pr-11.yaml"},{"id":"control--ogrl-ps-01","slug":"ogrl-ps-01","display_id":"OGRL-PS-01","name":"Physical Access Authorization and Review","family":"ps","control_type":"preventive","frequency":"quarterly","summary":"Keep an approved list of people allowed into controlled facilities, review it regularly, and remove access promptly when it is no longer needed.\n","statement":"Maintain a list of individuals authorized to enter {{ controlled_facilities }}, issue badges, keys, or other access credentials only after approval by {{ access_approver }}, review the list {{ access_review_cadence }}, and remove an individual's physical access within {{ access_removal_sla }} of termination or when access is no longer required.\n","objective":"Ensure only currently authorized individuals hold credentials that grant entry to facilities housing personnel or system components.\n","guidance":"Use the badge or door-access system as the source of truth and reconcile it against the HR roster during each review; tie offboarding tickets to badge deactivation so removal evidence is automatic. Coworking or shared offices can rely on the landlord's badge system if the organization can obtain the list of its credential holders. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.\n","parameters":{"access_approver":{"label":"Physical access approval authority","value":"the facilities owner or the requester's manager"},"access_removal_sla":{"label":"Physical access removal SLA","value":"1 business day"},"access_review_cadence":{"label":"Physical access list review frequency","value":"quarterly"},"controlled_facilities":{"label":"Controlled facilities","value":"company offices and any organization-operated server, network, or storage rooms"}},"tags":["physical-security","access-control","access-review"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-01-to-800-53-pe-2","source_ref":"control--ogrl-ps-01","target_ref":"requirement--nist-sp-800-53-r5-pe-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_02_odp":"access_review_cadence"},"summary":"Approved access list, credential issuance, periodic review, and timely removal cover all of PE-2.\n"},{"id":"mapping--ogrl-ps-01-to-soc2-cc6-4","source_ref":"control--ogrl-ps-01","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Authorizing and reviewing who may enter facilities is one part of restricting physical access under CC6.4.\n"}],"yaml_path":"library/control/ogrl-ps-01.yaml"},{"id":"control--ogrl-ps-02","slug":"ogrl-ps-02","display_id":"OGRL-PS-02","name":"Physical Access Control","family":"ps","control_type":"preventive","frequency":"continuous","summary":"Enforce authorized entry at every facility entry point and keep keys, badges, and combinations under inventory and control.\n","statement":"Enforce physical access authorizations at every entry and exit point of {{ controlled_facilities }} using {{ entry_control_mechanism }}, retain electronic entry logs for {{ entry_log_retention }}, secure unissued keys, badges, and combinations, inventory physical access devices {{ access_device_inventory_cadence }}, and change combinations or rekey locks when a key or code is lost or compromised or its holder leaves.\n","objective":"Prevent unauthorized individuals from entering facilities that house personnel or system components, and keep a record of who entered.\n","guidance":"Badge readers that log each entry satisfy both enforcement and logging; areas that rely on physical keys need a key register. Inventory issued badges against ps-01's authorized list to catch orphaned credentials. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.\n","parameters":{"access_device_inventory_cadence":{"label":"Physical access device inventory frequency","value":"annually"},"controlled_facilities":{"label":"Controlled facilities","value":"company offices and any organization-operated server, network, or storage rooms"},"entry_control_mechanism":{"label":"Entry control mechanism","value":"electronic badge readers or keyed locks"},"entry_log_retention":{"label":"Physical entry log retention","value":"90 days"}},"tags":["physical-security","access-control","facilities"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-a","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_03_odp_02":"entry_control_mechanism"},"summary":"Badge or lock enforcement at every entry and exit point satisfies PE-3(a)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-b","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Retained electronic entry logs at controlled entry points satisfy PE-3(b)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-e","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Securing unissued keys, badges, and combinations satisfies PE-3(e)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-f","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_03_odp_08":"access_device_inventory_cadence"},"summary":"Periodic inventory of physical access devices satisfies PE-3(f)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-g","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#g","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Event-triggered rekeying covers PE-3(g) except the periodic change cadence."},{"id":"mapping--ogrl-ps-02-to-soc2-cc6-4","source_ref":"control--ogrl-ps-02","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Enforced entry at facility access points is a core piece of physical access restriction under CC6.4.\n"}],"yaml_path":"library/control/ogrl-ps-02.yaml"},{"id":"control--ogrl-ps-03","slug":"ogrl-ps-03","display_id":"OGRL-PS-03","name":"Visitor Access Records","family":"ps","control_type":"detective","frequency":"monthly","summary":"Log every visitor, escort them in non-public areas, and review the visitor log for anomalies.\n","statement":"Record each visitor to {{ controlled_facilities }} with name, organization, host, and times of arrival and departure, escort visitors in non-public areas, retain visitor records for {{ visitor_record_retention }}, review the records {{ visitor_review_cadence }}, and report anomalies to {{ visitor_anomaly_recipient }}.\n","objective":"Maintain accountability for non-workforce individuals who enter facilities and detect unusual visitor activity.\n","guidance":"A tablet-based visitor management system or front-desk sign-in sheet both work; capture host and badge-return evidence. Anomalies include unescorted visitors, missing sign-outs, and unreturned visitor badges. In shared buildings, building-reception logs may be used if the organization can retrieve entries for its own visitors. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.\n","parameters":{"controlled_facilities":{"label":"Controlled facilities","value":"company offices and any organization-operated server, network, or storage rooms"},"visitor_anomaly_recipient":{"label":"Recipient of visitor anomaly reports","value":"the security team"},"visitor_record_retention":{"label":"Visitor record retention period","value":"1 year"},"visitor_review_cadence":{"label":"Visitor record review frequency","value":"monthly"}},"tags":["physical-security","visitor-management","facilities"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-03-to-800-53-pe-3-d","source_ref":"control--ogrl-ps-03","target_ref":"requirement--nist-sp-800-53-r5-pe-3#d","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Escorting visitors in non-public areas addresses PE-3(d) without broader visitor activity controls.\n"},{"id":"mapping--ogrl-ps-03-to-800-53-pe-8","source_ref":"control--ogrl-ps-03","target_ref":"requirement--nist-sp-800-53-r5-pe-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_08_odp_01":"visitor_record_retention","pe_08_odp_02":"visitor_review_cadence","pe_08_odp_03":"visitor_anomaly_recipient"},"summary":"Visitor logging, retention, periodic review, and anomaly reporting cover PE-8."},{"id":"mapping--ogrl-ps-03-to-soc2-cc6-4","source_ref":"control--ogrl-ps-03","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Visitor logging and escort contribute to restricting physical access under CC6.4.\n"}],"yaml_path":"library/control/ogrl-ps-03.yaml"},{"id":"control--ogrl-ps-04","slug":"ogrl-ps-04","display_id":"OGRL-PS-04","name":"Physical Access Monitoring","family":"ps","control_type":"detective","frequency":"monthly","summary":"Monitor facility entry points and review physical access logs to detect and escalate physical security incidents.\n","statement":"Monitor entry points of {{ controlled_facilities }} using {{ physical_monitoring_mechanisms }}, review physical access logs {{ access_log_review_cadence }} and upon {{ access_log_review_triggers }}, and escalate suspected physical security incidents to the incident response process.\n","objective":"Detect unauthorized or suspicious physical access in time to respond and feed findings into incident response.\n","guidance":"Configure badge-system alerts for forced or held-open doors and after-hours entry, and keep camera footage long enough to support investigations. Record each review (date, reviewer, exceptions) as evidence. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.\n","parameters":{"access_log_review_cadence":{"label":"Physical access log review frequency","value":"monthly"},"access_log_review_triggers":{"label":"Events triggering an ad hoc log review","value":"door alarms, forced-entry alerts, or reported physical security incidents"},"controlled_facilities":{"label":"Controlled facilities","value":"company offices and any organization-operated server, network, or storage rooms"},"physical_monitoring_mechanisms":{"label":"Physical monitoring mechanisms","value":"video surveillance and door alarms or badge-system alerts"}},"tags":["physical-security","monitoring","incident-detection"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-04-to-800-53-pe-6","source_ref":"control--ogrl-ps-04","target_ref":"requirement--nist-sp-800-53-r5-pe-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_06_odp_01":"access_log_review_cadence","pe_06_odp_02":"access_log_review_triggers"},"summary":"Entry-point monitoring, scheduled and triggered log reviews, and incident escalation cover PE-6.\n"},{"id":"mapping--ogrl-ps-04-to-soc2-cc6-4","source_ref":"control--ogrl-ps-04","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Monitoring physical entry supports enforcement of facility access restrictions under CC6.4.\n"},{"id":"mapping--ogrl-ps-04-to-soc2-cc7-2","source_ref":"control--ogrl-ps-04","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Physical access monitoring is one source of anomaly detection relevant to CC7.2, which is broader.\n"}],"yaml_path":"library/control/ogrl-ps-04.yaml"},{"id":"control--ogrl-ps-05","slug":"ogrl-ps-05","display_id":"OGRL-PS-05","name":"Environmental Safeguards","family":"ps","control_type":"preventive","frequency":"continuous","summary":"Protect organization-operated equipment rooms with environmental monitoring, backup power, fire protection, and water-damage protection.\n","statement":"In each organization-operated facility that houses in-scope system components, maintain {{ environmental_factors }} within {{ environmental_ranges }} and monitor them {{ environmental_monitoring_cadence }} with alerting; provide an uninterruptible power supply sufficient to allow {{ ups_capability }}; employ fire detection and suppression systems with an independent power source; and keep master water shutoff or isolation valves accessible, working, and known to facilities personnel.\n","objective":"Prevent loss of availability or equipment damage from environmental hazards in facilities the organization operates.\n","guidance":"Applies only to server rooms, network closets, or on-premises data centers run by the organization. For cloud-hosted production, these safeguards are inherited from the provider and validated through its SOC 2 report; document the inheritance and review the report each year. Office spaces with only laptops and a network switch typically need only UPS for network gear and landlord-provided fire protection.\n","parameters":{"environmental_factors":{"label":"Environmental factors controlled","value":"temperature and humidity"},"environmental_monitoring_cadence":{"label":"Environmental monitoring frequency","value":"continuously"},"environmental_ranges":{"label":"Acceptable environmental ranges","value":"the equipment manufacturer's recommended operating ranges"},"ups_capability":{"label":"Uninterruptible power supply capability","value":"an orderly shutdown of in-scope systems"}},"tags":["physical-security","environmental-controls","availability"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-05-to-800-53-pe-11","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-11","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_11_odp":"ups_capability"},"summary":"Providing a UPS sized for the defined capability satisfies PE-11."},{"id":"mapping--ogrl-ps-05-to-800-53-pe-13","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-13","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Fire detection and suppression with independent power satisfies PE-13."},{"id":"mapping--ogrl-ps-05-to-800-53-pe-14","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-14","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_14_odp_01":"environmental_factors","pe_14_odp_03":"environmental_ranges","pe_14_odp_04":"environmental_monitoring_cadence"},"summary":"Maintaining and monitoring environmental conditions within defined ranges satisfies PE-14.\n"},{"id":"mapping--ogrl-ps-05-to-800-53-pe-15","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-15","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Accessible, working, known master water shutoff valves satisfy PE-15."},{"id":"mapping--ogrl-ps-05-to-soc2-a1-2","source_ref":"control--ogrl-ps-05","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Environmental protections for organization-operated facilities are one part of A1.2.\n"}],"yaml_path":"library/control/ogrl-ps-05.yaml"},{"id":"control--ogrl-ps-06","slug":"ogrl-ps-06","display_id":"OGRL-PS-06","name":"Equipment Delivery and Removal","family":"ps","control_type":"preventive","frequency":"event-driven","summary":"Authorize and record system components entering or leaving organization facilities.\n","statement":"Authorize and record {{ controlled_component_types }} entering and leaving {{ controlled_facilities }}, require approval from {{ removal_approver }} before such components are removed, and record the asset identifier, date, responsible person, and purpose of each movement in the asset inventory.\n","objective":"Ensure that system components cannot enter or leave organization facilities without authorization and a traceable record.\n","guidance":"Track movements in the asset management system or ticketing tool; laptops assigned to employees for routine use need not be logged at each trip, but receipt, reassignment, repair shipment, and disposal should be. Pair with media sanitization controls for components leaving for repair or disposal. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.\n","parameters":{"controlled_component_types":{"label":"Component types subject to movement control","value":"servers, network devices, storage media, and workforce endpoints"},"controlled_facilities":{"label":"Controlled facilities","value":"company offices and any organization-operated server, network, or storage rooms"},"removal_approver":{"label":"Equipment removal approval authority","value":"IT or the asset owner"}},"tags":["physical-security","asset-management","media"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-06-to-800-53-pe-16","source_ref":"control--ogrl-ps-06","target_ref":"requirement--nist-sp-800-53-r5-pe-16","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_16_prm_1":"controlled_component_types"},"summary":"Authorizing and recording component movements in and out of facilities covers PE-16.\n"},{"id":"mapping--ogrl-ps-06-to-soc2-cc6-4","source_ref":"control--ogrl-ps-06","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Controlling equipment entering and leaving facilities contributes to physical protection under CC6.4.\n"},{"id":"mapping--ogrl-ps-06-to-soc2-cc6-5","source_ref":"control--ogrl-ps-06","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Approved, recorded removal of components supports control over assets leaving the organization under CC6.5.\n"}],"yaml_path":"library/control/ogrl-ps-06.yaml"},{"id":"control--ogrl-ps-07","slug":"ogrl-ps-07","display_id":"OGRL-PS-07","name":"Facility and Infrastructure Maintenance","family":"ps","control_type":"preventive","frequency":"quarterly","summary":"Schedule, approve, record, and verify maintenance on supporting infrastructure and system components in organization facilities.\n","statement":"Schedule maintenance of in-scope system components and supporting facility infrastructure in organization-operated facilities according to manufacturer or vendor specifications, require approval by {{ maintenance_approver }} for maintenance activities and for removing components off-site for service, verify affected safeguards function after maintenance, record {{ maintenance_record_contents }}, and review maintenance records {{ maintenance_review_cadence }}.\n","objective":"Keep supporting infrastructure reliable and ensure maintenance does not introduce unauthorized changes or degrade safeguards.\n","guidance":"Supporting infrastructure includes UPS units, HVAC, fire suppression, generators, and on-premises network or server hardware. Keep vendor service reports with the maintenance record. For cloud-hosted production, data-center maintenance is inherited from the provider and validated through its SOC 2 report; this control then covers only office or organization-operated equipment rooms.\n","parameters":{"maintenance_approver":{"label":"Maintenance approval authority","value":"the facilities or IT owner"},"maintenance_record_contents":{"label":"Required maintenance record contents","value":"date, component, maintenance performed, performer, and approver"},"maintenance_review_cadence":{"label":"Maintenance record review frequency","value":"quarterly"}},"tags":["maintenance","facilities","availability"],"tests":[],"mappings":[{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-a","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Scheduling maintenance to vendor specifications and reviewing records satisfies MA-2(a).\n"},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-b","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#b","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Approval of maintenance activities covers MA-2(b) except explicit monitoring of each activity.\n"},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-c","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ma_02_odp_01":"maintenance_approver"},"summary":"Required approval before off-site removal for service satisfies MA-2(c)."},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-e","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Post-maintenance verification of affected safeguards satisfies MA-2(e)."},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-f","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ma_02_odp_03":"maintenance_record_contents"},"summary":"Defined maintenance record contents satisfy MA-2(f)."},{"id":"mapping--ogrl-ps-07-to-soc2-a1-2","source_ref":"control--ogrl-ps-07","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Maintaining supporting infrastructure contributes to the availability protections in A1.2.\n"}],"yaml_path":"library/control/ogrl-ps-07.yaml"},{"id":"control--ogrl-rm-01","slug":"ogrl-rm-01","display_id":"OGRL-RM-01","name":"Risk Management Strategy","family":"rm","control_type":"preventive","frequency":"annual","summary":"Maintain an approved risk management methodology that defines risk appetite, scoring, acceptance authority, and treatment options.\n","statement":"Maintain a documented risk management methodology that defines risk appetite and tolerance thresholds, likelihood and impact scoring criteria, the treatment options available, and that risk acceptance requires approval by {{ risk_acceptance_authority }}. The methodology is approved by {{ strategy_approver }} and reviewed and updated {{ strategy_review_frequency }} or when significant organizational changes occur.\n","objective":"Risks are identified, rated, and treated consistently against criteria that leadership has approved.\n","guidance":"A two-page method is enough for a startup: a 5x5 likelihood and impact matrix with defined levels, a tolerance line above which risks must be treated, and named acceptance authority by risk level. The risk assessment (OGRL-RM-02) and treatment tracking (OGRL-RM-04) apply this method.\n","parameters":{"risk_acceptance_authority":{"label":"Risk acceptance authority","value":"the CEO for high risks and the security leader for others"},"strategy_approver":{"label":"Methodology approver","value":"executive leadership"},"strategy_review_frequency":{"label":"Methodology review frequency","value":"at least annually"}},"tags":["risk-management","governance","methodology"],"tests":[],"mappings":[{"id":"mapping--ogrl-rm-01-to-800-53-pm-9-a-1","source_ref":"control--ogrl-rm-01","target_ref":"requirement--nist-sp-800-53-r5-pm-9#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The approved methodology is the organization's strategy for managing security risk.\n"},{"id":"mapping--ogrl-rm-01-to-800-53-pm-9-c","source_ref":"control--ogrl-rm-01","target_ref":"requirement--nist-sp-800-53-r5-pm-9#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_09_odp":"strategy_review_frequency"},"summary":"Periodic and change-driven review of the methodology meets the strategy review requirement.\n"},{"id":"mapping--ogrl-rm-01-to-soc2-cc3-1","source_ref":"control--ogrl-rm-01","target_ref":"requirement--soc2-tsc-2017-cc3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Defined tolerance and scoring criteria enable risks to objectives to be identified and assessed.\n"},{"id":"mapping--ogrl-rm-01-to-soc2-cc3-2","source_ref":"control--ogrl-rm-01","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The methodology sets how risks are analyzed and how responses are determined; the assessment itself is a separate control.\n"},{"id":"mapping--ogrl-rm-01-to-soc2-cc9-1","source_ref":"control--ogrl-rm-01","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Defined treatment options, including transfer, frame how disruption risks are mitigated.\n"}],"yaml_path":"library/control/ogrl-rm-01.yaml"},{"id":"control--ogrl-rm-02","slug":"ogrl-rm-02","display_id":"OGRL-RM-02","name":"Periodic Risk Assessment","family":"rm","control_type":"detective","frequency":"annual","summary":"Identify and rate threats and vulnerabilities to in-scope systems on a fixed cadence and record the results in the risk register.\n","statement":"Perform a risk assessment of in-scope systems {{ risk_assessment_frequency }} that identifies threats and vulnerabilities, including those arising from vendors and subservice organizations, and rates the likelihood and impact of each risk using the approved methodology. Record results in {{ risk_register }} and communicate them to {{ results_audience }}.\n","objective":"Leadership has a current, rated view of the risks to in-scope systems and the data they handle.\n","guidance":"Run a structured workshop with engineering, product, and operations; seed it with incidents, vulnerability trends, vendor reviews, and audit findings from the period. Each register entry needs a description, affected assets, inherent rating, existing controls, residual rating, and owner. Evidence: the dated register snapshot and its sign-off.\n","parameters":{"results_audience":{"label":"Recipients of risk assessment results","value":"executive leadership and the board or its designated committee"},"risk_assessment_frequency":{"label":"Risk assessment frequency","value":"at least annually"},"risk_register":{"label":"Location of documented results","value":"the risk register"}},"tags":["risk-management","risk-assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-a-1","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The assessment identifies threats to and vulnerabilities in the system."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-a-2","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#a.2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Likelihood and impact ratings determine the likelihood and magnitude of harm."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-c","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_03_odp_02":"risk_register"},"summary":"Results are documented in the risk register."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-e","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_03_odp_04":"results_audience"},"summary":"Results are communicated to named recipients."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-f","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#f","relationship":"subset-of","review_status":"reviewed","parameter_map":{"ra_03_odp_05":"risk_assessment_frequency"},"summary":"Covers the periodic update; change-driven updates are handled by significant change risk evaluation.\n"},{"id":"mapping--ogrl-rm-02-to-soc2-cc3-1","source_ref":"control--ogrl-rm-02","target_ref":"requirement--soc2-tsc-2017-cc3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The assessment is the mechanism through which risks to stated objectives are identified.\n"},{"id":"mapping--ogrl-rm-02-to-soc2-cc3-2","source_ref":"control--ogrl-rm-02","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Identifies and rates risks to the system, including vendor risks; deciding how to respond is handled by risk treatment.\n"}],"yaml_path":"library/control/ogrl-rm-02.yaml"},{"id":"control--ogrl-rm-03","slug":"ogrl-rm-03","display_id":"OGRL-RM-03","name":"Fraud Risk Assessment","family":"rm","control_type":"detective","frequency":"annual","summary":"Assess the potential for fraud, including management override, as part of risk assessment and document the controls that address it.\n","statement":"Assess fraud risk {{ fraud_assessment_frequency }}, considering motive, opportunity, and rationalization for the workforce and third parties, the potential for management override of controls, and fraud scenarios relevant to the system such as misuse of privileged access or manipulation of customer or billing data. Document each scenario with its rating and mitigating controls, and review the results with {{ fraud_review_audience }}.\n","objective":"The organization has considered how fraud could compromise its systems and commitments, and each identified scenario has a documented response.\n","guidance":"Perform it as a dedicated section of the annual risk assessment (OGRL-RM-02) and record scenarios in the same register with a fraud tag. Typical SaaS scenarios: an engineer altering production data, an admin granting themselves access, payment redirection through a vendor change request, and executives bypassing change approval. Evidence: the fraud section of the assessment and its review record.\n","parameters":{"fraud_assessment_frequency":{"label":"Fraud risk assessment frequency","value":"at least annually"},"fraud_review_audience":{"label":"Fraud risk review audience","value":"executive leadership and the board or its designated committee"}},"tags":["risk-management","fraud","risk-assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-rm-03-to-800-53-ra-3-a-1","source_ref":"control--ogrl-rm-03","target_ref":"requirement--nist-sp-800-53-r5-ra-3#a.1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Fraud and insider-misuse scenarios are one category of threat identified in a system risk assessment.\n"},{"id":"mapping--ogrl-rm-03-to-soc2-cc3-3","source_ref":"control--ogrl-rm-03","target_ref":"requirement--soc2-tsc-2017-cc3-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Directly addresses consideration of fraud potential in risk assessment; the criterion's broader scope is not claimed.\n"}],"yaml_path":"library/control/ogrl-rm-03.yaml"},{"id":"control--ogrl-rm-04","slug":"ogrl-rm-04","display_id":"OGRL-RM-04","name":"Risk Treatment Tracking","family":"rm","control_type":"corrective","frequency":"quarterly","summary":"Record a treatment decision, owner, and target date for each risk above tolerance, with approved and time-bound risk acceptances.\n","statement":"For each risk rated above {{ risk_tolerance_threshold }}, record a treatment decision (mitigate, transfer, avoid, or accept), an owner, and a target date. Risk acceptances require documented approval by {{ risk_acceptance_authority }} and expire after {{ acceptance_duration }}. Review treatment progress and acceptances {{ treatment_review_frequency }}.\n","objective":"Every risk outside tolerance has an accountable, tracked response consistent with leadership's risk appetite.\n","guidance":"Track treatment in the risk register or link register entries to tickets. Mitigation plans should reference the controls being added or strengthened; transfer should reference the contract or insurance policy. Evidence: register entries with decisions, approvals, and review dates.\n","parameters":{"acceptance_duration":{"label":"Maximum risk acceptance duration","value":"12 months"},"risk_acceptance_authority":{"label":"Risk acceptance authority","value":"the CEO for high risks and the security leader for others"},"risk_tolerance_threshold":{"label":"Risk tolerance threshold","value":"the tolerance level defined in the risk methodology"},"treatment_review_frequency":{"label":"Treatment review frequency","value":"quarterly"}},"tags":["risk-management","risk-treatment"],"tests":[],"mappings":[{"id":"mapping--ogrl-rm-04-to-800-53-ra-7","source_ref":"control--ogrl-rm-04","target_ref":"requirement--nist-sp-800-53-r5-ra-7","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Responds to risk assessment results in line with risk tolerance; responses to audit and monitoring findings are covered by deficiency tracking.\n"},{"id":"mapping--ogrl-rm-04-to-soc2-cc3-2","source_ref":"control--ogrl-rm-04","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Determining and tracking how each identified risk will be managed."},{"id":"mapping--ogrl-rm-04-to-soc2-cc9-1","source_ref":"control--ogrl-rm-04","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Treatment decisions mitigate identified risks, including risks of business disruption.\n"}],"yaml_path":"library/control/ogrl-rm-04.yaml"},{"id":"control--ogrl-rm-05","slug":"ogrl-rm-05","display_id":"OGRL-RM-05","name":"Significant Change Risk Evaluation","family":"rm","control_type":"detective","frequency":"event-driven","summary":"Evaluate security risk before significant changes take effect and update the risk register accordingly.\n","statement":"Before a significant change takes effect, including {{ significant_changes }}, evaluate its effect on security risk and on existing controls, document the evaluation, update the risk register, and obtain approval from {{ change_risk_approver }}.\n","objective":"Risk and control impacts of significant changes are understood and addressed before the changes take effect.\n","guidance":"Trigger the evaluation from the architecture review or design-doc template, vendor onboarding, and leadership or legal change processes. A short structured note (what changed, new risks, affected controls, decision) linked to the register entry is sufficient. Routine code changes are covered by change management, not this control.\n","parameters":{"change_risk_approver":{"label":"Change risk approver","value":"the security leader"},"significant_changes":{"label":"Changes requiring risk evaluation","value":"new products or major features, architecture or hosting changes, new critical vendors, acquisitions, leadership changes, and new regulatory obligations\n"}},"tags":["risk-management","change-management","risk-assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-rm-05-to-800-53-ra-3-f","source_ref":"control--ogrl-rm-05","target_ref":"requirement--nist-sp-800-53-r5-ra-3#f","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Covers the change-driven update of the risk assessment; periodic updates are covered by periodic risk assessment.\n"},{"id":"mapping--ogrl-rm-05-to-soc2-cc3-4","source_ref":"control--ogrl-rm-05","target_ref":"requirement--soc2-tsc-2017-cc3-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Evaluates internal and external changes for their effect on risk and controls."}],"yaml_path":"library/control/ogrl-rm-05.yaml"},{"id":"control--ogrl-rm-06","slug":"ogrl-rm-06","display_id":"OGRL-RM-06","name":"Cyber Insurance","family":"rm","control_type":"corrective","frequency":"annual","summary":"Maintain cyber insurance sized to the organization's risk and review its adequacy at each renewal.\n","statement":"Maintain cyber liability insurance with limits of at least {{ coverage_minimum }} that covers incident response costs, business interruption, and third-party liability arising from security incidents. Review coverage adequacy against the risk register and customer contractual requirements {{ insurance_review_frequency }}.\n","objective":"The financial impact of a significant security incident is partially transferred, consistent with risk treatment decisions and customer commitments.\n","guidance":"Many enterprise customer contracts specify minimum cyber coverage; record those in the commitments register (OGRL-GV-07). Note insurer requirements such as MFA or EDR that become implicit control commitments, and include the carrier's breach hotline in the incident response plan. Evidence: the current certificate of insurance and the renewal review record.\n","parameters":{"coverage_minimum":{"label":"Minimum aggregate coverage limit","value":"USD 2,000,000 or the highest amount required by customer contracts"},"insurance_review_frequency":{"label":"Coverage review frequency","value":"at least annually at renewal"}},"tags":["risk-management","insurance","risk-transfer"],"tests":[],"mappings":[{"id":"mapping--ogrl-rm-06-to-soc2-cc9-1","source_ref":"control--ogrl-rm-06","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Insurance is a risk transfer mechanism for losses from business disruption."}],"yaml_path":"library/control/ogrl-rm-06.yaml"},{"id":"control--ogrl-sd-01","slug":"ogrl-sd-01","display_id":"OGRL-SD-01","name":"Secure Development Lifecycle","family":"sd","control_type":"preventive","frequency":"annual","summary":"Maintain a documented SDLC that builds security activities, roles, and design principles into every phase.\n","statement":"Maintain a documented secure development lifecycle that defines required security activities for design, implementation, testing, release, and maintenance, requires threat modeling for {{ threat_model_triggers }}, applies {{ secure_design_principles }}, assigns security responsibilities to named roles, and is reviewed and approved by {{ sdlc_owner }} {{ sdlc_review_frequency }}.\n","objective":"Ensure security is designed into systems consistently rather than added after release.\n","guidance":"Keep the SDLC as a short engineering handbook page that links to the concrete gates: design review template, code review (OGRL-SD-02), automated scanning (OGRL-SD-03), branch protection (OGRL-SD-04), and change testing (OGRL-CM-07). Record approval with a dated sign-off. Reference OWASP SAMM or NIST SSDF if a maturity model is helpful.\n","parameters":{"sdlc_owner":{"label":"SDLC approval authority","value":"the head of engineering and the security lead"},"sdlc_review_frequency":{"label":"SDLC review frequency","value":"annually"},"secure_design_principles":{"label":"Secure design principles","value":"least privilege, defense in depth, secure defaults, and attack-surface minimization\n"},"threat_model_triggers":{"label":"Work requiring threat modeling","value":"new services, new external integrations, and major architecture changes"}},"tags":["sdlc","secure-development","threat-modeling"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-01-to-800-53-sa-3-a","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-3#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"A documented SDLC with security activities in each phase satisfies SA-3(a)."},{"id":"mapping--ogrl-sd-01-to-800-53-sa-3-b","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-3#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The SDLC assigns security responsibilities to named roles, addressing SA-3(b)."},{"id":"mapping--ogrl-sd-01-to-800-53-sa-3-d","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-3#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Threat modeling integrates risk analysis into development, partly addressing SA-3(d).\n"},{"id":"mapping--ogrl-sd-01-to-800-53-sa-8","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-8","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"sa_8_prm_1":"secure_design_principles"},"summary":"The SDLC names secure design principles to apply, supplying the SA-8 principles; application across all lifecycle stages is broader.\n"},{"id":"mapping--ogrl-sd-01-to-soc2-cc5-2","source_ref":"control--ogrl-sd-01","target_ref":"requirement--soc2-tsc-2017-cc5-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The SDLC is a technology general control over development, contributing to CC5.2.\n"},{"id":"mapping--ogrl-sd-01-to-soc2-cc8-1","source_ref":"control--ogrl-sd-01","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A secure SDLC governs how changes are designed and developed, contributing to CC8.1.\n"}],"yaml_path":"library/control/ogrl-sd-01.yaml"},{"id":"control--ogrl-sd-02","slug":"ogrl-sd-02","display_id":"OGRL-SD-02","name":"Peer Code Review","family":"sd","control_type":"preventive","frequency":"event-driven","summary":"Require security-qualified review of changes to security-sensitive code before merge.\n","statement":"Require every pull request that modifies {{ security_sensitive_code }} to be reviewed and approved by {{ security_code_reviewer }} using {{ code_review_techniques }} before merge, enforced through code-owner rules in the source control platform.\n","objective":"Catch security defects in high-risk code paths that general peer review and automated scanning may miss.\n","guidance":"Map security-sensitive paths in a CODEOWNERS file to a security reviewer group and enable the require-code-owner-review branch protection setting. General independent peer review of all production changes is covered by OGRL-CM-01; this control adds security-focused review for high-risk code.\n","parameters":{"code_review_techniques":{"label":"Security code review technique","value":"the organization's secure code review checklist covering OWASP Top 10 weakness classes\n"},"security_code_reviewer":{"label":"Security code reviewer","value":"a designated security code owner other than the author"},"security_sensitive_code":{"label":"Security-sensitive code requiring security review","value":"authentication, authorization, cryptography, session management, payment, and tenant-isolation code paths\n"}},"tags":["code-review","secure-development","sdlc"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-02-to-800-53-sa-11-4","source_ref":"control--ogrl-sd-02","target_ref":"requirement--nist-sp-800-53-r5-sa-11-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sa_11_04_odp_01":"security_sensitive_code","sa_11_04_odp_02":"code_review_techniques"},"summary":"Checklist-driven manual review of designated security-sensitive code satisfies SA-11(4).\n"},{"id":"mapping--ogrl-sd-02-to-soc2-cc8-1","source_ref":"control--ogrl-sd-02","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Security review of high-risk code before merge is part of authorizing and testing changes under CC8.1.\n"}],"yaml_path":"library/control/ogrl-sd-02.yaml"},{"id":"control--ogrl-sd-03","slug":"ogrl-sd-03","display_id":"OGRL-SD-03","name":"Static Analysis and Dependency Scanning","family":"sd","control_type":"detective","frequency":"event-driven","summary":"Run SAST, secret scanning, and dependency analysis on every pull request and block merges on serious findings.\n","statement":"Run static application security testing, secret scanning, and software composition analysis on every pull request to {{ scanned_repositories }}, block merge on unresolved findings rated {{ blocking_severity }} or above unless an exception is approved by {{ scan_exception_approver }}, and retain scan results with the change record.\n","objective":"Prevent common code flaws, leaked secrets, and known-vulnerable dependencies from being merged.\n","guidance":"Use CI-integrated tools such as CodeQL or Semgrep, GitHub secret scanning with push protection, and Dependabot or Snyk, configured as required status checks. Track approved exceptions with an expiry date. Ongoing scanning of deployed images and dependencies is covered by OGRL-VM-01.\n","parameters":{"blocking_severity":{"label":"Minimum blocking severity","value":"high"},"scan_exception_approver":{"label":"Scan exception approver","value":"the security lead"},"scanned_repositories":{"label":"Repositories subject to scanning","value":"all repositories that build or deploy production code or infrastructure"}},"tags":["sast","dependency-scanning","ci-cd"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-03-to-800-53-sa-11-1","source_ref":"control--ogrl-sd-03","target_ref":"requirement--nist-sp-800-53-r5-sa-11-1","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Static analysis on every pull request with retained results meets SA-11(1), with secret and dependency scanning added.\n"},{"id":"mapping--ogrl-sd-03-to-soc2-cc7-1","source_ref":"control--ogrl-sd-03","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Pre-merge scanning identifies vulnerabilities introduced by new code, overlapping CC7.1 detection activities.\n"},{"id":"mapping--ogrl-sd-03-to-soc2-cc8-1","source_ref":"control--ogrl-sd-03","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated security testing gates contribute to testing changes before implementation under CC8.1.\n"}],"yaml_path":"library/control/ogrl-sd-03.yaml"},{"id":"control--ogrl-sd-04","slug":"ogrl-sd-04","display_id":"OGRL-SD-04","name":"Source Control and Branch Protection","family":"sd","control_type":"preventive","frequency":"continuous","summary":"Keep all production code and configuration in managed source control with enforced branch protection.\n","statement":"Maintain {{ versioned_assets }} in {{ source_control_platform }}, enforce branch protection on {{ protected_branches }} that blocks direct pushes, force-pushes, and deletion and requires an approved pull request with passing checks to merge, and verify protection settings on all production repositories {{ branch_protection_review_frequency }}.\n","objective":"Ensure every production change is versioned, attributable, and can only enter protected branches through the approved workflow.\n","guidance":"Apply organization-level rulesets so new repositories inherit protection, disallow administrator bypass, and require SSO for platform access. Script a quarterly export of branch protection settings across repositories (for example via the GitHub API) as evidence. Review content requirements are covered by OGRL-CM-01 and OGRL-SD-02.\n","parameters":{"branch_protection_review_frequency":{"label":"Branch protection verification frequency","value":"quarterly"},"protected_branches":{"label":"Protected branches","value":"default and release branches"},"source_control_platform":{"label":"Source control platform","value":"the organization's SSO-enforced source control platform"},"versioned_assets":{"label":"Assets kept under source control","value":"application source code, infrastructure-as-code, CI/CD pipeline definitions, and deployment configuration\n"}},"tags":["source-control","branch-protection","sdlc"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-04-to-800-53-sa-10-b","source_ref":"control--ogrl-sd-04","target_ref":"requirement--nist-sp-800-53-r5-sa-10#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sa_10_odp_02":"versioned_assets"},"summary":"Versioning all production assets and protecting branches controls the integrity of changes to configuration items per SA-10(b).\n"},{"id":"mapping--ogrl-sd-04-to-800-53-sa-10-c","source_ref":"control--ogrl-sd-04","target_ref":"requirement--nist-sp-800-53-r5-sa-10#c","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Branch protection ensures only approved pull requests enter release branches, partly enforcing SA-10(c).\n"},{"id":"mapping--ogrl-sd-04-to-soc2-cc8-1","source_ref":"control--ogrl-sd-04","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Protected, versioned source control enforces the authorized path for changes under CC8.1.\n"}],"yaml_path":"library/control/ogrl-sd-04.yaml"},{"id":"control--ogrl-sd-05","slug":"ogrl-sd-05","display_id":"OGRL-SD-05","name":"Processing Specifications and Data Definitions","family":"sd","control_type":"preventive","frequency":"event-driven","summary":"Document and maintain versioned specifications of inputs, processing rules, and outputs for in-scope systems.\n","statement":"Document, for each in-scope processing system, the input data definitions, accepted formats and value ranges, processing rules, and expected outputs in version-controlled specifications, update them with every change that alters processing behavior, have them reviewed by {{ spec_owner }} {{ spec_review_frequency }}, and make them available to {{ spec_audience }}.\n","objective":"Provide a single accurate reference for how each system is expected to process data, so processing can be built, tested, and verified against it.\n","guidance":"Machine-readable specifications work best: OpenAPI or GraphQL schemas, JSON Schema or protobuf data contracts, and database schema migrations, supplemented by short design notes for business rules. Generate customer-facing API documentation from the same source. Input validation (OGRL-SD-06) and output validation (OGRL-SD-08) should enforce these definitions.\n","parameters":{"spec_audience":{"label":"Specification audience","value":"engineering, support, and customers through published API documentation"},"spec_owner":{"label":"Specification owner","value":"the product or engineering owner of each system"},"spec_review_frequency":{"label":"Specification review frequency","value":"annually"}},"tags":["processing-integrity","documentation","data-definitions"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-05-to-800-53-pl-2-a-5","source_ref":"control--ogrl-sd-05","target_ref":"requirement--nist-sp-800-53-r5-pl-2#a.5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Data definitions identify the information types a system processes, loosely overlapping PL-2(a)(5).\n"},{"id":"mapping--ogrl-sd-05-to-800-53-sa-5-d","source_ref":"control--ogrl-sd-05","target_ref":"requirement--nist-sp-800-53-r5-sa-5#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"sa_05_odp_02":"spec_audience"},"summary":"Processing specifications are distributed to defined audiences, overlapping SA-5(d) distribution of system documentation.\n"},{"id":"mapping--ogrl-sd-05-to-soc2-pi1-1","source_ref":"control--ogrl-sd-05","target_ref":"requirement--soc2-tsc-2017-pi1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Documented data definitions and processing specifications support PI1.1."}],"yaml_path":"library/control/ogrl-sd-05.yaml"},{"id":"control--ogrl-sd-06","slug":"ogrl-sd-06","display_id":"OGRL-SD-06","name":"Input Validation","family":"sd","control_type":"preventive","frequency":"continuous","summary":"Validate all external inputs against defined schemas before processing and reject or quarantine invalid data.\n","statement":"Validate inputs received through {{ validated_input_channels }} against defined schemas for type, length, format, and range before processing, reject or quarantine invalid inputs and log the reason, and verify validation behavior with automated tests in the CI pipeline.\n","objective":"Ensure only complete, well-formed, and expected data enters processing, protecting both data accuracy and the application from injection attacks.\n","guidance":"Enforce validation at the API boundary with schema validators generated from the specification (for example OpenAPI request validation, zod, or pydantic). Use allow-list validation, parameterized queries, and size limits on uploads. Batch imports should report rejected rows back to the submitter.\n","parameters":{"validated_input_channels":{"label":"Input channels subject to validation","value":"public APIs, user interface forms, file uploads, webhooks, and batch data imports\n"}},"tags":["input-validation","processing-integrity","application-security"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-06-to-800-53-si-10","source_ref":"control--ogrl-sd-06","target_ref":"requirement--nist-sp-800-53-r5-si-10","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_10_odp":"validated_input_channels"},"summary":"Schema-based validity checks on named input channels satisfy SI-10."},{"id":"mapping--ogrl-sd-06-to-soc2-pi1-2","source_ref":"control--ogrl-sd-06","target_ref":"requirement--soc2-tsc-2017-pi1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Validating inputs for completeness and accuracy before processing contributes to PI1.2.\n"}],"yaml_path":"library/control/ogrl-sd-06.yaml"},{"id":"control--ogrl-sd-07","slug":"ogrl-sd-07","display_id":"OGRL-SD-07","name":"Error Handling","family":"sd","control_type":"corrective","frequency":"continuous","summary":"Return safe error messages, keep error detail restricted, and never silently drop failed transactions.\n","statement":"Implement application error handling that returns messages giving users enough information to correct the problem without exposing stack traces, internal identifiers, queries, or system details, records detailed error information only in logs accessible to {{ error_detail_roles }}, and rolls back or routes failed transactions to {{ error_queue }} for retry or correction so that no processing failure is silently discarded.\n","objective":"Ensure processing errors are corrected rather than lost, without leaking information useful to an attacker.\n","guidance":"Use a global exception handler that maps exceptions to generic responses with a correlation ID. Disable framework debug modes in production. Wrap multi-step writes in transactions and configure dead-letter queues with alerting on depth for asynchronous consumers. Reconciliation of processed volumes is covered by OGRL-LM-05.\n","parameters":{"error_detail_roles":{"label":"Roles permitted to view detailed errors","value":"authorized engineering and support personnel"},"error_queue":{"label":"Failed transaction handling destination","value":"a monitored dead-letter or error queue"}},"tags":["error-handling","processing-integrity","application-security"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-07-to-800-53-si-11-a","source_ref":"control--ogrl-sd-07","target_ref":"requirement--nist-sp-800-53-r5-si-11#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"User-facing errors that aid correction without revealing exploitable details satisfy SI-11(a).\n"},{"id":"mapping--ogrl-sd-07-to-800-53-si-11-b","source_ref":"control--ogrl-sd-07","target_ref":"requirement--nist-sp-800-53-r5-si-11#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_11_odp":"error_detail_roles"},"summary":"Detailed error information is restricted to defined roles per SI-11(b)."},{"id":"mapping--ogrl-sd-07-to-soc2-pi1-3","source_ref":"control--ogrl-sd-07","target_ref":"requirement--soc2-tsc-2017-pi1-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Rolling back or queuing failed transactions for correction supports complete and accurate processing under PI1.3.\n"}],"yaml_path":"library/control/ogrl-sd-07.yaml"},{"id":"control--ogrl-sd-08","slug":"ogrl-sd-08","display_id":"OGRL-SD-08","name":"Output Validation and Distribution","family":"sd","control_type":"detective","frequency":"event-driven","summary":"Validate system outputs before release and deliver them only to authorized recipients.\n","statement":"Validate outputs from {{ validated_output_sources }} against expected schemas, record counts, or control totals before release, deliver outputs only to authorized recipients through {{ output_delivery_channels }}, and hold, investigate, and correct any output that fails validation before it is redistributed.\n","objective":"Ensure outputs are complete, accurate, and reach only their intended recipients.\n","guidance":"Apply response schema validation in API tests, compare export row counts with source query counts, and enforce tenant scoping on download and API endpoints. Failed validations should block publication and page the owning team.\n","parameters":{"output_delivery_channels":{"label":"Authorized output delivery channels","value":"authenticated APIs, tenant-scoped downloads, and encrypted transfer channels"},"validated_output_sources":{"label":"Outputs subject to validation","value":"customer-facing reports, data exports, outbound data feeds, and API responses with defined schemas\n"}},"tags":["output-validation","processing-integrity","data-distribution"],"tests":[],"mappings":[{"id":"mapping--ogrl-sd-08-to-800-53-si-15","source_ref":"control--ogrl-sd-08","target_ref":"requirement--nist-sp-800-53-r5-si-15","relationship":"superset-of","review_status":"reviewed","parameter_map":{"si_15_odp":"validated_output_sources"},"summary":"Validating outputs against expected content meets SI-15, with authorized distribution added.\n"},{"id":"mapping--ogrl-sd-08-to-soc2-pi1-4","source_ref":"control--ogrl-sd-08","target_ref":"requirement--soc2-tsc-2017-pi1-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Output validation and restricted delivery support complete, accurate, and properly distributed outputs under PI1.4.\n"}],"yaml_path":"library/control/ogrl-sd-08.yaml"},{"id":"control--ogrl-tp-01","slug":"ogrl-tp-01","display_id":"OGRL-TP-01","name":"Vendor Inventory and Risk Tiering","family":"tp","control_type":"preventive","frequency":"annual","summary":"Keep an inventory of vendors that touch in-scope systems or data, each with an owner and a risk tier.\n","statement":"Maintain an inventory of every third party that stores, processes, or accesses customer data or supports in-scope systems, recording for each its internal owner, services provided, data shared, and a risk tier assigned using {{ tiering_criteria }}; add each vendor to the inventory before production use or data sharing, and review the full inventory {{ inventory_review_frequency }}.\n","objective":"Know which third parties the service depends on and how much risk each one carries, so oversight effort can be proportionate.\n","guidance":"Seed the inventory from finance and expense data, SSO application catalogs, and infrastructure-as-code provider lists to catch shadow vendors. Flag subservice organizations that will be carved out of the SOC 2 report. The risk tier drives due diligence depth (OGRL-TP-02) and monitoring cadence (OGRL-TP-04).\n","parameters":{"inventory_review_frequency":{"label":"Vendor inventory review frequency","value":"at least annually"},"tiering_criteria":{"label":"Risk tiering criteria","value":"the sensitivity of data shared, level of system access, and operational criticality of the service\n"}},"tags":["vendor-management","inventory","risk-assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-tp-01-to-800-53-sa-9-b","source_ref":"control--ogrl-tp-01","target_ref":"requirement--nist-sp-800-53-r5-sa-9#b","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Assigning an internal owner to each external service documents oversight responsibility; broader user roles and responsibilities are not addressed.\n"},{"id":"mapping--ogrl-tp-01-to-800-53-sr-2-a","source_ref":"control--ogrl-tp-01","target_ref":"requirement--nist-sp-800-53-r5-sr-2#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A tiered vendor inventory is a core input to supply chain risk planning but is not itself a supply chain risk management plan.\n"},{"id":"mapping--ogrl-tp-01-to-soc2-cc9-2","source_ref":"control--ogrl-tp-01","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Identifying vendors and tiering their risk is the starting point for vendor risk management under CC9.2.\n"}],"yaml_path":"library/control/ogrl-tp-01.yaml"},{"id":"control--ogrl-tp-02","slug":"ogrl-tp-02","display_id":"OGRL-TP-02","name":"Vendor Security Due Diligence","family":"tp","control_type":"preventive","frequency":"event-driven","summary":"Assess the security and privacy posture of higher-risk vendors and approve the risk before signing or sharing data.\n","statement":"Before onboarding any vendor rated {{ diligence_tiers }}, and again when the services or data shared materially change, assess its security and privacy posture using {{ assessment_evidence }}, document findings and any accepted risks, and obtain approval from {{ vendor_risk_approver }} before contract signature or data sharing.\n","objective":"Avoid taking on vendors whose security posture is inconsistent with the organization's commitments to customers.\n","guidance":"Scale the assessment to the tier: an independent assurance report review for critical vendors, a standard questionnaire for moderate ones, and a lightweight checklist for low-risk tools. Route approvals through procurement so contracts cannot be signed without security sign-off. Periodic reassessment after onboarding is covered by OGRL-TP-04.\n","parameters":{"assessment_evidence":{"label":"Due diligence evidence","value":"a current SOC 2 Type II report, ISO/IEC 27001 certificate, or completed security questionnaire\n"},"diligence_tiers":{"label":"Vendor tiers requiring due diligence","value":"high or moderate risk"},"vendor_risk_approver":{"label":"Vendor risk approval authority","value":"the security team"}},"tags":["vendor-management","due-diligence","risk-assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-tp-02-to-800-53-sr-6","source_ref":"control--ogrl-tp-02","target_ref":"requirement--nist-sp-800-53-r5-sr-6","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Pre-onboarding and change-triggered supplier assessments address SR-6; periodic reassessment is handled by OGRL-TP-04.\n"},{"id":"mapping--ogrl-tp-02-to-soc2-cc9-2","source_ref":"control--ogrl-tp-02","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Assessing vendor security before engagement is a key vendor risk management activity under CC9.2.\n"}],"yaml_path":"library/control/ogrl-tp-02.yaml"},{"id":"control--ogrl-tp-03","slug":"ogrl-tp-03","display_id":"OGRL-TP-03","name":"Vendor Contract Security and Privacy Requirements","family":"tp","control_type":"preventive","frequency":"event-driven","summary":"Put security, confidentiality, privacy, and breach notification obligations in writing before sharing sensitive data with a vendor.\n","statement":"Execute a written agreement with every vendor that will store, process, or access confidential or personal data before sharing that data, including security and confidentiality obligations, data protection terms that restrict use to the contracted purpose, notification of security incidents or unauthorized disclosures affecting organizational data within {{ breach_notification_window }}, disclosure of subprocessors, return or deletion of data at termination, and the right to obtain {{ assurance_rights }}.\n","objective":"Make vendors contractually accountable for protecting the organization's and its customers' data.\n","guidance":"Maintain a standard security addendum and data processing agreement; legal tracks deviations and security approves them. Align the vendor notification window with the organization's own customer notification commitments. Record contract status in the vendor inventory so missing agreements are visible.\n","parameters":{"assurance_rights":{"label":"Assurance rights required from vendors","value":"independent audit reports or security questionnaire responses at least annually"},"breach_notification_window":{"label":"Vendor breach notification deadline","value":"72 hours"}},"tags":["vendor-management","contracts","privacy"],"tests":[],"mappings":[{"id":"mapping--ogrl-tp-03-to-800-53-sa-4","source_ref":"control--ogrl-tp-03","target_ref":"requirement--nist-sp-800-53-r5-sa-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Contractual security, privacy, and responsibility-allocation terms overlap SA-4 acquisition requirements, which also address system development and assurance criteria not covered here.\n"},{"id":"mapping--ogrl-tp-03-to-800-53-sr-3-b","source_ref":"control--ogrl-tp-03","target_ref":"requirement--nist-sp-800-53-r5-sr-3#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Contract terms are one control employed to limit harm from supply chain events.\n"},{"id":"mapping--ogrl-tp-03-to-soc2-c1-1","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Vendor confidentiality and deletion obligations help protect confidential information under C1.1.\n"},{"id":"mapping--ogrl-tp-03-to-soc2-cc9-2","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Contractual security requirements are a primary means of managing vendor risk under CC9.2.\n"},{"id":"mapping--ogrl-tp-03-to-soc2-p6-4","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-p6-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Data protection terms bind vendors with access to personal information to privacy obligations relevant to P6.4.\n"},{"id":"mapping--ogrl-tp-03-to-soc2-p6-5","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-p6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Required vendor notification of unauthorized disclosures supports P6.5.\n"}],"yaml_path":"library/control/ogrl-tp-03.yaml"},{"id":"control--ogrl-tp-04","slug":"ogrl-tp-04","display_id":"OGRL-TP-04","name":"Ongoing Vendor Monitoring and SOC Report Review","family":"tp","control_type":"detective","frequency":"annual","summary":"Periodically review assurance reports for critical vendors and act on exceptions and complementary controls.\n","statement":"For each vendor rated {{ monitored_tiers }}, obtain and review {{ assurance_evidence }} {{ monitoring_frequency }}; evaluate reported exceptions, coverage gaps, and complementary user entity controls the organization must operate; track remediation of identified issues; and record the review outcome and any risk acceptance.\n","objective":"Detect deterioration in vendor security posture and confirm the organization performs its share of vendor-dependent controls.\n","guidance":"Track report periods and request bridge letters when coverage lapses. Map each relevant complementary user entity control to an internal control or owner. Subservice organizations carved out of the organization's own SOC 2 report need this review as evidence of monitoring. Also monitor public breach disclosures for critical vendors.\n","parameters":{"assurance_evidence":{"label":"Vendor assurance evidence reviewed","value":"the vendor's most recent SOC 2 Type II report, ISO/IEC 27001 certificate, or equivalent independent assessment\n"},"monitored_tiers":{"label":"Vendor tiers subject to periodic monitoring","value":"high risk"},"monitoring_frequency":{"label":"Vendor monitoring frequency","value":"annually"}},"tags":["vendor-management","monitoring","assurance-reports"],"tests":[],"mappings":[{"id":"mapping--ogrl-tp-04-to-800-53-sa-9-c","source_ref":"control--ogrl-tp-04","target_ref":"requirement--nist-sp-800-53-r5-sa-9#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sa_09_odp_02":"assurance_evidence"},"summary":"Periodic review of vendor assurance reports is the method used to monitor provider control compliance on an ongoing basis.\n"},{"id":"mapping--ogrl-tp-04-to-soc2-cc4-1","source_ref":"control--ogrl-tp-04","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Evaluating third-party assurance reports is a form of ongoing evaluation of controls relevant to CC4.1.\n"},{"id":"mapping--ogrl-tp-04-to-soc2-cc9-2","source_ref":"control--ogrl-tp-04","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Ongoing review of vendor assurance reports is a vendor monitoring activity under CC9.2.\n"}],"yaml_path":"library/control/ogrl-tp-04.yaml"},{"id":"control--ogrl-vm-01","slug":"ogrl-vm-01","display_id":"OGRL-VM-01","name":"Vulnerability Scanning and SLA-Driven Remediation","family":"vm","control_type":"detective","frequency":"weekly","summary":"Scan infrastructure, containers, and dependencies continuously for vulnerabilities and remediate findings within risk-based SLAs.\n","statement":"Scan in-scope infrastructure, container images, and application dependencies for vulnerabilities {{ scan_cadence }}, remediate confirmed findings within {{ remediation_sla }}, and share advisories with {{ advisory_audience }}.\n","objective":"Identify and remediate exploitable software flaws and misconfigurations before adversaries leverage them.\n","guidance":"Combine authenticated infrastructure scanning with CI/CD dependency/container scanning and track open vulnerabilities in an issue tracker with explicit SLA due dates.\n","parameters":{"advisory_audience":{"label":"Internal advisory recipients","value":"engineering service owners and platform security leads"},"remediation_sla":{"label":"Vulnerability remediation SLA","value":"15 days for critical and 30 days for high severity findings"},"scan_cadence":{"label":"Vulnerability scanning frequency","value":"at least weekly and on every release"}},"tags":["vulnerability-management","scanning","risk"],"tests":[{"id":"test--ogrl-vm-01-vuln-scanning","slug":"ogrl-vm-01-vuln-scanning","name":"Verify Vulnerability Scan Cadence and SLA Compliance","method":"automated","interval":"weekly","required":true,"description":"Confirm vulnerability scans completed within the configured cadence and no confirmed critical or high findings remain open past their remediation SLA.\n","objective_refs":["requirement--nist-sp-800-53-r5-ra-5#obj.a-2","requirement--nist-sp-800-53-r5-ra-5#obj.d"],"yaml_path":"library/test/ogrl-vm-01-vuln-scanning.yaml"}],"mappings":[{"id":"mapping--ogrl-vm-01-to-800-171-03-11-02","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-171-r3-03-11-02","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"a_03_11_02_odp_01":"scan_cadence","a_03_11_02_odp_03":"remediation_sla"},"summary":"Continuous vulnerability scanning and SLA remediation satisfy SP 800-171 03.11.02.\n"},{"id":"mapping--ogrl-vm-01-to-800-53-ra-5-a","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-53-r5-ra-5#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_5_prm_1":"scan_cadence"},"summary":"Scheduled infrastructure and release vulnerability scanning satisfies NIST RA-5(a).\n"},{"id":"mapping--ogrl-vm-01-to-800-53-ra-5-d","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-53-r5-ra-5#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_05_odp_03":"remediation_sla"},"summary":"Risk-based vulnerability remediation SLAs directly satisfy NIST RA-5(d)."},{"id":"mapping--ogrl-vm-01-to-800-53-ra-5-e","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-53-r5-ra-5#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_05_odp_04":"advisory_audience"},"summary":"Sharing vulnerability advisories with service owners satisfies NIST RA-5(e)."},{"id":"mapping--ogrl-vm-01-to-soc2-cc3-2","source_ref":"control--ogrl-vm-01","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Continuous vulnerability scanning identifies technical risks informing SOC 2 CC3.2.\n"},{"id":"mapping--ogrl-vm-01-to-soc2-cc7-1","source_ref":"control--ogrl-vm-01","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Vulnerability scanning and SLA remediation satisfy SOC 2 CC7.1 detection obligations.\n"}],"yaml_path":"library/control/ogrl-vm-01.yaml"},{"id":"control--ogrl-vm-02","slug":"ogrl-vm-02","display_id":"OGRL-VM-02","name":"Flaw Remediation and Patching","family":"vm","control_type":"corrective","frequency":"continuous","summary":"Apply security updates within defined timeframes after testing, through the normal change process.\n","statement":"Install security-relevant updates for operating systems, container base images, language runtimes, and third-party dependencies within {{ patch_sla }} of vendor release, test each update in a non-production environment before production deployment, and deploy updates through the standard change management process.\n","objective":"Close known software flaws quickly without destabilizing production.\n","guidance":"Automate update pull requests (for example Dependabot or Renovate), rebuild images on base-image releases, and enable managed-service auto-patching with maintenance windows. Track patch age as a metric against the SLA. Vulnerability identification and scanning is covered by OGRL-VM-01.\n","parameters":{"patch_sla":{"label":"Security update installation SLA","value":"14 days for critical, 30 days for high, and 90 days for other security updates"}},"tags":["patching","vulnerability-management","change-management"],"tests":[],"mappings":[{"id":"mapping--ogrl-vm-02-to-800-53-si-2-a","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#a","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Applying security updates corrects system flaws; identification and reporting are handled by vulnerability scanning.\n"},{"id":"mapping--ogrl-vm-02-to-800-53-si-2-b","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Updates are tested in non-production before production deployment per SI-2(b)."},{"id":"mapping--ogrl-vm-02-to-800-53-si-2-c","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_02_odp":"patch_sla"},"summary":"A defined installation timeframe for security updates satisfies SI-2(c)."},{"id":"mapping--ogrl-vm-02-to-800-53-si-2-d","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Patches flow through the standard change process, incorporating flaw remediation into configuration management per SI-2(d).\n"},{"id":"mapping--ogrl-vm-02-to-soc2-cc7-1","source_ref":"control--ogrl-vm-02","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Timely patching remediates the vulnerabilities that CC7.1 monitoring identifies."},{"id":"mapping--ogrl-vm-02-to-soc2-cc8-1","source_ref":"control--ogrl-vm-02","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Patches are tested and deployed as controlled changes, contributing to CC8.1."}],"yaml_path":"library/control/ogrl-vm-02.yaml"},{"id":"control--ogrl-vm-03","slug":"ogrl-vm-03","display_id":"OGRL-VM-03","name":"Malware Protection","family":"vm","control_type":"detective","frequency":"continuous","summary":"Run centrally managed, auto-updating anti-malware or EDR on endpoints and hosts and act on detections.\n","statement":"Deploy centrally managed anti-malware or endpoint detection and response on {{ malware_protected_assets }}, keep engines and signatures automatically updated, scan files in real time on download, open, or execution and perform full scans {{ malware_scan_frequency }}, automatically {{ malware_response_action }} detected malicious code and alert {{ malware_alert_recipients }}, and verify agent coverage {{ malware_coverage_review_frequency }}.\n","objective":"Detect and contain malicious code on systems that can execute it.\n","guidance":"Use MDM to deploy and lock the EDR agent on laptops, and runtime protection or EDR on general-purpose production hosts. Immutable containers rely on image scanning and least functionality (OGRL-CM-08) rather than agents. Scan customer-uploaded files before processing where the product accepts uploads. Compare the EDR agent list with the device inventory monthly.\n","parameters":{"malware_alert_recipients":{"label":"Malware detection alert recipients","value":"the security on-call team"},"malware_coverage_review_frequency":{"label":"Agent coverage verification frequency","value":"monthly"},"malware_protected_assets":{"label":"Assets requiring malware protection","value":"workforce endpoints and production hosts running general-purpose operating systems\n"},"malware_response_action":{"label":"Automatic response to detections","value":"block and quarantine"},"malware_scan_frequency":{"label":"Full malware scan frequency","value":"weekly"}},"tags":["malware","endpoint-security","edr"],"tests":[],"mappings":[{"id":"mapping--ogrl-vm-03-to-800-53-si-3-a","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Endpoint and host anti-malware provides detection and eradication, though not necessarily at every system entry and exit point required by SI-3(a).\n"},{"id":"mapping--ogrl-vm-03-to-800-53-si-3-b","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Automatic engine and signature updates satisfy SI-3(b)."},{"id":"mapping--ogrl-vm-03-to-800-53-si-3-c-1","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#c.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_03_odp_02":"malware_scan_frequency"},"summary":"Real-time scanning plus scheduled full scans meet SI-3(c)(1)."},{"id":"mapping--ogrl-vm-03-to-800-53-si-3-c-2","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#c.2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_03_odp_04":"malware_response_action","si_03_odp_06":"malware_alert_recipients"},"summary":"Automatic block or quarantine with alerts to defined recipients meets SI-3(c)(2).\n"},{"id":"mapping--ogrl-vm-03-to-soc2-cc6-8","source_ref":"control--ogrl-vm-03","target_ref":"requirement--soc2-tsc-2017-cc6-8","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Anti-malware detection and quarantine help prevent and detect malicious software under CC6.8.\n"}],"yaml_path":"library/control/ogrl-vm-03.yaml"},{"id":"control--ogrl-vm-04","slug":"ogrl-vm-04","display_id":"OGRL-VM-04","name":"Security Alerts and Threat Intelligence","family":"vm","control_type":"detective","frequency":"continuous","summary":"Receive external security advisories, triage those affecting in-scope technology, and drive required actions.\n","statement":"Subscribe to security advisories and threat intelligence from {{ advisory_sources }}, triage each advisory affecting in-scope technologies within {{ advisory_triage_sla }}, disseminate actionable advisories to {{ advisory_recipients }}, and track required actions to completion in the issue tracker.\n","objective":"Learn about relevant new threats and vulnerabilities promptly and ensure they result in action.\n","guidance":"Route vendor security bulletins, the CISA Known Exploited Vulnerabilities feed, and GitHub security advisories into a shared channel or ticket queue owned by security. Record a triage decision on each relevant advisory. Remediation timelines follow OGRL-VM-01 and OGRL-VM-02.\n","parameters":{"advisory_recipients":{"label":"Advisory dissemination recipients","value":"affected service owners and the engineering on-call channel"},"advisory_sources":{"label":"Advisory and threat intelligence sources","value":"vendors of in-scope software and cloud services, CISA (including the Known Exploited Vulnerabilities catalog), and GitHub security advisories\n"},"advisory_triage_sla":{"label":"Advisory triage SLA","value":"2 business days"}},"tags":["threat-intelligence","vulnerability-management","advisories"],"tests":[],"mappings":[{"id":"mapping--ogrl-vm-04-to-800-53-si-5-a","source_ref":"control--ogrl-vm-04","target_ref":"requirement--nist-sp-800-53-r5-si-5#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_05_odp_01":"advisory_sources"},"summary":"Ongoing subscriptions to named advisory sources satisfy SI-5(a)."},{"id":"mapping--ogrl-vm-04-to-800-53-si-5-c","source_ref":"control--ogrl-vm-04","target_ref":"requirement--nist-sp-800-53-r5-si-5#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Actionable advisories are disseminated to defined internal recipients per SI-5(c).\n"},{"id":"mapping--ogrl-vm-04-to-800-53-si-5-d","source_ref":"control--ogrl-vm-04","target_ref":"requirement--nist-sp-800-53-r5-si-5#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Tracking required actions to completion overlaps SI-5(d), which also covers formal directives and noncompliance notice.\n"},{"id":"mapping--ogrl-vm-04-to-soc2-cc7-1","source_ref":"control--ogrl-vm-04","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Monitoring external advisories helps identify newly discovered vulnerabilities under CC7.1.\n"}],"yaml_path":"library/control/ogrl-vm-04.yaml"},{"id":"control--ogrl-vm-05","slug":"ogrl-vm-05","display_id":"OGRL-VM-05","name":"Penetration Testing","family":"vm","control_type":"detective","frequency":"annual","summary":"Commission independent penetration tests on a schedule and after major changes, and remediate findings.\n","statement":"Engage {{ pentest_provider }} to perform penetration testing of {{ pentest_scope }} {{ pentest_frequency }} and after significant changes to the external attack surface, remediate findings within the organization's vulnerability remediation SLAs, and retest or otherwise validate fixes for critical and high findings.\n","objective":"Find exploitable weaknesses that automated scanning misses and confirm they are fixed.\n","guidance":"Define rules of engagement and scope in a statement of work, include authenticated testing of multi-tenant isolation, and import findings into the vulnerability tracker. Keep the executive summary and retest letter as evidence; many customers will request them.\n","parameters":{"pentest_frequency":{"label":"Penetration test frequency","value":"annually"},"pentest_provider":{"label":"Penetration test provider","value":"a qualified independent third party"},"pentest_scope":{"label":"Penetration test scope","value":"the production application, public APIs, and external-facing cloud infrastructure\n"}},"tags":["penetration-testing","vulnerability-management","assessment"],"tests":[],"mappings":[{"id":"mapping--ogrl-vm-05-to-800-53-ca-8","source_ref":"control--ogrl-vm-05","target_ref":"requirement--nist-sp-800-53-r5-ca-8","relationship":"superset-of","review_status":"reviewed","parameter_map":{"ca_08_odp_01":"pentest_frequency","ca_08_odp_02":"pentest_scope"},"summary":"Scheduled penetration testing of defined systems meets CA-8, with remediation and retesting added.\n"},{"id":"mapping--ogrl-vm-05-to-soc2-cc4-1","source_ref":"control--ogrl-vm-05","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Independent penetration tests are a separate evaluation of control effectiveness relevant to CC4.1.\n"},{"id":"mapping--ogrl-vm-05-to-soc2-cc7-1","source_ref":"control--ogrl-vm-05","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Penetration testing identifies vulnerabilities as part of CC7.1 detection activities.\n"}],"yaml_path":"library/control/ogrl-vm-05.yaml"},{"id":"control--ogrl-vm-06","slug":"ogrl-vm-06","display_id":"OGRL-VM-06","name":"Endpoint and Mobile Device Access Requirements","family":"vm","control_type":"preventive","frequency":"continuous","summary":"Allow access to company systems only from managed devices that meet defined security requirements.\n","statement":"Permit access to organizational systems and data only from laptops and mobile devices enrolled in {{ device_management_platform }} that meet {{ device_security_requirements }}, enforce compliance with device-posture checks at sign-on, and block access from non-compliant devices and revoke access and remotely wipe company data on lost or stolen devices within {{ device_revocation_sla }} of report.\n","objective":"Ensure company data is only accessed from devices that can protect it, including outside the office.\n","guidance":"Combine MDM (for example Jamf, Intune, or Kandji) with identity-provider device trust or conditional access so only compliant devices receive SSO sessions. Use app protection policies or work profiles for personal mobile devices. Evidence is the device compliance policy, the IdP conditional-access rule, and a compliance report.\n","parameters":{"device_management_platform":{"label":"Device management platform","value":"the organization's mobile device management (MDM) platform"},"device_revocation_sla":{"label":"Lost device revocation SLA","value":"24 hours"},"device_security_requirements":{"label":"Device security requirements","value":"full-disk encryption, screen lock after 15 minutes or less, a supported OS with automatic updates, and remote-wipe capability\n"}},"tags":["endpoint-security","mobile-devices","device-trust"],"tests":[],"mappings":[{"id":"mapping--ogrl-vm-06-to-800-53-ac-19-a","source_ref":"control--ogrl-vm-06","target_ref":"requirement--nist-sp-800-53-r5-ac-19#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Defined device security requirements and enrollment conditions establish configuration and connection requirements per AC-19(a).\n"},{"id":"mapping--ogrl-vm-06-to-800-53-ac-19-b","source_ref":"control--ogrl-vm-06","target_ref":"requirement--nist-sp-800-53-r5-ac-19#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Device-posture checks authorize only compliant devices to connect per AC-19(b)."},{"id":"mapping--ogrl-vm-06-to-soc2-cc6-1","source_ref":"control--ogrl-vm-06","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting access to managed, compliant devices is a logical access safeguard under CC6.1.\n"},{"id":"mapping--ogrl-vm-06-to-soc2-cc6-7","source_ref":"control--ogrl-vm-06","target_ref":"requirement--soc2-tsc-2017-cc6-7","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Encrypted, remotely wipeable devices protect information held on endpoints, overlapping CC6.7.\n"}],"yaml_path":"library/control/ogrl-vm-06.yaml"}],"requirements":[{"id":"requirement--iso-iec-27001-2022-a-5-15","slug":"a-5-15","display_id":"A.5.15","name":"Access Control Governance","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.5.15","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-03-to-iso27001-a-5-15","source_ref":"control--ogrl-ac-03","target_ref":"requirement--iso-iec-27001-2022-a-5-15","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege RBAC policies directly satisfy ISO/IEC 27001:2022 A.5.15."}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-5-15.yaml"},{"id":"requirement--iso-iec-27001-2022-a-5-16","slug":"a-5-16","display_id":"A.5.16","name":"Identity Lifecycle Management","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.5.16","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-01-to-iso27001-a-5-16","source_ref":"control--ogrl-ac-01","target_ref":"requirement--iso-iec-27001-2022-a-5-16","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Approved identity provisioning and timely offboarding satisfy ISO/IEC 27001:2022 A.5.16.\n"}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-5-16.yaml"},{"id":"requirement--iso-iec-27001-2022-a-5-17","slug":"a-5-17","display_id":"A.5.17","name":"Authentication Secret Management","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.5.17","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-06-to-iso27001-a-5-17","source_ref":"control--ogrl-ac-06","target_ref":"requirement--iso-iec-27001-2022-a-5-17","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Vaulted secret storage and rotation governance satisfy ISO/IEC 27001:2022 A.5.17.\n"}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-5-17.yaml"},{"id":"requirement--iso-iec-27001-2022-a-5-18","slug":"a-5-18","display_id":"A.5.18","name":"Access Rights Provisioning and Review","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.5.18","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-02-to-iso27001-a-5-18","source_ref":"control--ogrl-ac-02","target_ref":"requirement--iso-iec-27001-2022-a-5-18","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Periodic user access reviews and revocation satisfy ISO/IEC 27001:2022 A.5.18."}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-5-18.yaml"},{"id":"requirement--iso-iec-27001-2022-a-8-5","slug":"a-8-5","display_id":"A.8.5","name":"Strong Authentication Enforcement","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.8.5","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-05-to-iso27001-a-8-5","source_ref":"control--ogrl-ac-05","target_ref":"requirement--iso-iec-27001-2022-a-8-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Phishing-resistant MFA enforcement satisfies ISO/IEC 27001:2022 A.8.5 secure authentication.\n"}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-8-5.yaml"},{"id":"requirement--iso-iec-27001-2022-a-8-15","slug":"a-8-15","display_id":"A.8.15","name":"Security Event Logging","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.8.15","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-01-to-iso27001-a-8-15","source_ref":"control--ogrl-lm-01","target_ref":"requirement--iso-iec-27001-2022-a-8-15","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Centralized security logging and retention satisfy ISO/IEC 27001:2022 A.8.15."}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-8-15.yaml"},{"id":"requirement--iso-iec-27001-2022-a-8-24","slug":"a-8-24","display_id":"A.8.24","name":"Cryptographic Protection","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.8.24","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-01-to-iso27001-a-8-24","source_ref":"control--ogrl-cr-01","target_ref":"requirement--iso-iec-27001-2022-a-8-24","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Modern TLS and managed AES-256 storage encryption satisfy ISO/IEC 27001:2022 A.8.24.\n"}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-8-24.yaml"},{"id":"requirement--iso-iec-27001-2022-a-8-32","slug":"a-8-32","display_id":"A.8.32","name":"Production Change Management","framework_id":"framework--iso-iec-27001-2022","framework_slug":"iso-iec-27001-2022","class":"clause","withdrawn":false,"statement":null,"citation":"ISO/IEC 27001:2022 Annex A.8.32","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-01-to-iso27001-a-8-32","source_ref":"control--ogrl-cm-01","target_ref":"requirement--iso-iec-27001-2022-a-8-32","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Peer-reviewed production change control satisfies ISO/IEC 27001:2022 A.8.32."}],"yaml_path":"library/requirement/iso-iec-27001-2022/a-8-32.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-01","slug":"03-01-01","display_id":"03.01.01","name":"Account Management","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Define the types of system accounts allowed and prohibited."},{"id":"b","statement":"Create, enable, modify, disable, and remove system accounts in accordance with policy, procedures, prerequisites, and criteria.\n"},{"id":"c","statement":"Specify:"},{"id":"c.01","statement":"Authorized users of the system,"},{"id":"c.02","statement":"Group and role membership, and"},{"id":"c.03","statement":"Access authorizations (i.e., privileges) for each account."},{"id":"d","statement":"Authorize access to the system based on:"},{"id":"d.01","statement":"A valid access authorization and"},{"id":"d.02","statement":"Intended system usage."},{"id":"e","statement":"Monitor the use of system accounts."},{"id":"f","statement":"Disable system accounts when:"},{"id":"f.01","statement":"The accounts have expired,"},{"id":"f.02","statement":"The accounts have been inactive for {{ a_03_01_01_odp_01 }},"},{"id":"f.03","statement":"The accounts are no longer associated with a user or individual,"},{"id":"f.04","statement":"The accounts are in violation of organizational policy, or"},{"id":"f.05","statement":"Significant risks associated with individuals are discovered."},{"id":"g","statement":"Notify account managers and designated personnel or roles within:"},{"id":"g.01","statement":"{{ a_03_01_01_odp_02 }} when accounts are no longer required."},{"id":"g.02","statement":"{{ a_03_01_01_odp_03 }} when users are terminated or transferred."},{"id":"g.03","statement":"{{ a_03_01_01_odp_04 }} when system usage or the need-to-know changes for an individual.\n"},{"id":"h","statement":"Require that users log out of the system after {{ a_03_01_01_odp_05 }} of expected inactivity or when {{ a_03_01_01_odp_06 }}.\n"}],"objectives_count":22,"objectives_preview":[{"id":"b.01","statement":"system accounts are created in accordance with organizational policy, procedures, prerequisites, and criteria.\n"},{"id":"b.02","statement":"system accounts are enabled in accordance with organizational policy, procedures, prerequisites, and criteria.\n"},{"id":"b.03","statement":"system accounts are modified in accordance with organizational policy, procedures, prerequisites, and criteria.\n"},{"id":"b.04","statement":"system accounts are disabled in accordance with organizational policy, procedures, prerequisites, and criteria.\n"},{"id":"b.05","statement":"system accounts are removed in accordance with organizational policy, procedures, prerequisites, and criteria.\n"},{"id":"a.01","statement":"system account types allowed are defined."}],"params_count":6,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-01_to_nist-sp-800-53-r5-ac-2","source_ref":"requirement--nist-sp-800-171-r3-03-01-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-01_to_nist-sp-800-53-r5-ac-2-13","source_ref":"requirement--nist-sp-800-171-r3-03-01-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2-13","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-01_to_nist-sp-800-53-r5-ac-2-3","source_ref":"requirement--nist-sp-800-171-r3-03-01-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-01_to_nist-sp-800-53-r5-ac-2-5","source_ref":"requirement--nist-sp-800-171-r3-03-01-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-ac-01-to-800-171-03-01-01","source_ref":"control--ogrl-ac-01","target_ref":"requirement--nist-sp-800-171-r3-03-01-01","relationship":"subset-of","review_status":"reviewed","parameter_map":{"a_03_01_01_odp_01":"approver_role","a_03_01_01_odp_04":"deprovision_sla"},"summary":"Account provisioning approval and termination revocation contribute to SP 800-171 03.01.01 account management.\n"},{"id":"mapping--ogrl-ac-02-to-800-171-03-01-01","source_ref":"control--ogrl-ac-02","target_ref":"requirement--nist-sp-800-171-r3-03-01-01","relationship":"subset-of","review_status":"reviewed","parameter_map":{"a_03_01_01_odp_06":"review_cadence"},"summary":"Periodic user access reviews contribute to SP 800-171 03.01.01 account compliance reviews.\n"}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-02","slug":"03-01-02","display_id":"03.01.02","name":"Access Enforcement","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Enforce approved authorizations for logical access to CUI and system resources in accordance with applicable access control policies.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"approved authorizations for logical access to CUI are enforced in accordance with applicable access control policies.\n"},{"id":"02","statement":"approved authorizations for logical access to system resources are enforced in accordance with applicable access control policies.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-02_to_nist-sp-800-53-r5-ac-3","source_ref":"requirement--nist-sp-800-171-r3-03-01-02","target_ref":"requirement--nist-sp-800-53-r5-ac-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-03","slug":"03-01-03","display_id":"03.01.03","name":"Information Flow Enforcement","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Enforce approved authorizations for controlling the flow of CUI within the system and between connected systems.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"approved authorizations are enforced for controlling the flow of CUI within the system.\n"},{"id":"02","statement":"approved authorizations are enforced for controlling the flow of CUI between connected systems.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-03_to_nist-sp-800-53-r5-ac-4","source_ref":"requirement--nist-sp-800-171-r3-03-01-03","target_ref":"requirement--nist-sp-800-53-r5-ac-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-04","slug":"03-01-04","display_id":"03.01.04","name":"Separation of Duties","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify the duties of individuals requiring separation."},{"id":"b","statement":"Define system access authorizations to support separation of duties."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"duties of individuals requiring separation are identified."},{"id":"b","statement":"system access authorizations to support separation of duties are defined."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-04_to_nist-sp-800-53-r5-ac-5","source_ref":"requirement--nist-sp-800-171-r3-03-01-04","target_ref":"requirement--nist-sp-800-53-r5-ac-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-05","slug":"03-01-05","display_id":"03.01.05","name":"Least Privilege","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Allow only authorized system access for users (or processes acting on behalf of users) that is necessary to accomplish assigned organizational tasks.\n"},{"id":"b","statement":"Authorize access to {{ a_03_01_05_odp_01 }} and {{ a_03_01_05_odp_02 }}."},{"id":"c","statement":"Review the privileges assigned to roles or classes of users {{ a_03_01_05_odp_03 }} to validate the need for such privileges.\n"},{"id":"d","statement":"Reassign or remove privileges, as necessary."}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"system access for users (or processes acting on behalf of users) is authorized only when necessary to accomplish assigned organizational tasks.\n"},{"id":"b.01","statement":"access to {{ a_03_01_05_odp_01 }} is authorized."},{"id":"b.02","statement":"access to {{ a_03_01_05_odp_02 }} is authorized."},{"id":"c","statement":"the privileges assigned to roles or classes of users are reviewed {{ a_03_01_05_odp_03 }} to validate the need for such privileges.\n"},{"id":"d","statement":"privileges are reassigned or removed, as necessary."}],"params_count":3,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-05_to_nist-sp-800-53-r5-ac-6","source_ref":"requirement--nist-sp-800-171-r3-03-01-05","target_ref":"requirement--nist-sp-800-53-r5-ac-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-05_to_nist-sp-800-53-r5-ac-6-1","source_ref":"requirement--nist-sp-800-171-r3-03-01-05","target_ref":"requirement--nist-sp-800-53-r5-ac-6-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-05_to_nist-sp-800-53-r5-ac-6-7","source_ref":"requirement--nist-sp-800-171-r3-03-01-05","target_ref":"requirement--nist-sp-800-53-r5-ac-6-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-05_to_nist-sp-800-53-r5-au-9-4","source_ref":"requirement--nist-sp-800-171-r3-03-01-05","target_ref":"requirement--nist-sp-800-53-r5-au-9-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-ac-03-to-800-171-03-01-05","source_ref":"control--ogrl-ac-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-05","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege role enforcement directly satisfies SP 800-171 03.01.05."}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-06","slug":"03-01-06","display_id":"03.01.06","name":"Least Privilege – Privileged Accounts","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Restrict privileged accounts on the system to {{ a_03_01_06_odp_01 }}.."},{"id":"b","statement":"Require that users (or roles) with privileged accounts use non-privileged accounts when accessing non-security functions or non-security information.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"privileged accounts on the system are restricted to {{ a_03_01_06_odp_01 }}."},{"id":"b","statement":"users (or roles) with privileged accounts are required to use non-privileged accounts when accessing non-security functions or non-security information.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-06_to_nist-sp-800-53-r5-ac-6-2","source_ref":"requirement--nist-sp-800-171-r3-03-01-06","target_ref":"requirement--nist-sp-800-53-r5-ac-6-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-06_to_nist-sp-800-53-r5-ac-6-5","source_ref":"requirement--nist-sp-800-171-r3-03-01-06","target_ref":"requirement--nist-sp-800-53-r5-ac-6-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-07","slug":"03-01-07","display_id":"03.01.07","name":"Least Privilege – Privileged Functions","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prevent non-privileged users from executing privileged functions."},{"id":"b","statement":"Log the execution of privileged functions."}],"objectives_count":2,"objectives_preview":[{"id":"b","statement":"the execution of privileged functions is logged."},{"id":"a","statement":"non-privileged users are prevented from executing privileged functions."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-07_to_nist-sp-800-53-r5-ac-6-10","source_ref":"requirement--nist-sp-800-171-r3-03-01-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-10","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-07_to_nist-sp-800-53-r5-ac-6-9","source_ref":"requirement--nist-sp-800-171-r3-03-01-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-9","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-08","slug":"03-01-08","display_id":"03.01.08","name":"Unsuccessful Logon Attempts","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce a limit of {{ a_03_01_08_odp_01 }} consecutive invalid logon attempts by a user during a {{ a_03_01_08_odp_02 }}.\n"},{"id":"b","statement":"Automatically {{ a_03_01_08_odp_03 }} when the maximum number of unsuccessful attempts is exceeded.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a limit of {{ a_03_01_08_odp_01 }} consecutive invalid logon attempts by a user during {{ a_03_01_08_odp_02 }} is enforced.\n"},{"id":"b","statement":"{{ a_03_01_08_odp_03 }} when the maximum number of unsuccessful attempts is exceeded.\n"}],"params_count":4,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-08_to_nist-sp-800-53-r5-ac-7","source_ref":"requirement--nist-sp-800-171-r3-03-01-08","target_ref":"requirement--nist-sp-800-53-r5-ac-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-09","slug":"03-01-09","display_id":"03.01.09","name":"System Use Notification","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Display a system use notification message with privacy and security notices consistent with applicable CUI rules before granting access to the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"a system use notification message with privacy and security notices consistent with applicable CUI rules is displayed before granting access to the system.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-09_to_nist-sp-800-53-r5-ac-8","source_ref":"requirement--nist-sp-800-171-r3-03-01-09","target_ref":"requirement--nist-sp-800-53-r5-ac-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-09.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-10","slug":"03-01-10","display_id":"03.01.10","name":"Device Lock","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prevent access to the system by {{ a_03_01_10_odp_01 }}."},{"id":"b","statement":"Retain the device lock until the user reestablishes access using established identification and authentication procedures.\n"},{"id":"c","statement":"Conceal, via the device lock, information previously visible on the display with a publicly viewable image.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"access to the system is prevented by {{ a_03_01_10_odp_01 }}."},{"id":"c","statement":"information previously visible on the display is concealed via device lock with a publicly viewable image.\n"},{"id":"b","statement":"the device lock is retained until the user reestablishes access using established identification and authentication procedures.\n"}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-10_to_nist-sp-800-53-r5-ac-11","source_ref":"requirement--nist-sp-800-171-r3-03-01-10","target_ref":"requirement--nist-sp-800-53-r5-ac-11","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-10_to_nist-sp-800-53-r5-ac-11-1","source_ref":"requirement--nist-sp-800-171-r3-03-01-10","target_ref":"requirement--nist-sp-800-53-r5-ac-11-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-10.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-11","slug":"03-01-11","display_id":"03.01.11","name":"Session Termination","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Terminate a user session automatically after {{ a_03_01_11_odp_01 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"a user session is terminated automatically after {{ a_03_01_11_odp_01 }}."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-11_to_nist-sp-800-53-r5-ac-12","source_ref":"requirement--nist-sp-800-171-r3-03-01-11","target_ref":"requirement--nist-sp-800-53-r5-ac-12","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-11.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-12","slug":"03-01-12","display_id":"03.01.12","name":"Remote Access","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish usage restrictions, configuration requirements, and connection requirements for each type of allowable remote system access.\n"},{"id":"b","statement":"Authorize each type of remote system access prior to establishing such connections.\n"},{"id":"c","statement":"Route remote access to the system through authorized and managed access control points.\n"},{"id":"d","statement":"Authorize the remote execution of privileged commands and remote access to security-relevant information.\n"}],"objectives_count":9,"objectives_preview":[{"id":"a.01","statement":"types of allowable remote system access are defined."},{"id":"a.02","statement":"usage restrictions are established for each type of allowable remote system access.\n"},{"id":"a.03","statement":"configuration requirements are established for each type of allowable remote system access.\n"},{"id":"a.04","statement":"connection requirements are established for each type of allowable remote system access.\n"},{"id":"b","statement":"each type of remote system access is authorized prior to establishing such connections.\n"},{"id":"c.01","statement":"remote access to the system is routed through authorized access control points."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-12_to_nist-sp-800-53-r5-ac-17","source_ref":"requirement--nist-sp-800-171-r3-03-01-12","target_ref":"requirement--nist-sp-800-53-r5-ac-17","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-12_to_nist-sp-800-53-r5-ac-17-3","source_ref":"requirement--nist-sp-800-171-r3-03-01-12","target_ref":"requirement--nist-sp-800-53-r5-ac-17-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-12_to_nist-sp-800-53-r5-ac-17-4","source_ref":"requirement--nist-sp-800-171-r3-03-01-12","target_ref":"requirement--nist-sp-800-53-r5-ac-17-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-12.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-13","slug":"03-01-13","display_id":"03.01.13","name":"03.01.13","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-13_to_nist-sp-800-171-r3-03-13-08","source_ref":"requirement--nist-sp-800-171-r3-03-01-13","target_ref":"requirement--nist-sp-800-171-r3-03-13-08","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-13.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-14","slug":"03-01-14","display_id":"03.01.14","name":"03.01.14","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-14_to_nist-sp-800-171-r3-03-01-12","source_ref":"requirement--nist-sp-800-171-r3-03-01-14","target_ref":"requirement--nist-sp-800-171-r3-03-01-12","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-14.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-15","slug":"03-01-15","display_id":"03.01.15","name":"03.01.15","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-15_to_nist-sp-800-171-r3-03-01-12","source_ref":"requirement--nist-sp-800-171-r3-03-01-15","target_ref":"requirement--nist-sp-800-171-r3-03-01-12","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-15.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-16","slug":"03-01-16","display_id":"03.01.16","name":"Wireless Access","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish usage restrictions, configuration requirements, and connection requirements for each type of wireless access to the system.\n"},{"id":"b","statement":"Authorize each type of wireless access to the system prior to establishing such connections.\n"},{"id":"c","statement":"Disable, when not intended for use, wireless networking capabilities prior to issuance and deployment.\n"},{"id":"d","statement":"Protect wireless access to the system using authentication and encryption."}],"objectives_count":8,"objectives_preview":[{"id":"a.01","statement":"each type of wireless access to the system is defined."},{"id":"a.02","statement":"usage restrictions are established for each type of wireless access to the system.\n"},{"id":"a.03","statement":"configuration requirements are established for each type of wireless access to the system.\n"},{"id":"a.04","statement":"connection requirements are established for each type of wireless access to the system.\n"},{"id":"b","statement":"each type of wireless access to the system is authorized prior to establishing such connections.\n"},{"id":"c","statement":"wireless networking capabilities not intended for use are disabled prior to issuance and deployment.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-16_to_nist-sp-800-53-r5-ac-18","source_ref":"requirement--nist-sp-800-171-r3-03-01-16","target_ref":"requirement--nist-sp-800-53-r5-ac-18","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-16_to_nist-sp-800-53-r5-ac-18-1","source_ref":"requirement--nist-sp-800-171-r3-03-01-16","target_ref":"requirement--nist-sp-800-53-r5-ac-18-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-16_to_nist-sp-800-53-r5-ac-18-3","source_ref":"requirement--nist-sp-800-171-r3-03-01-16","target_ref":"requirement--nist-sp-800-53-r5-ac-18-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-16.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-17","slug":"03-01-17","display_id":"03.01.17","name":"03.01.17","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-17_to_nist-sp-800-171-r3-03-01-16","source_ref":"requirement--nist-sp-800-171-r3-03-01-17","target_ref":"requirement--nist-sp-800-171-r3-03-01-16","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-17.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-18","slug":"03-01-18","display_id":"03.01.18","name":"Access Control for Mobile Devices","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish usage restrictions, configuration requirements, and connection requirements for mobile devices.\n"},{"id":"b","statement":"Authorize the connection of mobile devices to the system."},{"id":"c","statement":"Implement full-device or container-based encryption to protect the confidentiality of CUI on mobile devices.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.01","statement":"usage restrictions are established for mobile devices."},{"id":"a.02","statement":"configuration requirements are established for mobile devices."},{"id":"a.03","statement":"connection requirements are established for mobile devices."},{"id":"b","statement":"the connection of mobile devices to the system is authorized."},{"id":"c","statement":"full-device or container-based encryption is implemented to protect the confidentiality of CUI on mobile devices.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-18_to_nist-sp-800-53-r5-ac-19","source_ref":"requirement--nist-sp-800-171-r3-03-01-18","target_ref":"requirement--nist-sp-800-53-r5-ac-19","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-18_to_nist-sp-800-53-r5-ac-19-5","source_ref":"requirement--nist-sp-800-171-r3-03-01-18","target_ref":"requirement--nist-sp-800-53-r5-ac-19-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-18.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-19","slug":"03-01-19","display_id":"03.01.19","name":"03.01.19","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-19_to_nist-sp-800-171-r3-03-01-18","source_ref":"requirement--nist-sp-800-171-r3-03-01-19","target_ref":"requirement--nist-sp-800-171-r3-03-01-18","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-19.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-20","slug":"03-01-20","display_id":"03.01.20","name":"Use of External Systems","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prohibit the use of external systems unless the systems are specifically authorized.\n"},{"id":"b","statement":"Establish the following security requirements to be satisfied on external systems prior to allowing use of or access to those systems by authorized individuals: {{ a_03_01_20_odp_01 }}.\n"},{"id":"c","statement":"Permit authorized individuals to use external systems to access the organizational system or to process, store, or transmit CUI only after:\n"},{"id":"c.01","statement":"Verifying that the security requirements on the external systems as specified in the organization’s system security plans have been satisfied and\n"},{"id":"c.02","statement":"Retaining approved system connection or processing agreements with the organizational entities hosting the external systems.\n"},{"id":"d","statement":"Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems.\n"}],"objectives_count":5,"objectives_preview":[{"id":"b","statement":"the following security requirements to be satisfied on external systems prior to allowing the use of or access to those systems by authorized individuals are established: {{ a_03_01_20_odp_01 }}.\n"},{"id":"a","statement":"the use of external systems is prohibited unless the systems are specifically authorized.\n"},{"id":"c.01","statement":"authorized individuals are permitted to use external systems to access the organizational system or to process, store, or transmit CUI only after verifying that the security requirements on the external systems as specified in the organization’s system security plans have been satisfied.\n"},{"id":"d","statement":"the use of organization-controlled portable storage devices by authorized individuals on external systems is restricted.\n"},{"id":"c.02","statement":"authorized individuals are permitted to use external systems to access the organizational system or to process, store, or transmit CUI only after retaining approved system connection or processing agreements with the organizational entity hosting the external systems.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-20_to_nist-sp-800-53-r5-ac-20","source_ref":"requirement--nist-sp-800-171-r3-03-01-20","target_ref":"requirement--nist-sp-800-53-r5-ac-20","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-20_to_nist-sp-800-53-r5-ac-20-1","source_ref":"requirement--nist-sp-800-171-r3-03-01-20","target_ref":"requirement--nist-sp-800-53-r5-ac-20-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-01-20_to_nist-sp-800-53-r5-ac-20-2","source_ref":"requirement--nist-sp-800-171-r3-03-01-20","target_ref":"requirement--nist-sp-800-53-r5-ac-20-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-20.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-21","slug":"03-01-21","display_id":"03.01.21","name":"03.01.21","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-21_to_nist-sp-800-171-r3-03-01-20","source_ref":"requirement--nist-sp-800-171-r3-03-01-21","target_ref":"requirement--nist-sp-800-171-r3-03-01-20","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-21.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-01-22","slug":"03-01-22","display_id":"03.01.22","name":"Publicly Accessible Content","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Train authorized individuals to ensure that publicly accessible information does not contain CUI.\n"},{"id":"b","statement":"Review the content on publicly accessible systems for CUI and remove such information, if discovered.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"authorized individuals are trained to ensure that publicly accessible information does not contain CUI.\n"},{"id":"b.01","statement":"the content on publicly accessible systems is reviewed for CUI."},{"id":"b.02","statement":"CUI is removed from publicly accessible systems, if discovered."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-01-22_to_nist-sp-800-53-r5-ac-22","source_ref":"requirement--nist-sp-800-171-r3-03-01-22","target_ref":"requirement--nist-sp-800-53-r5-ac-22","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-01-22.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-02-01","slug":"03-02-01","display_id":"03.02.01","name":"Literacy Training and Awareness","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide security literacy training to system users:"},{"id":"a.01","statement":"As part of initial training for new users and {{ a_03_02_01_odp_01 }} thereafter,\n"},{"id":"a.02","statement":"When required by system changes or following {{ a_03_02_01_odp_02 }}, and"},{"id":"a.03","statement":"On recognizing and reporting indicators of insider threat, social engineering, and social mining.\n"},{"id":"b","statement":"Update security literacy training content {{ a_03_02_01_odp_03 }} and following {{ a_03_02_01_odp_04 }}.\n"}],"objectives_count":11,"objectives_preview":[{"id":"a.01.01","statement":"security literacy training is provided to system users as part of initial training for new users.\n"},{"id":"a.01.02","statement":"security literacy training is provided to system users {{ a_03_02_01_odp_01 }} after initial training.\n"},{"id":"a.02","statement":"security literacy training is provided to system users when required by system changes or following {{ a_03_02_01_odp_02 }}.\n"},{"id":"a.03.01","statement":"security literacy training is provided to system users on recognizing indicators of insider threat.\n"},{"id":"a.03.02","statement":"security literacy training is provided to system users on reporting indicators of insider threat.\n"},{"id":"a.03.03","statement":"security literacy training is provided to system users on recognizing indicators of social engineering.\n"}],"params_count":4,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-02-01_to_nist-sp-800-53-r5-at-2","source_ref":"requirement--nist-sp-800-171-r3-03-02-01","target_ref":"requirement--nist-sp-800-53-r5-at-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-02-01_to_nist-sp-800-53-r5-at-2-2","source_ref":"requirement--nist-sp-800-171-r3-03-02-01","target_ref":"requirement--nist-sp-800-53-r5-at-2-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-02-01_to_nist-sp-800-53-r5-at-2-3","source_ref":"requirement--nist-sp-800-171-r3-03-02-01","target_ref":"requirement--nist-sp-800-53-r5-at-2-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-02-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-02-02","slug":"03-02-02","display_id":"03.02.02","name":"Role-Based Training","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide role-based security training to organizational personnel:"},{"id":"a.01","statement":"Before authorizing access to the system or CUI, before performing assigned duties, and {{ a_03_02_02_odp_01 }} thereafter\n"},{"id":"a.02","statement":"When required by system changes or following {{ a_03_02_02_odp_02 }}."},{"id":"b","statement":"Update role-based training content {{ a_03_02_02_odp_03 }} and following {{ a_03_02_02_odp_04 }}.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01.01","statement":"role-based security training is provided to organizational personnel before authorizing access to the system or CUI.\n"},{"id":"a.01.02","statement":"role-based security training is provided to organizational personnel before performing assigned duties.\n"},{"id":"a.01.03","statement":"role-based security training is provided to organizational personnel {{ a_03_02_02_odp_01 }} after initial training.\n"},{"id":"a.02","statement":"role-based security training is provided to organizational personnel when required by system changes or following {{ a_03_02_02_odp_02 }}.\n"},{"id":"b.01","statement":"role-based security training content is updated {{ a_03_02_02_odp_03 }}."},{"id":"b.02","statement":"role-based security training content is updated following {{ a_03_02_02_odp_04 }}.\n"}],"params_count":4,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-02-02_to_nist-sp-800-53-r5-at-3","source_ref":"requirement--nist-sp-800-171-r3-03-02-02","target_ref":"requirement--nist-sp-800-53-r5-at-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-02-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-02-03","slug":"03-02-03","display_id":"03.02.03","name":"03.02.03","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-02-03_to_nist-sp-800-171-r3-03-02-01","source_ref":"requirement--nist-sp-800-171-r3-03-02-03","target_ref":"requirement--nist-sp-800-171-r3-03-02-01","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-02-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-01","slug":"03-03-01","display_id":"03.03.01","name":"Event Logging","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Specify the following event types selected for logging within the system: {{ a_03_03_01_odp_01 }}.\n"},{"id":"b","statement":"Review and update the event types selected for logging {{ a_03_03_01_odp_02 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the following event types are specified for logging within the system: {{ a_03_03_01_odp_01 }}.\n"},{"id":"b.01","statement":"the event types selected for logging are reviewed {{ a_03_03_01_odp_02 }}."},{"id":"b.02","statement":"the event types selected for logging are updated {{ a_03_03_01_odp_02 }}."}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-01_to_nist-sp-800-53-r5-au-2","source_ref":"requirement--nist-sp-800-171-r3-03-03-01","target_ref":"requirement--nist-sp-800-53-r5-au-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-lm-01-to-800-171-03-03-01","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-171-r3-03-03-01","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"a_03_03_01_odp_01":"logged_events","a_03_03_01_odp_02":"logging_review_cadence"},"summary":"Centralized security event logging and review directly satisfy SP 800-171 03.03.01.\n"}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-02","slug":"03-03-02","display_id":"03.03.02","name":"Audit Record Content","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Include the following content in audit records:"},{"id":"a.01","statement":"What type of event occurred"},{"id":"a.02","statement":"When the event occurred"},{"id":"a.03","statement":"Where the event occurred"},{"id":"a.04","statement":"Source of the event"},{"id":"a.05","statement":"Outcome of the event"},{"id":"a.06","statement":"Identity of the individuals, subjects, objects, or entities associated with the event\n"},{"id":"b","statement":"Provide additional information for audit records as needed."}],"objectives_count":7,"objectives_preview":[{"id":"a.01","statement":"audit records contain information that establishes what type of event occurred."},{"id":"a.02","statement":"audit records contain information that establishes when the event occurred."},{"id":"a.03","statement":"audit records contain information that establishes where the event occurred."},{"id":"a.04","statement":"audit records contain information that establishes the source of the event."},{"id":"a.05","statement":"audit records contain information that establishes the outcome of the event."},{"id":"a.06","statement":"audit records contain information that establishes the identity of the individuals, subjects, objects, or entities associated with the event.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-02_to_nist-sp-800-53-r5-au-3","source_ref":"requirement--nist-sp-800-171-r3-03-03-02","target_ref":"requirement--nist-sp-800-53-r5-au-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-03-02_to_nist-sp-800-53-r5-au-3-1","source_ref":"requirement--nist-sp-800-171-r3-03-03-02","target_ref":"requirement--nist-sp-800-53-r5-au-3-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-03","slug":"03-03-03","display_id":"03.03.03","name":"Audit Record Generation","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Generate audit records for the selected event types and audit record content specified in 03.03.01 and 03.03.02.\n"},{"id":"b","statement":"Retain audit records for a time period consistent with the records retention policy.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"audit records for the selected event types and audit record content specified in 03.03.01 and 03.03.02 are generated.\n"},{"id":"b","statement":"audit records are retained for a time period consistent with the records retention policy.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-03_to_nist-sp-800-53-r5-au-11","source_ref":"requirement--nist-sp-800-171-r3-03-03-03","target_ref":"requirement--nist-sp-800-53-r5-au-11","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-03-03_to_nist-sp-800-53-r5-au-12","source_ref":"requirement--nist-sp-800-171-r3-03-03-03","target_ref":"requirement--nist-sp-800-53-r5-au-12","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-04","slug":"03-03-04","display_id":"03.03.04","name":"Response to Audit Logging Process Failures","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Alert organizational personnel or roles within {{ a_03_03_04_odp_01 }} in the event of an audit logging process failure.\n"},{"id":"b","statement":"Take the following additional actions: {{ a_03_03_04_odp_02 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"organizational personnel or roles are alerted in the event of an audit logging process failure within {{ a_03_03_04_odp_01 }}.\n"},{"id":"b","statement":"the following additional actions are taken: {{ a_03_03_04_odp_02 }}."}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-04_to_nist-sp-800-53-r5-au-5","source_ref":"requirement--nist-sp-800-171-r3-03-03-04","target_ref":"requirement--nist-sp-800-53-r5-au-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-05","slug":"03-03-05","display_id":"03.03.05","name":"Audit Record Review, Analysis, and Reporting","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Review and analyze system audit records {{ a_03_03_05_odp_01 }} for indications and the potential impact of inappropriate or unusual activity.\n"},{"id":"b","statement":"Report findings to organizational personnel or roles."},{"id":"c","statement":"Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"system audit records are reviewed and analyzed {{ a_03_03_05_odp_01 }} for indications and the potential impact of inappropriate or unusual activity.\n"},{"id":"b","statement":"findings are reported to organizational personnel or roles."},{"id":"c.01","statement":"audit records across different repositories are analyzed to gain organization-wide situational awareness.\n"},{"id":"c.02","statement":"audit records across different repositories are correlated to gain organization-wide situational awareness.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-05_to_nist-sp-800-53-r5-au-6","source_ref":"requirement--nist-sp-800-171-r3-03-03-05","target_ref":"requirement--nist-sp-800-53-r5-au-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-03-05_to_nist-sp-800-53-r5-au-6-3","source_ref":"requirement--nist-sp-800-171-r3-03-03-05","target_ref":"requirement--nist-sp-800-53-r5-au-6-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-06","slug":"03-03-06","display_id":"03.03.06","name":"Audit Record Reduction and Report Generation","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement an audit record reduction and report generation capability that supports audit record review, analysis, reporting requirements, and after-the-fact investigations of incidents.\n"},{"id":"b","statement":"Preserve the original content and time ordering of audit records."}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"an audit record reduction and report generation capability that supports audit record review is implemented.\n"},{"id":"a.02","statement":"an audit record reduction and report generation capability that supports audit record analysis is implemented.\n"},{"id":"a.03","statement":"an audit record reduction and report generation capability that supports audit record reporting requirements is implemented.\n"},{"id":"a.04","statement":"an audit record reduction and report generation capability that supports after-the-fact investigations of incidents is implemented.\n"},{"id":"b.01","statement":"the original content of audit records is preserved."},{"id":"b.02","statement":"the original time ordering of audit records is preserved."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-06_to_nist-sp-800-53-r5-au-7","source_ref":"requirement--nist-sp-800-171-r3-03-03-06","target_ref":"requirement--nist-sp-800-53-r5-au-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-07","slug":"03-03-07","display_id":"03.03.07","name":"Time Stamps","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Use internal system clocks to generate time stamps for audit records."},{"id":"b","statement":"Record time stamps for audit records that meet {{ a_03_03_07_odp_01 }} and that use Coordinated Universal Time (UTC), have a fixed local time offset from UTC, or include the local time offset as part of the time stamp.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"internal system clocks are used to generate time stamps for audit records."},{"id":"b.02","statement":"time stamps are recorded for audit records that use Coordinated Universal Time (UTC), have a fixed local time offset from UTC, or include the local time offset as part of the time stamp.\n"},{"id":"b.01","statement":"time stamps are recorded for audit records that meet {{ a_03_03_07_odp_01 }}."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-07_to_nist-sp-800-53-r5-au-8","source_ref":"requirement--nist-sp-800-171-r3-03-03-07","target_ref":"requirement--nist-sp-800-53-r5-au-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-08","slug":"03-03-08","display_id":"03.03.08","name":"Protection of Audit Information","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Protect audit information and audit logging tools from unauthorized access, modification, and deletion.\n"},{"id":"b","statement":"Authorize access to management of audit logging functionality to only a subset of privileged users or roles.\n"}],"objectives_count":3,"objectives_preview":[{"id":"b","statement":"access to management of audit logging functionality is authorized to only a subset of privileged users or roles.\n"},{"id":"a.01","statement":"audit information is protected from unauthorized access, modification, and deletion.\n"},{"id":"a.02","statement":"audit logging tools are protected from unauthorized access, modification, and deletion.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-08_to_nist-sp-800-53-r5-au-9","source_ref":"requirement--nist-sp-800-171-r3-03-03-08","target_ref":"requirement--nist-sp-800-53-r5-au-9","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-03-08_to_nist-sp-800-53-r5-au-9-4","source_ref":"requirement--nist-sp-800-171-r3-03-03-08","target_ref":"requirement--nist-sp-800-53-r5-au-9-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-03-09","slug":"03-03-09","display_id":"03.03.09","name":"03.03.09","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-03-09_to_nist-sp-800-171-r3-03-03-08","source_ref":"requirement--nist-sp-800-171-r3-03-03-09","target_ref":"requirement--nist-sp-800-171-r3-03-03-08","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-03-09.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-01","slug":"03-04-01","display_id":"03.04.01","name":"Baseline Configuration","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and maintain under configuration control, a current baseline configuration of the system.\n"},{"id":"b","statement":"Review and update the baseline configuration of the system {{ a_03_04_01_odp_01 }} and when system components are installed or modified.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"a current baseline configuration of the system is developed."},{"id":"a.02","statement":"a current baseline configuration of the system is maintained under configuration control.\n"},{"id":"b.02","statement":"the baseline configuration of the system is updated {{ a_03_04_01_odp_01 }}."},{"id":"b.03","statement":"the baseline configuration of the system is reviewed when system components are installed or modified.\n"},{"id":"b.04","statement":"the baseline configuration of the system is updated when system components are installed or modified.\n"},{"id":"b.01","statement":"the baseline configuration of the system is reviewed {{ a_03_04_01_odp_01 }}."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-01_to_nist-sp-800-53-r5-cm-2","source_ref":"requirement--nist-sp-800-171-r3-03-04-01","target_ref":"requirement--nist-sp-800-53-r5-cm-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-02","slug":"03-04-02","display_id":"03.04.02","name":"Configuration Settings","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish, document, and implement the following configuration settings for the system that reflect the most restrictive mode consistent with operational requirements: {{ a_03_04_02_odp_01 }} .\n"},{"id":"b","statement":"Identify, document, and approve any deviations from established configuration settings.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a.01","statement":"the following configuration settings for the system that reflect the most restrictive mode consistent with operational requirements are established and documented: {{ a_03_04_02_odp_01 }}.\n"},{"id":"b.01","statement":"any deviations from established configuration settings are identified and documented.\n"},{"id":"b.02","statement":"any deviations from established configuration settings are approved."},{"id":"a.02","statement":"the following configuration settings for the system are implemented: {{ a_03_04_02_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-02_to_nist-sp-800-53-r5-cm-6","source_ref":"requirement--nist-sp-800-171-r3-03-04-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-03","slug":"03-04-03","display_id":"03.04.03","name":"Configuration Change Control","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Define the types of changes to the system that are configuration-controlled."},{"id":"b","statement":"Review proposed configuration-controlled changes to the system, and approve or disapprove such changes with explicit consideration for security impacts.\n"},{"id":"c","statement":"Implement and document approved configuration-controlled changes to the system."},{"id":"d","statement":"Monitor and review activities associated with configuration-controlled changes to the system.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a","statement":"the types of changes to the system that are configuration-controlled are defined.\n"},{"id":"b.01","statement":"proposed configuration-controlled changes to the system are reviewed with explicit consideration for security impacts.\n"},{"id":"b.02","statement":"proposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security impacts.\n"},{"id":"d.01","statement":"activities associated with configuration-controlled changes to the system are monitored.\n"},{"id":"d.02","statement":"activities associated with configuration-controlled changes to the system are reviewed.\n"},{"id":"c.01","statement":"approved configuration-controlled changes to the system are implemented."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-03_to_nist-sp-800-53-r5-cm-3","source_ref":"requirement--nist-sp-800-171-r3-03-04-03","target_ref":"requirement--nist-sp-800-53-r5-cm-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-cm-01-to-800-171-03-04-03","source_ref":"control--ogrl-cm-01","target_ref":"requirement--nist-sp-800-171-r3-03-04-03","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Peer-reviewed change authorization and tracking satisfy SP 800-171 03.04.03."}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-04","slug":"03-04-04","display_id":"03.04.04","name":"Impact Analyses","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Analyze changes to the system to determine potential security impacts prior to change implementation.\n"},{"id":"b","statement":"Verify that the security requirements for the system continue to be satisfied after the system changes have been implemented.\n"}],"objectives_count":2,"objectives_preview":[{"id":"b","statement":"the security requirements for the system continue to be satisfied after the system changes have been implemented.\n"},{"id":"a","statement":"changes to the system are analyzed to determine potential security impacts prior to change implementation.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-04_to_nist-sp-800-53-r5-cm-4","source_ref":"requirement--nist-sp-800-171-r3-03-04-04","target_ref":"requirement--nist-sp-800-53-r5-cm-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-04_to_nist-sp-800-53-r5-cm-4-2","source_ref":"requirement--nist-sp-800-171-r3-03-04-04","target_ref":"requirement--nist-sp-800-53-r5-cm-4-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-05","slug":"03-04-05","display_id":"03.04.05","name":"Access Restrictions for Change","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"01","statement":"physical access restrictions associated with changes to the system are defined and documented.\n"},{"id":"02","statement":"physical access restrictions associated with changes to the system are approved."},{"id":"03","statement":"physical access restrictions associated with changes to the system are enforced."},{"id":"04","statement":"logical access restrictions associated with changes to the system are defined and documented.\n"},{"id":"05","statement":"logical access restrictions associated with changes to the system are approved."},{"id":"06","statement":"logical access restrictions associated with changes to the system are enforced."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-05_to_nist-sp-800-53-r5-cm-5","source_ref":"requirement--nist-sp-800-171-r3-03-04-05","target_ref":"requirement--nist-sp-800-53-r5-cm-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-06","slug":"03-04-06","display_id":"03.04.06","name":"Least Functionality","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Configure the system to provide only mission-essential capabilities."},{"id":"b","statement":"Prohibit or restrict use of the following functions, ports, protocols, connections, and services: {{ a_03_04_06_odp_01 }} .\n"},{"id":"c","statement":"Review the system {{ a_03_04_06_odp_06 }} to identify unnecessary or nonsecure functions, ports, protocols, connections, and services.\n"},{"id":"d","statement":"Disable or remove functions, ports, protocols, connections, and services that are unnecessary or nonsecure.\n"}],"objectives_count":8,"objectives_preview":[{"id":"b.01","statement":"the use of the following functions is prohibited or restricted: {{ a_03_04_06_odp_01 }}.\n"},{"id":"b.02","statement":"the use of the following ports is prohibited or restricted: {{ a_03_04_06_odp_02 }}.\n"},{"id":"b.03","statement":"the use of the following protocols is prohibited or restricted: {{ a_03_04_06_odp_03 }}.\n"},{"id":"b.04","statement":"the use of the following connections is prohibited or restricted: {{ a_03_04_06_odp_04 }}.\n"},{"id":"b.05","statement":"the use of the following services is prohibited or restricted: {{ a_03_04_06_odp_05 }}.\n"},{"id":"c","statement":"the system is reviewed {{ a_03_04_06_odp_06 }} to identify unnecessary or nonsecure functions, ports, protocols, connections, and services.\n"}],"params_count":6,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-06_to_nist-sp-800-53-r5-cm-7","source_ref":"requirement--nist-sp-800-171-r3-03-04-06","target_ref":"requirement--nist-sp-800-53-r5-cm-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-06_to_nist-sp-800-53-r5-cm-7-1","source_ref":"requirement--nist-sp-800-171-r3-03-04-06","target_ref":"requirement--nist-sp-800-53-r5-cm-7-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-07","slug":"03-04-07","display_id":"03.04.07","name":"03.04.07","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-07_to_nist-sp-800-171-r3-03-04-06","source_ref":"requirement--nist-sp-800-171-r3-03-04-07","target_ref":"requirement--nist-sp-800-171-r3-03-04-06","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-07_to_nist-sp-800-171-r3-03-04-08","source_ref":"requirement--nist-sp-800-171-r3-03-04-07","target_ref":"requirement--nist-sp-800-171-r3-03-04-08","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-08","slug":"03-04-08","display_id":"03.04.08","name":"Authorized Software – Allow by Exception","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify software programs authorized to execute on the system."},{"id":"b","statement":"Implement a deny-all, allow-by-exception policy for the execution of authorized software programs on the system.\n"},{"id":"c","statement":"Review and update the list of authorized software programs {{ a_03_04_08_odp_01 }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"software programs authorized to execute on the system are identified."},{"id":"b","statement":"a deny-all, allow-by-exception policy for the execution of authorized software programs on the system is implemented.\n"},{"id":"c","statement":"the list of authorized software programs is reviewed and updated {{ a_03_04_08_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-08_to_nist-sp-800-53-r5-cm-7-5","source_ref":"requirement--nist-sp-800-171-r3-03-04-08","target_ref":"requirement--nist-sp-800-53-r5-cm-7-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-09","slug":"03-04-09","display_id":"03.04.09","name":"03.04.09","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-09_to_nist-sp-800-171-r3-03-01-05","source_ref":"requirement--nist-sp-800-171-r3-03-04-09","target_ref":"requirement--nist-sp-800-171-r3-03-01-05","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-09_to_nist-sp-800-171-r3-03-01-06","source_ref":"requirement--nist-sp-800-171-r3-03-04-09","target_ref":"requirement--nist-sp-800-171-r3-03-01-06","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-09_to_nist-sp-800-171-r3-03-01-07","source_ref":"requirement--nist-sp-800-171-r3-03-04-09","target_ref":"requirement--nist-sp-800-171-r3-03-01-07","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-09_to_nist-sp-800-171-r3-03-04-08","source_ref":"requirement--nist-sp-800-171-r3-03-04-09","target_ref":"requirement--nist-sp-800-171-r3-03-04-08","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-09_to_nist-sp-800-171-r3-03-12-03","source_ref":"requirement--nist-sp-800-171-r3-03-04-09","target_ref":"requirement--nist-sp-800-171-r3-03-12-03","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-09.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-10","slug":"03-04-10","display_id":"03.04.10","name":"System Component Inventory","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and document an inventory of system components."},{"id":"b","statement":"Review and update the system component inventory {{ a_03_04_10_odp_01 }}."},{"id":"c","statement":"Update the system component inventory as part of installations, removals, and system updates.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"an inventory of system components is developed and documented."},{"id":"b.01","statement":"the system component inventory is reviewed {{ a_03_04_10_odp_01 }}."},{"id":"b.02","statement":"the system component inventory is updated {{ a_03_04_10_odp_01 }}."},{"id":"c.01","statement":"the system component inventory is updated as part of component installations."},{"id":"c.02","statement":"the system component inventory is updated as part of component removals."},{"id":"c.03","statement":"the system component inventory is updated as part of system updates."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-10_to_nist-sp-800-53-r5-cm-8","source_ref":"requirement--nist-sp-800-171-r3-03-04-10","target_ref":"requirement--nist-sp-800-53-r5-cm-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-04-10_to_nist-sp-800-53-r5-cm-8-1","source_ref":"requirement--nist-sp-800-171-r3-03-04-10","target_ref":"requirement--nist-sp-800-53-r5-cm-8-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-10.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-11","slug":"03-04-11","display_id":"03.04.11","name":"Information Location","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify and document the location of CUI and the system components on which the information is processed and stored.\n"},{"id":"b","statement":"Document changes to the system or system component location where CUI is processed and stored.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.01","statement":"the location of CUI is identified and documented."},{"id":"a.02","statement":"the system components on which CUI is processed are identified and documented."},{"id":"a.03","statement":"the system components on which CUI is stored are identified and documented."},{"id":"b.01","statement":"changes to the system or system component location where CUI is processed are documented.\n"},{"id":"b.02","statement":"changes to the system or system component location where CUI is stored are documented.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-11_to_nist-sp-800-53-r5-cm-12","source_ref":"requirement--nist-sp-800-171-r3-03-04-11","target_ref":"requirement--nist-sp-800-53-r5-cm-12","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-11.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-04-12","slug":"03-04-12","display_id":"03.04.12","name":"System and Component Configuration for High-Risk Areas","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Issue systems or system components with the following configurations to individuals traveling to high-risk locations: {{ a_03_04_12_odp_01 }}.\n"},{"id":"b","statement":"Apply the following security requirements to the systems or components when the individuals return from travel: {{ a_03_04_12_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"systems or system components with the following configurations are issued to individuals traveling to high-risk locations: {{ a_03_04_12_odp_01 }}.\n"},{"id":"b","statement":"the following security requirements are applied to the system or system components when the individuals return from travel: {{ a_03_04_12_odp_02 }}.\n"}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-04-12_to_nist-sp-800-53-r5-cm-2-7","source_ref":"requirement--nist-sp-800-171-r3-03-04-12","target_ref":"requirement--nist-sp-800-53-r5-cm-2-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-04-12.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-01","slug":"03-05-01","display_id":"03.05.01","name":"User Identification and Authentication","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Uniquely identify and authenticate system users, and associate that unique identification with processes acting on behalf of those users.\n"},{"id":"b","statement":"Re-authenticate users when {{ a_03_05_01_odp_01 }} ."}],"objectives_count":4,"objectives_preview":[{"id":"a.01","statement":"system users are uniquely identified."},{"id":"a.02","statement":"system users are authenticated."},{"id":"a.03","statement":"processes acting on behalf of users are associated with uniquely identified and authenticated system users.\n"},{"id":"b","statement":"users are reauthenticated when {{ a_03_05_01_odp_01 }} ."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-01_to_nist-sp-800-53-r5-ia-11","source_ref":"requirement--nist-sp-800-171-r3-03-05-01","target_ref":"requirement--nist-sp-800-53-r5-ia-11","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-05-01_to_nist-sp-800-53-r5-ia-2","source_ref":"requirement--nist-sp-800-171-r3-03-05-01","target_ref":"requirement--nist-sp-800-53-r5-ia-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-02","slug":"03-05-02","display_id":"03.05.02","name":"Device Identification and Authentication","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Uniquely identify and authenticate {{ a_03_05_02_odp_01 }} before establishing a system connection.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"02","statement":"{{ a_03_05_02_odp_01 }} are authenticated before establishing a system connection.\n"},{"id":"01","statement":"{{ a_03_05_02_odp_01 }} are uniquely identified before establishing a system connection.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-02_to_nist-sp-800-53-r5-ia-3","source_ref":"requirement--nist-sp-800-171-r3-03-05-02","target_ref":"requirement--nist-sp-800-53-r5-ia-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-03","slug":"03-05-03","display_id":"03.05.03","name":"Multi-Factor Authentication","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Implement multi-factor authentication for access to privileged and non-privileged accounts.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"multi-factor authentication for access to privileged accounts is implemented."},{"id":"02","statement":"multi-factor authentication for access to non-privileged accounts is implemented.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-03_to_nist-sp-800-53-r5-ia-2-1","source_ref":"requirement--nist-sp-800-171-r3-03-05-03","target_ref":"requirement--nist-sp-800-53-r5-ia-2-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-05-03_to_nist-sp-800-53-r5-ia-2-2","source_ref":"requirement--nist-sp-800-171-r3-03-05-03","target_ref":"requirement--nist-sp-800-53-r5-ia-2-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-ac-05-to-800-171-03-05-03","source_ref":"control--ogrl-ac-05","target_ref":"requirement--nist-sp-800-171-r3-03-05-03","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"MFA enforcement across interactive and privileged logins satisfies SP 800-171 03.05.03.\n"}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-04","slug":"03-05-04","display_id":"03.05.04","name":"Replay-Resistant Authentication","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Implement replay-resistant authentication mechanisms for access to privileged and non-privileged accounts.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"replay-resistant authentication mechanisms for access to privileged accounts are implemented.\n"},{"id":"02","statement":"replay-resistant authentication mechanisms for access to non-privileged accounts are implemented.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-04_to_nist-sp-800-53-r5-ia-2-8","source_ref":"requirement--nist-sp-800-171-r3-03-05-04","target_ref":"requirement--nist-sp-800-53-r5-ia-2-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-05","slug":"03-05-05","display_id":"03.05.05","name":"Identifier Management","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Receive authorization from organizational personnel or roles to assign an individual, group, role, service, or device identifier.\n"},{"id":"b","statement":"Select and assign an identifier that identifies an individual, group, role, service, or device.\n"},{"id":"c","statement":"Prevent the reuse of identifiers for {{ a_03_05_05_odp_01 }}."},{"id":"d","statement":"Manage individual identifiers by uniquely identifying each individual as {{ a_03_05_05_odp_02 }}.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"authorization is received from organizational personnel or roles to assign an individual, group, role, service, or device identifier.\n"},{"id":"b.01","statement":"an identifier that identifies an individual, group, role, service, or device is selected.\n"},{"id":"b.02","statement":"an identifier that identifies an individual, group, role, service, or device is assigned.\n"},{"id":"c","statement":"the reuse of identifiers for {{ a_03_05_05_odp_01 }} is prevented."},{"id":"d","statement":"individual identifiers are managed by uniquely identifying each individual as {{ a_03_05_05_odp_02 }}.\n"}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-05_to_nist-sp-800-53-r5-ia-4","source_ref":"requirement--nist-sp-800-171-r3-03-05-05","target_ref":"requirement--nist-sp-800-53-r5-ia-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-05-05_to_nist-sp-800-53-r5-ia-4-4","source_ref":"requirement--nist-sp-800-171-r3-03-05-05","target_ref":"requirement--nist-sp-800-53-r5-ia-4-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-06","slug":"03-05-06","display_id":"03.05.06","name":"03.05.06","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-07","slug":"03-05-07","display_id":"03.05.07","name":"Password Management","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Maintain a list of commonly-used, expected, or compromised passwords, and update the list {{ a_03_05_07_odp_01 }} and when organizational passwords are suspected to have been compromised.\n"},{"id":"b","statement":"Verify that passwords are not found on the list of commonly used, expected, or compromised passwords when users create or update passwords.\n"},{"id":"c","statement":"Transmit passwords only over cryptographically protected channels."},{"id":"d","statement":"Store passwords in a cryptographically protected form."},{"id":"e","statement":"Select a new password upon first use after account recovery."},{"id":"f","statement":"Enforce the following composition and complexity rules for passwords: {{ a_03_05_07_odp_02 }}.\n"}],"objectives_count":8,"objectives_preview":[{"id":"a.01","statement":"a list of commonly used, expected, or compromised passwords is maintained."},{"id":"a.02","statement":"a list of commonly used, expected, or compromised passwords is updated {{ a_03_05_07_odp_01 }}.\n"},{"id":"a.03","statement":"a list of commonly used, expected, or compromised passwords is updated when organizational passwords are suspected to have been compromised.\n"},{"id":"b","statement":"passwords are verified not to be found on the list of commonly used, expected, or compromised passwords when they are created or updated by users.\n"},{"id":"c","statement":"passwords are only transmitted over cryptographically protected channels."},{"id":"d","statement":"passwords are stored in a cryptographically protected form."}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-07_to_nist-sp-800-53-r5-ia-5-1","source_ref":"requirement--nist-sp-800-171-r3-03-05-07","target_ref":"requirement--nist-sp-800-53-r5-ia-5-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-08","slug":"03-05-08","display_id":"03.05.08","name":"03.05.08","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-09","slug":"03-05-09","display_id":"03.05.09","name":"03.05.09","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-09.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-10","slug":"03-05-10","display_id":"03.05.10","name":"03.05.10","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-10_to_nist-sp-800-171-r3-03-05-07","source_ref":"requirement--nist-sp-800-171-r3-03-05-10","target_ref":"requirement--nist-sp-800-171-r3-03-05-07","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-10.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-11","slug":"03-05-11","display_id":"03.05.11","name":"Authentication Feedback","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Obscure feedback of authentication information during the authentication process.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"feedback of authentication information during the authentication process is obscured.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-11_to_nist-sp-800-53-r5-ia-6","source_ref":"requirement--nist-sp-800-171-r3-03-05-11","target_ref":"requirement--nist-sp-800-53-r5-ia-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-11.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-05-12","slug":"03-05-12","display_id":"03.05.12","name":"Authenticator Management","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Verify the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution.\n"},{"id":"b","statement":"Establish initial authenticator content for any authenticators issued by the organization.\n"},{"id":"c","statement":"Establish and implement administrative procedures for initial authenticator distribution; for lost, compromised, or damaged authenticators; and for revoking authenticators.\n"},{"id":"d","statement":"Change default authenticators at first use."},{"id":"e","statement":"Change or refresh authenticators {{ a_03_05_12_odp_01 }} or when the following events occur: {{ a_03_05_12_odp_02 }}.\n"},{"id":"f","statement":"Protect authenticator content from unauthorized disclosure and modification."}],"objectives_count":12,"objectives_preview":[{"id":"a","statement":"the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution is verified.\n"},{"id":"b","statement":"initial authenticator content for any authenticators issued by the organization is established.\n"},{"id":"c.01","statement":"administrative procedures for initial authenticator distribution are established.\n"},{"id":"c.02","statement":"administrative procedures for lost, compromised, or damaged authenticators are established.\n"},{"id":"c.03","statement":"administrative procedures for revoking authenticators are established."},{"id":"c.04","statement":"administrative procedures for initial authenticator distribution are implemented.\n"}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-05-12_to_nist-sp-800-53-r5-ia-5","source_ref":"requirement--nist-sp-800-171-r3-03-05-12","target_ref":"requirement--nist-sp-800-53-r5-ia-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-05-12.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-06-01","slug":"03-06-01","display_id":"03.06.01","name":"Incident Handling","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Implement an incident-handling capability that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"01","statement":"an incident-handling capability that is consistent with the incident response plan is implemented.\n"},{"id":"02","statement":"the incident handling capability includes preparation."},{"id":"03","statement":"the incident handling capability includes detection and analysis."},{"id":"04","statement":"the incident handling capability includes containment."},{"id":"05","statement":"the incident handling capability includes eradication."},{"id":"06","statement":"the incident handling capability includes recovery."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-06-01_to_nist-sp-800-53-r5-ir-4","source_ref":"requirement--nist-sp-800-171-r3-03-06-01","target_ref":"requirement--nist-sp-800-53-r5-ir-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-06-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-06-02","slug":"03-06-02","display_id":"03.06.02","name":"Incident Monitoring, Reporting, and Response Assistance","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Track and document system security incidents."},{"id":"b","statement":"Report suspected incidents to the organizational incident response capability within {{ a_03_06_02_odp_01 }}.\n"},{"id":"c","statement":"Report incident information to {{ a_03_06_02_odp_02 }}."},{"id":"d","statement":"Provide an incident response support resource that offers advice and assistance to system users on handling and reporting incidents.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.01","statement":"system security incidents are tracked."},{"id":"a.02","statement":"system security incidents are documented."},{"id":"b","statement":"suspected incidents are reported to the organizational incident response capability within {{ a_03_06_02_odp_01 }}.\n"},{"id":"c","statement":"incident information is reported to {{ a_03_06_02_odp_02 }}."},{"id":"d","statement":"an incident response support resource that offers advice and assistance to system users on handling and reporting incidents is provided.\n"}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-06-02_to_nist-sp-800-53-r5-ir-5","source_ref":"requirement--nist-sp-800-171-r3-03-06-02","target_ref":"requirement--nist-sp-800-53-r5-ir-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-06-02_to_nist-sp-800-53-r5-ir-6","source_ref":"requirement--nist-sp-800-171-r3-03-06-02","target_ref":"requirement--nist-sp-800-53-r5-ir-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-06-02_to_nist-sp-800-53-r5-ir-7","source_ref":"requirement--nist-sp-800-171-r3-03-06-02","target_ref":"requirement--nist-sp-800-53-r5-ir-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-06-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-06-03","slug":"03-06-03","display_id":"03.06.03","name":"Incident Response Testing","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Test the effectiveness of the incident response capability {{ a_03_06_03_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"the effectiveness of the incident response capability is tested {{ a_03_06_03_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-06-03_to_nist-sp-800-53-r5-ir-3","source_ref":"requirement--nist-sp-800-171-r3-03-06-03","target_ref":"requirement--nist-sp-800-53-r5-ir-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-ir-01-to-800-171-03-06-03","source_ref":"control--ogrl-ir-01","target_ref":"requirement--nist-sp-800-171-r3-03-06-03","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"a_03_06_03_odp_01":"ir_test_cadence"},"summary":"Periodic incident response tabletop drills satisfy SP 800-171 03.06.03."}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-06-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-06-04","slug":"03-06-04","display_id":"03.06.04","name":"Incident Response Training","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide incident response training to system users consistent with assigned roles and responsibilities:\n"},{"id":"a.01","statement":"Within {{ a_03_06_04_odp_01 }} of assuming an incident response role or responsibility or acquiring system access,\n"},{"id":"a.02","statement":"When required by system changes, and"},{"id":"a.03","statement":"{{ a_03_06_04_odp_02 }} thereafter."},{"id":"b","statement":"Review and update incident response training content {{ a_03_06_04_odp_03 }} and following {{ a_03_06_04_odp_04 }}.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a.01","statement":"incident response training for system users consistent with assigned roles and responsibilities is provided within {{ a_03_06_04_odp_01 }} of assuming an incident response role or responsibility or acquiring system access.\n"},{"id":"a.02","statement":"incident response training for system users consistent with assigned roles and responsibilities is provided when required by system changes.\n"},{"id":"a.03","statement":"incident response training for system users consistent with assigned roles and responsibilities is provided {{ a_03_06_04_odp_02 }} thereafter.\n"},{"id":"b.04","statement":"incident response training content is updated following {{ a_03_06_04_odp_04 }}."},{"id":"b.02","statement":"incident response training content is updated {{ a_03_06_04_odp_03 }}."},{"id":"b.03","statement":"incident response training content is reviewed following {{ a_03_06_04_odp_04 }}.\n"}],"params_count":4,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-06-04_to_nist-sp-800-53-r5-ir-2","source_ref":"requirement--nist-sp-800-171-r3-03-06-04","target_ref":"requirement--nist-sp-800-53-r5-ir-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-06-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-06-05","slug":"03-06-05","display_id":"03.06.05","name":"Incident Response Plan","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop an incident response plan that:"},{"id":"a.01","statement":"Provides the organization with a roadmap for implementing its incident response capability,\n"},{"id":"a.02","statement":"Describes the structure and organization of the incident response capability,"},{"id":"a.03","statement":"Provides a high-level approach for how the incident response capability fits into the overall organization,\n"},{"id":"a.04","statement":"Defines reportable incidents,"},{"id":"a.05","statement":"Addresses the sharing of incident information, and"},{"id":"a.06","statement":"Designates responsibilities to organizational entities, personnel, or roles."},{"id":"b","statement":"Distribute copies of the incident response plan to designated incident response personnel (identified by name and/or by role) and organizational elements.\n"},{"id":"c","statement":"Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing.\n"},{"id":"d","statement":"Protect the incident response plan from unauthorized disclosure."}],"objectives_count":10,"objectives_preview":[{"id":"a.01","statement":"an incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability.\n"},{"id":"a.02","statement":"an incident response plan is developed that describes the structure and organization of the incident response capability.\n"},{"id":"a.03","statement":"an incident response plan is developed that provides a high-level approach for how the incident response capability fits into the overall organization.\n"},{"id":"a.04","statement":"an incident response plan is developed that defines reportable incidents."},{"id":"a.05","statement":"an incident response plan is developed that addresses the sharing of incident information.\n"},{"id":"a.06","statement":"an incident response plan is developed that designates responsibilities to organizational entities, personnel, or roles.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-06-05_to_nist-sp-800-53-r5-ir-8","source_ref":"requirement--nist-sp-800-171-r3-03-06-05","target_ref":"requirement--nist-sp-800-53-r5-ir-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-06-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-07-01","slug":"03-07-01","display_id":"03.07.01","name":"03.07.01","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-07-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-07-02","slug":"03-07-02","display_id":"03.07.02","name":"03.07.02","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-07-02_to_nist-sp-800-171-r3-03-07-04","source_ref":"requirement--nist-sp-800-171-r3-03-07-02","target_ref":"requirement--nist-sp-800-171-r3-03-07-04","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-07-02_to_nist-sp-800-171-r3-03-07-06","source_ref":"requirement--nist-sp-800-171-r3-03-07-02","target_ref":"requirement--nist-sp-800-171-r3-03-07-06","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-07-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-07-03","slug":"03-07-03","display_id":"03.07.03","name":"03.07.03","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-07-03_to_nist-sp-800-171-r3-03-08-03","source_ref":"requirement--nist-sp-800-171-r3-03-07-03","target_ref":"requirement--nist-sp-800-171-r3-03-08-03","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-07-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-07-04","slug":"03-07-04","display_id":"03.07.04","name":"Maintenance Tools","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve, control, and monitor the use of system maintenance tools."},{"id":"b","statement":"Check media with diagnostic and test programs for malicious code before it is used in the system.\n"},{"id":"c","statement":"Prevent the removal of system maintenance equipment containing CUI by verifying that there is no CUI on the equipment, sanitizing or destroying the equipment, or retaining the equipment within the facility.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.01","statement":"the use of system maintenance tools is approved."},{"id":"a.02","statement":"the use of system maintenance tools is controlled."},{"id":"a.03","statement":"the use of system maintenance tools is monitored."},{"id":"b","statement":"media with diagnostic and test programs are checked for malicious code before the media are used in the system.\n"},{"id":"c","statement":"the removal of system maintenance equipment containing CUI is prevented by verifying that there is no CUI on the equipment, sanitizing or destroying the equipment, or retaining the equipment within the facility.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-07-04_to_nist-sp-800-53-r5-ma-3","source_ref":"requirement--nist-sp-800-171-r3-03-07-04","target_ref":"requirement--nist-sp-800-53-r5-ma-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-07-04_to_nist-sp-800-53-r5-ma-3-1","source_ref":"requirement--nist-sp-800-171-r3-03-07-04","target_ref":"requirement--nist-sp-800-53-r5-ma-3-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-07-04_to_nist-sp-800-53-r5-ma-3-2","source_ref":"requirement--nist-sp-800-171-r3-03-07-04","target_ref":"requirement--nist-sp-800-53-r5-ma-3-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-07-04_to_nist-sp-800-53-r5-ma-3-3","source_ref":"requirement--nist-sp-800-171-r3-03-07-04","target_ref":"requirement--nist-sp-800-53-r5-ma-3-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-07-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-07-05","slug":"03-07-05","display_id":"03.07.05","name":"Nonlocal Maintenance","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve and monitor nonlocal maintenance and diagnostic activities."},{"id":"b","statement":"Implement multi-factor authentication and replay resistance in the establishment of nonlocal maintenance and diagnostic sessions.\n"},{"id":"c","statement":"Terminate session and network connections when nonlocal maintenance is completed.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"nonlocal maintenance and diagnostic activities are approved."},{"id":"a.02","statement":"nonlocal maintenance and diagnostic activities are monitored."},{"id":"c.01","statement":"session connections are terminated when nonlocal maintenance is completed."},{"id":"c.02","statement":"network connections are terminated when nonlocal maintenance is completed."},{"id":"b.01","statement":"multi-factor authentication is implemented in the establishment of nonlocal maintenance and diagnostic sessions.\n"},{"id":"b.02","statement":"replay resistance is implemented in the establishment of nonlocal maintenance and diagnostic sessions.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-07-05_to_nist-sp-800-53-r5-ma-4","source_ref":"requirement--nist-sp-800-171-r3-03-07-05","target_ref":"requirement--nist-sp-800-53-r5-ma-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-07-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-07-06","slug":"03-07-06","display_id":"03.07.06","name":"Maintenance Personnel","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish a process for maintenance personnel authorization."},{"id":"b","statement":"Maintain a list of authorized maintenance organizations or personnel."},{"id":"c","statement":"Verify that non-escorted personnel who perform maintenance on the system possess the required access authorizations.\n"},{"id":"d","statement":"Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"a process for maintenance personnel authorization is established."},{"id":"b","statement":"a list of authorized maintenance organizations or personnel is maintained."},{"id":"d.01","statement":"organizational personnel with required access authorizations are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.\n"},{"id":"d.02","statement":"organizational personnel with required technical competence are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.\n"},{"id":"c","statement":"non-escorted personnel who perform maintenance on the system possess the required access authorizations.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-07-06_to_nist-sp-800-53-r5-ma-5","source_ref":"requirement--nist-sp-800-171-r3-03-07-06","target_ref":"requirement--nist-sp-800-53-r5-ma-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-07-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-01","slug":"03-08-01","display_id":"03.08.01","name":"Media Storage","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Physically control and securely store system media that contain CUI.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"system media that contain CUI are physically controlled."},{"id":"02","statement":"system media that contain CUI are securely stored."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-01_to_nist-sp-800-53-r5-mp-4","source_ref":"requirement--nist-sp-800-171-r3-03-08-01","target_ref":"requirement--nist-sp-800-53-r5-mp-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-02","slug":"03-08-02","display_id":"03.08.02","name":"Media Access","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Restrict access to CUI on system media to authorized personnel or roles.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"access to CUI on system media is restricted to authorized personnel or roles."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-02_to_nist-sp-800-53-r5-mp-2","source_ref":"requirement--nist-sp-800-171-r3-03-08-02","target_ref":"requirement--nist-sp-800-53-r5-mp-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-03","slug":"03-08-03","display_id":"03.08.03","name":"Media Sanitization","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Sanitize system media that contain CUI prior to disposal, release out of organizational control, or release for reuse.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"system media that contain CUI are sanitized prior to disposal, release out of organizational control, or release for reuse.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-03_to_nist-sp-800-53-r5-mp-6","source_ref":"requirement--nist-sp-800-171-r3-03-08-03","target_ref":"requirement--nist-sp-800-53-r5-mp-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-04","slug":"03-08-04","display_id":"03.08.04","name":"Media Marking","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Mark system media that contain CUI to indicate distribution limitations, handling caveats, and applicable CUI markings.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"01","statement":"system media that contain CUI are marked to indicate distribution limitations."},{"id":"02","statement":"system media that contain CUI are marked to indicate handling caveats."},{"id":"03","statement":"system media that contain CUI are marked to indicate applicable CUI markings."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-04_to_nist-sp-800-53-r5-mp-3","source_ref":"requirement--nist-sp-800-171-r3-03-08-04","target_ref":"requirement--nist-sp-800-53-r5-mp-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-05","slug":"03-08-05","display_id":"03.08.05","name":"Media Transport","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Protect and control system media that contain CUI during transport outside of controlled areas.\n"},{"id":"b","statement":"Maintain accountability of system media that contain CUI during transport outside of controlled areas.\n"},{"id":"c","statement":"Document activities associated with the transport of system media that contain CUI.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a.01","statement":"system media that contain CUI are protected during transport outside of controlled areas.\n"},{"id":"a.02","statement":"system media that contain CUI are controlled during transport outside of controlled areas.\n"},{"id":"c","statement":"activities associated with the transport of system media that contain CUI are documented.\n"},{"id":"b","statement":"accountability for system media that contain CUI is maintained during transport outside of controlled areas.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-05_to_nist-sp-800-53-r5-mp-5","source_ref":"requirement--nist-sp-800-171-r3-03-08-05","target_ref":"requirement--nist-sp-800-53-r5-mp-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-08-05_to_nist-sp-800-53-r5-sc-28","source_ref":"requirement--nist-sp-800-171-r3-03-08-05","target_ref":"requirement--nist-sp-800-53-r5-sc-28","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-06","slug":"03-08-06","display_id":"03.08.06","name":"03.08.06","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-06_to_nist-sp-800-171-r3-03-13-08","source_ref":"requirement--nist-sp-800-171-r3-03-08-06","target_ref":"requirement--nist-sp-800-171-r3-03-13-08","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-07","slug":"03-08-07","display_id":"03.08.07","name":"Media Use","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Restrict or prohibit the use of {{ a_03_08_07_odp_01 }}."},{"id":"b","statement":"Prohibit the use of removable system media without an identifiable owner."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the use of the following types of system media is restricted or prohibited: {{ a_03_08_07_odp_01 }}.\n"},{"id":"b","statement":"the use of removable system media without an identifiable owner is prohibited."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-07_to_nist-sp-800-53-r5-mp-7","source_ref":"requirement--nist-sp-800-171-r3-03-08-07","target_ref":"requirement--nist-sp-800-53-r5-mp-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-08","slug":"03-08-08","display_id":"03.08.08","name":"03.08.08","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-08_to_nist-sp-800-171-r3-03-08-07","source_ref":"requirement--nist-sp-800-171-r3-03-08-08","target_ref":"requirement--nist-sp-800-171-r3-03-08-07","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-08-09","slug":"03-08-09","display_id":"03.08.09","name":"System Backup – Cryptographic Protection","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Protect the confidentiality of backup information."},{"id":"b","statement":"Implement cryptographic mechanisms to prevent the unauthorized disclosure of CUI at backup storage locations.\n"}],"objectives_count":2,"objectives_preview":[{"id":"b","statement":"cryptographic mechanisms are implemented to prevent the unauthorized disclosure of CUI at backup storage locations.\n"},{"id":"a","statement":"the confidentiality of backup information is protected."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-08-09_to_nist-sp-800-53-r5-cp-9","source_ref":"requirement--nist-sp-800-171-r3-03-08-09","target_ref":"requirement--nist-sp-800-53-r5-cp-9","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-08-09_to_nist-sp-800-53-r5-cp-9-8","source_ref":"requirement--nist-sp-800-171-r3-03-08-09","target_ref":"requirement--nist-sp-800-53-r5-cp-9-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-08-09.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-09-01","slug":"03-09-01","display_id":"03.09.01","name":"Personnel Screening","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Screen individuals prior to authorizing access to the system."},{"id":"b","statement":"Rescreen individuals in accordance with {{ a_03_09_01_odp_01 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"individuals are screened prior to authorizing access to the system."},{"id":"b","statement":"individuals are rescreened in accordance with the following conditions: {{ a_03_09_01_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-09-01_to_nist-sp-800-53-r5-ps-3","source_ref":"requirement--nist-sp-800-171-r3-03-09-01","target_ref":"requirement--nist-sp-800-53-r5-ps-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-09-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-09-02","slug":"03-09-02","display_id":"03.09.02","name":"Personnel Termination and Transfer","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"When individual employment is terminated:"},{"id":"a.01","statement":"Disable system access within {{ a_03_09_02_odp_01 }},"},{"id":"a.02","statement":"Terminate or revoke authenticators and credentials associated with the individual, and\n"},{"id":"a.03","statement":"Retrieve security-related system property."},{"id":"b","statement":"When individuals are reassigned or transferred to other positions in the organization:\n"},{"id":"b.01","statement":"Review and confirm the ongoing operational need for current logical and physical access authorizations to the system and facility, and\n"},{"id":"b.02","statement":"Modify access authorization to correspond with any changes in operational need."}],"objectives_count":7,"objectives_preview":[{"id":"a.01","statement":"upon termination of individual employment, system access is disabled within {{ a_03_09_02_odp_01 }}.\n"},{"id":"a.02.01","statement":"upon termination of individual employment, authenticators associated with the individual are terminated or revoked.\n"},{"id":"a.02.02","statement":"upon termination of individual employment, credentials associated with the individual are terminated or revoked.\n"},{"id":"a.03","statement":"upon termination of individual employment, security-related system property is retrieved.\n"},{"id":"b.02","statement":"upon individual reassignment or transfer to other positions in the organization, access authorization is modified to correspond with any changes in operational need.\n"},{"id":"b.01.01","statement":"upon individual reassignment or transfer to other positions in the organization, the ongoing operational need for current logical and physical access authorizations to the system and facility is reviewed.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-09-02_to_nist-sp-800-53-r5-ps-4","source_ref":"requirement--nist-sp-800-171-r3-03-09-02","target_ref":"requirement--nist-sp-800-53-r5-ps-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-09-02_to_nist-sp-800-53-r5-ps-5","source_ref":"requirement--nist-sp-800-171-r3-03-09-02","target_ref":"requirement--nist-sp-800-53-r5-ps-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-09-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-01","slug":"03-10-01","display_id":"03.10.01","name":"Physical Access Authorizations","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, approve, and maintain a list of individuals with authorized access to the facility where the system resides.\n"},{"id":"b","statement":"Issue authorization credentials for facility access."},{"id":"c","statement":"Review the facility access list {{ a_03_10_01_odp_01 }}."},{"id":"d","statement":"Remove individuals from the facility access list when access is no longer required.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"a list of individuals with authorized access to the facility where the system resides is developed.\n"},{"id":"a.02","statement":"a list of individuals with authorized access to the facility where the system resides is approved.\n"},{"id":"a.03","statement":"a list of individuals with authorized access to the facility where the system resides is maintained.\n"},{"id":"c","statement":"the facility access list is reviewed {{ a_03_10_01_odp_01 }}."},{"id":"d","statement":"individuals from the facility access list are removed when access is no longer required.\n"},{"id":"b","statement":"authorization credentials for facility access are issued."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-01_to_nist-sp-800-53-r5-pe-2","source_ref":"requirement--nist-sp-800-171-r3-03-10-01","target_ref":"requirement--nist-sp-800-53-r5-pe-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-02","slug":"03-10-02","display_id":"03.10.02","name":"Monitoring Physical Access","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor physical access to the facility where the system resides to detect and respond to physical security incidents.\n"},{"id":"b","statement":"Review physical access logs {{ a_03_10_02_odp_01 }} and upon occurrence of {{ a_03_10_02_odp_02 }}.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a.01","statement":"physical access to the facility where the system resides is monitored to detect physical security incidents.\n"},{"id":"a.02","statement":"physical security incidents are responded to."},{"id":"b.01","statement":"physical access logs are reviewed {{ a_03_10_02_odp_01 }} ."},{"id":"b.02","statement":"physical access logs are reviewed upon occurrence of {{ a_03_10_02_odp_02 }}."}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-02_to_nist-sp-800-53-r5-pe-6","source_ref":"requirement--nist-sp-800-171-r3-03-10-02","target_ref":"requirement--nist-sp-800-53-r5-pe-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-03","slug":"03-10-03","display_id":"03.10.03","name":"03.10.03","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-03_to_nist-sp-800-171-r3-03-10-07","source_ref":"requirement--nist-sp-800-171-r3-03-10-03","target_ref":"requirement--nist-sp-800-171-r3-03-10-07","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-04","slug":"03-10-04","display_id":"03.10.04","name":"03.10.04","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-04_to_nist-sp-800-171-r3-03-10-07","source_ref":"requirement--nist-sp-800-171-r3-03-10-04","target_ref":"requirement--nist-sp-800-171-r3-03-10-07","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-05","slug":"03-10-05","display_id":"03.10.05","name":"03.10.05","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-05_to_nist-sp-800-171-r3-03-10-07","source_ref":"requirement--nist-sp-800-171-r3-03-10-05","target_ref":"requirement--nist-sp-800-171-r3-03-10-07","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-06","slug":"03-10-06","display_id":"03.10.06","name":"Alternate Work Site","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine alternate work sites allowed for use by employees."},{"id":"b","statement":"Employ the following security requirements at alternate work sites: {{ a_03_10_06_odp_01 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"alternate work sites allowed for use by employees are determined."},{"id":"b","statement":"the following security requirements are employed at alternate work sites: {{ a_03_10_06_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-06_to_nist-sp-800-53-r5-pe-17","source_ref":"requirement--nist-sp-800-171-r3-03-10-06","target_ref":"requirement--nist-sp-800-53-r5-pe-17","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-07","slug":"03-10-07","display_id":"03.10.07","name":"Physical Access Control","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce physical access authorizations at entry and exit points to the facility where the system resides by:\n"},{"id":"a.01","statement":"Verifying individual physical access authorizations before granting access to the facility and\n"},{"id":"a.02","statement":"Controlling ingress and egress with physical access control systems, devices, or guards.\n"},{"id":"b","statement":"Maintain physical access audit logs for entry or exit points."},{"id":"c","statement":"Escort visitors, and control visitor activity."},{"id":"d","statement":"Secure keys, combinations, and other physical access devices."},{"id":"e","statement":"Control physical access to output devices to prevent unauthorized individuals from obtaining access to CUI.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a.01","statement":"physical access authorizations are enforced at entry and exit points to the facility where the system resides by verifying individual physical access authorizations before granting access.\n"},{"id":"a.02","statement":"physical access authorizations are enforced at entry and exit points to the facility where the system resides by controlling ingress and egress with physical access control systems, devices, or guards.\n"},{"id":"b","statement":"physical access audit logs for entry or exit points are maintained."},{"id":"c.01","statement":"visitors are escorted."},{"id":"c.02","statement":"visitor activity is controlled."},{"id":"e","statement":"physical access to output devices is controlled to prevent unauthorized individuals from obtaining access to CUI.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-07_to_nist-sp-800-53-r5-pe-3","source_ref":"requirement--nist-sp-800-171-r3-03-10-07","target_ref":"requirement--nist-sp-800-53-r5-pe-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-10-07_to_nist-sp-800-53-r5-pe-5","source_ref":"requirement--nist-sp-800-171-r3-03-10-07","target_ref":"requirement--nist-sp-800-53-r5-pe-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-10-08","slug":"03-10-08","display_id":"03.10.08","name":"Access Control for Transmission","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Control physical access to system distribution and transmission lines within organizational facilities.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"physical access to system distribution and transmission lines within organizational facilities is controlled.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-10-08_to_nist-sp-800-53-r5-pe-4","source_ref":"requirement--nist-sp-800-171-r3-03-10-08","target_ref":"requirement--nist-sp-800-53-r5-pe-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-10-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-11-01","slug":"03-11-01","display_id":"03.11.01","name":"Risk Assessment","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Assess the risk (including supply chain risk) of unauthorized disclosure resulting from the processing, storage, or transmission of CUI.\n"},{"id":"b","statement":"Update risk assessments {{ a_03_11_01_odp_01 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the risk (including supply chain risk) of unauthorized disclosure resulting from the processing, storage, or transmission of CUI is assessed.\n"},{"id":"b","statement":"risk assessments are updated {{ a_03_11_01_odp_01 }}."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-11-01_to_nist-sp-800-53-r5-ra-3","source_ref":"requirement--nist-sp-800-171-r3-03-11-01","target_ref":"requirement--nist-sp-800-53-r5-ra-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-11-01_to_nist-sp-800-53-r5-ra-3-1","source_ref":"requirement--nist-sp-800-171-r3-03-11-01","target_ref":"requirement--nist-sp-800-53-r5-ra-3-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-11-01_to_nist-sp-800-53-r5-sr-6","source_ref":"requirement--nist-sp-800-171-r3-03-11-01","target_ref":"requirement--nist-sp-800-53-r5-sr-6","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-11-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-11-02","slug":"03-11-02","display_id":"03.11.02","name":"Vulnerability Monitoring and Scanning","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor and scan the system for vulnerabilities {{ a_03_11_02_odp_01 }} and when new vulnerabilities affecting the system are identified.\n"},{"id":"b","statement":"Remediate system vulnerabilities within {{ a_03_11_02_odp_03 }}."},{"id":"c","statement":"Update system vulnerabilities to be scanned {{ a_03_11_02_odp_04 }} and when new vulnerabilities are identified and reported.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a.01","statement":"the system is monitored for vulnerabilities {{ a_03_11_02_odp_01 }}."},{"id":"a.02","statement":"the system is scanned for vulnerabilities {{ a_03_11_02_odp_02 }}."},{"id":"b","statement":"system vulnerabilities are remediated within {{ a_03_11_02_odp_03 }}."},{"id":"a.03","statement":"the system is monitored for vulnerabilities when new vulnerabilities that affect the system are identified.\n"},{"id":"a.04","statement":"the system is scanned for vulnerabilities when new vulnerabilities that affect the system are identified.\n"},{"id":"c.01","statement":"system vulnerabilities to be scanned are updated {{ a_03_11_02_odp_04 }}."}],"params_count":4,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-11-02_to_nist-sp-800-53-r5-ra-5","source_ref":"requirement--nist-sp-800-171-r3-03-11-02","target_ref":"requirement--nist-sp-800-53-r5-ra-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-11-02_to_nist-sp-800-53-r5-ra-5-2","source_ref":"requirement--nist-sp-800-171-r3-03-11-02","target_ref":"requirement--nist-sp-800-53-r5-ra-5-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-vm-01-to-800-171-03-11-02","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-171-r3-03-11-02","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"a_03_11_02_odp_01":"scan_cadence","a_03_11_02_odp_03":"remediation_sla"},"summary":"Continuous vulnerability scanning and SLA remediation satisfy SP 800-171 03.11.02.\n"}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-11-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-11-03","slug":"03-11-03","display_id":"03.11.03","name":"03.11.03","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-11-03_to_nist-sp-800-171-r3-03-11-02","source_ref":"requirement--nist-sp-800-171-r3-03-11-03","target_ref":"requirement--nist-sp-800-171-r3-03-11-02","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-11-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-11-04","slug":"03-11-04","display_id":"03.11.04","name":"Risk Response","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Respond to findings from security assessments, monitoring, and audits.","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"01","statement":"findings from security assessments are responded to."},{"id":"02","statement":"findings from security monitoring are responded to."},{"id":"03","statement":"findings from security audits are responded to."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-11-04_to_nist-sp-800-53-r5-ra-7","source_ref":"requirement--nist-sp-800-171-r3-03-11-04","target_ref":"requirement--nist-sp-800-53-r5-ra-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-11-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-12-01","slug":"03-12-01","display_id":"03.12.01","name":"Security Assessment","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Assess the security requirements for the system and its environment of operation {{ a_03_12_01_odp_01 }} to determine if the requirements have been satisfied.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"the security requirements for the system and its environment of operation are assessed {{ a_03_12_01_odp_01 }} to determine if the requirements have been satisfied.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-12-01_to_nist-sp-800-53-r5-ca-2","source_ref":"requirement--nist-sp-800-171-r3-03-12-01","target_ref":"requirement--nist-sp-800-53-r5-ca-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-12-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-12-02","slug":"03-12-02","display_id":"03.12.02","name":"Plan of Action and Milestones","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a plan of action and milestones for the system:"},{"id":"a.01","statement":"To document the planned remediation actions to correct weaknesses or deficiencies noted during security assessments and\n"},{"id":"a.02","statement":"To reduce or eliminate known system vulnerabilities."},{"id":"b","statement":"Update the existing plan of action and milestones based on the findings from:"},{"id":"b.01","statement":"Security assessments,"},{"id":"b.02","statement":"Audits or reviews, and"},{"id":"b.03","statement":"Continuous monitoring activities."}],"objectives_count":5,"objectives_preview":[{"id":"a.01","statement":"a plan of action and milestones for the system is developed to document the planned remediation actions for correcting weaknesses or deficiencies noted during security assessments.\n"},{"id":"a.02","statement":"a plan of action and milestones for the system is developed to reduce or eliminate known system vulnerabilities.\n"},{"id":"b.01","statement":"the existing plan of action and milestones is updated based on the findings from security assessments.\n"},{"id":"b.03","statement":"the existing plan of action and milestones is updated based on the findings from continuous monitoring activities.\n"},{"id":"b.02","statement":"the existing plan of action and milestones is updated based on the findings from audits or reviews.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-12-02_to_nist-sp-800-53-r5-ca-5","source_ref":"requirement--nist-sp-800-171-r3-03-12-02","target_ref":"requirement--nist-sp-800-53-r5-ca-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-12-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-12-03","slug":"03-12-03","display_id":"03.12.03","name":"Continuous Monitoring","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Develop and implement a system-level continuous monitoring strategy that includes ongoing monitoring and security assessments.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"01","statement":"a system-level continuous monitoring strategy is developed."},{"id":"02","statement":"a system-level continuous monitoring strategy is implemented."},{"id":"03","statement":"ongoing monitoring is included in the continuous monitoring strategy."},{"id":"04","statement":"security assessments are included in the continuous monitoring strategy."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-12-03_to_nist-sp-800-53-r5-ca-7","source_ref":"requirement--nist-sp-800-171-r3-03-12-03","target_ref":"requirement--nist-sp-800-53-r5-ca-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-12-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-12-04","slug":"03-12-04","display_id":"03.12.04","name":"03.12.04","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-12-04_to_nist-sp-800-171-r3-03-15-02","source_ref":"requirement--nist-sp-800-171-r3-03-12-04","target_ref":"requirement--nist-sp-800-171-r3-03-15-02","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-12-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-12-05","slug":"03-12-05","display_id":"03.12.05","name":"Information Exchange","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve and manage the exchange of CUI between the system and other systems using {{ a_03_12_05_odp_01 }}.\n"},{"id":"b","statement":"Document interface characteristics, security requirements, and responsibilities for each system as part of the exchange agreements.\n"},{"id":"c","statement":"Review and update the exchange agreements {{ a_03_12_05_odp_02 }}."}],"objectives_count":7,"objectives_preview":[{"id":"a.01","statement":"the exchange of CUI between the system and other systems is approved using {{ a_03_12_05_odp_01 }}.\n"},{"id":"a.02","statement":"the exchange of CUI between the system and other systems is managed using {{ a_03_12_05_odp_01 }}.\n"},{"id":"b.01","statement":"interface characteristics for each system are documented as part of the exchange agreements.\n"},{"id":"b.02","statement":"security requirements for each system are documented as part of the exchange agreements.\n"},{"id":"b.03","statement":"responsibilities for each system are documented as part of the exchange agreements.\n"},{"id":"c.01","statement":"exchange agreements are reviewed {{ a_03_12_05_odp_02 }} ."}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-12-05_to_nist-sp-800-53-r5-ca-3","source_ref":"requirement--nist-sp-800-171-r3-03-12-05","target_ref":"requirement--nist-sp-800-53-r5-ca-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-12-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-01","slug":"03-13-01","display_id":"03.13.01","name":"Boundary Protection","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor and control communications at external managed interfaces to the system and key internal managed interfaces within the system.\n"},{"id":"b","statement":"Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.\n"},{"id":"c","statement":"Connect to external systems only through managed interfaces that consist of boundary protection devices arranged in accordance with an organizational security architecture.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"communications at external managed interfaces to the system are monitored."},{"id":"a.02","statement":"communications at external managed interfaces to the system are controlled."},{"id":"a.03","statement":"communications at key internal managed interfaces within the system are monitored.\n"},{"id":"a.04","statement":"communications at key internal managed interfaces within the system are controlled.\n"},{"id":"b","statement":"subnetworks are implemented for publicly accessible system components that are physically or logically separated from internal networks.\n"},{"id":"c","statement":"external system connections are only made through managed interfaces that consist of boundary protection devices arranged in accordance with an organizational security architecture.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-01_to_nist-sp-800-53-r5-sc-7","source_ref":"requirement--nist-sp-800-171-r3-03-13-01","target_ref":"requirement--nist-sp-800-53-r5-sc-7","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-02","slug":"03-13-02","display_id":"03.13.02","name":"03.13.02","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-03","slug":"03-13-03","display_id":"03.13.03","name":"03.13.03","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-01","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-01","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-02","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-02","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-03","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-03","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-04","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-04","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-05","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-05","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-06","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-06","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-03_to_nist-sp-800-171-r3-03-01-07","source_ref":"requirement--nist-sp-800-171-r3-03-13-03","target_ref":"requirement--nist-sp-800-171-r3-03-01-07","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-04","slug":"03-13-04","display_id":"03.13.04","name":"Information in Shared System Resources","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Prevent unauthorized and unintended information transfer via shared system resources.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"unauthorized information transfer via shared system resources is prevented."},{"id":"02","statement":"unintended information transfer via shared system resources is prevented."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-04_to_nist-sp-800-53-r5-sc-4","source_ref":"requirement--nist-sp-800-171-r3-03-13-04","target_ref":"requirement--nist-sp-800-53-r5-sc-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-05","slug":"03-13-05","display_id":"03.13.05","name":"03.13.05","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-05_to_nist-sp-800-171-r3-03-13-01","source_ref":"requirement--nist-sp-800-171-r3-03-13-05","target_ref":"requirement--nist-sp-800-171-r3-03-13-01","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-06","slug":"03-13-06","display_id":"03.13.06","name":"Network Communications – Deny by Default – Allow by Exception","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Deny network communications traffic by default, and allow network communications traffic by exception.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"network communications traffic is denied by default."},{"id":"02","statement":"network communications traffic is allowed by exception."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-06_to_nist-sp-800-53-r5-sc-7-5","source_ref":"requirement--nist-sp-800-171-r3-03-13-06","target_ref":"requirement--nist-sp-800-53-r5-sc-7-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-07","slug":"03-13-07","display_id":"03.13.07","name":"03.13.07","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-07_to_nist-sp-800-171-r3-03-01-12","source_ref":"requirement--nist-sp-800-171-r3-03-13-07","target_ref":"requirement--nist-sp-800-171-r3-03-01-12","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-07_to_nist-sp-800-171-r3-03-04-02","source_ref":"requirement--nist-sp-800-171-r3-03-13-07","target_ref":"requirement--nist-sp-800-171-r3-03-04-02","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-07_to_nist-sp-800-171-r3-03-04-06","source_ref":"requirement--nist-sp-800-171-r3-03-13-07","target_ref":"requirement--nist-sp-800-171-r3-03-04-06","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-08","slug":"03-13-08","display_id":"03.13.08","name":"Transmission and Storage Confidentiality","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Implement cryptographic mechanisms to prevent the unauthorized disclosure of CUI during transmission and while in storage.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"cryptographic mechanisms are implemented to prevent the unauthorized disclosure of CUI during transmission.\n"},{"id":"02","statement":"cryptographic mechanisms are implemented to prevent the unauthorized disclosure of CUI while in storage.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-08_to_nist-sp-800-53-r5-sc-28","source_ref":"requirement--nist-sp-800-171-r3-03-13-08","target_ref":"requirement--nist-sp-800-53-r5-sc-28","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-08_to_nist-sp-800-53-r5-sc-28-1","source_ref":"requirement--nist-sp-800-171-r3-03-13-08","target_ref":"requirement--nist-sp-800-53-r5-sc-28-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-08_to_nist-sp-800-53-r5-sc-8","source_ref":"requirement--nist-sp-800-171-r3-03-13-08","target_ref":"requirement--nist-sp-800-53-r5-sc-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-13-08_to_nist-sp-800-53-r5-sc-8-1","source_ref":"requirement--nist-sp-800-171-r3-03-13-08","target_ref":"requirement--nist-sp-800-53-r5-sc-8-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[{"id":"mapping--ogrl-cr-01-to-800-171-03-13-08","source_ref":"control--ogrl-cr-01","target_ref":"requirement--nist-sp-800-171-r3-03-13-08","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Modern TLS and storage encryption satisfy SP 800-171 03.13.08 data protection."}],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-09","slug":"03-13-09","display_id":"03.13.09","name":"Network Disconnect","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Terminate the network connection associated with a communications session at the end of the session or after {{ a_03_13_09_odp_01 }} of inactivity.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"the network connection associated with a communications session is terminated at the end of the session or after {{ a_03_13_09_odp_01 }} of inactivity.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-09_to_nist-sp-800-53-r5-sc-10","source_ref":"requirement--nist-sp-800-171-r3-03-13-09","target_ref":"requirement--nist-sp-800-53-r5-sc-10","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-09.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-10","slug":"03-13-10","display_id":"03.13.10","name":"Cryptographic Key Establishment and Management","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Establish and manage cryptographic keys in the system in accordance with the following key management requirements: {{ a_03_13_10_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"01","statement":"cryptographic keys are established in the system in accordance with the following key management requirements: {{ a_03_13_10_odp_01 }}.\n"},{"id":"02","statement":"cryptographic keys are managed in the system in accordance with the following key management requirements: {{ a_03_13_10_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-10_to_nist-sp-800-53-r5-sc-12","source_ref":"requirement--nist-sp-800-171-r3-03-13-10","target_ref":"requirement--nist-sp-800-53-r5-sc-12","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-10.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-11","slug":"03-13-11","display_id":"03.13.11","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Implement the following types of cryptography to protect the confidentiality of CUI: {{ a_03_13_11_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"the following types of cryptography are implemented to protect the confidentiality of CUI: {{ a_03_13_11_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-11_to_nist-sp-800-53-r5-sc-13","source_ref":"requirement--nist-sp-800-171-r3-03-13-11","target_ref":"requirement--nist-sp-800-53-r5-sc-13","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-11.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-12","slug":"03-13-12","display_id":"03.13.12","name":"Collaborative Computing Devices and Applications","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prohibit the remote activation of collaborative computing devices and applications with the following exceptions: {{ a_03_13_12_odp_01 }}.\n"},{"id":"b","statement":"Provide an explicit indication of use to users physically present at the devices.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the remote activation of collaborative computing devices and applications is prohibited with the following exceptions: {{ a_03_13_12_odp_01 }}.\n"},{"id":"b","statement":"an explicit indication of use is provided to users who are physically present at the devices.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-12_to_nist-sp-800-53-r5-sc-15","source_ref":"requirement--nist-sp-800-171-r3-03-13-12","target_ref":"requirement--nist-sp-800-53-r5-sc-15","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-12.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-13","slug":"03-13-13","display_id":"03.13.13","name":"Mobile Code","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Define acceptable mobile code and mobile code technologies."},{"id":"b","statement":"Authorize, monitor, and control the use of mobile code."}],"objectives_count":5,"objectives_preview":[{"id":"b.01","statement":"the use of mobile code is authorized."},{"id":"b.02","statement":"the use of mobile code is monitored."},{"id":"b.03","statement":"the use of mobile code is controlled."},{"id":"a.01","statement":"acceptable mobile code is defined."},{"id":"a.02","statement":"acceptable mobile code technologies are defined."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-13_to_nist-sp-800-53-r5-sc-18","source_ref":"requirement--nist-sp-800-171-r3-03-13-13","target_ref":"requirement--nist-sp-800-53-r5-sc-18","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-13.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-14","slug":"03-13-14","display_id":"03.13.14","name":"03.13.14","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-14.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-15","slug":"03-13-15","display_id":"03.13.15","name":"Session Authenticity","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Protect the authenticity of communications sessions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"the authenticity of communications sessions is protected."}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-15_to_nist-sp-800-53-r5-sc-23","source_ref":"requirement--nist-sp-800-171-r3-03-13-15","target_ref":"requirement--nist-sp-800-53-r5-sc-23","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-15.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-13-16","slug":"03-13-16","display_id":"03.13.16","name":"03.13.16","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-13-16_to_nist-sp-800-171-r3-03-13-08","source_ref":"requirement--nist-sp-800-171-r3-03-13-16","target_ref":"requirement--nist-sp-800-171-r3-03-13-08","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-13-16.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-01","slug":"03-14-01","display_id":"03.14.01","name":"Flaw Remediation","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify, report, and correct system flaws."},{"id":"b","statement":"Install security-relevant software and firmware updates within {{ a_03_14_01_odp_01 }} of the release of the updates.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.01","statement":"system flaws are identified."},{"id":"a.02","statement":"system flaws are reported."},{"id":"a.03","statement":"system flaws are corrected."},{"id":"b.01","statement":"security-relevant software updates are installed within {{ a_03_14_01_odp_01 }} of the release of the updates.\n"},{"id":"b.02","statement":"security-relevant firmware updates are installed within {{ a_03_14_01_odp_02 }} of the release of the updates.\n"}],"params_count":2,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-01_to_nist-sp-800-53-r5-si-2","source_ref":"requirement--nist-sp-800-171-r3-03-14-01","target_ref":"requirement--nist-sp-800-53-r5-si-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-02","slug":"03-14-02","display_id":"03.14.02","name":"Malicious Code Protection","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code.\n"},{"id":"b","statement":"Update malicious code protection mechanisms as new releases are available in accordance with configuration management policies and procedures.\n"},{"id":"c","statement":"Configure malicious code protection mechanisms to:"},{"id":"c.01","statement":"Perform scans of the system {{ a_03_14_02_odp_01 }} and real-time scans of files from external sources at endpoints or system entry and exit points as the files are downloaded, opened, or executed; and\n"},{"id":"c.02","statement":"Block malicious code, quarantine malicious code, or take other mitigation actions in response to malicious code detection.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code.\n"},{"id":"a.02","statement":"malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code.\n"},{"id":"b","statement":"malicious code protection mechanisms are updated as new releases are available in accordance with configuration management policy and procedures.\n"},{"id":"c.01.01","statement":"malicious code protection mechanisms are configured to perform scans of the system {{ a_03_14_02_odp_01 }}.\n"},{"id":"c.02","statement":"malicious code protection mechanisms are configured to block malicious code, quarantine malicious code, or take other actions in response to malicious code detection.\n"},{"id":"c.01.02","statement":"malicious code protection mechanisms are configured to perform real-time scans of files from external sources at endpoints or system entry and exit points as the files are downloaded, opened, or executed.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-02_to_nist-sp-800-53-r5-si-3","source_ref":"requirement--nist-sp-800-171-r3-03-14-02","target_ref":"requirement--nist-sp-800-53-r5-si-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-03","slug":"03-14-03","display_id":"03.14.03","name":"Security Alerts, Advisories, and Directives","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Receive system security alerts, advisories, and directives from external organizations on an ongoing basis.\n"},{"id":"b","statement":"Generate and disseminate internal system security alerts, advisories, and directives, as necessary.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"system security alerts, advisories, and directives from external organizations are received on an ongoing basis.\n"},{"id":"b.01","statement":"internal security alerts, advisories, and directives are generated, as necessary.\n"},{"id":"b.02","statement":"internal security alerts, advisories, and directives are disseminated, as necessary.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-03_to_nist-sp-800-53-r5-si-5","source_ref":"requirement--nist-sp-800-171-r3-03-14-03","target_ref":"requirement--nist-sp-800-53-r5-si-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-04","slug":"03-14-04","display_id":"03.14.04","name":"03.14.04","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-04_to_nist-sp-800-171-r3-03-14-02","source_ref":"requirement--nist-sp-800-171-r3-03-14-04","target_ref":"requirement--nist-sp-800-171-r3-03-14-02","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-04.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-05","slug":"03-14-05","display_id":"03.14.05","name":"03.14.05","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-05_to_nist-sp-800-171-r3-03-14-02","source_ref":"requirement--nist-sp-800-171-r3-03-14-05","target_ref":"requirement--nist-sp-800-171-r3-03-14-02","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL addressed-by link. NIST records the source requirement as addressed by the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-05.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-06","slug":"03-14-06","display_id":"03.14.06","name":"System Monitoring","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor the system to detect:"},{"id":"a.01","statement":"Attacks and indicators of potential attacks and"},{"id":"a.02","statement":"Unauthorized connections."},{"id":"b","statement":"Identify unauthorized use of the system."},{"id":"c","statement":"Monitor inbound and outbound communications traffic to detect unusual or unauthorized activities or conditions.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a.01.01","statement":"the system is monitored to detect attacks."},{"id":"a.01.02","statement":"the system is monitored to detect indicators of potential attacks."},{"id":"a.02","statement":"the system is monitored to detect unauthorized connections."},{"id":"b","statement":"unauthorized use of the system is identified."},{"id":"c.01","statement":"inbound communications traffic is monitored to detect unusual or unauthorized activities or conditions.\n"},{"id":"c.02","statement":"outbound communications traffic is monitored to detect unusual or unauthorized activities or conditions.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-06_to_nist-sp-800-53-r5-si-4","source_ref":"requirement--nist-sp-800-171-r3-03-14-06","target_ref":"requirement--nist-sp-800-53-r5-si-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-14-06_to_nist-sp-800-53-r5-si-4-4","source_ref":"requirement--nist-sp-800-171-r3-03-14-06","target_ref":"requirement--nist-sp-800-53-r5-si-4-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-06.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-07","slug":"03-14-07","display_id":"03.14.07","name":"03.14.07","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-07_to_nist-sp-800-171-r3-03-14-06","source_ref":"requirement--nist-sp-800-171-r3-03-14-07","target_ref":"requirement--nist-sp-800-171-r3-03-14-06","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-07.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-14-08","slug":"03-14-08","display_id":"03.14.08","name":"Information Management and Retention","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Manage and retain CUI within the system and CUI output from the system in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"01","statement":"CUI within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.\n"},{"id":"02","statement":"CUI within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.\n"},{"id":"03","statement":"CUI output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.\n"},{"id":"04","statement":"CUI output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-14-08_to_nist-sp-800-53-r5-si-12","source_ref":"requirement--nist-sp-800-171-r3-03-14-08","target_ref":"requirement--nist-sp-800-53-r5-si-12","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-14-08.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-15-01","slug":"03-15-01","display_id":"03.15.01","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to organizational personnel or roles the policies and procedures needed to satisfy the security requirements for the protection of CUI.\n"},{"id":"b","statement":"Review and update policies and procedures {{ a_03_15_01_odp_01 }}."}],"objectives_count":6,"objectives_preview":[{"id":"a.01","statement":"policies needed to satisfy the security requirements for the protection of CUI are developed and documented.\n"},{"id":"a.02","statement":"policies needed to satisfy the security requirements for the protection of CUI are disseminated to organizational personnel or roles.\n"},{"id":"a.03","statement":"procedures needed to satisfy the security requirements for the protection of CUI are developed and documented.\n"},{"id":"a.04","statement":"procedures needed to satisfy the security requirements for the protection of CUI are disseminated to organizational personnel or roles.\n"},{"id":"b.01","statement":"policies and procedures are reviewed {{ a_03_15_01_odp_01 }}."},{"id":"b.02","statement":"policies and procedures are updated {{ a_03_15_01_odp_01 }}."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ac-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ac-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-at-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-at-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-au-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-au-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ca-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ca-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-cm-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-cm-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ia-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ia-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ir-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ir-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ma-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ma-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-mp-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-mp-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-pe-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-pe-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-pl-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-pl-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ps-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ps-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-ra-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-ra-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-sa-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-sa-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-sc-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-sc-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-si-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-si-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"},{"id":"mapping--nist-sp-800-171-r3-03-15-01_to_nist-sp-800-53-r5-sr-1","source_ref":"requirement--nist-sp-800-171-r3-03-15-01","target_ref":"requirement--nist-sp-800-53-r5-sr-1","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-15-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-15-02","slug":"03-15-02","display_id":"03.15.02","name":"System Security Plan","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a system security plan that:"},{"id":"a.01","statement":"Defines the constituent system components;"},{"id":"a.02","statement":"Identifies the information types processed, stored, and transmitted by the system;\n"},{"id":"a.03","statement":"Describes specific threats to the system that are of concern to the organization;\n"},{"id":"a.04","statement":"Describes the operational environment for the system and any dependencies on or connections to other systems or system components;\n"},{"id":"a.05","statement":"Provides an overview of the security requirements for the system;"},{"id":"a.06","statement":"Describes the safeguards in place or planned for meeting the security requirements;\n"},{"id":"a.07","statement":"Identifies individuals that fulfill system roles and responsibilities; and"},{"id":"a.08","statement":"Includes other relevant information necessary for the protection of CUI."},{"id":"b","statement":"Review and update the system security plan {{ a_03_15_02_odp_01 }}."},{"id":"c","statement":"Protect the system security plan from unauthorized disclosure."}],"objectives_count":11,"objectives_preview":[{"id":"a.01","statement":"a system security plan that defines the constituent system components is developed.\n"},{"id":"a.02","statement":"a system security plan that identifies the information types processed, stored, and transmitted by the system is developed.\n"},{"id":"a.03","statement":"a system security plan that describes specific threats to the system that are of concern to the organization is developed.\n"},{"id":"a.04","statement":"a system security plan that describes the operational environment for the system and any dependencies on or connections to other systems or system components is developed.\n"},{"id":"a.05","statement":"a system security plan that provides an overview of the security requirements for the system is developed.\n"},{"id":"a.06","statement":"a system security plan that describes the safeguards in place or planned for meeting the security requirements is developed.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-15-02_to_nist-sp-800-53-r5-pl-2","source_ref":"requirement--nist-sp-800-171-r3-03-15-02","target_ref":"requirement--nist-sp-800-53-r5-pl-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-15-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-15-03","slug":"03-15-03","display_id":"03.15.03","name":"Rules of Behavior","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish rules that describe the responsibilities and expected behavior for system usage and protecting CUI.\n"},{"id":"b","statement":"Provide rules to individuals who require access to the system."},{"id":"c","statement":"Receive a documented acknowledgement from individuals indicating that they have read, understand, and agree to abide by the rules of behavior before authorizing access to CUI and the system.\n"},{"id":"d","statement":"Review and update the rules of behavior {{ a_03_15_03_odp_01 }}."}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"rules that describe responsibilities and expected behavior for system usage and protecting CUI are established.\n"},{"id":"b","statement":"rules are provided to individuals who require access to the system."},{"id":"c","statement":"a documented acknowledgement from individuals indicating that they have read, understand, and agree to abide by the rules of behavior is received before authorizing access to CUI and the system.\n"},{"id":"d.02","statement":"the rules of behavior are updated {{ a_03_15_03_odp_01 }} ."},{"id":"d.01","statement":"the rules of behavior are reviewed {{ a_03_15_03_odp_01 }}."}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-15-03_to_nist-sp-800-53-r5-pl-4","source_ref":"requirement--nist-sp-800-171-r3-03-15-03","target_ref":"requirement--nist-sp-800-53-r5-pl-4","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-15-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-16-01","slug":"03-16-01","display_id":"03.16.01","name":"Security Engineering Principles","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Apply the following systems security engineering principles to the development or modification of the system and system components: {{ a_03_16_01_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"a","statement":"{{ a_03_16_01_odp_01 }} are applied to the development or modification of the system and system components.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-16-01_to_nist-sp-800-53-r5-sa-8","source_ref":"requirement--nist-sp-800-171-r3-03-16-01","target_ref":"requirement--nist-sp-800-53-r5-sa-8","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-16-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-16-02","slug":"03-16-02","display_id":"03.16.02","name":"Unsupported System Components","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer.\n"},{"id":"b","statement":"Provide options for risk mitigation or alternative sources for continued support for unsupported components that cannot be replaced.\n"}],"objectives_count":2,"objectives_preview":[{"id":"b","statement":"options for risk mitigation or alternative sources for continued support for unsupported components that cannot be replaced are provided.\n"},{"id":"a","statement":"system components are replaced when support for the components is no longer available from the developer, vendor, or manufacturer.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-16-02_to_nist-sp-800-53-r5-sa-22","source_ref":"requirement--nist-sp-800-171-r3-03-16-02","target_ref":"requirement--nist-sp-800-53-r5-sa-22","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-16-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-16-03","slug":"03-16-03","display_id":"03.16.03","name":"External System Services","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require the providers of external system services used for the processing, storage, or transmission of CUI to comply with the following security requirements: {{ a_03_16_03_odp_01 }}.\n"},{"id":"b","statement":"Define and document user roles and responsibilities with regard to external system services, including shared responsibilities with external service providers.\n"},{"id":"c","statement":"Implement processes, methods, and techniques to monitor security requirement compliance by external service providers on an ongoing basis.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the providers of external system services used for the processing, storage, or transmission of CUI comply with the following security requirements: {{ a_03_16_03_odp_01 }}.\n"},{"id":"c","statement":"processes, methods, and techniques to monitor security requirement compliance by external service providers on an ongoing basis are implemented.\n"},{"id":"b","statement":"user roles and responsibilities with regard to external system services, including shared responsibilities with external service providers, are defined and documented.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-16-03_to_nist-sp-800-53-r5-sa-9","source_ref":"requirement--nist-sp-800-171-r3-03-16-03","target_ref":"requirement--nist-sp-800-53-r5-sa-9","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-16-03.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-17-01","slug":"03-17-01","display_id":"03.17.01","name":"Supply Chain Risk Management Plan","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a plan for managing supply chain risks associated with the research and development, design, manufacturing, acquisition, delivery, integration, operations, maintenance, and disposal of the system, system components, or system services.\n"},{"id":"b","statement":"Review and update the supply chain risk management plan {{ a_03_17_01_odp_01 }}."},{"id":"c","statement":"Protect the supply chain risk management plan from unauthorized disclosure."}],"objectives_count":13,"objectives_preview":[{"id":"a.01","statement":"a plan for managing supply chain risks is developed."},{"id":"a.02","statement":"the SCRM plan addresses risks associated with the research and development of the system, system components, or system services.\n"},{"id":"a.03","statement":"the SCRM plan addresses risks associated with the design of the system, system components, or system services.\n"},{"id":"a.04","statement":"the SCRM plan addresses risks associated with the manufacturing of the system, system components, or system services.\n"},{"id":"a.05","statement":"the SCRM plan addresses risks associated with the acquisition of the system, system components, or system services.\n"},{"id":"a.06","statement":"the SCRM plan addresses risks associated with the delivery of the system, system components, or system services.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-17-01_to_nist-sp-800-53-r5-sr-2","source_ref":"requirement--nist-sp-800-171-r3-03-17-01","target_ref":"requirement--nist-sp-800-53-r5-sr-2","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-17-01.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-17-02","slug":"03-17-02","display_id":"03.17.02","name":"Acquisition Strategies, Tools, and Methods","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":"Develop and implement acquisition strategies, contract tools, and procurement methods to identify, protect against, and mitigate supply chain risks.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"01","statement":"acquisition strategies, contract tools, and procurement methods are developed to identify supply chain risks.\n"},{"id":"02","statement":"acquisition strategies, contract tools, and procurement methods are developed to protect against supply chain risks.\n"},{"id":"03","statement":"acquisition strategies, contract tools, and procurement methods are developed to mitigate supply chain risks.\n"},{"id":"04","statement":"acquisition strategies, contract tools, and procurement methods are implemented to identify supply chain risks.\n"},{"id":"05","statement":"acquisition strategies, contract tools, and procurement methods are implemented to protect against supply chain risks.\n"},{"id":"06","statement":"acquisition strategies, contract tools, and procurement methods are implemented to mitigate supply chain risks.\n"}],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-17-02_to_nist-sp-800-53-r5-sr-5","source_ref":"requirement--nist-sp-800-171-r3-03-17-02","target_ref":"requirement--nist-sp-800-53-r5-sr-5","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-17-02.yaml"},{"id":"requirement--nist-sp-800-171-r3-03-17-03","slug":"03-17-03","display_id":"03.17.03","name":"Supply Chain Requirements and Processes","framework_id":"framework--nist-sp-800-171-r3","framework_slug":"nist-sp-800-171-r3","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish a process for identifying and addressing weaknesses or deficiencies in the supply chain elements and processes.\n"},{"id":"b","statement":"Enforce the following security requirements to protect against supply chain risks to the system, system components, or system services and to limit the harm or consequences from supply chain-related events: {{ a_03_17_03_odp_01 }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a.01","statement":"a process for identifying weaknesses or deficiencies in the supply chain elements and processes is established.\n"},{"id":"a.02","statement":"a process for addressing weaknesses or deficiencies in the supply chain elements and processes is established.\n"},{"id":"b","statement":"the following security requirements are enforced to protect against supply chain risks to the system, system components, or system services and to limit the harm or consequences of supply chain-related events: {{ a_03_17_03_odp_01 }}.\n"}],"params_count":1,"mappings":[{"id":"mapping--nist-sp-800-171-r3-03-17-03_to_nist-sp-800-53-r5-sr-3","source_ref":"requirement--nist-sp-800-171-r3-03-17-03","target_ref":"requirement--nist-sp-800-53-r5-sr-3","relationship":"intersects-with","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL reference link. NIST cites this SP 800-53 control from the requirement. The set relationship is unreviewed.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-171-r3/03-17-03.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-1","slug":"ac-1","display_id":"AC-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ac_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ac_01_odp_03 }} access control policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the access control policy and the associated access controls;\n"},{"id":"b","statement":"Designate an {{ ac_01_odp_04 }} to manage the development, documentation, and dissemination of the access control policy and procedures; and\n"},{"id":"c","statement":"Review and update the current access control:"},{"id":"c.1","statement":"Policy {{ ac_01_odp_05 }} and following {{ ac_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ac_01_odp_07 }} and following {{ ac_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"an access control policy is developed and documented;"},{"id":"a-2","statement":"the access control policy is disseminated to {{ ac_01_odp_01 }};"},{"id":"a-3","statement":"access control procedures to facilitate the implementation of the access control policy and associated controls are developed and documented;\n"},{"id":"a-4","statement":"the access control procedures are disseminated to {{ ac_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ ac_01_odp_03 }} access control policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ ac_01_odp_03 }} access control policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2","slug":"ac-2","display_id":"AC-2","name":"Account Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Define and document the types of accounts allowed and specifically prohibited for use within the system;\n"},{"id":"b","statement":"Assign account managers;"},{"id":"c","statement":"Require {{ ac_02_odp_01 }} for group and role membership;"},{"id":"d","statement":"Specify:"},{"id":"d.1","statement":"Authorized users of the system;"},{"id":"d.2","statement":"Group and role membership; and"},{"id":"d.3","statement":"Access authorizations (i.e., privileges) and {{ ac_02_odp_02 }} for each account;\n"},{"id":"e","statement":"Require approvals by {{ ac_02_odp_03 }} for requests to create accounts;"},{"id":"f","statement":"Create, enable, modify, disable, and remove accounts in accordance with {{ ac_02_odp_04 }};\n"},{"id":"g","statement":"Monitor the use of accounts;"},{"id":"h","statement":"Notify account managers and {{ ac_02_odp_05 }} within:"},{"id":"h.1","statement":"{{ ac_02_odp_06 }} when accounts are no longer required;"},{"id":"h.2","statement":"{{ ac_02_odp_07 }} when users are terminated or transferred; and"},{"id":"h.3","statement":"{{ ac_02_odp_08 }} when system usage or need-to-know changes for an individual;"},{"id":"i","statement":"Authorize access to the system based on:"},{"id":"i.1","statement":"A valid access authorization;"},{"id":"i.2","statement":"Intended system usage; and"},{"id":"i.3","statement":"{{ ac_02_odp_09 }};"},{"id":"j","statement":"Review accounts for compliance with account management requirements {{ ac_02_odp_10 }};\n"},{"id":"k","statement":"Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and\n"},{"id":"l","statement":"Align account management processes with personnel termination and transfer processes.\n"}],"objectives_count":26,"objectives_preview":[{"id":"a-1","statement":"account types allowed for use within the system are defined and documented;"},{"id":"a-2","statement":"account types specifically prohibited for use within the system are defined and documented;\n"},{"id":"b","statement":"account managers are assigned;"},{"id":"c","statement":"{{ ac_02_odp_01 }} for group and role membership are required;"},{"id":"d.1","statement":"authorized users of the system are specified;"},{"id":"d.2","statement":"group and role membership are specified;"}],"params_count":10,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-01-to-800-53-ac-2-e","source_ref":"control--ogrl-ac-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_odp_03":"approver_role"},"summary":"Pre-provisioning account approval directly satisfies NIST AC-2(e)."},{"id":"mapping--ogrl-ac-01-to-800-53-ac-2-h-2","source_ref":"control--ogrl-ac-01","target_ref":"requirement--nist-sp-800-53-r5-ac-2#h.2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_odp_07":"deprovision_sla"},"summary":"Timely termination deprovisioning satisfies NIST AC-2(h.2) notification and suspension timing.\n"},{"id":"mapping--ogrl-ac-02-to-800-53-ac-2-j","source_ref":"control--ogrl-ac-02","target_ref":"requirement--nist-sp-800-53-r5-ac-2#j","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_odp_10":"review_cadence"},"summary":"Periodic user access review directly satisfies NIST AC-2(j) account compliance reviews.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-1","slug":"ac-2-1","display_id":"AC-2(1)","name":"Automated System Account Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Support the management of system accounts using {{ ac_02_01_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(01)","statement":"the management of system accounts is supported using {{ ac_02_01_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-2","slug":"ac-2-2","display_id":"AC-2(2)","name":"Automated Temporary and Emergency Account Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Automatically {{ ac_02_02_odp_01 }} temporary and emergency accounts after {{ ac_02_02_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(02)","statement":"temporary and emergency accounts are automatically {{ ac_02_02_odp_01 }} after {{ ac_02_02_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-09-to-800-53-ac-2-2","source_ref":"control--ogrl-ac-09","target_ref":"requirement--nist-sp-800-53-r5-ac-2-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_02_odp_01":"temporary_account_action","ac_02_02_odp_02":"temporary_account_lifetime"},"summary":"Temporary and emergency accounts are automatically disabled or removed after a defined period.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-3","slug":"ac-2-3","display_id":"AC-2(3)","name":"Disable Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Disable accounts within {{ ac_02_03_odp_01 }} when the accounts:","citation":null,"parts":[{"id":"a","statement":"Have expired;"},{"id":"b","statement":"Are no longer associated with a user or individual;"},{"id":"c","statement":"Are in violation of organizational policy; or"},{"id":"d","statement":"Have been inactive for {{ ac_02_03_odp_02 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"accounts are disabled within {{ ac_02_03_odp_01 }} when the accounts have expired;\n"},{"id":"b","statement":"accounts are disabled within {{ ac_02_03_odp_01 }} when the accounts are no longer associated with a user or individual;\n"},{"id":"c","statement":"accounts are disabled within {{ ac_02_03_odp_01 }} when the accounts are in violation of organizational policy;\n"},{"id":"d","statement":"accounts are disabled within {{ ac_02_03_odp_01 }} when the accounts have been inactive for {{ ac_02_03_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-09-to-800-53-ac-2-3","source_ref":"control--ogrl-ac-09","target_ref":"requirement--nist-sp-800-53-r5-ac-2-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_02_03_odp_01":"disable_window","ac_02_03_odp_02":"inactivity_period"},"summary":"Disabling expired, orphaned, non-compliant, and inactive accounts within a defined window covers all of AC-2(3).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-4","slug":"ac-2-4","display_id":"AC-2(4)","name":"Automated Audit Actions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Automatically audit account creation, modification, enabling, disabling, and removal actions.\n","citation":null,"parts":[],"objectives_count":5,"objectives_preview":[{"id":"ac-02(04).ac-02(04)[01]","statement":"account creation is automatically audited;"},{"id":"ac-02(04).ac-02(04)[02]","statement":"account modification is automatically audited;"},{"id":"ac-02(04).ac-02(04)[03]","statement":"account enabling is automatically audited;"},{"id":"ac-02(04).ac-02(04)[04]","statement":"account disabling is automatically audited;"},{"id":"ac-02(04).ac-02(04)[05]","statement":"account removal actions are automatically audited."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-5","slug":"ac-2-5","display_id":"AC-2(5)","name":"Inactivity Logout","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that users log out when {{ ac_02_05_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(05)","statement":"users are required to log out when {{ ac_02_05_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-6","slug":"ac-2-6","display_id":"AC-2(6)","name":"Dynamic Privilege Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ ac_02_06_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(06)","statement":"{{ ac_02_06_odp }} are implemented."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-7","slug":"ac-2-7","display_id":"AC-2(7)","name":"Privileged User Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish and administer privileged user accounts in accordance with {{ ac_02_07_odp }};\n"},{"id":"b","statement":"Monitor privileged role or attribute assignments;"},{"id":"c","statement":"Monitor changes to roles or attributes; and"},{"id":"d","statement":"Revoke access when privileged role or attribute assignments are no longer appropriate.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"privileged user accounts are established and administered in accordance with {{ ac_02_07_odp }};\n"},{"id":"b","statement":"privileged role or attribute assignments are monitored;"},{"id":"c","statement":"changes to roles or attributes are monitored;"},{"id":"d","statement":"access is revoked when privileged role or attribute assignments are no longer appropriate.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-07-to-800-53-ac-2-7","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-2-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Role-based privileged accounts, alerting on privileged assignments and role changes, and removal of unapproved privileges cover AC-2(7).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-8","slug":"ac-2-8","display_id":"AC-2(8)","name":"Dynamic Account Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Create, activate, manage, and deactivate {{ ac_02_08_odp }} dynamically.","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ac-02(08).ac-02(08)[01]","statement":"{{ ac_02_08_odp }} are created dynamically;"},{"id":"ac-02(08).ac-02(08)[02]","statement":"{{ ac_02_08_odp }} are activated dynamically;"},{"id":"ac-02(08).ac-02(08)[03]","statement":"{{ ac_02_08_odp }} are managed dynamically;"},{"id":"ac-02(08).ac-02(08)[04]","statement":"{{ ac_02_08_odp }} are deactivated dynamically."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-9","slug":"ac-2-9","display_id":"AC-2(9)","name":"Restrictions on Use of Shared and Group Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Only permit the use of shared and group accounts that meet {{ ac_02_09_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(09)","statement":"the use of shared and group accounts is only permitted if {{ ac_02_09_odp }} are met.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-10","slug":"ac-2-10","display_id":"AC-2(10)","name":"Shared and Group Account Credential Change","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-2-10_to_nist-sp-800-53-r5-ac-2_part_k","source_ref":"requirement--nist-sp-800-53-r5-ac-2-10","target_ref":"requirement--nist-sp-800-53-r5-ac-2#k","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-11","slug":"ac-2-11","display_id":"AC-2(11)","name":"Usage Conditions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce {{ ac_02_11_odp_01 }} for {{ ac_02_11_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(11)","statement":"{{ ac_02_11_odp_01 }} for {{ ac_02_11_odp_02 }} are enforced."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-12","slug":"ac-2-12","display_id":"AC-2(12)","name":"Account Monitoring for Atypical Usage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor system accounts for {{ ac_02_12_odp_01 }} ; and"},{"id":"b","statement":"Report atypical usage of system accounts to {{ ac_02_12_odp_02 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"system accounts are monitored for {{ ac_02_12_odp_01 }};"},{"id":"b","statement":"atypical usage of system accounts is reported to {{ ac_02_12_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-2-13","slug":"ac-2-13","display_id":"AC-2(13)","name":"Disable Accounts for High-risk Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Disable accounts of individuals within {{ ac_02_13_odp_01 }} of discovery of {{ ac_02_13_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-02(13)","statement":"accounts of individuals are disabled within {{ ac_02_13_odp_01 }} of discovery of {{ ac_02_13_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-2-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3","slug":"ac-3","display_id":"AC-3","name":"Access Enforcement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-03","statement":"approved authorizations for logical access to information and system resources are enforced in accordance with applicable access control policies.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-03-to-800-53-ac-3","source_ref":"control--ogrl-ac-03","target_ref":"requirement--nist-sp-800-53-r5-ac-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Role-based access control enforces approved logical access authorizations per AC-3.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-1","slug":"ac-3-1","display_id":"AC-3(1)","name":"Restricted Access to Privileged Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-3-1_to_nist-sp-800-53-r5-ac-6","source_ref":"requirement--nist-sp-800-53-r5-ac-3-1","target_ref":"requirement--nist-sp-800-53-r5-ac-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-2","slug":"ac-3-2","display_id":"AC-3(2)","name":"Dual Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce dual authorization for {{ ac_03_02_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-03(02)","statement":"dual authorization is enforced for {{ ac_03_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-3","slug":"ac-3-3","display_id":"AC-3(3)","name":"Mandatory Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce {{ ac_3_3_prm_1 }} over the set of covered subjects and objects specified in the policy, and where the policy:\n","citation":null,"parts":[{"id":"a","statement":"Is uniformly enforced across the covered subjects and objects within the system;"},{"id":"b","statement":"Specifies that a subject that has been granted access to information is constrained from doing any of the following;\n"},{"id":"b.1","statement":"Passing the information to unauthorized subjects or objects;"},{"id":"b.2","statement":"Granting its privileges to other subjects;"},{"id":"b.3","statement":"Changing one or more security attributes (specified by the policy) on subjects, objects, the system, or system components;\n"},{"id":"b.4","statement":"Choosing the security attributes and attribute values (specified by the policy) to be associated with newly created or modified objects; and\n"},{"id":"b.5","statement":"Changing the rules governing access control; and"},{"id":"c","statement":"Specifies that {{ ac_03_03_odp_03 }} may explicitly be granted {{ ac_03_03_odp_04 }} such that they are not limited by any defined subset (or all) of the above constraints.\n"}],"objectives_count":10,"objectives_preview":[{"id":"ac-03(03).ac-03(03)[01]","statement":"{{ ac_03_03_odp_01 }} is enforced over the set of covered subjects specified in the policy;\n"},{"id":"ac-03(03).ac-03(03)[02]","statement":"{{ ac_03_03_odp_02 }} is enforced over the set of covered objects specified in the policy;\n"},{"id":"a-1","statement":"{{ ac_03_03_odp_01 }} is uniformly enforced across the covered subjects within the system;\n"},{"id":"a-2","statement":"{{ ac_03_03_odp_02 }} is uniformly enforced across the covered objects within the system;\n"},{"id":"b.1","statement":"{{ ac_03_03_odp_01 }} and {{ ac_03_03_odp_02 }} specifying that a subject that has been granted access to information is constrained from passing the information to unauthorized subjects or objects are enforced;\n"},{"id":"b.2","statement":"{{ ac_03_03_odp_01 }} and {{ ac_03_03_odp_02 }} specifying that a subject that has been granted access to information is constrained from granting its privileges to other subjects are enforced;\n"}],"params_count":5,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-4","slug":"ac-3-4","display_id":"AC-3(4)","name":"Discretionary Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce {{ ac_3_4_prm_1 }} over the set of covered subjects and objects specified in the policy, and where the policy specifies that a subject that has been granted access to information can do one or more of the following:\n","citation":null,"parts":[{"id":"a","statement":"Pass the information to any other subjects or objects;"},{"id":"b","statement":"Grant its privileges to other subjects;"},{"id":"c","statement":"Change security attributes on subjects, objects, the system, or the system’s components;\n"},{"id":"d","statement":"Choose the security attributes to be associated with newly created or revised objects; or\n"},{"id":"e","statement":"Change the rules governing access control."}],"objectives_count":7,"objectives_preview":[{"id":"ac-03(04).ac-03(04)[01]","statement":"{{ ac_03_04_odp_01 }} is enforced over the set of covered subjects specified in the policy;\n"},{"id":"ac-03(04).ac-03(04)[02]","statement":"{{ ac_03_04_odp_02 }} is enforced over the set of covered objects specified in the policy;\n"},{"id":"a","statement":"{{ ac_03_04_odp_01 }} and {{ ac_03_04_odp_02 }} are enforced where the policy specifies that a subject that has been granted access to information can pass the information to any other subjects or objects;\n"},{"id":"b","statement":"{{ ac_03_04_odp_01 }} and {{ ac_03_04_odp_02 }} are enforced where the policy specifies that a subject that has been granted access to information can grant its privileges to other subjects;\n"},{"id":"c","statement":"{{ ac_03_04_odp_01 }} and {{ ac_03_04_odp_02 }} are enforced where the policy specifies that a subject that has been granted access to information can change security attributes on subjects, objects, the system, or the system’s components;\n"},{"id":"d","statement":"{{ ac_03_04_odp_01 }} and {{ ac_03_04_odp_02 }} are enforced where the policy specifies that a subject that has been granted access to information can choose the security attributes to be associated with newly created or revised objects;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-5","slug":"ac-3-5","display_id":"AC-3(5)","name":"Security-relevant Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent access to {{ ac_03_05_odp }} except during secure, non-operable system states.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-03(05)","statement":"access to {{ ac_03_05_odp }} is prevented except during secure, non-operable system states.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-6","slug":"ac-3-6","display_id":"AC-3(6)","name":"Protection of User and System Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-3-6_to_nist-sp-800-53-r5-mp-4","source_ref":"requirement--nist-sp-800-53-r5-ac-3-6","target_ref":"requirement--nist-sp-800-53-r5-mp-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-ac-3-6_to_nist-sp-800-53-r5-sc-28","source_ref":"requirement--nist-sp-800-53-r5-ac-3-6","target_ref":"requirement--nist-sp-800-53-r5-sc-28","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-7","slug":"ac-3-7","display_id":"AC-3(7)","name":"Role-based Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce a role-based access control policy over defined subjects and objects and control access based upon {{ ac_3_7_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"ac-03(07).ac-03(07)[01]","statement":"a role-based access control policy is enforced over defined subjects;"},{"id":"ac-03(07).ac-03(07)[02]","statement":"a role-based access control policy is enforced over defined objects;"},{"id":"ac-03(07).ac-03(07)[03]","statement":"access is controlled based on {{ ac_03_07_odp_01 }} and {{ ac_03_07_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-8","slug":"ac-3-8","display_id":"AC-3(8)","name":"Revocation of Access Authorizations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on {{ ac_03_08_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-03(08).ac-03(08)[01]","statement":"revocation of access authorizations is enforced, resulting from changes to the security attributes of subjects based on {{ ac_03_08_odp }};\n"},{"id":"ac-03(08).ac-03(08)[02]","statement":"revocation of access authorizations is enforced resulting from changes to the security attributes of objects based on {{ ac_03_08_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-9","slug":"ac-3-9","display_id":"AC-3(9)","name":"Controlled Release","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Release information outside of the system only if:","citation":null,"parts":[{"id":"a","statement":"The receiving {{ ac_03_09_odp_01 }} provides {{ ac_03_09_odp_02 }} ; and"},{"id":"b","statement":"{{ ac_03_09_odp_03 }} are used to validate the appropriateness of the information designated for release.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"information is released outside of the system only if the receiving {{ ac_03_09_odp_01 }} provides {{ ac_03_09_odp_02 }};\n"},{"id":"b","statement":"information is released outside of the system only if {{ ac_03_09_odp_03 }} are used to validate the appropriateness of the information designated for release.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-10","slug":"ac-3-10","display_id":"AC-3(10)","name":"Audited Override of Access Control Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ an audited override of automated access control mechanisms under {{ ac_03_10_odp_01 }} by {{ ac_03_10_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-03(10)","statement":"an audited override of automated access control mechanisms is employed under {{ ac_03_10_odp_01 }} by {{ ac_03_10_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-11","slug":"ac-3-11","display_id":"AC-3(11)","name":"Restrict Access to Specific Information Types","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict access to data repositories containing {{ ac_03_11_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-03(11)","statement":"access to data repositories containing {{ ac_03_11_odp }} is restricted."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-12","slug":"ac-3-12","display_id":"AC-3(12)","name":"Assert and Enforce Application Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require applications to assert, as part of the installation process, the access needed to the following system applications and functions: {{ ac_03_12_odp }};\n"},{"id":"b","statement":"Provide an enforcement mechanism to prevent unauthorized access; and"},{"id":"c","statement":"Approve access changes after initial installation of the application."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"as part of the installation process, applications are required to assert the access needed to the following system applications and functions: {{ ac_03_12_odp }};\n"},{"id":"b","statement":"an enforcement mechanism to prevent unauthorized access is provided;"},{"id":"c","statement":"access changes after initial installation of the application are approved."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-13","slug":"ac-3-13","display_id":"AC-3(13)","name":"Attribute-based Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce attribute-based access control policy over defined subjects and objects and control access based upon {{ ac_03_13_odp }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"ac-03(13).ac-03(13)[01]","statement":"the attribute-based access control policy is enforced over defined subjects;"},{"id":"ac-03(13).ac-03(13)[02]","statement":"the attribute-based access control policy is enforced over defined objects;"},{"id":"ac-03(13).ac-03(13)[03]","statement":"access is controlled based on {{ ac_03_13_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-14","slug":"ac-3-14","display_id":"AC-3(14)","name":"Individual Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ ac_03_14_odp_01 }} to enable individuals to have access to the following elements of their personally identifiable information: {{ ac_03_14_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-03(14)","statement":"{{ ac_03_14_odp_01 }} are provided to enable individuals to have access to {{ ac_03_14_odp_02 }} of their personally identifiable information.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-06-to-800-53-ac-3-14","source_ref":"control--ogrl-pr-06","target_ref":"requirement--nist-sp-800-53-r5-ac-3-14","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_03_14_odp_01":"access_request_channels","ac_03_14_odp_02":"access_request_elements"},"summary":"Request channels and defined disclosed elements implement individual access under AC-3(14).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-3-15","slug":"ac-3-15","display_id":"AC-3(15)","name":"Discretionary and Mandatory Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce {{ ac_3_15_prm_1 }} over the set of covered subjects and objects specified in the policy; and\n"},{"id":"b","statement":"Enforce {{ ac_3_15_prm_2 }} over the set of covered subjects and objects specified in the policy.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"{{ ac_03_15_odp_01 }} is enforced over the set of covered subjects specified in the policy;\n"},{"id":"a-2","statement":"{{ ac_03_15_odp_02 }} is enforced over the set of covered objects specified in the policy;\n"},{"id":"b-1","statement":"{{ ac_03_15_odp_03 }} is enforced over the set of covered subjects specified in the policy;\n"},{"id":"b-2","statement":"{{ ac_03_15_odp_04 }} is enforced over the set of covered objects specified in the policy.\n"}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-3-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4","slug":"ac-4","display_id":"AC-4","name":"Information Flow Enforcement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Enforce approved authorizations for controlling the flow of information within the system and between connected systems based on {{ ac_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04","statement":"approved authorizations are enforced for controlling the flow of information within the system and between connected systems based on {{ ac_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-12-to-800-53-ac-4","source_ref":"control--ogrl-ac-12","target_ref":"requirement--nist-sp-800-53-r5-ac-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Tenant isolation enforces one information flow policy within the system; network and inter-system flow controls are outside this control.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-1","slug":"ac-4-1","display_id":"AC-4(1)","name":"Object Security and Privacy Attributes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use {{ ac_4_1_prm_1 }} associated with {{ ac_4_1_prm_2 }} to enforce {{ ac_04_01_odp_09 }} as a basis for flow control decisions.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(01).ac-04(01)[01]","statement":"{{ ac_04_01_odp_01 }} associated with {{ ac_04_01_odp_03 }}, {{ ac_04_01_odp_05 }} , and {{ ac_04_01_odp_07 }} are used to enforce {{ ac_04_01_odp_09 }} as a basis for flow control decisions;\n"},{"id":"ac-04(01).ac-04(01)[02]","statement":"{{ ac_04_01_odp_02 }} associated with {{ ac_04_01_odp_04 }}, {{ ac_04_01_odp_06 }} , and {{ ac_04_01_odp_08 }} are used to enforce {{ ac_04_01_odp_09 }} as a basis for flow control decisions.\n"}],"params_count":11,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-2","slug":"ac-4-2","display_id":"AC-4(2)","name":"Processing Domains","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use protected processing domains to enforce {{ ac_04_02_odp }} as a basis for flow control decisions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(02)","statement":"protected processing domains are used to enforce {{ ac_04_02_odp }} as a basis for flow control decisions.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-3","slug":"ac-4-3","display_id":"AC-4(3)","name":"Dynamic Information Flow Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce {{ ac_04_03_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(03)","statement":"{{ ac_04_03_odp }} are enforced."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-4","slug":"ac-4-4","display_id":"AC-4(4)","name":"Flow Control of Encrypted Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent encrypted information from bypassing {{ ac_04_04_odp_01 }} by {{ ac_04_04_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(04)","statement":"encrypted information is prevented from bypassing {{ ac_04_04_odp_01 }} by {{ ac_04_04_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-5","slug":"ac-4-5","display_id":"AC-4(5)","name":"Embedded Data Types","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce {{ ac_04_05_odp }} on embedding data types within other data types.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(05)","statement":"{{ ac_04_05_odp }} are enforced on embedding data types within other data types."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-6","slug":"ac-4-6","display_id":"AC-4(6)","name":"Metadata","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce information flow control based on {{ ac_04_06_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(06)","statement":"information flow control enforcement is based on {{ ac_04_06_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-7","slug":"ac-4-7","display_id":"AC-4(7)","name":"One-way Flow Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce one-way information flows through hardware-based flow control mechanisms.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(07)","statement":"one-way information flows are enforced through hardware-based flow control mechanisms.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-8","slug":"ac-4-8","display_id":"AC-4(8)","name":"Security and Privacy Policy Filters","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce information flow control using {{ ac_4_8_prm_1 }} as a basis for flow control decisions for {{ ac_4_8_prm_2 }} ; and\n"},{"id":"b","statement":"{{ ac_04_08_odp_05 }} data after a filter processing failure in accordance with {{ ac_4_8_prm_4 }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"information flow control is enforced using {{ ac_04_08_odp_01 }} as a basis for flow control decisions for {{ ac_04_08_odp_03 }};\n"},{"id":"a-2","statement":"information flow control is enforced using {{ ac_04_08_odp_02 }} as a basis for flow control decisions for {{ ac_04_08_odp_04 }};\n"},{"id":"b","statement":"{{ ac_04_08_odp_05 }} data after a filter processing failure in accordance with {{ ac_04_08_odp_06 }};\n\n{{ ac_04_08_odp_05 }} data after a filter processing failure in accordance with {{ ac_04_08_odp_07 }}.\n"}],"params_count":10,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-9","slug":"ac-4-9","display_id":"AC-4(9)","name":"Human Reviews","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce the use of human reviews for {{ ac_04_09_odp_01 }} under the following conditions: {{ ac_04_09_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(09)","statement":"human reviews are used for {{ ac_04_09_odp_01 }} under {{ ac_04_09_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-10","slug":"ac-4-10","display_id":"AC-4(10)","name":"Enable and Disable Security or Privacy Policy Filters","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability for privileged administrators to enable and disable {{ ac_4_10_prm_1 }} under the following conditions: {{ ac_4_10_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(10).ac-04(10)[01]","statement":"capability is provided for privileged administrators to enable and disable {{ ac_04_10_odp_01 }} under {{ ac_04_10_odp_03 }};\n"},{"id":"ac-04(10).ac-04(10)[02]","statement":"capability is provided for privileged administrators to enable and disable {{ ac_04_10_odp_02 }} under {{ ac_04_10_odp_04 }}.\n"}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-11","slug":"ac-4-11","display_id":"AC-4(11)","name":"Configuration of Security or Privacy Policy Filters","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability for privileged administrators to configure {{ ac_4_11_prm_1 }} to support different security or privacy policies.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(11).ac-04(11)[01]","statement":"capability is provided for privileged administrators to configure {{ ac_04_11_odp_01 }} to support different security or privacy policies;\n"},{"id":"ac-04(11).ac-04(11)[02]","statement":"capability is provided for privileged administrators to configure {{ ac_04_11_odp_02 }} to support different security or privacy policies.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-12","slug":"ac-4-12","display_id":"AC-4(12)","name":"Data Type Identifiers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, use {{ ac_04_12_odp }} to validate data essential for information flow decisions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(12)","statement":"when transferring information between different security domains, {{ ac_04_12_odp }} are used to validate data essential for information flow decisions.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-13","slug":"ac-4-13","display_id":"AC-4(13)","name":"Decomposition into Policy-relevant Subcomponents","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, decompose information into {{ ac_04_13_odp }} for submission to policy enforcement mechanisms.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(13)","statement":"when transferring information between different security domains, information is decomposed into {{ ac_04_13_odp }} for submission to policy enforcement mechanisms.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-14","slug":"ac-4-14","display_id":"AC-4(14)","name":"Security or Privacy Policy Filter Constraints","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, implement {{ ac_4_14_prm_1 }} requiring fully enumerated formats that restrict data structure and content.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(14).ac-04(14)[01]","statement":"when transferring information between different security domains, implemented {{ ac_04_14_odp_01 }} require fully enumerated formats that restrict data structure and content;\n"},{"id":"ac-04(14).ac-04(14)[02]","statement":"when transferring information between different security domains, implemented {{ ac_04_14_odp_02 }} require fully enumerated formats that restrict data structure and content.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-15","slug":"ac-4-15","display_id":"AC-4(15)","name":"Detection of Unsanctioned Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, examine the information for the presence of {{ ac_04_15_odp_01 }} and prohibit the transfer of such information in accordance with the {{ ac_4_15_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"ac-04(15).ac-04(15)[01]","statement":"when transferring information between different security domains, information is examined for the presence of {{ ac_04_15_odp_01 }};\n"},{"id":"ac-04(15).ac-04(15)[02]","statement":"when transferring information between different security domains, transfer of {{ ac_04_15_odp_01 }} is prohibited in accordance with the {{ ac_04_15_odp_02 }};\n"},{"id":"ac-04(15).ac-04(15)[03]","statement":"when transferring information between different security domains, transfer of {{ ac_04_15_odp_01 }} is prohibited in accordance with the {{ ac_04_15_odp_03 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-16","slug":"ac-4-16","display_id":"AC-4(16)","name":"Information Transfers on Interconnected Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-4-16_to_nist-sp-800-53-r5-ac-4","source_ref":"requirement--nist-sp-800-53-r5-ac-4-16","target_ref":"requirement--nist-sp-800-53-r5-ac-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-17","slug":"ac-4-17","display_id":"AC-4(17)","name":"Domain Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Uniquely identify and authenticate source and destination points by {{ ac_04_17_odp }} for information transfer.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(17)","statement":"source and destination points are uniquely identified and authenticated by {{ ac_04_17_odp }} for information transfer.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-18","slug":"ac-4-18","display_id":"AC-4(18)","name":"Security Attribute Binding","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-4-18_to_nist-sp-800-53-r5-ac-16","source_ref":"requirement--nist-sp-800-53-r5-ac-4-18","target_ref":"requirement--nist-sp-800-53-r5-ac-16","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-19","slug":"ac-4-19","display_id":"AC-4(19)","name":"Validation of Metadata","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, implement {{ ac_4_19_prm_1 }} on metadata.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(19).ac-04(19)[01]","statement":"when transferring information between different security domains, {{ ac_04_19_odp_01 }} are implemented on metadata;\n"},{"id":"ac-04(19).ac-04(19)[02]","statement":"when transferring information between different security domains, {{ ac_04_19_odp_02 }} are implemented on metadata.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-20","slug":"ac-4-20","display_id":"AC-4(20)","name":"Approved Solutions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ ac_04_20_odp_01 }} to control the flow of {{ ac_04_20_odp_02 }} across security domains.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(20)","statement":"{{ ac_04_20_odp_01 }} are employed to control the flow of {{ ac_04_20_odp_02 }} across security domains.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-21","slug":"ac-4-21","display_id":"AC-4(21)","name":"Physical or Logical Separation of Information Flows","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Separate information flows logically or physically using {{ ac_4_21_prm_1 }} to accomplish {{ ac_04_21_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(21).ac-04(21)[01]","statement":"information flows are separated logically using {{ ac_04_21_odp_01 }} to accomplish {{ ac_04_21_odp_03 }};\n"},{"id":"ac-04(21).ac-04(21)[02]","statement":"information flows are separated physically using {{ ac_04_21_odp_02 }} to accomplish {{ ac_04_21_odp_03 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-22","slug":"ac-4-22","display_id":"AC-4(22)","name":"Access Only","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide access from a single device to computing platforms, applications, or data residing in multiple different security domains, while preventing information flow between the different security domains.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(22)","statement":"access is provided from a single device to computing platforms, applications, or data that reside in multiple different security domains while preventing information flow between the different security domains.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-23","slug":"ac-4-23","display_id":"AC-4(23)","name":"Modify Non-releasable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, modify non-releasable information by implementing {{ ac_04_23_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(23)","statement":"when transferring information between security domains, non-releasable information is modified by implementing {{ ac_04_23_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-24","slug":"ac-4-24","display_id":"AC-4(24)","name":"Internal Normalized Format","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, parse incoming data into an internal normalized format and regenerate the data to be consistent with its intended specification.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(24).ac-04(24)[01]","statement":"when transferring information between different security domains, incoming data is parsed into an internal, normalized format;\n"},{"id":"ac-04(24).ac-04(24)[02]","statement":"when transferring information between different security domains, the data is regenerated to be consistent with its intended specification.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-25","slug":"ac-4-25","display_id":"AC-4(25)","name":"Data Sanitization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, sanitize data to minimize {{ ac_04_25_odp_01 }} in accordance with {{ ac_04_25_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(25)","statement":"when transferring information between different security domains, data is sanitized to minimize {{ ac_04_25_odp_01 }} in accordance with {{ ac_04_25_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-26","slug":"ac-4-26","display_id":"AC-4(26)","name":"Audit Filtering Actions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-04(26).ac-04(26)[01]","statement":"when transferring information between different security domains, content-filtering actions are recorded and audited;\n"},{"id":"ac-04(26).ac-04(26)[02]","statement":"when transferring information between different security domains, results for the information being filtered are recorded and audited.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-26.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-27","slug":"ac-4-27","display_id":"AC-4(27)","name":"Redundant/Independent Filtering Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, implement content filtering solutions that provide redundant and independent filtering mechanisms for each data type.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(27)","statement":"when transferring information between security domains, implemented content filtering solutions provide redundant and independent filtering mechanisms for each data type.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-27.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-28","slug":"ac-4-28","display_id":"AC-4(28)","name":"Linear Filter Pipelines","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, implement a linear content filter pipeline that is enforced with discretionary and mandatory access controls.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(28)","statement":"when transferring information between security domains, a linear content filter pipeline is implemented that is enforced with discretionary and mandatory access controls.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-28.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-29","slug":"ac-4-29","display_id":"AC-4(29)","name":"Filter Orchestration Engines","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, employ content filter orchestration engines to ensure that:\n","citation":null,"parts":[{"id":"a","statement":"Content filtering mechanisms successfully complete execution without errors; and"},{"id":"b","statement":"Content filtering actions occur in the correct order and comply with {{ ac_04_29_odp }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering mechanisms successfully complete execution without errors;\n"},{"id":"b-1","statement":"when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering actions occur in the correct order;\n"},{"id":"b-2","statement":"when transferring information between security domains, content filter orchestration engines are employed to ensure that content-filtering actions comply with {{ ac_04_29_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-29.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-30","slug":"ac-4-30","display_id":"AC-4(30)","name":"Filter Mechanisms Using Multiple Processes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, implement content filtering mechanisms using multiple processes.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(30)","statement":"when transferring information between security domains, content-filtering mechanisms using multiple processes are implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-30.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-31","slug":"ac-4-31","display_id":"AC-4(31)","name":"Failed Content Transfer Prevention","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, prevent the transfer of failed content to the receiving domain.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-04(31)","statement":"when transferring information between different security domains, the transfer of failed content to the receiving domain is prevented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-31.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-4-32","slug":"ac-4-32","display_id":"AC-4(32)","name":"Process Requirements for Information Transfer","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When transferring information between different security domains, the process that transfers information between filter pipelines:\n","citation":null,"parts":[{"id":"a","statement":"Does not filter message content;"},{"id":"b","statement":"Validates filtering metadata;"},{"id":"c","statement":"Ensures the content associated with the filtering metadata has successfully completed filtering; and\n"},{"id":"d","statement":"Transfers the content to the destination filter pipeline."}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"when transferring information between different security domains, the process that transfers information between filter pipelines does not filter message content;\n"},{"id":"b","statement":"when transferring information between different security domains, the process that transfers information between filter pipelines validates filtering metadata;\n"},{"id":"c","statement":"when transferring information between different security domains, the process that transfers information between filter pipelines ensures that the content with the filtering metadata has successfully completed filtering;\n"},{"id":"d","statement":"when transferring information between different security domains, the process that transfers information between filter pipelines transfers the content to the destination filter pipeline.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-4-32.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-5","slug":"ac-5","display_id":"AC-5","name":"Separation of Duties","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify and document {{ ac_05_odp }} ; and"},{"id":"b","statement":"Define system access authorizations to support separation of duties."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ ac_05_odp }} are identified and documented;"},{"id":"b","statement":"system access authorizations to support separation of duties are defined."}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-08-to-800-53-ac-5","source_ref":"control--ogrl-ac-08","target_ref":"requirement--nist-sp-800-53-r5-ac-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_05_odp":"separated_duties"},"summary":"Documenting separated duties and configuring access authorizations to enforce them satisfies both parts of AC-5.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6","slug":"ac-6","display_id":"AC-6","name":"Least Privilege","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06","statement":"the principle of least privilege is employed, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-03-to-800-53-ac-6","source_ref":"control--ogrl-ac-03","target_ref":"requirement--nist-sp-800-53-r5-ac-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege role scoping and just-in-time elevation satisfy NIST AC-6."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-1","slug":"ac-6-1","display_id":"AC-6(1)","name":"Authorize Access to Security Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Authorize access for {{ ac_06_01_odp_01 }} to:","citation":null,"parts":[{"id":"a","statement":"{{ ac_6_1_prm_2 }} ; and"},{"id":"b","statement":"{{ ac_06_01_odp_05 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"access is authorized for {{ ac_06_01_odp_01 }} to {{ ac_06_01_odp_02 }};"},{"id":"a-2","statement":"access is authorized for {{ ac_06_01_odp_01 }} to {{ ac_06_01_odp_03 }};"},{"id":"a-3","statement":"access is authorized for {{ ac_06_01_odp_01 }} to {{ ac_06_01_odp_04 }};"},{"id":"b","statement":"access is authorized for {{ ac_06_01_odp_01 }} to {{ ac_06_01_odp_05 }}."}],"params_count":6,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-1","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_01_odp_01":"privileged_roles"},"summary":"The approved roster explicitly authorizes which individuals may access security functions and security-relevant systems.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-2","slug":"ac-6-2","display_id":"AC-6(2)","name":"Non-privileged Access for Nonsecurity Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that users of system accounts (or roles) with access to {{ ac_06_02_odp }} use non-privileged accounts or roles, when accessing nonsecurity functions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(02)","statement":"users of system accounts (or roles) with access to {{ ac_06_02_odp }} are required to use non-privileged accounts or roles when accessing non-security functions.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-2","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_02_odp":"privileged_scope"},"summary":"Dedicated privileged accounts or elevated roles are not used for routine, non-security work.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-3","slug":"ac-6-3","display_id":"AC-6(3)","name":"Network Access to Privileged Commands","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Authorize network access to {{ ac_06_03_odp_01 }} only for {{ ac_06_03_odp_02 }} and document the rationale for such access in the security plan for the system.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-06(03).ac-06(03)[01]","statement":"network access to {{ ac_06_03_odp_01 }} is authorized only for {{ ac_06_03_odp_02 }};\n"},{"id":"ac-06(03).ac-06(03)[02]","statement":"the rationale for authorizing network access to privileged commands is documented in the security plan for the system.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-4","slug":"ac-6-4","display_id":"AC-6(4)","name":"Separate Processing Domains","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide separate processing domains to enable finer-grained allocation of user privileges.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(04)","statement":"separate processing domains are provided to enable finer-grain allocation of user privileges.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-5","slug":"ac-6-5","display_id":"AC-6(5)","name":"Privileged Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict privileged accounts on the system to {{ ac_06_05_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(05)","statement":"privileged accounts on the system are restricted to {{ ac_06_05_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-5","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_05_odp":"privileged_roles"},"summary":"Privileged accounts are restricted to the defined set of eligible personnel.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-6","slug":"ac-6-6","display_id":"AC-6(6)","name":"Privileged Access by Non-organizational Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit privileged access to the system by non-organizational users.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(06)","statement":"privileged access to the system by non-organizational users is prohibited."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-7","slug":"ac-6-7","display_id":"AC-6(7)","name":"Review of User Privileges","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Review {{ ac_06_07_odp_01 }} the privileges assigned to {{ ac_06_07_odp_02 }} to validate the need for such privileges; and\n"},{"id":"b","statement":"Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"privileges assigned to {{ ac_06_07_odp_02 }} are reviewed {{ ac_06_07_odp_01 }} to validate the need for such privileges;\n"},{"id":"b","statement":"privileges are reassigned or removed, if necessary, to correctly reflect organizational mission and business needs.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-07-to-800-53-ac-6-7","source_ref":"control--ogrl-ac-07","target_ref":"requirement--nist-sp-800-53-r5-ac-6-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_06_07_odp_01":"privileged_review_frequency","ac_06_07_odp_02":"privileged_roles"},"summary":"Periodic reconciliation of privileged assignments validates need and removes unapproved privileges; non-privileged access review is in OGRL-AC-02.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-8","slug":"ac-6-8","display_id":"AC-6(8)","name":"Privilege Levels for Code Execution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent the following software from executing at higher privilege levels than users executing the software: {{ ac_06_08_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(08)","statement":"{{ ac_06_08_odp }} is prevented from executing at higher privilege levels than users executing the software.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-9","slug":"ac-6-9","display_id":"AC-6(9)","name":"Log Use of Privileged Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Log the execution of privileged functions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(09)","statement":"the execution of privileged functions is logged."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-6-10","slug":"ac-6-10","display_id":"AC-6(10)","name":"Prohibit Non-privileged Users from Executing Privileged Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent non-privileged users from executing privileged functions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-06(10)","statement":"non-privileged users are prevented from executing privileged functions."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-6-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-7","slug":"ac-7","display_id":"AC-7","name":"Unsuccessful Logon Attempts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce a limit of {{ ac_07_odp_01 }} consecutive invalid logon attempts by a user during a {{ ac_07_odp_02 }} ; and\n"},{"id":"b","statement":"Automatically {{ ac_07_odp_03 }} when the maximum number of unsuccessful attempts is exceeded.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a limit of {{ ac_07_odp_01 }} consecutive invalid logon attempts by a user during {{ ac_07_odp_02 }} is enforced;\n"},{"id":"b","statement":"automatically {{ ac_07_odp_03 }} when the maximum number of unsuccessful attempts is exceeded.\n"}],"params_count":6,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-14-to-800-53-ac-7","source_ref":"control--ogrl-ac-14","target_ref":"requirement--nist-sp-800-53-r5-ac-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_07_odp_01":"max_failed_attempts","ac_07_odp_02":"failed_attempt_window"},"summary":"A limit on consecutive failed attempts within a window with automatic lockout or delay satisfies AC-7.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-7-1","slug":"ac-7-1","display_id":"AC-7(1)","name":"Automatic Account Lock","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-7-1_to_nist-sp-800-53-r5-ac-7","source_ref":"requirement--nist-sp-800-53-r5-ac-7-1","target_ref":"requirement--nist-sp-800-53-r5-ac-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-7-2","slug":"ac-7-2","display_id":"AC-7(2)","name":"Purge or Wipe Mobile Device","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Purge or wipe information from {{ ac_07_02_odp_01 }} based on {{ ac_07_02_odp_02 }} after {{ ac_07_02_odp_03 }} consecutive, unsuccessful device logon attempts.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-07(02)","statement":"information is purged or wiped from {{ ac_07_02_odp_01 }} based on {{ ac_07_02_odp_02 }} after {{ ac_07_02_odp_03 }} consecutive, unsuccessful device logon attempts.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-7-3","slug":"ac-7-3","display_id":"AC-7(3)","name":"Biometric Attempt Limiting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit the number of unsuccessful biometric logon attempts to {{ ac_07_03_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-07(03)","statement":"unsuccessful biometric logon attempts are limited to {{ ac_07_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-7-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-7-4","slug":"ac-7-4","display_id":"AC-7(4)","name":"Use of Alternate Authentication Factor","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Allow the use of {{ ac_07_04_odp_01 }} that are different from the primary authentication factors after the number of organization-defined consecutive invalid logon attempts have been exceeded; and\n"},{"id":"b","statement":"Enforce a limit of {{ ac_07_04_odp_02 }} consecutive invalid logon attempts through use of the alternative factors by a user during a {{ ac_07_04_odp_03 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ ac_07_04_odp_01 }} that are different from the primary authentication factors are allowed to be used after the number of organization-defined consecutive invalid logon attempts have been exceeded;\n"},{"id":"b","statement":"a limit of {{ ac_07_04_odp_02 }} consecutive invalid logon attempts through the use of the alternative factors by the user during a {{ ac_07_04_odp_03 }} is enforced.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-7-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-8","slug":"ac-8","display_id":"AC-8","name":"System Use Notification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Display {{ ac_08_odp_01 }} to users before granting access to the system that provides privacy and security notices consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and state that:\n"},{"id":"a.1","statement":"Users are accessing a U.S. Government system;"},{"id":"a.2","statement":"System usage may be monitored, recorded, and subject to audit;"},{"id":"a.3","statement":"Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and\n"},{"id":"a.4","statement":"Use of the system indicates consent to monitoring and recording;"},{"id":"b","statement":"Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system; and\n"},{"id":"c","statement":"For publicly accessible systems:"},{"id":"c.1","statement":"Display system use information {{ ac_08_odp_02 }} , before granting further access to the publicly accessible system;\n"},{"id":"c.2","statement":"Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and\n"},{"id":"c.3","statement":"Include a description of the authorized uses of the system."}],"objectives_count":8,"objectives_preview":[{"id":"a.1","statement":"the system use notification states that users are accessing a U.S. Government system;\n"},{"id":"a.2","statement":"the system use notification states that system usage may be monitored, recorded, and subject to audit;\n"},{"id":"a.3","statement":"the system use notification states that unauthorized use of the system is prohibited and subject to criminal and civil penalties; and\n"},{"id":"a.4","statement":"the system use notification states that use of the system indicates consent to monitoring and recording;\n"},{"id":"b","statement":"the notification message or banner is retained on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system;\n"},{"id":"c.1","statement":"for publicly accessible systems, system use information {{ ac_08_odp_02 }} is displayed before granting further access to the publicly accessible system;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-9","slug":"ac-9","display_id":"AC-9","name":"Previous Logon Notification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Notify the user, upon successful logon to the system, of the date and time of the last logon.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-09","statement":"the user is notified, upon successful logon to the system, of the date and time of the last logon.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-9-1","slug":"ac-9-1","display_id":"AC-9(1)","name":"Unsuccessful Logons","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Notify the user, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-09(01)","statement":"the user is notified, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-9-2","slug":"ac-9-2","display_id":"AC-9(2)","name":"Successful and Unsuccessful Logons","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Notify the user, upon successful logon, of the number of {{ ac_09_02_odp_01 }} during {{ ac_09_02_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-09(02)","statement":"the user is notified, upon successful logon, of the number of {{ ac_09_02_odp_01 }} during {{ ac_09_02_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-9-3","slug":"ac-9-3","display_id":"AC-9(3)","name":"Notification of Account Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Notify the user, upon successful logon, of changes to {{ ac_09_03_odp_01 }} during {{ ac_09_03_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-09(03)","statement":"the user is notified, upon successful logon, of changes to {{ ac_09_03_odp_01 }} during {{ ac_09_03_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-9-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-9-4","slug":"ac-9-4","display_id":"AC-9(4)","name":"Additional Logon Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Notify the user, upon successful logon, of the following additional information: {{ ac_09_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-09(04)","statement":"the user is notified, upon successful logon, of {{ ac_09_04_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-9-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-10","slug":"ac-10","display_id":"AC-10","name":"Concurrent Session Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Limit the number of concurrent sessions for each {{ ac_10_odp_01 }} to {{ ac_10_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the number of concurrent sessions for each {{ ac_10_odp_01 }} is limited to {{ ac_10_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-11","slug":"ac-11","display_id":"AC-11","name":"Device Lock","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prevent further access to the system by {{ ac_11_odp_01 }} ; and"},{"id":"b","statement":"Retain the device lock until the user reestablishes access using established identification and authentication procedures.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"further access to the system is prevented by {{ ac_11_odp_01 }};"},{"id":"b","statement":"device lock is retained until the user re-establishes access using established identification and authentication procedures.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-10-to-800-53-ac-11","source_ref":"control--ogrl-ac-10","target_ref":"requirement--nist-sp-800-53-r5-ac-11","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_11_odp_02":"device_lock_timeout"},"summary":"Inactivity-based screen lock that persists until re-authentication satisfies AC-11.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-11-1","slug":"ac-11-1","display_id":"AC-11(1)","name":"Pattern-hiding Displays","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Conceal, via the device lock, information previously visible on the display with a publicly viewable image.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-11(01)","statement":"information previously visible on the display is concealed, via device lock, with a publicly viewable image.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-12","slug":"ac-12","display_id":"AC-12","name":"Session Termination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Automatically terminate a user session after {{ ac_12_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a user session is automatically terminated after {{ ac_12_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-10-to-800-53-ac-12","source_ref":"control--ogrl-ac-10","target_ref":"requirement--nist-sp-800-53-r5-ac-12","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ac_12_odp":"session_termination_conditions"},"summary":"Sessions to in-scope systems are automatically terminated under defined conditions.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-12-1","slug":"ac-12-1","display_id":"AC-12(1)","name":"User-initiated Logouts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to {{ ac_12_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-12(01)","statement":"a logout capability is provided for user-initiated communications sessions whenever authentication is used to gain access to {{ ac_12_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-12-2","slug":"ac-12-2","display_id":"AC-12(2)","name":"Termination Message","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Display an explicit logout message to users indicating the termination of authenticated communications sessions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-12(02)","statement":"an explicit logout message is displayed to users indicating the termination of authenticated communication sessions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-12-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-12-3","slug":"ac-12-3","display_id":"AC-12(3)","name":"Timeout Warning Message","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Display an explicit message to users indicating that the session will end in {{ ac_12_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-12(03)","statement":"an explicit message to users is displayed indicating that the session will end in {{ ac_12_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-12-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-13","slug":"ac-13","display_id":"AC-13","name":"Supervision and Review — Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-13_to_nist-sp-800-53-r5-ac-2","source_ref":"requirement--nist-sp-800-53-r5-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ac-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-ac-13_to_nist-sp-800-53-r5-au-6","source_ref":"requirement--nist-sp-800-53-r5-ac-13","target_ref":"requirement--nist-sp-800-53-r5-au-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-14","slug":"ac-14","display_id":"AC-14","name":"Permitted Actions Without Identification or Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify {{ ac_14_odp }} that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and\n"},{"id":"b","statement":"Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ ac_14_odp }} that can be performed on the system without identification or authentication consistent with organizational mission and business functions are identified;\n"},{"id":"b-1","statement":"user actions not requiring identification or authentication are documented in the security plan for the system;\n"},{"id":"b-2","statement":"a rationale for user actions not requiring identification or authentication is provided in the security plan for the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-14-1","slug":"ac-14-1","display_id":"AC-14(1)","name":"Necessary Uses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-14-1_to_nist-sp-800-53-r5-ac-14","source_ref":"requirement--nist-sp-800-53-r5-ac-14-1","target_ref":"requirement--nist-sp-800-53-r5-ac-14","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-14-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-15","slug":"ac-15","display_id":"AC-15","name":"Automated Marking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-15_to_nist-sp-800-53-r5-mp-3","source_ref":"requirement--nist-sp-800-53-r5-ac-15","target_ref":"requirement--nist-sp-800-53-r5-mp-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16","slug":"ac-16","display_id":"AC-16","name":"Security and Privacy Attributes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide the means to associate {{ ac_16_prm_1 }} with {{ ac_16_prm_2 }} for information in storage, in process, and/or in transmission;\n"},{"id":"b","statement":"Ensure that the attribute associations are made and retained with the information;\n"},{"id":"c","statement":"Establish the following permitted security and privacy attributes from the attributes defined in [AC-16a](#ac-16_smt.a) for {{ ac_16_prm_3 }}: {{ ac_16_prm_4 }};\n"},{"id":"d","statement":"Determine the following permitted attribute values or ranges for each of the established attributes: {{ ac_16_odp_09 }};\n"},{"id":"e","statement":"Audit changes to attributes; and"},{"id":"f","statement":"Review {{ ac_16_prm_6 }} for applicability {{ ac_16_prm_7 }}."}],"objectives_count":10,"objectives_preview":[{"id":"a-1","statement":"the means to associate {{ ac_16_odp_01 }} with {{ ac_16_odp_03 }} for information in storage, in process, and/or in transmission are provided;\n"},{"id":"a-2","statement":"the means to associate {{ ac_16_odp_02 }} with {{ ac_16_odp_04 }} for information in storage, in process, and/or in transmission are provided;\n"},{"id":"b-1","statement":"attribute associations are made;"},{"id":"b-2","statement":"attribute associations are retained with the information;"},{"id":"c-1","statement":"the following permitted security attributes are established from the attributes defined in AC-16_ODP[01] for {{ ac_16_odp_05 }}: {{ ac_16_odp_07 }};\n"},{"id":"c-2","statement":"the following permitted privacy attributes are established from the attributes defined in AC-16_ODP[02] for {{ ac_16_odp_06 }}: {{ ac_16_odp_08 }};\n"}],"params_count":17,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-1","slug":"ac-16-1","display_id":"AC-16(1)","name":"Dynamic Attribute Association","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Dynamically associate security and privacy attributes with {{ ac_16_1_prm_1 }} in accordance with the following security and privacy policies as information is created and combined: {{ ac_16_1_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ac-16(01).ac-16(01)[01]","statement":"security attributes are dynamically associated with {{ ac_16_01_odp_01 }} in accordance with the following security policies as information is created and combined: {{ ac_16_01_odp_05 }};\n"},{"id":"ac-16(01).ac-16(01)[02]","statement":"security attributes are dynamically associated with {{ ac_16_01_odp_02 }} in accordance with the following security policies as information is created and combined: {{ ac_16_01_odp_05 }};\n"},{"id":"ac-16(01).ac-16(01)[03]","statement":"privacy attributes are dynamically associated with {{ ac_16_01_odp_03 }} in accordance with the following privacy policies as information is created and combined: {{ ac_16_01_odp_06 }};\n"},{"id":"ac-16(01).ac-16(01)[04]","statement":"privacy attributes are dynamically associated with {{ ac_16_01_odp_04 }} in accordance with the following privacy policies as information is created and combined: {{ ac_16_01_odp_06 }}.\n"}],"params_count":8,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-2","slug":"ac-16-2","display_id":"AC-16(2)","name":"Attribute Value Changes by Authorized Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide authorized individuals (or processes acting on behalf of individuals) the capability to define or change the value of associated security and privacy attributes.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-16(02).ac-16(02)[01]","statement":"authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated security attributes;\n"},{"id":"ac-16(02).ac-16(02)[02]","statement":"authorized individuals (or processes acting on behalf of individuals) are provided with the capability to define or change the value of associated privacy attributes.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-3","slug":"ac-16-3","display_id":"AC-16(3)","name":"Maintenance of Attribute Associations by System","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain the association and integrity of {{ ac_16_3_prm_1 }} to {{ ac_16_3_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ac-16(03).ac-16(03)[01]","statement":"the association and integrity of {{ ac_16_03_odp_01 }} to {{ ac_16_03_odp_03 }} is maintained;\n"},{"id":"ac-16(03).ac-16(03)[02]","statement":"the association and integrity of {{ ac_16_03_odp_01 }} to {{ ac_16_03_odp_04 }} is maintained.\n"},{"id":"ac-16(03).ac-16(03)[03]","statement":"the association and integrity of {{ ac_16_03_odp_02 }} to {{ ac_16_03_odp_05 }} is maintained;\n"},{"id":"ac-16(03).ac-16(03)[04]","statement":"the association and integrity of {{ ac_16_03_odp_02 }} to {{ ac_16_03_odp_06 }} is maintained.\n"}],"params_count":8,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-4","slug":"ac-16-4","display_id":"AC-16(4)","name":"Association of Attributes by Authorized Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability to associate {{ ac_16_4_prm_1 }} with {{ ac_16_4_prm_2 }} by authorized individuals (or processes acting on behalf of individuals).\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ac-16(04).ac-16(04)[01]","statement":"authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate {{ ac_16_04_odp_01 }} with {{ ac_16_04_odp_05 }};\n"},{"id":"ac-16(04).ac-16(04)[02]","statement":"authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate {{ ac_16_04_odp_02 }} with {{ ac_16_04_odp_06 }};\n"},{"id":"ac-16(04).ac-16(04)[03]","statement":"authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate {{ ac_16_04_odp_03 }} with {{ ac_16_04_odp_07 }};\n"},{"id":"ac-16(04).ac-16(04)[04]","statement":"authorized individuals (or processes acting on behalf of individuals) are provided with the capability to associate {{ ac_16_04_odp_04 }} with {{ ac_16_04_odp_08 }}.\n"}],"params_count":10,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-5","slug":"ac-16-5","display_id":"AC-16(5)","name":"Attribute Displays on Objects to Be Output","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Display security and privacy attributes in human-readable form on each object that the system transmits to output devices to identify {{ ac_16_05_odp_01 }} using {{ ac_16_05_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-16(05).ac-16(05)[01]","statement":"security attributes are displayed in human-readable form on each object that the system transmits to output devices to identify {{ ac_16_05_odp_01 }} using {{ ac_16_05_odp_02 }};\n"},{"id":"ac-16(05).ac-16(05)[02]","statement":"privacy attributes are displayed in human-readable form on each object that the system transmits to output devices to identify {{ ac_16_05_odp_01 }} using {{ ac_16_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-6","slug":"ac-16-6","display_id":"AC-16(6)","name":"Maintenance of Attribute Association","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require personnel to associate and maintain the association of {{ ac_16_6_prm_1 }} with {{ ac_16_6_prm_2 }} in accordance with {{ ac_16_6_prm_3 }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ac-16(06).ac-16(06)[01]","statement":"personnel are required to associate and maintain the association of {{ ac_16_06_odp_01 }} with {{ ac_16_06_odp_05 }} in accordance with {{ ac_16_06_odp_09 }};\n"},{"id":"ac-16(06).ac-16(06)[02]","statement":"personnel are required to associate and maintain the association of {{ ac_16_06_odp_02 }} with {{ ac_16_06_odp_06 }} in accordance with {{ ac_16_06_odp_09 }};\n"},{"id":"ac-16(06).ac-16(06)[03]","statement":"personnel are required to associate and maintain the association of {{ ac_16_06_odp_03 }} with {{ ac_16_06_odp_07 }} in accordance with {{ ac_16_06_odp_10 }};\n"},{"id":"ac-16(06).ac-16(06)[04]","statement":"personnel are required to associate and maintain the association of {{ ac_16_06_odp_04 }} with {{ ac_16_06_odp_08 }} in accordance with {{ ac_16_06_odp_10 }}.\n"}],"params_count":13,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-7","slug":"ac-16-7","display_id":"AC-16(7)","name":"Consistent Attribute Interpretation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide a consistent interpretation of security and privacy attributes transmitted between distributed system components.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-16(07).ac-16(07)[01]","statement":"a consistent interpretation of security attributes transmitted between distributed system components is provided;\n"},{"id":"ac-16(07).ac-16(07)[02]","statement":"a consistent interpretation of privacy attributes transmitted between distributed system components is provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-8","slug":"ac-16-8","display_id":"AC-16(8)","name":"Association Techniques and Technologies","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ ac_16_8_prm_1 }} in associating security and privacy attributes to information.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-16(08).ac-16(08)[01]","statement":"{{ ac_16_08_odp_01 }} are implemented in associating security attributes to information;\n"},{"id":"ac-16(08).ac-16(08)[02]","statement":"{{ ac_16_08_odp_02 }} are implemented in associating privacy attributes to information.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-9","slug":"ac-16-9","display_id":"AC-16(9)","name":"Attribute Reassignment — Regrading Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Change security and privacy attributes associated with information only via regrading mechanisms validated using {{ ac_16_9_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-16(09).ac-16(09)[01]","statement":"security attributes associated with information are changed only via regrading mechanisms validated using {{ ac_16_09_odp_01 }};\n"},{"id":"ac-16(09).ac-16(09)[02]","statement":"privacy attributes associated with information are changed only via regrading mechanisms validated using {{ ac_16_09_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-16-10","slug":"ac-16-10","display_id":"AC-16(10)","name":"Attribute Configuration by Authorized Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide authorized individuals the capability to define or change the type and value of security and privacy attributes available for association with subjects and objects.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"authorized individuals are provided with the capability to define or change the type and value of security attributes available for association with subjects and objects;\n"},{"id":"_obj-2","statement":"authorized individuals are provided with the capability to define or change the type and value of privacy attributes available for association with subjects and objects.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-16-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17","slug":"ac-17","display_id":"AC-17","name":"Remote Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and\n"},{"id":"b","statement":"Authorize each type of remote access to the system prior to allowing such connections.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"usage restrictions are established and documented for each type of remote access allowed;\n"},{"id":"a-2","statement":"configuration/connection requirements are established and documented for each type of remote access allowed;\n"},{"id":"a-3","statement":"implementation guidance is established and documented for each type of remote access allowed;\n"},{"id":"b","statement":"each type of remote access to the system is authorized prior to allowing such connections.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-11-to-800-53-ac-17","source_ref":"control--ogrl-ac-11","target_ref":"requirement--nist-sp-800-53-r5-ac-17","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Documented restrictions and configuration requirements per remote access type, with authorization before enablement, satisfy AC-17.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-1","slug":"ac-17-1","display_id":"AC-17(1)","name":"Monitoring and Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automated mechanisms to monitor and control remote access methods.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-17(01).ac-17(01)[01]","statement":"automated mechanisms are employed to monitor remote access methods;"},{"id":"ac-17(01).ac-17(01)[02]","statement":"automated mechanisms are employed to control remote access methods."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-2","slug":"ac-17-2","display_id":"AC-17(2)","name":"Protection of Confidentiality and Integrity Using Encryption","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-17(02)","statement":"cryptographic mechanisms are implemented to protect the confidentiality and integrity of remote access sessions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-3","slug":"ac-17-3","display_id":"AC-17(3)","name":"Managed Access Control Points","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Route remote accesses through authorized and managed network access control points.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-17(03)","statement":"remote accesses are routed through authorized and managed network access control points.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-4","slug":"ac-17-4","display_id":"AC-17(4)","name":"Privileged Commands and Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: {{ ac_17_4_prm_1 }} ; and\n"},{"id":"b","statement":"Document the rationale for remote access in the security plan for the system."}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"the execution of privileged commands via remote access is authorized only in a format that provides assessable evidence;\n"},{"id":"a-2","statement":"access to security-relevant information via remote access is authorized only in a format that provides assessable evidence;\n"},{"id":"a-3","statement":"the execution of privileged commands via remote access is authorized only for the following needs: {{ ac_17_04_odp_01 }};\n"},{"id":"a-4","statement":"access to security-relevant information via remote access is authorized only for the following needs: {{ ac_17_04_odp_02 }};\n"},{"id":"b","statement":"the rationale for remote access is documented in the security plan for the system.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-5","slug":"ac-17-5","display_id":"AC-17(5)","name":"Monitoring for Unauthorized Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-17-5_to_nist-sp-800-53-r5-si-4","source_ref":"requirement--nist-sp-800-53-r5-ac-17-5","target_ref":"requirement--nist-sp-800-53-r5-si-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-6","slug":"ac-17-6","display_id":"AC-17(6)","name":"Protection of Mechanism Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect information about remote access mechanisms from unauthorized use and disclosure.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-17(06)","statement":"information about remote access mechanisms is protected from unauthorized use and disclosure.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-7","slug":"ac-17-7","display_id":"AC-17(7)","name":"Additional Protection for Security Function Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-17-7_to_nist-sp-800-53-r5-ac-3-10","source_ref":"requirement--nist-sp-800-53-r5-ac-17-7","target_ref":"requirement--nist-sp-800-53-r5-ac-3-10","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-8","slug":"ac-17-8","display_id":"AC-17(8)","name":"Disable Nonsecure Network Protocols","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-17-8_to_nist-sp-800-53-r5-cm-7","source_ref":"requirement--nist-sp-800-53-r5-ac-17-8","target_ref":"requirement--nist-sp-800-53-r5-cm-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-9","slug":"ac-17-9","display_id":"AC-17(9)","name":"Disconnect or Disable Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability to disconnect or disable remote access to the system within {{ ac_17_09_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-17(09)","statement":"the capability to disconnect or disable remote access to the system within {{ ac_17_09_odp }} is provided.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-17-10","slug":"ac-17-10","display_id":"AC-17(10)","name":"Authenticate Remote Commands","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ ac_17_10_odp_01 }} to authenticate {{ ac_17_10_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ ac_17_10_odp_01 }} are implemented to authenticate {{ ac_17_10_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-17-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-18","slug":"ac-18","display_id":"AC-18","name":"Wireless Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and\n"},{"id":"b","statement":"Authorize each type of wireless access to the system prior to allowing such connections.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"configuration requirements are established for each type of wireless access;"},{"id":"a-2","statement":"connection requirements are established for each type of wireless access;"},{"id":"a-3","statement":"implementation guidance is established for each type of wireless access;"},{"id":"b","statement":"each type of wireless access to the system is authorized prior to allowing such connections.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-18-1","slug":"ac-18-1","display_id":"AC-18(1)","name":"Authentication and Encryption","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect wireless access to the system using authentication of {{ ac_18_01_odp }} and encryption.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-18(01).ac-18(01)[01]","statement":"wireless access to the system is protected using authentication of {{ ac_18_01_odp }};\n"},{"id":"ac-18(01).ac-18(01)[02]","statement":"wireless access to the system is protected using encryption."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-18-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-18-2","slug":"ac-18-2","display_id":"AC-18(2)","name":"Monitoring Unauthorized Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-18-2_to_nist-sp-800-53-r5-si-4","source_ref":"requirement--nist-sp-800-53-r5-ac-18-2","target_ref":"requirement--nist-sp-800-53-r5-si-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-18-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-18-3","slug":"ac-18-3","display_id":"AC-18(3)","name":"Disable Wireless Networking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Disable, when not intended for use, wireless networking capabilities embedded within system components prior to issuance and deployment.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-18(03)","statement":"when not intended for use, wireless networking capabilities embedded within system components are disabled prior to issuance and deployment.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-18-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-18-4","slug":"ac-18-4","display_id":"AC-18(4)","name":"Restrict Configurations by Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify and explicitly authorize users allowed to independently configure wireless networking capabilities.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-18(04).ac-18(04)[01]","statement":"users allowed to independently configure wireless networking capabilities are identified;\n"},{"id":"ac-18(04).ac-18(04)[02]","statement":"users allowed to independently configure wireless networking capabilities are explicitly authorized.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-18-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-18-5","slug":"ac-18-5","display_id":"AC-18(5)","name":"Antennas and Transmission Power Levels","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Select radio antennas and calibrate transmission power levels to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-18(05).ac-18(05)[01]","statement":"radio antennas are selected to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries;\n"},{"id":"ac-18(05).ac-18(05)[02]","statement":"transmission power levels are calibrated to reduce the probability that signals from wireless access points can be received outside of organization-controlled boundaries.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-18-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-19","slug":"ac-19","display_id":"AC-19","name":"Access Control for Mobile Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and\n"},{"id":"b","statement":"Authorize the connection of mobile devices to organizational systems."}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"configuration requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;\n"},{"id":"a-2","statement":"connection requirements are established for organization-controlled mobile devices, including when such devices are outside of the controlled area;\n"},{"id":"a-3","statement":"implementation guidance is established for organization-controlled mobile devices, including when such devices are outside of the controlled area;\n"},{"id":"b","statement":"the connection of mobile devices to organizational systems is authorized."}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-vm-06-to-800-53-ac-19-a","source_ref":"control--ogrl-vm-06","target_ref":"requirement--nist-sp-800-53-r5-ac-19#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Defined device security requirements and enrollment conditions establish configuration and connection requirements per AC-19(a).\n"},{"id":"mapping--ogrl-vm-06-to-800-53-ac-19-b","source_ref":"control--ogrl-vm-06","target_ref":"requirement--nist-sp-800-53-r5-ac-19#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Device-posture checks authorize only compliant devices to connect per AC-19(b)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-19-1","slug":"ac-19-1","display_id":"AC-19(1)","name":"Use of Writable and Portable Storage Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-19-1_to_nist-sp-800-53-r5-mp-7","source_ref":"requirement--nist-sp-800-53-r5-ac-19-1","target_ref":"requirement--nist-sp-800-53-r5-mp-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-19-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-19-2","slug":"ac-19-2","display_id":"AC-19(2)","name":"Use of Personally Owned Portable Storage Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-19-2_to_nist-sp-800-53-r5-mp-7","source_ref":"requirement--nist-sp-800-53-r5-ac-19-2","target_ref":"requirement--nist-sp-800-53-r5-mp-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-19-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-19-3","slug":"ac-19-3","display_id":"AC-19(3)","name":"Use of Portable Storage Devices with No Identifiable Owner","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ac-19-3_to_nist-sp-800-53-r5-mp-7","source_ref":"requirement--nist-sp-800-53-r5-ac-19-3","target_ref":"requirement--nist-sp-800-53-r5-mp-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-19-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-19-4","slug":"ac-19-4","display_id":"AC-19(4)","name":"Restrictions for Classified Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prohibit the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information unless specifically permitted by the authorizing official; and\n"},{"id":"b","statement":"Enforce the following restrictions on individuals permitted by the authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information:\n"},{"id":"b.1","statement":"Connection of unclassified mobile devices to classified systems is prohibited;"},{"id":"b.2","statement":"Connection of unclassified mobile devices to unclassified systems requires approval from the authorizing official;\n"},{"id":"b.3","statement":"Use of internal or external modems or wireless interfaces within the unclassified mobile devices is prohibited; and\n"},{"id":"b.4","statement":"Unclassified mobile devices and the information stored on those devices are subject to random reviews and inspections by {{ ac_19_04_odp_01 }} , and if classified information is found, the incident handling policy is followed.\n"},{"id":"c","statement":"Restrict the connection of classified mobile devices to classified systems in accordance with {{ ac_19_04_odp_02 }}.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a","statement":"the use of unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information is prohibited unless specifically permitted by the authorizing official;\n"},{"id":"b.1","statement":"prohibition of the connection of unclassified mobile devices to classified systems is enforced on individuals permitted by an authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information;\n"},{"id":"b.2","statement":"approval by the authorizing official for the connection of unclassified mobile devices to unclassified systems is enforced on individuals permitted to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information;\n"},{"id":"b.3","statement":"prohibition of the use of internal or external modems or wireless interfaces within unclassified mobile devices is enforced on individuals permitted by an authorizing official to use unclassified mobile devices in facilities containing systems processing, storing, or transmitting classified information;\n"},{"id":"b.4-1","statement":"random review and inspection of unclassified mobile devices and the information stored on those devices by {{ ac_19_04_odp_01 }} are enforced;\n"},{"id":"b.4-2","statement":"following of the incident handling policy is enforced if classified information is found during a random review and inspection of unclassified mobile devices;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-19-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-19-5","slug":"ac-19-5","display_id":"AC-19(5)","name":"Full Device or Container-based Encryption","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ ac_19_05_odp_01 }} to protect the confidentiality and integrity of information on {{ ac_19_05_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-19(05)","statement":"{{ ac_19_05_odp_01 }} is employed to protect the confidentiality and integrity of information on {{ ac_19_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-19-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-20","slug":"ac-20","display_id":"AC-20","name":"Use of External Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"{{ ac_20_odp_01 }} , consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to:\n"},{"id":"a.1","statement":"Access the system from external systems; and"},{"id":"a.2","statement":"Process, store, or transmit organization-controlled information using external systems; or\n"},{"id":"b","statement":"Prohibit the use of {{ ac_20_odp_04 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a.1","statement":"{{ ac_20_odp_01 }} is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable);\n"},{"id":"a.2","statement":"{{ ac_20_odp_01 }} is/are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store, or transmit organization-controlled information using external systems (if applicable);\n"},{"id":"b","statement":"the use of {{ ac_20_odp_04 }} is prohibited (if applicable)."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-20-1","slug":"ac-20-1","display_id":"AC-20(1)","name":"Limits on Authorized Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Permit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after:\n","citation":null,"parts":[{"id":"a","statement":"Verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans; or\n"},{"id":"b","statement":"Retention of approved system connection or processing agreements with the organizational entity hosting the external system.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans (if applicable);\n"},{"id":"b","statement":"authorized individuals are permitted to use an external system to access the system or to process, store, or transmit organization-controlled information only after retention of approved system connection or processing agreements with the organizational entity hosting the external system (if applicable).\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-20-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-20-2","slug":"ac-20-2","display_id":"AC-20(2)","name":"Portable Storage Devices — Restricted Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the use of organization-controlled portable storage devices by authorized individuals on external systems using {{ ac_20_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-20(02)","statement":"the use of organization-controlled portable storage devices by authorized individuals is restricted on external systems using {{ ac_20_02_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-20-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-20-3","slug":"ac-20-3","display_id":"AC-20(3)","name":"Non-organizationally Owned Systems — Restricted Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the use of non-organizationally owned systems or system components to process, store, or transmit organizational information using {{ ac_20_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-20(03)","statement":"the use of non-organizationally owned systems or system components to process, store, or transmit organizational information is restricted using {{ ac_20_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-20-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-20-4","slug":"ac-20-4","display_id":"AC-20(4)","name":"Network Accessible Storage Devices — Prohibited Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the use of {{ ac_20_04_odp }} in external systems.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-20(04)","statement":"the use of {{ ac_20_04_odp }} is prohibited in external systems."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-20-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-20-5","slug":"ac-20-5","display_id":"AC-20(5)","name":"Portable Storage Devices — Prohibited Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the use of organization-controlled portable storage devices by authorized individuals on external systems.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-20(05)","statement":"the use of organization-controlled portable storage devices by authorized individuals is prohibited on external systems.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-20-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-21","slug":"ac-21","display_id":"AC-21","name":"Information Sharing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for {{ ac_21_odp_01 }} ; and\n"},{"id":"b","statement":"Employ {{ ac_21_odp_02 }} to assist users in making information sharing and collaboration decisions.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"authorized users are enabled to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for {{ ac_21_odp_01 }};\n"},{"id":"b","statement":"{{ ac_21_odp_02 }} are employed to assist users in making information-sharing and collaboration decisions.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-08-to-800-53-ac-21-a","source_ref":"control--ogrl-pr-08","target_ref":"requirement--nist-sp-800-53-r5-ac-21#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"ac_21_odp_01":"disclosure_circumstances"},"summary":"Approval of PII recipients against permitted uses overlaps the sharing-partner check in AC-21(a); automated aids in AC-21(b) are not covered.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-21-1","slug":"ac-21-1","display_id":"AC-21(1)","name":"Automated Decision Support","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ ac_21_01_odp }} to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-21(01)","statement":"{{ ac_21_01_odp }} are employed to enforce information-sharing decisions by authorized users based on access authorizations of sharing partners and access restrictions on information to be shared.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-21-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-21-2","slug":"ac-21-2","display_id":"AC-21(2)","name":"Information Search and Retrieval","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement information search and retrieval services that enforce {{ ac_21_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-21(02)","statement":"information search and retrieval services that enforce {{ ac_21_02_odp }} are implemented.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-21-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-22","slug":"ac-22","display_id":"AC-22","name":"Publicly Accessible Content","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Designate individuals authorized to make information publicly accessible;"},{"id":"b","statement":"Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information;\n"},{"id":"c","statement":"Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and\n"},{"id":"d","statement":"Review the content on the publicly accessible system for nonpublic information {{ ac_22_odp }} and remove such information, if discovered.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"designated individuals are authorized to make information publicly accessible;"},{"id":"b","statement":"authorized individuals are trained to ensure that publicly accessible information does not contain non-public information;\n"},{"id":"c","statement":"the proposed content of information is reviewed prior to posting onto the publicly accessible system to ensure that non-public information is not included;\n"},{"id":"d-1","statement":"the content on the publicly accessible system is reviewed for non-public information {{ ac_22_odp }};\n"},{"id":"d-2","statement":"non-public information is removed from the publicly accessible system, if discovered.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-23","slug":"ac-23","display_id":"AC-23","name":"Data Mining Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ {{ ac_23_odp_01 }} for {{ ac_23_odp_02 }} to detect and protect against unauthorized data mining.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ ac_23_odp_01 }} are employed for {{ ac_23_odp_02 }} to detect and protect against unauthorized data mining.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-24","slug":"ac-24","display_id":"AC-24","name":"Access Control Decisions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"{{ ac_24_odp_01 }} to ensure {{ ac_24_odp_02 }} are applied to each access request prior to access enforcement.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ ac_24_odp_01 }} are taken to ensure that {{ ac_24_odp_02 }} are applied to each access request prior to access enforcement.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-24-1","slug":"ac-24-1","display_id":"AC-24(1)","name":"Transmit Access Authorization Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Transmit {{ ac_24_01_odp_01 }} using {{ ac_24_01_odp_02 }} to {{ ac_24_01_odp_03 }} that enforce access control decisions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ac-24(01)","statement":"{{ ac_24_01_odp_01 }} is transmitted using {{ ac_24_01_odp_02 }} to {{ ac_24_01_odp_03 }} that enforce access control decisions.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-24-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-24-2","slug":"ac-24-2","display_id":"AC-24(2)","name":"No User or Process Identity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce access control decisions based on {{ ac_24_2_prm_1 }} that do not include the identity of the user or process acting on behalf of the user.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ac-24(02).ac-24(02)[01]","statement":"access control decisions are enforced based on {{ ac_24_02_odp_01 }} that do not include the identity of the user or process acting on behalf of the user (if selected);\n"},{"id":"ac-24(02).ac-24(02)[02]","statement":"access control decisions are enforced based on {{ ac_24_02_odp_02 }} that do not include the identity of the user or process acting on behalf of the user (if selected).\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-24-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ac-25","slug":"ac-25","display_id":"AC-25","name":"Reference Monitor","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement a reference monitor for {{ ac_25_odp }} that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a reference monitor is implemented for {{ ac_25_odp }} that is tamper-proof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ac-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-1","slug":"at-1","display_id":"AT-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ at_1_prm_1 }}:"},{"id":"a.1","statement":"{{ at_01_odp_03 }} awareness and training policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls;\n"},{"id":"b","statement":"Designate an {{ at_01_odp_04 }} to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and\n"},{"id":"c","statement":"Review and update the current awareness and training:"},{"id":"c.1","statement":"Policy {{ at_01_odp_05 }} and following {{ at_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ at_01_odp_07 }} and following {{ at_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"an awareness and training policy is developed and documented;"},{"id":"a-2","statement":"the awareness and training policy is disseminated to {{ at_01_odp_01 }};"},{"id":"a-3","statement":"awareness and training procedures to facilitate the implementation of the awareness and training policy and associated access controls are developed and documented;\n"},{"id":"a-4","statement":"the awareness and training procedures are disseminated to {{ at_01_odp_02 }}."},{"id":"a.1.a-1","statement":"the {{ at_01_odp_03 }} awareness and training policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ at_01_odp_03 }} awareness and training policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2","slug":"at-2","display_id":"AT-2","name":"Literacy Training and Awareness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide security and privacy literacy training to system users (including managers, senior executives, and contractors):\n"},{"id":"a.1","statement":"As part of initial training for new users and {{ at_2_prm_1 }} thereafter; and"},{"id":"a.2","statement":"When required by system changes or following {{ at_2_prm_2 }};"},{"id":"b","statement":"Employ the following techniques to increase the security and privacy awareness of system users {{ at_02_odp_05 }};\n"},{"id":"c","statement":"Update literacy training and awareness content {{ at_02_odp_06 }} and following {{ at_02_odp_07 }} ; and\n"},{"id":"d","statement":"Incorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques.\n"}],"objectives_count":10,"objectives_preview":[{"id":"a.1-1","statement":"security literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users;\n"},{"id":"a.1-2","statement":"privacy literacy training is provided to system users (including managers, senior executives, and contractors) as part of initial training for new users;\n"},{"id":"a.1-3","statement":"security literacy training is provided to system users (including managers, senior executives, and contractors) {{ at_02_odp_01 }} thereafter;\n"},{"id":"a.1-4","statement":"privacy literacy training is provided to system users (including managers, senior executives, and contractors) {{ at_02_odp_02 }} thereafter;\n"},{"id":"a.2-1","statement":"security literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following {{ at_02_odp_03 }};\n"},{"id":"a.2-2","statement":"privacy literacy training is provided to system users (including managers, senior executives, and contractors) when required by system changes or following {{ at_02_odp_04 }};\n"}],"params_count":9,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-07-to-800-53-at-2-a-1","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"at_02_odp_01":"training_frequency","at_02_odp_02":"training_frequency"},"summary":"Training at onboarding and on a recurring cadence covers initial and periodic literacy training.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-b","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Simulated phishing exercises are the awareness technique the control employs.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-c","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"at_02_odp_06":"content_review_frequency","at_02_odp_07":"content_update_events"},"summary":"Content is updated on a defined cadence and after defined events.\n"},{"id":"mapping--ogrl-hr-07-to-800-53-at-2-d","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Lessons learned from security incidents are incorporated into training content.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2-1","slug":"at-2-1","display_id":"AT-2(1)","name":"Practical Exercises","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide practical exercises in literacy training that simulate events and incidents.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-02(01)","statement":"practical exercises in literacy training that simulate events and incidents are provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-07-to-800-53-at-2-1","source_ref":"control--ogrl-hr-07","target_ref":"requirement--nist-sp-800-53-r5-at-2-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Simulated phishing exercises are practical exercises that simulate real attack events.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2-2","slug":"at-2-2","display_id":"AT-2(2)","name":"Insider Threat","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide literacy training on recognizing and reporting potential indicators of insider threat.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"at-02(02).at-02(02)[01]","statement":"literacy training on recognizing potential indicators of insider threat is provided;\n"},{"id":"at-02(02).at-02(02)[02]","statement":"literacy training on reporting potential indicators of insider threat is provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2-3","slug":"at-2-3","display_id":"AT-2(3)","name":"Social Engineering and Mining","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"at-02(03).at-02(03)[01]","statement":"literacy training on recognizing potential and actual instances of social engineering is provided;\n"},{"id":"at-02(03).at-02(03)[02]","statement":"literacy training on reporting potential and actual instances of social engineering is provided;\n"},{"id":"at-02(03).at-02(03)[03]","statement":"literacy training on recognizing potential and actual instances of social mining is provided;\n"},{"id":"at-02(03).at-02(03)[04]","statement":"literacy training on reporting potential and actual instances of social mining is provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2-4","slug":"at-2-4","display_id":"AT-2(4)","name":"Suspicious Communications and Anomalous System Behavior","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using {{ at_02_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-02(04)","statement":"literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using {{ at_02_04_odp }} is provided.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2-5","slug":"at-2-5","display_id":"AT-2(5)","name":"Advanced Persistent Threat","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide literacy training on the advanced persistent threat.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-02(05)","statement":"literacy training on the advanced persistent threat is provided."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-2-6","slug":"at-2-6","display_id":"AT-2(6)","name":"Cyber Threat Environment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide literacy training on the cyber threat environment; and"},{"id":"b","statement":"Reflect current cyber threat information in system operations."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"literacy training on the cyber threat environment is provided;"},{"id":"b","statement":"system operations reflects current cyber threat information."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-2-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-3","slug":"at-3","display_id":"AT-3","name":"Role-based Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide role-based security and privacy training to personnel with the following roles and responsibilities: {{ at_3_prm_1 }}:\n"},{"id":"a.1","statement":"Before authorizing access to the system, information, or performing assigned duties, and {{ at_03_odp_03 }} thereafter; and\n"},{"id":"a.2","statement":"When required by system changes;"},{"id":"b","statement":"Update role-based training content {{ at_03_odp_04 }} and following {{ at_03_odp_05 }} ; and\n"},{"id":"c","statement":"Incorporate lessons learned from internal or external security incidents or breaches into role-based training.\n"}],"objectives_count":9,"objectives_preview":[{"id":"a.1-1","statement":"role-based security training is provided to {{ at_03_odp_01 }} before authorizing access to the system, information, or performing assigned duties;\n"},{"id":"a.1-2","statement":"role-based privacy training is provided to {{ at_03_odp_02 }} before authorizing access to the system, information, or performing assigned duties;\n"},{"id":"a.1-3","statement":"role-based security training is provided to {{ at_03_odp_01 }} {{ at_03_odp_03 }} thereafter;\n"},{"id":"a.1-4","statement":"role-based privacy training is provided to {{ at_03_odp_02 }} {{ at_03_odp_03 }} thereafter;\n"},{"id":"a.2-1","statement":"role-based security training is provided to personnel with assigned security roles and responsibilities when required by system changes;\n"},{"id":"a.2-2","statement":"role-based privacy training is provided to personnel with assigned security roles and responsibilities when required by system changes;\n"}],"params_count":6,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-08-to-800-53-at-3","source_ref":"control--ogrl-hr-08","target_ref":"requirement--nist-sp-800-53-r5-at-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"at_03_odp_01":"trained_roles","at_03_odp_02":"trained_roles","at_03_odp_03":"role_training_frequency","at_03_odp_04":"role_content_review_frequency","at_03_odp_05":"role_content_update_events"},"summary":"Role-specific training before access, on a cadence, on system change, with content updates and lessons learned covers all parts of AT-3.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-3-1","slug":"at-3-1","display_id":"AT-3(1)","name":"Environmental Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ at_03_01_odp_01 }} with initial and {{ at_03_01_odp_02 }} training in the employment and operation of environmental controls.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-03(01)","statement":"{{ at_03_01_odp_01 }} are provided with initial and refresher training {{ at_03_01_odp_02 }} in the employment and operation of environmental controls.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-3-2","slug":"at-3-2","display_id":"AT-3(2)","name":"Physical Security Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ at_03_02_odp_01 }} with initial and {{ at_03_02_odp_02 }} training in the employment and operation of physical security controls.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-03(02)","statement":"{{ at_03_02_odp_01 }} is/are provided with initial and refresher training {{ at_03_02_odp_02 }} in the employment and operation of physical security controls.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-3-3","slug":"at-3-3","display_id":"AT-3(3)","name":"Practical Exercises","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide practical exercises in security and privacy training that reinforce training objectives.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"at-03(03).at-03(03)[01]","statement":"practical exercises in security training that reinforce training objectives are provided;\n"},{"id":"at-03(03).at-03(03)[02]","statement":"practical exercises in privacy training that reinforce training objectives are provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-3-4","slug":"at-3-4","display_id":"AT-3(4)","name":"Suspicious Communications and Anomalous System Behavior","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-at-3-4_to_nist-sp-800-53-r5-at-2-4","source_ref":"requirement--nist-sp-800-53-r5-at-3-4","target_ref":"requirement--nist-sp-800-53-r5-at-2-4","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-3-5","slug":"at-3-5","display_id":"AT-3(5)","name":"Processing Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ at_03_05_odp_01 }} with initial and {{ at_03_05_odp_02 }} training in the employment and operation of personally identifiable information processing and transparency controls.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-03(05)","statement":"{{ at_03_05_odp_01 }} are provided with initial and refresher training {{ at_03_05_odp_02 }} in the employment and operation of personally identifiable information processing and transparency controls.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-4","slug":"at-4","display_id":"AT-4","name":"Training Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Document and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training; and\n"},{"id":"b","statement":"Retain individual training records for {{ at_04_odp }}."}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are documented;\n"},{"id":"a-2","statement":"information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training, are monitored;\n"},{"id":"b","statement":"individual training records are retained for {{ at_04_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-5","slug":"at-5","display_id":"AT-5","name":"Contacts with Security Groups and Associations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-at-5_to_nist-sp-800-53-r5-pm-15","source_ref":"requirement--nist-sp-800-53-r5-at-5","target_ref":"requirement--nist-sp-800-53-r5-pm-15","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-at-6","slug":"at-6","display_id":"AT-6","name":"Training Feedback","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide feedback on organizational training results to the following personnel {{ at_06_odp_01 }}: {{ at_06_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"at-06","statement":"feedback on organizational training results is provided {{ at_06_odp_01 }} to {{ at_06_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/at-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-1","slug":"au-1","display_id":"AU-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ au_1_prm_1 }}:"},{"id":"a.1","statement":"{{ au_01_odp_03 }} audit and accountability policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls;\n"},{"id":"b","statement":"Designate an {{ au_01_odp_04 }} to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and\n"},{"id":"c","statement":"Review and update the current audit and accountability:"},{"id":"c.1","statement":"Policy {{ au_01_odp_05 }} and following {{ au_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ au_01_odp_07 }} and following {{ au_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"an audit and accountability policy is developed and documented;"},{"id":"a-2","statement":"the audit and accountability policy is disseminated to {{ au_01_odp_01 }};"},{"id":"a-3","statement":"audit and accountability procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls are developed and documented;\n"},{"id":"a-4","statement":"the audit and accountability procedures are disseminated to {{ au_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ au_01_odp_03 }} of the audit and accountability policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ au_01_odp_03 }} of the audit and accountability policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-2","slug":"au-2","display_id":"AU-2","name":"Event Logging","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify the types of events that the system is capable of logging in support of the audit function: {{ au_02_odp_01 }};\n"},{"id":"b","statement":"Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;\n"},{"id":"c","statement":"Specify the following event types for logging within the system: {{ au_2_prm_2 }};\n"},{"id":"d","statement":"Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and\n"},{"id":"e","statement":"Review and update the event types selected for logging {{ au_02_odp_04 }}."}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"{{ au_02_odp_01 }} that the system is capable of logging are identified in support of the audit logging function;\n"},{"id":"b","statement":"the event logging function is coordinated with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged;\n"},{"id":"c-1","statement":"{{ au_02_odp_02 }} are specified for logging within the system;"},{"id":"c-2","statement":"the specified event types are logged within the system {{ au_02_odp_03 }};"},{"id":"d","statement":"a rationale is provided for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents;\n"},{"id":"e","statement":"the event types selected for logging are reviewed and updated {{ au_02_odp_04 }}.\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-01-to-800-53-au-2-a","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-53-r5-au-2#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_02_odp_01":"logged_events"},"summary":"Centralized logging defines and captures auditable security event types per AU-2(a).\n"},{"id":"mapping--ogrl-lm-01-to-800-53-au-2-e","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-53-r5-au-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_02_odp_04":"logging_review_cadence"},"summary":"Periodic review of logged event scope directly satisfies NIST AU-2(e)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-2-1","slug":"au-2-1","display_id":"AU-2(1)","name":"Compilation of Audit Records from Multiple Sources","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-2-1_to_nist-sp-800-53-r5-au-12","source_ref":"requirement--nist-sp-800-53-r5-au-2-1","target_ref":"requirement--nist-sp-800-53-r5-au-12","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-2-2","slug":"au-2-2","display_id":"AU-2(2)","name":"Selection of Audit Events by Component","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-2-2_to_nist-sp-800-53-r5-au-12","source_ref":"requirement--nist-sp-800-53-r5-au-2-2","target_ref":"requirement--nist-sp-800-53-r5-au-12","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-2-3","slug":"au-2-3","display_id":"AU-2(3)","name":"Reviews and Updates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-2-3_to_nist-sp-800-53-r5-au-2","source_ref":"requirement--nist-sp-800-53-r5-au-2-3","target_ref":"requirement--nist-sp-800-53-r5-au-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-2-4","slug":"au-2-4","display_id":"AU-2(4)","name":"Privileged Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-2-4_to_nist-sp-800-53-r5-ac-6-9","source_ref":"requirement--nist-sp-800-53-r5-au-2-4","target_ref":"requirement--nist-sp-800-53-r5-ac-6-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-3","slug":"au-3","display_id":"AU-3","name":"Content of Audit Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Ensure that audit records contain information that establishes the following:","citation":null,"parts":[{"id":"a","statement":"What type of event occurred;"},{"id":"b","statement":"When the event occurred;"},{"id":"c","statement":"Where the event occurred;"},{"id":"d","statement":"Source of the event;"},{"id":"e","statement":"Outcome of the event; and"},{"id":"f","statement":"Identity of any individuals, subjects, or objects/entities associated with the event.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"audit records contain information that establishes what type of event occurred;"},{"id":"b","statement":"audit records contain information that establishes when the event occurred;"},{"id":"c","statement":"audit records contain information that establishes where the event occurred;"},{"id":"d","statement":"audit records contain information that establishes the source of the event;"},{"id":"e","statement":"audit records contain information that establishes the outcome of the event;"},{"id":"f","statement":"audit records contain information that establishes the identity of any individuals, subjects, or objects/entities associated with the event.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-3-1","slug":"au-3-1","display_id":"AU-3(1)","name":"Additional Audit Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Generate audit records containing the following additional information: {{ au_03_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-03(01)","statement":"generated audit records contain the following {{ au_03_01_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-3-2","slug":"au-3-2","display_id":"AU-3(2)","name":"Centralized Management of Planned Audit Record Content","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-3-2_to_nist-sp-800-53-r5-pl-9","source_ref":"requirement--nist-sp-800-53-r5-au-3-2","target_ref":"requirement--nist-sp-800-53-r5-pl-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-3-3","slug":"au-3-3","display_id":"AU-3(3)","name":"Limit Personally Identifiable Information Elements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit personally identifiable information contained in audit records to the following elements identified in the privacy risk assessment: {{ au_03_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-03(03)","statement":"personally identifiable information contained in audit records is limited to {{ au_03_03_odp }} identified in the privacy risk assessment.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-4","slug":"au-4","display_id":"AU-4","name":"Audit Log Storage Capacity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Allocate audit log storage capacity to accommodate {{ au_04_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-04","statement":"audit log storage capacity is allocated to accommodate {{ au_04_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-4-1","slug":"au-4-1","display_id":"AU-4(1)","name":"Transfer to Alternate Storage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Transfer audit logs {{ au_04_01_odp }} to a different system, system component, or media other than the system or system component conducting the logging.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-04(01)","statement":"audit logs are transferred {{ au_04_01_odp }} to a different system, system component, or media other than the system or system component conducting the logging.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-5","slug":"au-5","display_id":"AU-5","name":"Response to Audit Logging Process Failures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Alert {{ au_05_odp_01 }} within {{ au_05_odp_02 }} in the event of an audit logging process failure; and\n"},{"id":"b","statement":"Take the following additional actions: {{ au_05_odp_03 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ au_05_odp_01 }} are alerted in the event of an audit logging process failure within {{ au_05_odp_02 }};\n"},{"id":"b","statement":"{{ au_05_odp_03 }} are taken in the event of an audit logging process failure."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-5-1","slug":"au-5-1","display_id":"AU-5(1)","name":"Storage Capacity Warning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide a warning to {{ au_05_01_odp_01 }} within {{ au_05_01_odp_02 }} when allocated audit log storage volume reaches {{ au_05_01_odp_03 }} of repository maximum audit log storage capacity.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-05(01)","statement":"a warning is provided to {{ au_05_01_odp_01 }} within {{ au_05_01_odp_02 }} when allocated audit log storage volume reaches {{ au_05_01_odp_03 }} of repository maximum audit log storage capacity.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-5-2","slug":"au-5-2","display_id":"AU-5(2)","name":"Real-time Alerts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an alert within {{ au_05_02_odp_01 }} to {{ au_05_02_odp_02 }} when the following audit failure events occur: {{ au_05_02_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-05(02)","statement":"an alert is provided within {{ au_05_02_odp_01 }} to {{ au_05_02_odp_02 }} when {{ au_05_02_odp_03 }} occur.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-5-3","slug":"au-5-3","display_id":"AU-5(3)","name":"Configurable Traffic Volume Thresholds","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and {{ au_05_03_odp }} network traffic above those thresholds.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"au-05(03).au-05(03)[01]","statement":"configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity are enforced;\n"},{"id":"au-05(03).au-05(03)[02]","statement":"network traffic is {{ au_05_03_odp }} if network traffic volume is above configured thresholds.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-5-4","slug":"au-5-4","display_id":"AU-5(4)","name":"Shutdown on Failure","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Invoke a {{ au_05_04_odp_01 }} in the event of {{ au_05_04_odp_02 }} , unless an alternate audit logging capability exists.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-05(04)","statement":"{{ au_05_04_odp_01 }} is/are invoked in the event of {{ au_05_04_odp_02 }} , unless an alternate audit logging capability exists.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-5-5","slug":"au-5-5","display_id":"AU-5(5)","name":"Alternate Audit Logging Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements {{ au_05_05_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-05(05)","statement":"an alternate audit logging capability is provided in the event of a failure in primary audit logging capability that implements {{ au_05_05_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-5-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6","slug":"au-6","display_id":"AU-6","name":"Audit Record Review, Analysis, and Reporting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Review and analyze system audit records {{ au_06_odp_01 }} for indications of {{ au_06_odp_02 }} and the potential impact of the inappropriate or unusual activity;\n"},{"id":"b","statement":"Report findings to {{ au_06_odp_03 }} ; and"},{"id":"c","statement":"Adjust the level of audit record review, analysis, and reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"system audit records are reviewed and analyzed {{ au_06_odp_01 }} for indications of {{ au_06_odp_02 }} and the potential impact of the inappropriate or unusual activity;\n"},{"id":"b","statement":"findings are reported to {{ au_06_odp_03 }};"},{"id":"c","statement":"the level of audit record review, analysis, and reporting within the system is adjusted when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-04-to-800-53-au-6-a","source_ref":"control--ogrl-lm-04","target_ref":"requirement--nist-sp-800-53-r5-au-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_06_odp_01":"log_review_frequency","au_06_odp_02":"reviewed_activity"},"summary":"Scheduled analysis of audit records for defined unusual activity satisfies AU-6(a).\n"},{"id":"mapping--ogrl-lm-04-to-800-53-au-6-b","source_ref":"control--ogrl-lm-04","target_ref":"requirement--nist-sp-800-53-r5-au-6#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_06_odp_03":"log_review_report_recipients"},"summary":"Findings are reported to defined recipients per AU-6(b)."},{"id":"mapping--ogrl-lm-04-to-800-53-au-6-c","source_ref":"control--ogrl-lm-04","target_ref":"requirement--nist-sp-800-53-r5-au-6#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Review scope is adjusted when credible information indicates a change in risk, as AU-6(c) requires.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-1","slug":"au-6-1","display_id":"AU-6(1)","name":"Automated Process Integration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Integrate audit record review, analysis, and reporting processes using {{ au_06_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(01)","statement":"audit record review, analysis, and reporting processes are integrated using {{ au_06_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-2","slug":"au-6-2","display_id":"AU-6(2)","name":"Automated Security Alerts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-6-2_to_nist-sp-800-53-r5-si-4","source_ref":"requirement--nist-sp-800-53-r5-au-6-2","target_ref":"requirement--nist-sp-800-53-r5-si-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-3","slug":"au-6-3","display_id":"AU-6(3)","name":"Correlate Audit Record Repositories","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(03)","statement":"audit records across different repositories are analyzed and correlated to gain organization-wide situational awareness.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-4","slug":"au-6-4","display_id":"AU-6(4)","name":"Central Review and Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide and implement the capability to centrally review and analyze audit records from multiple components within the system.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"au-06(04).au-06(04)[01]","statement":"the capability to centrally review and analyze audit records from multiple components within the system is provided;\n"},{"id":"au-06(04).au-06(04)[02]","statement":"the capability to centrally review and analyze audit records from multiple components within the system is implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-5","slug":"au-6-5","display_id":"AU-6(5)","name":"Integrated Analysis of Audit Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Integrate analysis of audit records with analysis of {{ au_06_05_odp_01 }} to further enhance the ability to identify inappropriate or unusual activity.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(05)","statement":"analysis of audit records is integrated with analysis of {{ au_06_05_odp_01 }} to further enhance the ability to identify inappropriate or unusual activity.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-6","slug":"au-6-6","display_id":"AU-6(6)","name":"Correlation with Physical Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correlate information from audit records with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(06)","statement":"information from audit records is correlated with information obtained from monitoring physical access to further enhance the ability to identify suspicious, inappropriate, unusual, or malevolent activity.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-7","slug":"au-6-7","display_id":"AU-6(7)","name":"Permitted Actions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Specify the permitted actions for each {{ au_06_07_odp }} associated with the review, analysis, and reporting of audit record information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(07)","statement":"the permitted actions for each {{ au_06_07_odp }} associated with the review, analysis, and reporting of audit record information are specified.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-8","slug":"au-6-8","display_id":"AU-6(8)","name":"Full Text Analysis of Privileged Commands","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform a full text analysis of logged privileged commands in a physically distinct component or subsystem of the system, or other system that is dedicated to that analysis.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(08)","statement":"a full text analysis of logged privileged commands in a physically distinct component or subsystem of the system or other system that is dedicated to that analysis is performed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-9","slug":"au-6-9","display_id":"AU-6(9)","name":"Correlation with Information from Nontechnical Sources","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correlate information from nontechnical sources with audit record information to enhance organization-wide situational awareness.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-06(09)","statement":"information from non-technical sources is correlated with audit record information to enhance organization-wide situational awareness.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-6-10","slug":"au-6-10","display_id":"AU-6(10)","name":"Audit Level Adjustment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-6-10_to_nist-sp-800-53-r5-au-6","source_ref":"requirement--nist-sp-800-53-r5-au-6-10","target_ref":"requirement--nist-sp-800-53-r5-au-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-6-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-7","slug":"au-7","display_id":"AU-7","name":"Audit Record Reduction and Report Generation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide and implement an audit record reduction and report generation capability that:\n","citation":null,"parts":[{"id":"a","statement":"Supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents; and\n"},{"id":"b","statement":"Does not alter the original content or time ordering of audit records."}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"an audit record reduction and report generation capability is provided that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents;\n"},{"id":"a-2","statement":"an audit record reduction and report generation capability is implemented that supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents;\n"},{"id":"b-1","statement":"an audit record reduction and report generation capability is provided that does not alter the original content or time ordering of audit records;\n"},{"id":"b-2","statement":"an audit record reduction and report generation capability is implemented that does not alter the original content or time ordering of audit records.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-7-1","slug":"au-7-1","display_id":"AU-7(1)","name":"Automatic Processing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide and implement the capability to process, sort, and search audit records for events of interest based on the following content: {{ au_07_01_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"au-07(01).au-07(01)[01]","statement":"the capability to process, sort, and search audit records for events of interest based on {{ au_07_01_odp }} are provided;\n"},{"id":"au-07(01).au-07(01)[02]","statement":"the capability to process, sort, and search audit records for events of interest based on {{ au_07_01_odp }} are implemented.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-7-2","slug":"au-7-2","display_id":"AU-7(2)","name":"Automatic Sort and Search","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-7-2_to_nist-sp-800-53-r5-au-7-1","source_ref":"requirement--nist-sp-800-53-r5-au-7-2","target_ref":"requirement--nist-sp-800-53-r5-au-7-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-8","slug":"au-8","display_id":"AU-8","name":"Time Stamps","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Use internal system clocks to generate time stamps for audit records; and"},{"id":"b","statement":"Record time stamps for audit records that meet {{ au_08_odp }} and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or that include the local time offset as part of the time stamp.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"internal system clocks are used to generate timestamps for audit records;"},{"id":"b","statement":"timestamps are recorded for audit records that meet {{ au_08_odp }} and that use Coordinated Universal Time, have a fixed local time offset from Coordinated Universal Time, or include the local time offset as part of the timestamp.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-8-1","slug":"au-8-1","display_id":"AU-8(1)","name":"Synchronization with Authoritative Time Source","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-8-1_to_nist-sp-800-53-r5-sc-45-1","source_ref":"requirement--nist-sp-800-53-r5-au-8-1","target_ref":"requirement--nist-sp-800-53-r5-sc-45-1","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-8-2","slug":"au-8-2","display_id":"AU-8(2)","name":"Secondary Authoritative Time Source","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-8-2_to_nist-sp-800-53-r5-sc-45-2","source_ref":"requirement--nist-sp-800-53-r5-au-8-2","target_ref":"requirement--nist-sp-800-53-r5-sc-45-2","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9","slug":"au-9","display_id":"AU-9","name":"Protection of Audit Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Protect audit information and audit logging tools from unauthorized access, modification, and deletion; and\n"},{"id":"b","statement":"Alert {{ au_09_odp }} upon detection of unauthorized access, modification, or deletion of audit information.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"audit information and audit logging tools are protected from unauthorized access, modification, and deletion;\n"},{"id":"b","statement":"{{ au_09_odp }} are alerted upon detection of unauthorized access, modification, or deletion of audit information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-03-to-800-53-au-9-a","source_ref":"control--ogrl-lm-03","target_ref":"requirement--nist-sp-800-53-r5-au-9#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Immutable storage and restricted access protect audit information from unauthorized access, modification, and deletion per AU-9(a).\n"},{"id":"mapping--ogrl-lm-03-to-800-53-au-9-b","source_ref":"control--ogrl-lm-03","target_ref":"requirement--nist-sp-800-53-r5-au-9#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_09_odp":"log_tamper_alert_recipients"},"summary":"Tampering alerts to defined recipients satisfy AU-9(b)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-1","slug":"au-9-1","display_id":"AU-9(1)","name":"Hardware Write-once Media","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Write audit trails to hardware-enforced, write-once media.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(01)","statement":"audit trails are written to hardware-enforced, write-once media."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-2","slug":"au-9-2","display_id":"AU-9(2)","name":"Store on Separate Physical Systems or Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Store audit records {{ au_09_02_odp }} in a repository that is part of a physically different system or system component than the system or component being audited.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(02)","statement":"audit records are stored {{ au_09_02_odp }} in a repository that is part of a physically different system or system component than the system or component being audited.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-3","slug":"au-9-3","display_id":"AU-9(3)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to protect the integrity of audit information and audit tools.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(03)","statement":"cryptographic mechanisms to protect the integrity of audit information and audit tools are implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-4","slug":"au-9-4","display_id":"AU-9(4)","name":"Access by Subset of Privileged Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Authorize access to management of audit logging functionality to only {{ au_09_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(04)","statement":"access to management of audit logging functionality is authorized only to {{ au_09_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-5","slug":"au-9-5","display_id":"AU-9(5)","name":"Dual Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce dual authorization for {{ au_09_05_odp_01 }} of {{ au_09_05_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(05)","statement":"dual authorization is enforced for the {{ au_09_05_odp_01 }} of {{ au_09_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-6","slug":"au-9-6","display_id":"AU-9(6)","name":"Read-only Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Authorize read-only access to audit information to {{ au_09_06_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(06)","statement":"read-only access to audit information is authorized to {{ au_09_06_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-9-7","slug":"au-9-7","display_id":"AU-9(7)","name":"Store on Component with Different Operating System","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Store audit information on a component running a different operating system than the system or component being audited.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-09(07)","statement":"audit information is stored on a component running a different operating system than the system or component being audited.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-9-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-10","slug":"au-10","display_id":"AU-10","name":"Non-repudiation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed {{ au_10_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"irrefutable evidence is provided that an individual (or process acting on behalf of an individual) has performed {{ au_10_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-10-1","slug":"au-10-1","display_id":"AU-10(1)","name":"Association of Identities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Bind the identity of the information producer with the information to {{ au_10_01_odp }} ; and\n"},{"id":"b","statement":"Provide the means for authorized individuals to determine the identity of the producer of the information.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the identity of the information producer is bound with the information to {{ au_10_01_odp }};\n"},{"id":"b","statement":"the means for authorized individuals to determine the identity of the producer of the information is provided.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-10-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-10-2","slug":"au-10-2","display_id":"AU-10(2)","name":"Validate Binding of Information Producer Identity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Validate the binding of the information producer identity to the information at {{ au_10_02_odp_01 }} ; and\n"},{"id":"b","statement":"Perform {{ au_10_02_odp_02 }} in the event of a validation error."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the binding of the information producer identity to the information is validated at {{ au_10_02_odp_01 }};\n"},{"id":"b","statement":"{{ au_10_02_odp_02 }} in the event of a validation error are performed."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-10-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-10-3","slug":"au-10-3","display_id":"AU-10(3)","name":"Chain of Custody","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain reviewer or releaser credentials within the established chain of custody for information reviewed or released.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-10(03)","statement":"reviewer or releaser credentials are maintained within the established chain of custody for information reviewed or released.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-10-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-10-4","slug":"au-10-4","display_id":"AU-10(4)","name":"Validate Binding of Information Reviewer Identity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Validate the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between {{ au_10_04_odp_01 }} ; and\n"},{"id":"b","statement":"Perform {{ au_10_04_odp_02 }} in the event of a validation error."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the binding of the information reviewer identity to the information at the transfer or release points prior to release or transfer between {{ au_10_04_odp_01 }} is validated;\n"},{"id":"b","statement":"{{ au_10_04_odp_02 }} are performed in the event of a validation error."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-10-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-10-5","slug":"au-10-5","display_id":"AU-10(5)","name":"Digital Signatures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-10-5_to_nist-sp-800-53-r5-si-7","source_ref":"requirement--nist-sp-800-53-r5-au-10-5","target_ref":"requirement--nist-sp-800-53-r5-si-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-10-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-11","slug":"au-11","display_id":"AU-11","name":"Audit Record Retention","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Retain audit records for {{ au_11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"audit records are retained for {{ au_11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-01-to-800-53-au-11","source_ref":"control--ogrl-lm-01","target_ref":"requirement--nist-sp-800-53-r5-au-11","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"au_11_odp":"retention_period"},"summary":"Centralized tamper-resistant retention directly satisfies NIST AU-11 audit record retention.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-11-1","slug":"au-11-1","display_id":"AU-11(1)","name":"Long-term Retrieval Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ au_11_01_odp }} to ensure that long-term audit records generated by the system can be retrieved.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-11(01)","statement":"{{ au_11_01_odp }} are employed to ensure that long-term audit records generated by the system can be retrieved.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-12","slug":"au-12","display_id":"AU-12","name":"Audit Record Generation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide audit record generation capability for the event types the system is capable of auditing as defined in [AU-2a](#au-2_smt.a) on {{ au_12_odp_01 }};\n"},{"id":"b","statement":"Allow {{ au_12_odp_02 }} to select the event types that are to be logged by specific components of the system; and\n"},{"id":"c","statement":"Generate audit records for the event types defined in [AU-2c](#au-2_smt.c) that include the audit record content defined in [AU-3](#au-3).\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"audit record generation capability for the event types the system is capable of auditing (defined in AU-02_ODP[01]) is provided by {{ au_12_odp_01 }};\n"},{"id":"b","statement":"{{ au_12_odp_02 }} is/are allowed to select the event types that are to be logged by specific components of the system;\n"},{"id":"c","statement":"audit records for the event types defined in AU-02_ODP[02] that include the audit record content defined in AU-03 are generated.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-12-1","slug":"au-12-1","display_id":"AU-12(1)","name":"System-wide and Time-correlated Audit Trail","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Compile audit records from {{ au_12_01_odp_01 }} into a system-wide (logical or physical) audit trail that is time-correlated to within {{ au_12_01_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-12(01)","statement":"audit records from {{ au_12_01_odp_01 }} are compiled into a system-wide (logical or physical) audit trail that is time-correlated to within {{ au_12_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-12-2","slug":"au-12-2","display_id":"AU-12(2)","name":"Standardized Formats","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-12(02)","statement":"a system-wide (logical or physical) audit trail composed of audit records is produced in a standardized format.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-12-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-12-3","slug":"au-12-3","display_id":"AU-12(3)","name":"Changes by Authorized Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide and implement the capability for {{ au_12_03_odp_01 }} to change the logging to be performed on {{ au_12_03_odp_02 }} based on {{ au_12_03_odp_03 }} within {{ au_12_03_odp_04 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"au-12(03).au-12(03)[01]","statement":"the capability for {{ au_12_03_odp_01 }} to change the logging to be performed on {{ au_12_03_odp_02 }} based on {{ au_12_03_odp_03 }} within {{ au_12_03_odp_04 }} is provided;\n"},{"id":"au-12(03).au-12(03)[02]","statement":"the capability for {{ au_12_03_odp_01 }} to change the logging to be performed on {{ au_12_03_odp_02 }} based on {{ au_12_03_odp_03 }} within {{ au_12_03_odp_04 }} is implemented.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-12-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-12-4","slug":"au-12-4","display_id":"AU-12(4)","name":"Query Parameter Audits of Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide and implement the capability for auditing the parameters of user query events for data sets containing personally identifiable information.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"au-12(04).au-12(04)[01]","statement":"the capability to audit the parameters of user query events for data sets containing personally identifiable information is provided;\n"},{"id":"au-12(04).au-12(04)[02]","statement":"the capability to audit the parameters of user query events for data sets containing personally identifiable information is implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-12-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-13","slug":"au-13","display_id":"AU-13","name":"Monitoring for Information Disclosure","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor {{ au_13_odp_01 }} {{ au_13_odp_02 }} for evidence of unauthorized disclosure of organizational information; and\n"},{"id":"b","statement":"If an information disclosure is discovered:"},{"id":"b.1","statement":"Notify {{ au_13_odp_03 }} ; and"},{"id":"b.2","statement":"Take the following additional actions: {{ au_13_odp_04 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ au_13_odp_01 }} is/are monitored {{ au_13_odp_02 }} for evidence of unauthorized disclosure of organizational information;\n"},{"id":"b.1","statement":"{{ au_13_odp_03 }} are notified if an information disclosure is discovered;"},{"id":"b.2","statement":"{{ au_13_odp_04 }} are taken if an information disclosure is discovered."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-13-1","slug":"au-13-1","display_id":"AU-13(1)","name":"Use of Automated Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Monitor open-source information and information sites using {{ au_13_01_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-13(01)","statement":"open-source information and information sites are monitored using {{ au_13_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-13-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-13-2","slug":"au-13-2","display_id":"AU-13(2)","name":"Review of Monitored Sites","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review the list of open-source information sites being monitored {{ au_13_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-13(02)","statement":"the list of open-source information sites being monitored is reviewed {{ au_13_02_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-13-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-13-3","slug":"au-13-3","display_id":"AU-13(3)","name":"Unauthorized Replication of Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ discovery techniques, processes, and tools to determine if external entities are replicating organizational information in an unauthorized manner.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-13(03)","statement":"discovery techniques, processes, and tools are employed to determine if external entities are replicating organizational information in an unauthorized manner.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-13-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-14","slug":"au-14","display_id":"AU-14","name":"Session Audit","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide and implement the capability for {{ au_14_odp_01 }} to {{ au_14_odp_02 }} the content of a user session under {{ au_14_odp_03 }} ; and\n"},{"id":"b","statement":"Develop, integrate, and use session auditing activities in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"{{ au_14_odp_01 }} are provided with the capability to {{ au_14_odp_02 }} the content of a user session under {{ au_14_odp_03 }};\n"},{"id":"a-2","statement":"the capability for {{ au_14_odp_01 }} to {{ au_14_odp_02 }} the content of a user session under {{ au_14_odp_03 }} is implemented;\n"},{"id":"b-1","statement":"session auditing activities are developed in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;\n"},{"id":"b-2","statement":"session auditing activities are integrated in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;\n"},{"id":"b-3","statement":"session auditing activities are used in consultation with legal counsel and in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-14-1","slug":"au-14-1","display_id":"AU-14(1)","name":"System Start-up","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Initiate session audits automatically at system start-up.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-14(01)","statement":"session audits are initiated automatically at system start-up."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-14-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-14-2","slug":"au-14-2","display_id":"AU-14(2)","name":"Capture and Record Content","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-14-2_to_nist-sp-800-53-r5-au-14","source_ref":"requirement--nist-sp-800-53-r5-au-14-2","target_ref":"requirement--nist-sp-800-53-r5-au-14","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-14-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-14-3","slug":"au-14-3","display_id":"AU-14(3)","name":"Remote Viewing and Listening","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide and implement the capability for authorized users to remotely view and hear content related to an established user session in real time.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"au-14(03).au-14(03)[01]","statement":"the capability for authorized users to remotely view and hear content related to an established user session in real time is provided;\n"},{"id":"au-14(03).au-14(03)[02]","statement":"the capability for authorized users to remotely view and hear content related to an established user session in real time is implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-14-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-15","slug":"au-15","display_id":"AU-15","name":"Alternate Audit Logging Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-au-15_to_nist-sp-800-53-r5-au-5-5","source_ref":"requirement--nist-sp-800-53-r5-au-15","target_ref":"requirement--nist-sp-800-53-r5-au-5-5","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-16","slug":"au-16","display_id":"AU-16","name":"Cross-organizational Audit Logging","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ {{ au_16_odp_01 }} for coordinating {{ au_16_odp_02 }} among external organizations when audit information is transmitted across organizational boundaries.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ au_16_odp_01 }} for coordinating {{ au_16_odp_02 }} among external organizations when audit information is transmitted across organizational boundaries are employed.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-16-1","slug":"au-16-1","display_id":"AU-16(1)","name":"Identity Preservation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Preserve the identity of individuals in cross-organizational audit trails.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-16(01)","statement":"the identity of individuals in cross-organizational audit trails is preserved."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-16-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-16-2","slug":"au-16-2","display_id":"AU-16(2)","name":"Sharing of Audit Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide cross-organizational audit information to {{ au_16_02_odp_01 }} based on {{ au_16_02_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-16(02)","statement":"cross-organizational audit information is provided to {{ au_16_02_odp_01 }} based on {{ au_16_02_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-16-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-au-16-3","slug":"au-16-3","display_id":"AU-16(3)","name":"Disassociability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ au_16_03_odp }} to disassociate individuals from audit information transmitted across organizational boundaries.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"au-16(03)","statement":"{{ au_16_03_odp }} are implemented to disassociate individuals from audit information transmitted across organizational boundaries.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/au-16-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-1","slug":"ca-1","display_id":"CA-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ca_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ca_01_odp_03 }} assessment, authorization, and monitoring policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls;\n"},{"id":"b","statement":"Designate an {{ ca_01_odp_04 }} to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; and\n"},{"id":"c","statement":"Review and update the current assessment, authorization, and monitoring:"},{"id":"c.1","statement":"Policy {{ ca_01_odp_05 }} and following {{ ca_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ca_01_odp_07 }} and following {{ ca_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"an assessment, authorization, and monitoring policy is developed and documented;"},{"id":"a-2","statement":"the assessment, authorization, and monitoring policy is disseminated to {{ ca_01_odp_01 }};\n"},{"id":"a-3","statement":"assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented;\n"},{"id":"a-4","statement":"the assessment, authorization, and monitoring procedures are disseminated to {{ ca_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ ca_01_odp_03 }} assessment, authorization, and monitoring policy addresses purpose;\n"},{"id":"a.1.a-2","statement":"the {{ ca_01_odp_03 }} assessment, authorization, and monitoring policy addresses scope;\n"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-2","slug":"ca-2","display_id":"CA-2","name":"Control Assessments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Select the appropriate assessor or assessment team for the type of assessment to be conducted;\n"},{"id":"b","statement":"Develop a control assessment plan that describes the scope of the assessment including:\n"},{"id":"b.1","statement":"Controls and control enhancements under assessment;"},{"id":"b.2","statement":"Assessment procedures to be used to determine control effectiveness; and"},{"id":"b.3","statement":"Assessment environment, assessment team, and assessment roles and responsibilities;\n"},{"id":"c","statement":"Ensure the control assessment plan is reviewed and approved by the authorizing official or designated representative prior to conducting the assessment;\n"},{"id":"d","statement":"Assess the controls in the system and its environment of operation {{ ca_02_odp_01 }} to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security and privacy requirements;\n"},{"id":"e","statement":"Produce a control assessment report that document the results of the assessment; and\n"},{"id":"f","statement":"Provide the results of the control assessment to {{ ca_02_odp_02 }}."}],"objectives_count":11,"objectives_preview":[{"id":"a","statement":"an appropriate assessor or assessment team is selected for the type of assessment to be conducted;\n"},{"id":"b.1","statement":"a control assessment plan is developed that describes the scope of the assessment, including controls and control enhancements under assessment;\n"},{"id":"b.2","statement":"a control assessment plan is developed that describes the scope of the assessment, including assessment procedures to be used to determine control effectiveness;\n"},{"id":"b.3-1","statement":"a control assessment plan is developed that describes the scope of the assessment, including the assessment environment;\n"},{"id":"b.3-2","statement":"a control assessment plan is developed that describes the scope of the assessment, including the assessment team;\n"},{"id":"b.3-3","statement":"a control assessment plan is developed that describes the scope of the assessment, including assessment roles and responsibilities;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-10-to-800-53-ca-2","source_ref":"control--ogrl-gv-10","target_ref":"requirement--nist-sp-800-53-r5-ca-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_02_odp_01":"assessment_frequency","ca_02_odp_02":"results_recipients"},"summary":"Covers assessor selection, an approved assessment plan, periodic assessment, reporting, and distribution of results.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-2-1","slug":"ca-2-1","display_id":"CA-2(1)","name":"Independent Assessors","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ independent assessors or assessment teams to conduct control assessments.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-02(01)","statement":"independent assessors or assessment teams are employed to conduct control assessments.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-2-2","slug":"ca-2-2","display_id":"CA-2(2)","name":"Specialized Assessments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include as part of control assessments, {{ ca_02_02_odp_01 }}, {{ ca_02_02_odp_02 }}, {{ ca_02_02_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-02(02)","statement":"{{ ca_02_02_odp_01 }} {{ ca_02_02_odp_02 }} {{ ca_02_02_odp_03 }} are included as part of control assessments.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-2-3","slug":"ca-2-3","display_id":"CA-2(3)","name":"Leveraging Results from External Organizations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Leverage the results of control assessments performed by {{ ca_02_03_odp_01 }} on {{ ca_02_03_odp_02 }} when the assessment meets {{ ca_02_03_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-02(03)","statement":"the results of control assessments performed by {{ ca_02_03_odp_01 }} on {{ ca_02_03_odp_02 }} are leveraged when the assessment meets {{ ca_02_03_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3","slug":"ca-3","display_id":"CA-3","name":"Information Exchange","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve and manage the exchange of information between the system and other systems using {{ ca_03_odp_01 }};\n"},{"id":"b","statement":"Document, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level of the information communicated; and\n"},{"id":"c","statement":"Review and update the agreements {{ ca_03_odp_03 }}."}],"objectives_count":8,"objectives_preview":[{"id":"a","statement":"the exchange of information between the system and other systems is approved and managed using {{ ca_03_odp_01 }};\n"},{"id":"b-1","statement":"the interface characteristics are documented as part of each exchange agreement;"},{"id":"b-2","statement":"security requirements are documented as part of each exchange agreement;"},{"id":"b-3","statement":"privacy requirements are documented as part of each exchange agreement;"},{"id":"b-4","statement":"controls are documented as part of each exchange agreement;"},{"id":"b-5","statement":"responsibilities for each system are documented as part of each exchange agreement;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-1","slug":"ca-3-1","display_id":"CA-3(1)","name":"Unclassified National Security System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-3-1_to_nist-sp-800-53-r5-sc-7-25","source_ref":"requirement--nist-sp-800-53-r5-ca-3-1","target_ref":"requirement--nist-sp-800-53-r5-sc-7-25","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-2","slug":"ca-3-2","display_id":"CA-3(2)","name":"Classified National Security System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-3-2_to_nist-sp-800-53-r5-sc-7-26","source_ref":"requirement--nist-sp-800-53-r5-ca-3-2","target_ref":"requirement--nist-sp-800-53-r5-sc-7-26","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-3","slug":"ca-3-3","display_id":"CA-3(3)","name":"Unclassified Non-national Security System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-3-3_to_nist-sp-800-53-r5-sc-7-27","source_ref":"requirement--nist-sp-800-53-r5-ca-3-3","target_ref":"requirement--nist-sp-800-53-r5-sc-7-27","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-4","slug":"ca-3-4","display_id":"CA-3(4)","name":"Connections to Public Networks","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-3-4_to_nist-sp-800-53-r5-sc-7-28","source_ref":"requirement--nist-sp-800-53-r5-ca-3-4","target_ref":"requirement--nist-sp-800-53-r5-sc-7-28","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-5","slug":"ca-3-5","display_id":"CA-3(5)","name":"Restrictions on External System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-3-5_to_nist-sp-800-53-r5-sc-7-5","source_ref":"requirement--nist-sp-800-53-r5-ca-3-5","target_ref":"requirement--nist-sp-800-53-r5-sc-7-5","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-6","slug":"ca-3-6","display_id":"CA-3(6)","name":"Transfer Authorizations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-03(06)","statement":"individuals or systems transferring data between interconnecting systems have the requisite authorizations (i.e., write permissions or privileges) prior to accepting such data.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-3-7","slug":"ca-3-7","display_id":"CA-3(7)","name":"Transitive Information Exchanges","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify transitive (downstream) information exchanges with other systems through the systems identified in [CA-3a](#ca-3_smt.a) ; and\n"},{"id":"b","statement":"Take measures to ensure that transitive (downstream) information exchanges cease when the controls on identified transitive (downstream) systems cannot be verified or validated.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"transitive (downstream) information exchanges with other systems through the systems identified in CA-03a are identified;\n"},{"id":"b","statement":"measures are taken to ensure that transitive (downstream) information exchanges cease when the controls on identified transitive (downstream) systems cannot be verified or validated.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-3-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-4","slug":"ca-4","display_id":"CA-4","name":"Security Certification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-4_to_nist-sp-800-53-r5-ca-2","source_ref":"requirement--nist-sp-800-53-r5-ca-4","target_ref":"requirement--nist-sp-800-53-r5-ca-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-5","slug":"ca-5","display_id":"CA-5","name":"Plan of Action and Milestones","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and\n"},{"id":"b","statement":"Update existing plan of action and milestones {{ ca_05_odp }} based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a plan of action and milestones for the system is developed to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system;\n"},{"id":"b","statement":"existing plan of action and milestones are updated {{ ca_05_odp }} based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-12-to-800-53-ca-5","source_ref":"control--ogrl-gv-12","target_ref":"requirement--nist-sp-800-53-r5-ca-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_05_odp":"review_frequency"},"summary":"The deficiency register is the plan of action and milestones, updated on a fixed cadence from assessment, audit, and monitoring findings.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-5-1","slug":"ca-5-1","display_id":"CA-5(1)","name":"Automation Support for Accuracy and Currency","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure the accuracy, currency, and availability of the plan of action and milestones for the system using {{ ca_05_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-05(01)","statement":"{{ ca_05_01_odp }} are used to ensure the accuracy, currency, and availability of the plan of action and milestones for the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-6","slug":"ca-6","display_id":"CA-6","name":"Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Assign a senior official as the authorizing official for the system;"},{"id":"b","statement":"Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems;\n"},{"id":"c","statement":"Ensure that the authorizing official for the system, before commencing operations:\n"},{"id":"c.1","statement":"Accepts the use of common controls inherited by the system; and"},{"id":"c.2","statement":"Authorizes the system to operate;"},{"id":"d","statement":"Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;\n"},{"id":"e","statement":"Update the authorizations {{ ca_06_odp }}."}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"a senior official is assigned as the authorizing official for the system;"},{"id":"b","statement":"a senior official is assigned as the authorizing official for common controls available for inheritance by organizational systems;\n"},{"id":"c.1","statement":"before commencing operations, the authorizing official for the system accepts the use of common controls inherited by the system;\n"},{"id":"c.2","statement":"before commencing operations, the authorizing official for the system authorizes the system to operate;\n"},{"id":"d","statement":"the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;\n"},{"id":"e","statement":"the authorizations are updated {{ ca_06_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-6-1","slug":"ca-6-1","display_id":"CA-6(1)","name":"Joint Authorization — Intra-organization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ a joint authorization process for the system that includes multiple authorizing officials from the same organization conducting the authorization.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ca-06(01).ca-06(01)[01]","statement":"a joint authorization process is employed for the system;"},{"id":"ca-06(01).ca-06(01)[02]","statement":"the joint authorization process employed for the system includes multiple authorizing officials from the same organization conducting the authorization.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-6-2","slug":"ca-6-2","display_id":"CA-6(2)","name":"Joint Authorization — Inter-organization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ca-06(02).ca-06(02)[01]","statement":"a joint authorization process is employed for the system;"},{"id":"ca-06(02).ca-06(02)[02]","statement":"the joint authorization process employed for the system includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7","slug":"ca-7","display_id":"CA-7","name":"Continuous Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes:\n","citation":null,"parts":[{"id":"a","statement":"Establishing the following system-level metrics to be monitored: {{ ca_07_odp_01 }};\n"},{"id":"b","statement":"Establishing {{ ca_07_odp_02 }} for monitoring and {{ ca_07_odp_03 }} for assessment of control effectiveness;\n"},{"id":"c","statement":"Ongoing control assessments in accordance with the continuous monitoring strategy;\n"},{"id":"d","statement":"Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy;\n"},{"id":"e","statement":"Correlation and analysis of information generated by control assessments and monitoring;\n"},{"id":"f","statement":"Response actions to address results of the analysis of control assessment and monitoring information; and\n"},{"id":"g","statement":"Reporting the security and privacy status of the system to {{ ca_7_prm_4 }} {{ ca_7_prm_5 }}.\n"}],"objectives_count":11,"objectives_preview":[{"id":"[01]","statement":"a system-level continuous monitoring strategy is developed;"},{"id":"[02]","statement":"system-level continuous monitoring is implemented in accordance with the organization-level continuous monitoring strategy;\n"},{"id":"a","statement":"system-level continuous monitoring includes establishment of the following system-level metrics to be monitored: {{ ca_07_odp_01 }};\n"},{"id":"b-1","statement":"system-level continuous monitoring includes established {{ ca_07_odp_02 }} for monitoring;\n"},{"id":"b-2","statement":"system-level continuous monitoring includes established {{ ca_07_odp_03 }} for assessment of control effectiveness;\n"},{"id":"c","statement":"system-level continuous monitoring includes ongoing control assessments in accordance with the continuous monitoring strategy;\n"}],"params_count":9,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-a","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_07_odp_01":"monitored_metrics"},"summary":"Defines the control metrics that automated monitoring tracks."},{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-d","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Automated checks provide ongoing monitoring of the defined metrics."},{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-f","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Owner assignment and remediation tickets for failing checks are the response actions to monitoring results.\n"},{"id":"mapping--ogrl-gv-11-to-800-53-ca-7-g","source_ref":"control--ogrl-gv-11","target_ref":"requirement--nist-sp-800-53-r5-ca-7#g","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ca_7_prm_4":"status_audience","ca_7_prm_5":"status_reporting_frequency"},"summary":"Regular control health reporting to named recipients meets the status reporting requirement.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7-1","slug":"ca-7-1","display_id":"CA-7(1)","name":"Independent Assessment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ independent assessors or assessment teams to monitor the controls in the system on an ongoing basis.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-07(01)","statement":"independent assessors or assessment teams are employed to monitor the controls in the system on an ongoing basis.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7-2","slug":"ca-7-2","display_id":"CA-7(2)","name":"Types of Assessments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ca-7-2_to_nist-sp-800-53-r5-ca-2","source_ref":"requirement--nist-sp-800-53-r5-ca-7-2","target_ref":"requirement--nist-sp-800-53-r5-ca-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7-3","slug":"ca-7-3","display_id":"CA-7(3)","name":"Trend Analyses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ trend analyses to determine if control implementations, the frequency of continuous monitoring activities, and the types of activities used in the continuous monitoring process need to be modified based on empirical data.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"ca-07(03).ca-07(03)[01]","statement":"trend analysis is employed to determine if control implementations used in the continuous monitoring process need to be modified based on empirical data;\n"},{"id":"ca-07(03).ca-07(03)[02]","statement":"trend analysis is employed to determine if the frequency of continuous monitoring activities used in the continuous monitoring process needs to be modified based on empirical data;\n"},{"id":"ca-07(03).ca-07(03)[03]","statement":"trend analysis is employed to determine if the types of activities used in the continuous monitoring process need to be modified based on empirical data.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7-4","slug":"ca-7-4","display_id":"CA-7(4)","name":"Risk Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following:\n","citation":null,"parts":[{"id":"a","statement":"Effectiveness monitoring;"},{"id":"b","statement":"Compliance monitoring; and"},{"id":"c","statement":"Change monitoring."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"effectiveness monitoring is included in risk monitoring;"},{"id":"b","statement":"compliance monitoring is included in risk monitoring;"},{"id":"c","statement":"change monitoring is included in risk monitoring."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7-5","slug":"ca-7-5","display_id":"CA-7(5)","name":"Consistency Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following actions to validate that policies are established and implemented controls are operating in a consistent manner: {{ ca_7_5_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ca-07(05).ca-07(05)[01]","statement":"{{ ca_07_05_odp_01 }} are employed to validate that policies are established;"},{"id":"ca-07(05).ca-07(05)[02]","statement":"{{ ca_07_05_odp_02 }} are employed to validate that implemented controls are operating in a consistent manner.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-7-6","slug":"ca-7-6","display_id":"CA-7(6)","name":"Automation Support for Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure the accuracy, currency, and availability of monitoring results for the system using {{ ca_07_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-07(06)","statement":"{{ ca_07_06_odp }} are used to ensure the accuracy, currency, and availability of monitoring results for the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-7-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-8","slug":"ca-8","display_id":"CA-8","name":"Penetration Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Conduct penetration testing {{ ca_08_odp_01 }} on {{ ca_08_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-08","statement":"penetration testing is conducted {{ ca_08_odp_01 }} on {{ ca_08_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-vm-05-to-800-53-ca-8","source_ref":"control--ogrl-vm-05","target_ref":"requirement--nist-sp-800-53-r5-ca-8","relationship":"superset-of","review_status":"reviewed","parameter_map":{"ca_08_odp_01":"pentest_frequency","ca_08_odp_02":"pentest_scope"},"summary":"Scheduled penetration testing of defined systems meets CA-8, with remediation and retesting added.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-8-1","slug":"ca-8-1","display_id":"CA-8(1)","name":"Independent Penetration Testing Agent or Team","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ an independent penetration testing agent or team to perform penetration testing on the system or system components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-08(01)","statement":"an independent penetration testing agent or team is employed to perform penetration testing on the system or system components.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-8-2","slug":"ca-8-2","display_id":"CA-8(2)","name":"Red Team Exercises","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following red-team exercises to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement: {{ ca_08_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-08(02)","statement":"{{ ca_08_02_odp }} are employed to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-8-3","slug":"ca-8-3","display_id":"CA-8(3)","name":"Facility Penetration Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ a penetration testing process that includes {{ ca_08_03_odp_01 }} {{ ca_08_03_odp_02 }} attempts to bypass or circumvent controls associated with physical access points to the facility.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ca-08(03)","statement":"the penetration testing process includes {{ ca_08_03_odp_01 }} {{ ca_08_03_odp_02 }} attempts to bypass or circumvent controls associated with physical access points to facility.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-9","slug":"ca-9","display_id":"CA-9","name":"Internal System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Authorize internal connections of {{ ca_09_odp_01 }} to the system;"},{"id":"b","statement":"Document, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated;\n"},{"id":"c","statement":"Terminate internal system connections after {{ ca_09_odp_02 }} ; and"},{"id":"d","statement":"Review {{ ca_09_odp_03 }} the continued need for each internal connection."}],"objectives_count":7,"objectives_preview":[{"id":"a","statement":"internal connections of {{ ca_09_odp_01 }} to the system are authorized;"},{"id":"b-1","statement":"for each internal connection, the interface characteristics are documented;"},{"id":"b-2","statement":"for each internal connection, the security requirements are documented;"},{"id":"b-3","statement":"for each internal connection, the privacy requirements are documented;"},{"id":"b-4","statement":"for each internal connection, the nature of the information communicated is documented;\n"},{"id":"c","statement":"internal system connections are terminated after {{ ca_09_odp_02 }};"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ca-9-1","slug":"ca-9-1","display_id":"CA-9(1)","name":"Compliance Checks","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform security and privacy compliance checks on constituent system components prior to the establishment of the internal connection.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ca-09(01).ca-09(01)[01]","statement":"security compliance checks are performed on constituent system components prior to the establishment of the internal connection;\n"},{"id":"ca-09(01).ca-09(01)[02]","statement":"privacy compliance checks are performed on constituent system components prior to the establishment of the internal connection.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ca-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-1","slug":"cm-1","display_id":"CM-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ cm_1_prm_1 }}:"},{"id":"a.1","statement":"{{ cm_01_odp_03 }} configuration management policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls;\n"},{"id":"b","statement":"Designate an {{ cm_01_odp_04 }} to manage the development, documentation, and dissemination of the configuration management policy and procedures; and\n"},{"id":"c","statement":"Review and update the current configuration management:"},{"id":"c.1","statement":"Policy {{ cm_01_odp_05 }} and following {{ cm_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ cm_01_odp_07 }} and following {{ cm_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a configuration management policy is developed and documented;"},{"id":"a-2","statement":"the configuration management policy is disseminated to {{ cm_01_odp_01 }};"},{"id":"a-3","statement":"configuration management procedures to facilitate the implementation of the configuration management policy and associated configuration management controls are developed and documented;\n"},{"id":"a-4","statement":"the configuration management procedures are disseminated to {{ cm_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ cm_01_odp_03 }} of the configuration management policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ cm_01_odp_03 }} of the configuration management policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2","slug":"cm-2","display_id":"CM-2","name":"Baseline Configuration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and maintain under configuration control, a current baseline configuration of the system; and\n"},{"id":"b","statement":"Review and update the baseline configuration of the system:"},{"id":"b.1","statement":"{{ cm_02_odp_01 }};"},{"id":"b.2","statement":"When required due to {{ cm_02_odp_02 }} ; and"},{"id":"b.3","statement":"When system components are installed or upgraded."}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"a current baseline configuration of the system is developed and documented;"},{"id":"a-2","statement":"a current baseline configuration of the system is maintained under configuration control;\n"},{"id":"b.1","statement":"the baseline configuration of the system is reviewed and updated {{ cm_02_odp_01 }};\n"},{"id":"b.2","statement":"the baseline configuration of the system is reviewed and updated when required due to {{ cm_02_odp_02 }};\n"},{"id":"b.3","statement":"the baseline configuration of the system is reviewed and updated when system components are installed or upgraded.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-02-to-800-53-cm-2-a","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-2#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Version-controlled hardened baselines satisfy the CM-2(a) obligation to develop, document, and maintain a baseline under configuration control.\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-2-b-1","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-2#b.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_02_odp_01":"baseline_review_frequency"},"summary":"The periodic baseline review supplies the CM-2(b)(1) review frequency."},{"id":"mapping--ogrl-cm-02-to-800-53-cm-2-b-3","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-2#b.3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Baselines are reviewed and updated whenever covered components are introduced or upgraded, as CM-2(b)(3) requires.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-1","slug":"cm-2-1","display_id":"CM-2(1)","name":"Reviews and Updates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-2-1_to_nist-sp-800-53-r5-cm-2","source_ref":"requirement--nist-sp-800-53-r5-cm-2-1","target_ref":"requirement--nist-sp-800-53-r5-cm-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-2","slug":"cm-2-2","display_id":"CM-2(2)","name":"Automation Support for Accuracy and Currency","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using {{ cm_02_02_odp }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"cm-02(02).cm-02(02)[01]","statement":"the currency of the baseline configuration of the system is maintained using {{ cm_02_02_odp }};\n"},{"id":"cm-02(02).cm-02(02)[02]","statement":"the completeness of the baseline configuration of the system is maintained using {{ cm_02_02_odp }};\n"},{"id":"cm-02(02).cm-02(02)[03]","statement":"the accuracy of the baseline configuration of the system is maintained using {{ cm_02_02_odp }};\n"},{"id":"cm-02(02).cm-02(02)[04]","statement":"the availability of the baseline configuration of the system is maintained using {{ cm_02_02_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-03-to-800-53-cm-2-2","source_ref":"control--ogrl-cm-03","target_ref":"requirement--nist-sp-800-53-r5-cm-2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"cm_02_02_odp":"drift_detection_tooling"},"summary":"Automated drift checks keep the recorded baseline and actual state aligned, partly supporting CM-2(2) accuracy and currency.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-3","slug":"cm-2-3","display_id":"CM-2(3)","name":"Retention of Previous Configurations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Retain {{ cm_02_03_odp }} of previous versions of baseline configurations of the system to support rollback.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-02(03)","statement":"{{ cm_02_03_odp }} of previous baseline configuration version(s) of the system is/are retained to support rollback.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-4","slug":"cm-2-4","display_id":"CM-2(4)","name":"Unauthorized Software","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-2-4_to_nist-sp-800-53-r5-cm-7-4","source_ref":"requirement--nist-sp-800-53-r5-cm-2-4","target_ref":"requirement--nist-sp-800-53-r5-cm-7-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-5","slug":"cm-2-5","display_id":"CM-2(5)","name":"Authorized Software","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-2-5_to_nist-sp-800-53-r5-cm-7-5","source_ref":"requirement--nist-sp-800-53-r5-cm-2-5","target_ref":"requirement--nist-sp-800-53-r5-cm-7-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-6","slug":"cm-2-6","display_id":"CM-2(6)","name":"Development and Test Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cm-02(06).cm-02(06)[01]","statement":"a baseline configuration for system development environments that is managed separately from the operational baseline configuration is maintained;\n"},{"id":"cm-02(06).cm-02(06)[02]","statement":"a baseline configuration for test environments that is managed separately from the operational baseline configuration is maintained.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-2-7","slug":"cm-2-7","display_id":"CM-2(7)","name":"Configure Systems and Components for High-risk Areas","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Issue {{ cm_02_07_odp_01 }} with {{ cm_02_07_odp_02 }} to individuals traveling to locations that the organization deems to be of significant risk; and\n"},{"id":"b","statement":"Apply the following controls to the systems or components when the individuals return from travel: {{ cm_02_07_odp_03 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ cm_02_07_odp_01 }} with {{ cm_02_07_odp_02 }} are issued to individuals traveling to locations that the organization deems to be of significant risk;\n"},{"id":"b","statement":"{{ cm_02_07_odp_03 }} are applied to the systems or system components when the individuals return from travel.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-2-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3","slug":"cm-3","display_id":"CM-3","name":"Configuration Change Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine and document the types of changes to the system that are configuration-controlled;\n"},{"id":"b","statement":"Review proposed configuration-controlled changes to the system and approve or disapprove such changes with explicit consideration for security and privacy impact analyses;\n"},{"id":"c","statement":"Document configuration change decisions associated with the system;"},{"id":"d","statement":"Implement approved configuration-controlled changes to the system;"},{"id":"e","statement":"Retain records of configuration-controlled changes to the system for {{ cm_03_odp_01 }};\n"},{"id":"f","statement":"Monitor and review activities associated with configuration-controlled changes to the system; and\n"},{"id":"g","statement":"Coordinate and provide oversight for configuration change control activities through {{ cm_03_odp_02 }} that convenes {{ cm_03_odp_03 }}.\n"}],"objectives_count":10,"objectives_preview":[{"id":"a","statement":"the types of changes to the system that are configuration-controlled are determined and documented;\n"},{"id":"b-1","statement":"proposed configuration-controlled changes to the system are reviewed;"},{"id":"b-2","statement":"proposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security and privacy impact analyses;\n"},{"id":"c","statement":"configuration change decisions associated with the system are documented;"},{"id":"d","statement":"approved configuration-controlled changes to the system are implemented;"},{"id":"e","statement":"records of configuration-controlled changes to the system are retained for {{ cm_03_odp_01 }};\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-01-to-800-53-cm-3-e","source_ref":"control--ogrl-cm-01","target_ref":"requirement--nist-sp-800-53-r5-cm-3#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_03_odp_01":"change_record_retention"},"summary":"Retaining pull-request review and deployment audit trails satisfies NIST CM-3(e).\n"},{"id":"mapping--ogrl-cm-01-to-800-53-cm-3-g","source_ref":"control--ogrl-cm-01","target_ref":"requirement--nist-sp-800-53-r5-cm-3#g","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_03_odp_02":"change_authority"},"summary":"Change oversight through code owners and change advisory workflows satisfies NIST CM-3(g).\n"},{"id":"mapping--ogrl-cm-06-to-800-53-cm-3-b","source_ref":"control--ogrl-cm-06","target_ref":"requirement--nist-sp-800-53-r5-cm-3#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Emergency changes receive authorization and retrospective review, a variant of CM-3(b) approval for the expedited path.\n"},{"id":"mapping--ogrl-cm-06-to-800-53-cm-3-c","source_ref":"control--ogrl-cm-06","target_ref":"requirement--nist-sp-800-53-r5-cm-3#c","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Recording each emergency change with its justification documents change decisions for that class of change under CM-3(c).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-1","slug":"cm-3-1","display_id":"CM-3(1)","name":"Automated Documentation, Notification, and Prohibition of Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use {{ cm_03_01_odp_01 }} to:","citation":null,"parts":[{"id":"a","statement":"Document proposed changes to the system;"},{"id":"b","statement":"Notify {{ cm_03_01_odp_02 }} of proposed changes to the system and request change approval;\n"},{"id":"c","statement":"Highlight proposed changes to the system that have not been approved or disapproved within {{ cm_03_01_odp_03 }};\n"},{"id":"d","statement":"Prohibit changes to the system until designated approvals are received;"},{"id":"e","statement":"Document all changes to the system; and"},{"id":"f","statement":"Notify {{ cm_03_01_odp_04 }} when approved changes to the system are completed."}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"{{ cm_03_01_odp_01 }} are used to document proposed changes to the system;"},{"id":"b","statement":"{{ cm_03_01_odp_01 }} are used to notify {{ cm_03_01_odp_02 }} of proposed changes to the system and request change approval;\n"},{"id":"c","statement":"{{ cm_03_01_odp_01 }} are used to highlight proposed changes to the system that have not been approved or disapproved within {{ cm_03_01_odp_03 }};\n"},{"id":"d","statement":"{{ cm_03_01_odp_01 }} are used to prohibit changes to the system until designated approvals are received;\n"},{"id":"e","statement":"{{ cm_03_01_odp_01 }} are used to document all changes to the system;"},{"id":"f","statement":"{{ cm_03_01_odp_01 }} are used to notify {{ cm_03_01_odp_04 }} when approved changes to the system are completed.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-2","slug":"cm-3-2","display_id":"CM-3(2)","name":"Testing, Validation, and Documentation of Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test, validate, and document changes to the system before finalizing the implementation of the changes.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"cm-03(02).cm-03(02)[01]","statement":"changes to the system are tested before finalizing the implementation of the changes;\n"},{"id":"cm-03(02).cm-03(02)[02]","statement":"changes to the system are validated before finalizing the implementation of the changes;\n"},{"id":"cm-03(02).cm-03(02)[03]","statement":"changes to the system are documented before finalizing the implementation of the changes.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-07-to-800-53-cm-3-2","source_ref":"control--ogrl-cm-07","target_ref":"requirement--nist-sp-800-53-r5-cm-3-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Gated testing, validation, and retained results before deployment meet CM-3(2)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-3","slug":"cm-3-3","display_id":"CM-3(3)","name":"Automated Change Implementation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement changes to the current system baseline and deploy the updated baseline across the installed base using {{ cm_03_03_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cm-03(03).cm-03(03)[01]","statement":"changes to the current system baseline are implemented using {{ cm_03_03_odp }};"},{"id":"cm-03(03).cm-03(03)[02]","statement":"the updated baseline is deployed across the installed base using {{ cm_03_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-4","slug":"cm-3-4","display_id":"CM-3(4)","name":"Security and Privacy Representatives","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require {{ cm_3_4_prm_1 }} to be members of the {{ cm_03_04_odp_03 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cm-03(04).cm-03(04)[01]","statement":"{{ cm_03_04_odp_01 }} are required to be members of the {{ cm_03_04_odp_03 }};"},{"id":"cm-03(04).cm-03(04)[02]","statement":"{{ cm_03_04_odp_02 }} are required to be members of the {{ cm_03_04_odp_03 }}."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-5","slug":"cm-3-5","display_id":"CM-3(5)","name":"Automated Security Response","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following security responses automatically if baseline configurations are changed in an unauthorized manner: {{ cm_03_05_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-03(05)","statement":"{{ cm_03_05_odp }} are automatically implemented if baseline configurations are changed in an unauthorized manner.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-6","slug":"cm-3-6","display_id":"CM-3(6)","name":"Cryptography Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure that cryptographic mechanisms used to provide the following controls are under configuration management: {{ cm_03_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-03(06)","statement":"cryptographic mechanisms used to provide {{ cm_03_06_odp }} are under configuration management.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-7","slug":"cm-3-7","display_id":"CM-3(7)","name":"Review System Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review changes to the system {{ cm_03_07_odp_01 }} or when {{ cm_03_07_odp_02 }} to determine whether unauthorized changes have occurred.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-03(07)","statement":"changes to the system are reviewed {{ cm_03_07_odp_01 }} or when {{ cm_03_07_odp_02 }} to determine whether unauthorized changes have occurred.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-3-8","slug":"cm-3-8","display_id":"CM-3(8)","name":"Prevent or Restrict Configuration Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent or restrict changes to the configuration of the system under the following circumstances: {{ cm_03_08_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-03(08)","statement":"changes to the configuration of the system are prevented or restricted under {{ cm_03_08_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-3-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-4","slug":"cm-4","display_id":"CM-4","name":"Impact Analyses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Analyze changes to the system to determine potential security and privacy impacts prior to change implementation.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"changes to the system are analyzed to determine potential security impacts prior to change implementation;\n"},{"id":"[02]","statement":"changes to the system are analyzed to determine potential privacy impacts prior to change implementation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-04-to-800-53-cm-4","source_ref":"control--ogrl-cm-04","target_ref":"requirement--nist-sp-800-53-r5-cm-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Pre-deployment security and privacy impact analysis for significant changes covers CM-4 for that subset of changes.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-4-1","slug":"cm-4-1","display_id":"CM-4(1)","name":"Separate Test Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Analyze changes to the system in a separate test environment before implementation in an operational environment, looking for security and privacy impacts due to flaws, weaknesses, incompatibility, or intentional malice.\n","citation":null,"parts":[],"objectives_count":9,"objectives_preview":[{"id":"cm-04(01).cm-04(01)[01]","statement":"changes to the system are analyzed in a separate test environment before implementation in an operational environment;\n"},{"id":"cm-04(01).cm-04(01)[02]","statement":"changes to the system are analyzed for security impacts due to flaws;"},{"id":"cm-04(01).cm-04(01)[03]","statement":"changes to the system are analyzed for privacy impacts due to flaws;"},{"id":"cm-04(01).cm-04(01)[04]","statement":"changes to the system are analyzed for security impacts due to weaknesses;"},{"id":"cm-04(01).cm-04(01)[05]","statement":"changes to the system are analyzed for privacy impacts due to weaknesses;"},{"id":"cm-04(01).cm-04(01)[06]","statement":"changes to the system are analyzed for security impacts due to incompatibility;"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-07-to-800-53-cm-4-1","source_ref":"control--ogrl-cm-07","target_ref":"requirement--nist-sp-800-53-r5-cm-4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Changes are exercised in a separate test environment, though analysis is not necessarily focused on security and privacy impact as CM-4(1) expects.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-4-2","slug":"cm-4-2","display_id":"CM-4(2)","name":"Verification of Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"cm-04(02).cm-04(02)[01]","statement":"the impacted controls are implemented correctly with regard to meeting the security requirements for the system after system changes;\n"},{"id":"cm-04(02).cm-04(02)[02]","statement":"the impacted controls are implemented correctly with regard to meeting the privacy requirements for the system after system changes;\n"},{"id":"cm-04(02).cm-04(02)[03]","statement":"the impacted controls are operating as intended with regard to meeting the security requirements for the system after system changes;\n"},{"id":"cm-04(02).cm-04(02)[04]","statement":"the impacted controls are operating as intended with regard to meeting the privacy requirements for the system after system changes;\n"},{"id":"cm-04(02).cm-04(02)[05]","statement":"the impacted controls are producing the desired outcome with regard to meeting the security requirements for the system after system changes;\n"},{"id":"cm-04(02).cm-04(02)[06]","statement":"the impacted controls are producing the desired outcome with regard to meeting the privacy requirements for the system after system changes.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5","slug":"cm-5","display_id":"CM-5","name":"Access Restrictions for Change","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"[01]","statement":"physical access restrictions associated with changes to the system are defined and documented;\n"},{"id":"[02]","statement":"physical access restrictions associated with changes to the system are approved;"},{"id":"[03]","statement":"physical access restrictions associated with changes to the system are enforced;"},{"id":"[04]","statement":"logical access restrictions associated with changes to the system are defined and documented;\n"},{"id":"[05]","statement":"logical access restrictions associated with changes to the system are approved;"},{"id":"[06]","statement":"logical access restrictions associated with changes to the system are enforced."}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-05-to-800-53-cm-5","source_ref":"control--ogrl-cm-05","target_ref":"requirement--nist-sp-800-53-r5-cm-5","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Defines and enforces logical access restrictions for changing production; physical change restrictions are out of scope.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-1","slug":"cm-5-1","display_id":"CM-5(1)","name":"Automated Access Enforcement and Audit Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce access restrictions using {{ cm_05_01_odp }} ; and"},{"id":"b","statement":"Automatically generate audit records of the enforcement actions."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"access restrictions for change are enforced using {{ cm_05_01_odp }};"},{"id":"b","statement":"audit records of enforcement actions are automatically generated."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-2","slug":"cm-5-2","display_id":"CM-5(2)","name":"Review System Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-5-2_to_nist-sp-800-53-r5-cm-3-7","source_ref":"requirement--nist-sp-800-53-r5-cm-5-2","target_ref":"requirement--nist-sp-800-53-r5-cm-3-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-3","slug":"cm-5-3","display_id":"CM-5(3)","name":"Signed Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-5-3_to_nist-sp-800-53-r5-cm-14","source_ref":"requirement--nist-sp-800-53-r5-cm-5-3","target_ref":"requirement--nist-sp-800-53-r5-cm-14","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-4","slug":"cm-5-4","display_id":"CM-5(4)","name":"Dual Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce dual authorization for implementing changes to {{ cm_5_4_prm_1 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cm-05(04).cm-05(04)[01]","statement":"dual authorization for implementing changes to {{ cm_05_04_odp_01 }} is enforced;\n"},{"id":"cm-05(04).cm-05(04)[02]","statement":"dual authorization for implementing changes to {{ cm_05_04_odp_02 }} is enforced.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-5","slug":"cm-5-5","display_id":"CM-5(5)","name":"Privilege Limitation for Production and Operation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Limit privileges to change system components and system-related information within a production or operational environment; and\n"},{"id":"b","statement":"Review and reevaluate privileges {{ cm_5_5_prm_1 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"privileges to change system components within a production or operational environment are limited;\n"},{"id":"a-2","statement":"privileges to change system-related information within a production or operational environment are limited;\n"},{"id":"b-1","statement":"privileges are reviewed {{ cm_05_05_odp_01 }};"},{"id":"b-2","statement":"privileges are reevaluated {{ cm_05_05_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-6","slug":"cm-5-6","display_id":"CM-5(6)","name":"Limit Library Privileges","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit privileges to change software resident within software libraries.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-05(06)","statement":"privileges to change software resident within software libraries are limited."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-5-7","slug":"cm-5-7","display_id":"CM-5(7)","name":"Automatic Implementation of Security Safeguards","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-5-7_to_nist-sp-800-53-r5-si-7","source_ref":"requirement--nist-sp-800-53-r5-cm-5-7","target_ref":"requirement--nist-sp-800-53-r5-si-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-5-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-6","slug":"cm-6","display_id":"CM-6","name":"Configuration Settings","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using {{ cm_06_odp_01 }};\n"},{"id":"b","statement":"Implement the configuration settings;"},{"id":"c","statement":"Identify, document, and approve any deviations from established configuration settings for {{ cm_06_odp_02 }} based on {{ cm_06_odp_03 }} ; and\n"},{"id":"d","statement":"Monitor and control changes to the configuration settings in accordance with organizational policies and procedures.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"configuration settings that reflect the most restrictive mode consistent with operational requirements are established and documented for components employed within the system using {{ cm_06_odp_01 }};\n"},{"id":"b","statement":"the configuration settings documented in CM-06a are implemented;"},{"id":"c-1","statement":"any deviations from established configuration settings for {{ cm_06_odp_02 }} are identified and documented based on {{ cm_06_odp_03 }};\n"},{"id":"c-2","statement":"any deviations from established configuration settings for {{ cm_06_odp_02 }} are approved;\n"},{"id":"d-1","statement":"changes to the configuration settings are monitored in accordance with organizational policies and procedures;\n"},{"id":"d-2","statement":"changes to the configuration settings are controlled in accordance with organizational policies and procedures.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-02-to-800-53-cm-6-a","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_06_odp_01":"hardening_benchmark"},"summary":"Baselines derived from a named hardening benchmark establish restrictive configuration settings per CM-6(a).\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-6-b","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Provisioning only from approved baselines implements the documented configuration settings per CM-6(b).\n"},{"id":"mapping--ogrl-cm-02-to-800-53-cm-6-c","source_ref":"control--ogrl-cm-02","target_ref":"requirement--nist-sp-800-53-r5-cm-6#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_06_odp_02":"baseline_scope"},"summary":"Documented, approved baseline deviations for in-scope components address CM-6(c).\n"},{"id":"mapping--ogrl-cm-03-to-800-53-cm-6-d","source_ref":"control--ogrl-cm-03","target_ref":"requirement--nist-sp-800-53-r5-cm-6#d","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated drift detection and resolution monitors and controls changes to configuration settings under CM-6(d).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-6-1","slug":"cm-6-1","display_id":"CM-6(1)","name":"Automated Management, Application, and Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manage, apply, and verify configuration settings for {{ cm_06_01_odp_01 }} using {{ cm_6_1_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"cm-06(01).cm-06(01)[01]","statement":"configuration settings for {{ cm_06_01_odp_01 }} are managed using {{ cm_06_01_odp_02 }};\n"},{"id":"cm-06(01).cm-06(01)[02]","statement":"configuration settings for {{ cm_06_01_odp_01 }} are applied using {{ cm_06_01_odp_03 }};\n"},{"id":"cm-06(01).cm-06(01)[03]","statement":"configuration settings for {{ cm_06_01_odp_01 }} are verified using {{ cm_06_01_odp_04 }}.\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-03-to-800-53-cm-6-1","source_ref":"control--ogrl-cm-03","target_ref":"requirement--nist-sp-800-53-r5-cm-6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":{"cm_6_1_prm_2":"drift_detection_tooling"},"summary":"Drift tooling provides the automated verification element of CM-6(1); central management and application are covered elsewhere.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-6-2","slug":"cm-6-2","display_id":"CM-6(2)","name":"Respond to Unauthorized Changes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Take the following actions in response to unauthorized changes to {{ cm_06_02_odp_02 }}: {{ cm_06_02_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-06(02)","statement":"{{ cm_06_02_odp_01 }} are taken in response to unauthorized changes to {{ cm_06_02_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-6-3","slug":"cm-6-3","display_id":"CM-6(3)","name":"Unauthorized Change Detection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-6-3_to_nist-sp-800-53-r5-si-7","source_ref":"requirement--nist-sp-800-53-r5-cm-6-3","target_ref":"requirement--nist-sp-800-53-r5-si-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-6-4","slug":"cm-6-4","display_id":"CM-6(4)","name":"Conformance Demonstration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-6-4_to_nist-sp-800-53-r5-cm-4","source_ref":"requirement--nist-sp-800-53-r5-cm-6-4","target_ref":"requirement--nist-sp-800-53-r5-cm-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-6-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7","slug":"cm-7","display_id":"CM-7","name":"Least Functionality","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Configure the system to provide only {{ cm_07_odp_01 }} ; and"},{"id":"b","statement":"Prohibit or restrict the use of the following functions, ports, protocols, software, and/or services: {{ cm_7_prm_2 }}.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"the system is configured to provide only {{ cm_07_odp_01 }};"},{"id":"b-1","statement":"the use of {{ cm_07_odp_02 }} is prohibited or restricted;"},{"id":"b-2","statement":"the use of {{ cm_07_odp_03 }} is prohibited or restricted;"},{"id":"b-3","statement":"the use of {{ cm_07_odp_04 }} is prohibited or restricted;"},{"id":"b-4","statement":"the use of {{ cm_07_odp_05 }} is prohibited or restricted;"},{"id":"b-5","statement":"the use of {{ cm_07_odp_06 }} is prohibited or restricted."}],"params_count":7,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-08-to-800-53-cm-7-a","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-7#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Running only required services, ports, and protocols provides only essential capabilities per CM-7(a).\n"},{"id":"mapping--ogrl-cm-08-to-800-53-cm-7-b","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-7#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Default-deny of unneeded services and restricted software sources overlap with the CM-7(b) prohibitions, which the organization still enumerates.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-1","slug":"cm-7-1","display_id":"CM-7(1)","name":"Periodic Review","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Review the system {{ cm_07_01_odp_01 }} to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services; and\n"},{"id":"b","statement":"Disable or remove {{ cm_7_1_prm_2 }}."}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"the system is reviewed {{ cm_07_01_odp_01 }} to identify unnecessary and/or non-secure functions, ports, protocols, software, and services:\n"},{"id":"b-1","statement":"{{ cm_07_01_odp_02 }} deemed to be unnecessary and/or non-secure are disabled or removed;\n"},{"id":"b-2","statement":"{{ cm_07_01_odp_03 }} deemed to be unnecessary and/or non-secure are disabled or removed;\n"},{"id":"b-3","statement":"{{ cm_07_01_odp_04 }} deemed to be unnecessary and/or non-secure are disabled or removed;\n"},{"id":"b-4","statement":"{{ cm_07_01_odp_05 }} deemed to be unnecessary and/or non-secure is disabled or removed;\n"},{"id":"b-5","statement":"{{ cm_07_01_odp_06 }} deemed to be unnecessary and/or non-secure are disabled or removed.\n"}],"params_count":7,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-2","slug":"cm-7-2","display_id":"CM-7(2)","name":"Prevent Program Execution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent program execution in accordance with {{ cm_07_02_odp_01 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-07(02)","statement":"program execution is prevented in accordance with {{ cm_07_02_odp_01 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-3","slug":"cm-7-3","display_id":"CM-7(3)","name":"Registration Compliance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure compliance with {{ cm_07_03_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-07(03)","statement":"{{ cm_07_03_odp }} are complied with."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-4","slug":"cm-7-4","display_id":"CM-7(4)","name":"Unauthorized Software — Deny-by-exception","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify {{ cm_07_04_odp_01 }};"},{"id":"b","statement":"Employ an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the system; and\n"},{"id":"c","statement":"Review and update the list of unauthorized software programs {{ cm_07_04_odp_02 }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ cm_07_04_odp_01 }} are identified;"},{"id":"b","statement":"an allow-all, deny-by-exception policy is employed to prohibit the execution of unauthorized software programs on the system;\n"},{"id":"c","statement":"the list of unauthorized software programs is reviewed and updated {{ cm_07_04_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-5","slug":"cm-7-5","display_id":"CM-7(5)","name":"Authorized Software — Allow-by-exception","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify {{ cm_07_05_odp_01 }};"},{"id":"b","statement":"Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and\n"},{"id":"c","statement":"Review and update the list of authorized software programs {{ cm_07_05_odp_02 }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ cm_07_05_odp_01 }} are identified;"},{"id":"b","statement":"a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system is employed;\n"},{"id":"c","statement":"the list of authorized software programs is reviewed and updated {{ cm_07_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-6","slug":"cm-7-6","display_id":"CM-7(6)","name":"Confined Environments with Limited Privileges","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that the following user-installed software execute in a confined physical or virtual machine environment with limited privileges: {{ cm_07_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-07(06)","statement":"{{ cm_07_06_odp }} is required to be executed in a confined physical or virtual machine environment with limited privileges.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-7","slug":"cm-7-7","display_id":"CM-7(7)","name":"Code Execution in Protected Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Allow execution of binary or machine-executable code only in confined physical or virtual machine environments and with the explicit approval of {{ cm_07_07_odp }} when such code is:\n","citation":null,"parts":[{"id":"a","statement":"Obtained from sources with limited or no warranty; and/or"},{"id":"b","statement":"Without the provision of source code."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the execution of binary or machine-executable code obtained from sources with limited or no warranty is only allowed with the explicit approval of {{ cm_07_07_odp }};\n"},{"id":"b","statement":"the execution of binary or machine-executable code without the provision of source code is only allowed with the explicit approval of {{ cm_07_07_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-8","slug":"cm-7-8","display_id":"CM-7(8)","name":"Binary or Machine Executable Code","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prohibit the use of binary or machine-executable code from sources with limited or no warranty or without the provision of source code; and\n"},{"id":"b","statement":"Allow exceptions only for compelling mission or operational requirements and with the approval of the authorizing official.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the use of binary or machine-executable code is prohibited when it originates from sources with limited or no warranty or without the provision of source code;\n"},{"id":"b-1","statement":"exceptions to the prohibition of binary or machine-executable code from sources with limited or no warranty or without the provision of source code are allowed only for compelling mission or operational requirements;\n"},{"id":"b-2","statement":"exceptions to the prohibition of binary or machine-executable code from sources with limited or no warranty or without the provision of source code are allowed only with the approval of the authorizing official.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-7-9","slug":"cm-7-9","display_id":"CM-7(9)","name":"Prohibiting The Use of Unauthorized Hardware","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify {{ cm_07_09_odp_01 }};"},{"id":"b","statement":"Prohibit the use or connection of unauthorized hardware components;"},{"id":"c","statement":"Review and update the list of authorized hardware components {{ cm_07_09_odp_02 }}.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ cm_07_09_odp_01 }} are identified;"},{"id":"b","statement":"the use or connection of unauthorized hardware components is prohibited;"},{"id":"c","statement":"the list of authorized hardware components is reviewed and updated {{ cm_07_09_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-7-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8","slug":"cm-8","display_id":"CM-8","name":"System Component Inventory","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and document an inventory of system components that:"},{"id":"a.1","statement":"Accurately reflects the system;"},{"id":"a.2","statement":"Includes all components within the system;"},{"id":"a.3","statement":"Does not include duplicate accounting of components or components assigned to any other system;\n"},{"id":"a.4","statement":"Is at the level of granularity deemed necessary for tracking and reporting; and"},{"id":"a.5","statement":"Includes the following information to achieve system component accountability: {{ cm_08_odp_01 }} ; and\n"},{"id":"b","statement":"Review and update the system component inventory {{ cm_08_odp_02 }}."}],"objectives_count":6,"objectives_preview":[{"id":"a.1","statement":"an inventory of system components that accurately reflects the system is developed and documented;\n"},{"id":"a.2","statement":"an inventory of system components that includes all components within the system is developed and documented;\n"},{"id":"a.3","statement":"an inventory of system components that does not include duplicate accounting of components or components assigned to any other system is developed and documented;\n"},{"id":"a.4","statement":"an inventory of system components that is at the level of granularity deemed necessary for tracking and reporting is developed and documented;\n"},{"id":"a.5","statement":"an inventory of system components that includes {{ cm_08_odp_01 }} is developed and documented;\n"},{"id":"b","statement":"the system component inventory is reviewed and updated {{ cm_08_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-am-01-to-800-53-cm-8","source_ref":"control--ogrl-am-01","target_ref":"requirement--nist-sp-800-53-r5-cm-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_08_odp_01":"inventory_attributes","cm_08_odp_02":"inventory_review_frequency"},"summary":"An accurate, non-duplicated inventory with defined attributes, reconciled on a fixed cadence, covers both parts of the requirement.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-1","slug":"cm-8-1","display_id":"CM-8(1)","name":"Updates During Installation and Removal","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Update the inventory of system components as part of component installations, removals, and system updates.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"cm-08(01).cm-08(01)[01]","statement":"the inventory of system components is updated as part of component installations;\n"},{"id":"cm-08(01).cm-08(01)[02]","statement":"the inventory of system components is updated as part of component removals;"},{"id":"cm-08(01).cm-08(01)[03]","statement":"the inventory of system components is updated as part of system updates."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-2","slug":"cm-8-2","display_id":"CM-8(2)","name":"Automated Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain the currency, completeness, accuracy, and availability of the inventory of system components using {{ cm_8_2_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"cm-08(02).cm-08(02)[01]","statement":"{{ cm_08_02_odp_01 }} are used to maintain the currency of the system component inventory;\n"},{"id":"cm-08(02).cm-08(02)[02]","statement":"{{ cm_08_02_odp_02 }} are used to maintain the completeness of the system component inventory;\n"},{"id":"cm-08(02).cm-08(02)[03]","statement":"{{ cm_08_02_odp_03 }} are used to maintain the accuracy of the system component inventory;\n"},{"id":"cm-08(02).cm-08(02)[04]","statement":"{{ cm_08_02_odp_04 }} are used to maintain the availability of the system component inventory.\n"}],"params_count":5,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-3","slug":"cm-8-3","display_id":"CM-8(3)","name":"Automated Unauthorized Component Detection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Detect the presence of unauthorized hardware, software, and firmware components within the system using {{ cm_8_3_prm_1 }} {{ cm_08_03_odp_04 }} ; and\n"},{"id":"b","statement":"Take the following actions when unauthorized components are detected: {{ cm_08_03_odp_05 }}.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"the presence of unauthorized hardware within the system is detected using {{ cm_08_03_odp_01 }} {{ cm_08_03_odp_04 }};\n"},{"id":"a-2","statement":"the presence of unauthorized software within the system is detected using {{ cm_08_03_odp_02 }} {{ cm_08_03_odp_04 }};\n"},{"id":"a-3","statement":"the presence of unauthorized firmware within the system is detected using {{ cm_08_03_odp_03 }} {{ cm_08_03_odp_04 }};\n"},{"id":"b-1","statement":"{{ cm_08_03_odp_05 }} are taken when unauthorized hardware is detected;"},{"id":"b-2","statement":"{{ cm_08_03_odp_05 }} are taken when unauthorized software is detected;"},{"id":"b-3","statement":"{{ cm_08_03_odp_05 }} are taken when unauthorized firmware is detected."}],"params_count":7,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-4","slug":"cm-8-4","display_id":"CM-8(4)","name":"Accountability Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include in the system component inventory information, a means for identifying by {{ cm_08_04_odp }} , individuals responsible and accountable for administering those components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-08(04)","statement":"individuals responsible and accountable for administering system components are identified by {{ cm_08_04_odp }} in the system component inventory.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-5","slug":"cm-8-5","display_id":"CM-8(5)","name":"No Duplicate Accounting of Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-8-5_to_nist-sp-800-53-r5-cm-8","source_ref":"requirement--nist-sp-800-53-r5-cm-8-5","target_ref":"requirement--nist-sp-800-53-r5-cm-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-6","slug":"cm-8-6","display_id":"CM-8(6)","name":"Assessed Configurations and Approved Deviations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include assessed component configurations and any approved deviations to current deployed configurations in the system component inventory.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cm-08(06).cm-08(06)[01]","statement":"assessed component configurations are included in the system component inventory;\n"},{"id":"cm-08(06).cm-08(06)[02]","statement":"any approved deviations to current deployed configurations are included in the system component inventory.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-7","slug":"cm-8-7","display_id":"CM-8(7)","name":"Centralized Repository","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide a centralized repository for the inventory of system components.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-08(07)","statement":"a centralized repository for the system component inventory is provided."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-8","slug":"cm-8-8","display_id":"CM-8(8)","name":"Automated Location Tracking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Support the tracking of system components by geographic location using {{ cm_08_08_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-08(08)","statement":"{{ cm_08_08_odp }} are used to support the tracking of system components by geographic location.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-8-9","slug":"cm-8-9","display_id":"CM-8(9)","name":"Assignment of Components to Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Assign system components to a system; and"},{"id":"b","statement":"Receive an acknowledgement from {{ cm_08_09_odp }} of this assignment."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"system components are assigned to a system;"},{"id":"b","statement":"an acknowledgement of the component assignment is received from {{ cm_08_09_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-8-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-9","slug":"cm-9","display_id":"CM-9","name":"Configuration Management Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop, document, and implement a configuration management plan for the system that:\n","citation":null,"parts":[{"id":"a","statement":"Addresses roles, responsibilities, and configuration management processes and procedures;\n"},{"id":"b","statement":"Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items;\n"},{"id":"c","statement":"Defines the configuration items for the system and places the configuration items under configuration management;\n"},{"id":"d","statement":"Is reviewed and approved by {{ cm_09_odp }} ; and"},{"id":"e","statement":"Protects the configuration management plan from unauthorized disclosure and modification.\n"}],"objectives_count":12,"objectives_preview":[{"id":"[01]","statement":"a configuration management plan for the system is developed and documented;"},{"id":"[02]","statement":"a configuration management plan for the system is implemented;"},{"id":"a-1","statement":"the configuration management plan addresses roles;"},{"id":"a-2","statement":"the configuration management plan addresses responsibilities;"},{"id":"a-3","statement":"the configuration management plan addresses configuration management processes and procedures;\n"},{"id":"b-1","statement":"the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-9-1","slug":"cm-9-1","display_id":"CM-9(1)","name":"Assignment of Responsibility","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Assign responsibility for developing the configuration management process to organizational personnel that are not directly involved in system development.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-09(01)","statement":"the responsibility for developing the configuration management process is assigned to organizational personnel who are not directly involved in system development.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-10","slug":"cm-10","display_id":"CM-10","name":"Software Usage Restrictions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Use software and associated documentation in accordance with contract agreements and copyright laws;\n"},{"id":"b","statement":"Track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and\n"},{"id":"c","statement":"Control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"software and associated documentation are used in accordance with contract agreements and copyright laws;\n"},{"id":"b","statement":"the use of software and associated documentation protected by quantity licenses is tracked to control copying and distribution;\n"},{"id":"c","statement":"the use of peer-to-peer file sharing technology is controlled and documented to ensure that peer-to-peer file sharing is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-10-1","slug":"cm-10-1","display_id":"CM-10(1)","name":"Open-source Software","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish the following restrictions on the use of open-source software: {{ cm_10_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-10(01)","statement":"{{ cm_10_01_odp }} are established for the use of open-source software."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-10-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-11","slug":"cm-11","display_id":"CM-11","name":"User-installed Software","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish {{ cm_11_odp_01 }} governing the installation of software by users;"},{"id":"b","statement":"Enforce software installation policies through the following methods: {{ cm_11_odp_02 }} ; and\n"},{"id":"c","statement":"Monitor policy compliance {{ cm_11_odp_03 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ cm_11_odp_01 }} governing the installation of software by users are established;\n"},{"id":"b","statement":"software installation policies are enforced through {{ cm_11_odp_02 }};"},{"id":"c","statement":"compliance with {{ cm_11_odp_01 }} is monitored {{ cm_11_odp_03 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-08-to-800-53-cm-11-b","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-11#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_11_odp_02":"software_enforcement_methods"},"summary":"Named enforcement methods for software installation satisfy CM-11(b)."},{"id":"mapping--ogrl-cm-08-to-800-53-cm-11-c","source_ref":"control--ogrl-cm-08","target_ref":"requirement--nist-sp-800-53-r5-cm-11#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cm_11_odp_03":"software_compliance_review_frequency"},"summary":"Periodic compliance review supplies the CM-11(c) monitoring frequency."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-11-1","slug":"cm-11-1","display_id":"CM-11(1)","name":"Alerts for Unauthorized Installations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cm-11-1_to_nist-sp-800-53-r5-cm-8-3","source_ref":"requirement--nist-sp-800-53-r5-cm-11-1","target_ref":"requirement--nist-sp-800-53-r5-cm-8-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-11-2","slug":"cm-11-2","display_id":"CM-11(2)","name":"Software Installation with Privileged Status","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Allow user installation of software only with explicit privileged status.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-11(02)","statement":"user installation of software is allowed only with explicit privileged status."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-11-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-11-3","slug":"cm-11-3","display_id":"CM-11(3)","name":"Automated Enforcement and Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce and monitor compliance with software installation policies using {{ cm_11_3_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cm-11(03).cm-11(03)[01]","statement":"compliance with software installation policies is enforced using {{ cm_11_03_odp_01 }};\n"},{"id":"cm-11(03).cm-11(03)[02]","statement":"compliance with software installation policies is monitored using {{ cm_11_03_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-11-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-12","slug":"cm-12","display_id":"CM-12","name":"Information Location","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify and document the location of {{ cm_12_odp }} and the specific system components on which the information is processed and stored;\n"},{"id":"b","statement":"Identify and document the users who have access to the system and system components where the information is processed and stored; and\n"},{"id":"c","statement":"Document changes to the location (i.e., system or system components) where the information is processed and stored.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a-1","statement":"the location of {{ cm_12_odp }} is identified and documented;"},{"id":"a-2","statement":"the specific system components on which {{ cm_12_odp }} is processed are identified and documented;\n"},{"id":"a-3","statement":"the specific system components on which {{ cm_12_odp }} is stored are identified and documented;\n"},{"id":"b-1","statement":"the users who have access to the system and system components where {{ cm_12_odp }} is processed are identified and documented;\n"},{"id":"b-2","statement":"the users who have access to the system and system components where {{ cm_12_odp }} is stored are identified and documented;\n"},{"id":"c-1","statement":"changes to the location (i.e., system or system components) where {{ cm_12_odp }} is processed are documented;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-12-1","slug":"cm-12-1","display_id":"CM-12(1)","name":"Automated Tools to Support Information Location","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use automated tools to identify {{ cm_12_01_odp_01 }} on {{ cm_12_01_odp_02 }} to ensure controls are in place to protect organizational information and individual privacy.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cm-12(01)","statement":"automated tools are used to identify {{ cm_12_01_odp_01 }} on {{ cm_12_01_odp_02 }} to ensure that controls are in place to protect organizational information and individual privacy.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-13","slug":"cm-13","display_id":"CM-13","name":"Data Action Mapping","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop and document a map of system data actions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a map of system data actions is developed and documented."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-cm-14","slug":"cm-14","display_id":"CM-14","name":"Signed Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Prevent the installation of {{ cm_14_prm_1 }} without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"the installation of {{ cm_14_odp_01 }} is prevented unless it is verified that the software has been digitally signed using a certificate recognized and approved by the organization;\n"},{"id":"_obj-2","statement":"the installation of {{ cm_14_odp_02 }} is prevented unless it is verified that the firmware has been digitally signed using a certificate recognized and approved by the organization.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cm-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-1","slug":"cp-1","display_id":"CP-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ cp_1_prm_1 }}:"},{"id":"a.1","statement":"{{ cp_01_odp_03 }} contingency planning policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls;\n"},{"id":"b","statement":"Designate an {{ cp_01_odp_04 }} to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and\n"},{"id":"c","statement":"Review and update the current contingency planning:"},{"id":"c.1","statement":"Policy {{ cp_01_odp_05 }} and following {{ cp_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ cp_01_odp_07 }} and following {{ cp_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a contingency planning policy is developed and documented;"},{"id":"a-2","statement":"the contingency planning policy is disseminated to {{ cp_01_odp_01 }};"},{"id":"a-3","statement":"contingency planning procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls are developed and documented;\n"},{"id":"a-4","statement":"the contingency planning procedures are disseminated to {{ cp_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ cp_01_odp_03 }} contingency planning policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ cp_01_odp_03 }} contingency planning policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2","slug":"cp-2","display_id":"CP-2","name":"Contingency Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a contingency plan for the system that:"},{"id":"a.1","statement":"Identifies essential mission and business functions and associated contingency requirements;\n"},{"id":"a.2","statement":"Provides recovery objectives, restoration priorities, and metrics;"},{"id":"a.3","statement":"Addresses contingency roles, responsibilities, assigned individuals with contact information;\n"},{"id":"a.4","statement":"Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;\n"},{"id":"a.5","statement":"Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;\n"},{"id":"a.6","statement":"Addresses the sharing of contingency information; and"},{"id":"a.7","statement":"Is reviewed and approved by {{ cp_2_prm_1 }};"},{"id":"b","statement":"Distribute copies of the contingency plan to {{ cp_2_prm_2 }};"},{"id":"c","statement":"Coordinate contingency planning activities with incident handling activities;"},{"id":"d","statement":"Review the contingency plan for the system {{ cp_02_odp_05 }};"},{"id":"e","statement":"Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;\n"},{"id":"f","statement":"Communicate contingency plan changes to {{ cp_2_prm_4 }};"},{"id":"g","statement":"Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and\n"},{"id":"h","statement":"Protect the contingency plan from unauthorized disclosure and modification."}],"objectives_count":24,"objectives_preview":[{"id":"a.1","statement":"a contingency plan for the system is developed that identifies essential mission and business functions and associated contingency requirements;\n"},{"id":"a.2-1","statement":"a contingency plan for the system is developed that provides recovery objectives;\n"},{"id":"a.2-2","statement":"a contingency plan for the system is developed that provides restoration priorities;\n"},{"id":"a.2-3","statement":"a contingency plan for the system is developed that provides metrics;"},{"id":"a.3-1","statement":"a contingency plan for the system is developed that addresses contingency roles;"},{"id":"a.3-2","statement":"a contingency plan for the system is developed that addresses contingency responsibilities;\n"}],"params_count":10,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-a","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#a","relationship":"subset-of","review_status":"reviewed","parameter_map":{"cp_2_prm_1":"plan_approver"},"summary":"The plan identifies critical functions, recovery objectives and priorities, roles, continuity and restoration procedures, and approval, but does not address sharing of contingency information.\n"},{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-d","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_02_odp_05":"plan_review_cadence"},"summary":"Periodic plan review satisfies CP-2(d)."},{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-e","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Updating the plan after significant changes and tests satisfies CP-2(e)."},{"id":"mapping--ogrl-bc-01-to-800-53-cp-2-f","source_ref":"control--ogrl-bc-01","target_ref":"requirement--nist-sp-800-53-r5-cp-2#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_2_prm_4":"plan_recipients"},"summary":"Communicating plan changes to key contingency personnel satisfies CP-2(f)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-1","slug":"cp-2-1","display_id":"CP-2(1)","name":"Coordinate with Related Plans","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate contingency plan development with organizational elements responsible for related plans.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-02(01)","statement":"contingency plan development is coordinated with organizational elements responsible for related plans.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-2","slug":"cp-2-2","display_id":"CP-2(2)","name":"Capacity Planning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"cp-02(02).cp-02(02)[01]","statement":"capacity planning is conducted so that the necessary capacity exists during contingency operations for information processing;\n"},{"id":"cp-02(02).cp-02(02)[02]","statement":"capacity planning is conducted so that the necessary capacity exists during contingency operations for telecommunications;\n"},{"id":"cp-02(02).cp-02(02)[03]","statement":"capacity planning is conducted so that the necessary capacity exists during contingency operations for environmental support.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-08-to-800-53-cp-2-2","source_ref":"control--ogrl-bc-08","target_ref":"requirement--nist-sp-800-53-r5-cp-2-2","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Capacity forecasting explicitly includes contingency operations, covering CP-2(2), and adds ongoing utilization monitoring and alerting.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-3","slug":"cp-2-3","display_id":"CP-2(3)","name":"Resume Mission and Business Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Plan for the resumption of {{ cp_02_03_odp_01 }} mission and business functions within {{ cp_02_03_odp_02 }} of contingency plan activation.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-02(03)","statement":"the resumption of {{ cp_02_03_odp_01 }} mission and business functions are planned for within {{ cp_02_03_odp_02 }} of contingency plan activation.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-4","slug":"cp-2-4","display_id":"CP-2(4)","name":"Resume All Mission and Business Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cp-2-4_to_nist-sp-800-53-r5-cp-2-3","source_ref":"requirement--nist-sp-800-53-r5-cp-2-4","target_ref":"requirement--nist-sp-800-53-r5-cp-2-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-5","slug":"cp-2-5","display_id":"CP-2(5)","name":"Continue Mission and Business Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Plan for the continuance of {{ cp_02_05_odp }} mission and business functions with minimal or no loss of operational continuity and sustains that continuity until full system restoration at primary processing and/or storage sites.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-02(05).cp-02(05)[01]","statement":"the continuance of {{ cp_02_05_odp }} mission and business functions with minimal or no loss of operational continuity is planned for;\n"},{"id":"cp-02(05).cp-02(05)[02]","statement":"continuity is sustained until full system restoration at primary processing and/or storage sites.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-6","slug":"cp-2-6","display_id":"CP-2(6)","name":"Alternate Processing and Storage Sites","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Plan for the transfer of {{ cp_02_06_odp }} mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity and sustain that continuity through system restoration to primary processing and/or storage sites.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-02(06).cp-02(06)[01]","statement":"the transfer of {{ cp_02_06_odp }} mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity is planned for;\n"},{"id":"cp-02(06).cp-02(06)[02]","statement":"operational continuity is sustained until full system restoration at primary processing and/or storage sites.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-7","slug":"cp-2-7","display_id":"CP-2(7)","name":"Coordinate with External Service Providers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate the contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-02(07)","statement":"the contingency plan is coordinated with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-2-8","slug":"cp-2-8","display_id":"CP-2(8)","name":"Identify Critical Assets","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify critical system assets supporting {{ cp_02_08_odp }} mission and business functions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-02(08)","statement":"critical system assets supporting {{ cp_02_08_odp }} mission and business functions are identified.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-07-to-800-53-cp-2-8","source_ref":"control--ogrl-bc-07","target_ref":"requirement--nist-sp-800-53-r5-cp-2-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The analysis identifies the critical system assets supporting essential business functions as CP-2(8) requires.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-2-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-3","slug":"cp-3","display_id":"CP-3","name":"Contingency Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide contingency training to system users consistent with assigned roles and responsibilities:\n"},{"id":"a.1","statement":"Within {{ cp_03_odp_01 }} of assuming a contingency role or responsibility;"},{"id":"a.2","statement":"When required by system changes; and"},{"id":"a.3","statement":"{{ cp_03_odp_02 }} thereafter; and"},{"id":"b","statement":"Review and update contingency training content {{ cp_03_odp_03 }} and following {{ cp_03_odp_04 }}.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.1","statement":"contingency training is provided to system users consistent with assigned roles and responsibilities within {{ cp_03_odp_01 }} of assuming a contingency role or responsibility;\n"},{"id":"a.2","statement":"contingency training is provided to system users consistent with assigned roles and responsibilities when required by system changes;\n"},{"id":"a.3","statement":"contingency training is provided to system users consistent with assigned roles and responsibilities {{ cp_03_odp_02 }} thereafter;\n"},{"id":"b-1","statement":"the contingency plan training content is reviewed and updated {{ cp_03_odp_03 }};\n"},{"id":"b-2","statement":"the contingency plan training content is reviewed and updated following {{ cp_03_odp_04 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-3-1","slug":"cp-3-1","display_id":"CP-3(1)","name":"Simulated Events","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-03(01)","statement":"simulated events are incorporated into contingency training to facilitate effective response by personnel in crisis situations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-3-2","slug":"cp-3-2","display_id":"CP-3(2)","name":"Mechanisms Used in Training Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ mechanisms used in operations to provide a more thorough and realistic contingency training environment.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-03(02)","statement":"mechanisms used in operations are employed to provide a more thorough and realistic contingency training environment.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-4","slug":"cp-4","display_id":"CP-4","name":"Contingency Plan Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Test the contingency plan for the system {{ cp_04_odp_01 }} using the following tests to determine the effectiveness of the plan and the readiness to execute the plan: {{ cp_4_prm_2 }}.\n"},{"id":"b","statement":"Review the contingency plan test results; and"},{"id":"c","statement":"Initiate corrective actions, if needed."}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"the contingency plan for the system is tested {{ cp_04_odp_01 }};"},{"id":"a-2","statement":"{{ cp_04_odp_02 }} are used to determine the effectiveness of the plan;"},{"id":"a-3","statement":"{{ cp_04_odp_03 }} are used to determine the readiness to execute the plan;"},{"id":"b","statement":"the contingency plan test results are reviewed;"},{"id":"c","statement":"corrective actions are initiated, if needed."}],"params_count":4,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-02-to-800-53-cp-4","source_ref":"control--ogrl-bc-02","target_ref":"requirement--nist-sp-800-53-r5-cp-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_04_odp_01":"dr_test_cadence","cp_4_prm_2":"dr_test_methods"},"summary":"Scheduled plan testing with defined methods, results review, and gap remediation satisfies CP-4 in full.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-4-1","slug":"cp-4-1","display_id":"CP-4(1)","name":"Coordinate with Related Plans","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate contingency plan testing with organizational elements responsible for related plans.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-04(01)","statement":"contingency plan testing is coordinated with organizational elements responsible for related plans.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-4-2","slug":"cp-4-2","display_id":"CP-4(2)","name":"Alternate Processing Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test the contingency plan at the alternate processing site:","citation":null,"parts":[{"id":"a","statement":"To familiarize contingency personnel with the facility and available resources; and\n"},{"id":"b","statement":"To evaluate the capabilities of the alternate processing site to support contingency operations.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the contingency plan is tested at the alternate processing site to familiarize contingency personnel with the facility and available resources;\n"},{"id":"b","statement":"the contingency plan is tested at the alternate processing site to evaluate the capabilities of the alternate processing site to support contingency operations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-4-3","slug":"cp-4-3","display_id":"CP-4(3)","name":"Automated Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test the contingency plan using {{ cp_04_03_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-04(03)","statement":"the contingency plan is tested using {{ cp_04_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-4-4","slug":"cp-4-4","display_id":"CP-4(4)","name":"Full Recovery and Reconstitution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include a full recovery and reconstitution of the system to a known state as part of contingency plan testing.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-04(04).cp-04(04)[01]","statement":"a full recovery of the system to a known state is included as part of contingency plan testing;\n"},{"id":"cp-04(04).cp-04(04)[02]","statement":"a full reconstitution of the system to a known state is included as part of contingency plan testing.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-4-5","slug":"cp-4-5","display_id":"CP-4(5)","name":"Self-challenge","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ cp_04_05_odp_01 }} to {{ cp_04_05_odp_02 }} to disrupt and adversely affect the system or system component.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-04(05)","statement":"{{ cp_04_05_odp_01 }} are employed to disrupt and adversely affect the {{ cp_04_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-5","slug":"cp-5","display_id":"CP-5","name":"Contingency Plan Update","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cp-5_to_nist-sp-800-53-r5-cp-2","source_ref":"requirement--nist-sp-800-53-r5-cp-5","target_ref":"requirement--nist-sp-800-53-r5-cp-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-6","slug":"cp-6","display_id":"CP-6","name":"Alternate Storage Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and\n"},{"id":"b","statement":"Ensure that the alternate storage site provides controls equivalent to that of the primary site.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"an alternate storage site is established;"},{"id":"a-2","statement":"establishment of the alternate storage site includes necessary agreements to permit the storage and retrieval of system backup information;\n"},{"id":"b","statement":"the alternate storage site provides controls equivalent to that of the primary site.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-05-to-800-53-cp-6","source_ref":"control--ogrl-bc-05","target_ref":"requirement--nist-sp-800-53-r5-cp-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Storing backups in a separate region with an equivalent security baseline establishes an alternate storage site per CP-6.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-6-1","slug":"cp-6-1","display_id":"CP-6(1)","name":"Separation from Primary Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-06(01)","statement":"an alternate storage site that is sufficiently separated from the primary storage site is identified to reduce susceptibility to the same threats.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-6-2","slug":"cp-6-2","display_id":"CP-6(2)","name":"Recovery Time and Recovery Point Objectives","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-06(02).cp-06(02)[01]","statement":"the alternate storage site is configured to facilitate recovery operations in accordance with recovery time objectives;\n"},{"id":"cp-06(02).cp-06(02)[02]","statement":"the alternate storage site is configured to facilitate recovery operations in accordance with recovery point objectives.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-6-3","slug":"cp-6-3","display_id":"CP-6(3)","name":"Accessibility","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-06(03).cp-06(03)[01]","statement":"potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster are identified;\n"},{"id":"cp-06(03).cp-06(03)[02]","statement":"explicit mitigation actions to address identified accessibility problems are outlined.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7","slug":"cp-7","display_id":"CP-7","name":"Alternate Processing Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish an alternate processing site, including necessary agreements to permit the transfer and resumption of {{ cp_07_odp_01 }} for essential mission and business functions within {{ cp_07_odp_02 }} when the primary processing capabilities are unavailable;\n"},{"id":"b","statement":"Make available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site within the organization-defined time period for transfer and resumption; and\n"},{"id":"c","statement":"Provide controls at the alternate processing site that are equivalent to those at the primary site.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"an alternate processing site, including necessary agreements to permit the transfer and resumption of {{ cp_07_odp_01 }} for essential mission and business functions, is established within {{ cp_07_odp_02 }} when the primary processing capabilities are unavailable;\n"},{"id":"b-1","statement":"the equipment and supplies required to transfer operations are made available at the alternate processing site or if contracts are in place to support delivery to the site within {{ cp_07_odp_02 }} for transfer;\n"},{"id":"b-2","statement":"the equipment and supplies required to resume operations are made available at the alternate processing site or if contracts are in place to support delivery to the site within {{ cp_07_odp_02 }} for resumption;\n"},{"id":"c","statement":"controls provided at the alternate processing site are equivalent to those at the primary site.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-05-to-800-53-cp-7-a","source_ref":"control--ogrl-bc-05","target_ref":"requirement--nist-sp-800-53-r5-cp-7#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_07_odp_02":"failover_time_limit"},"summary":"Multi-zone deployment with the ability to resume at an alternate location within a defined time establishes an alternate processing capability per CP-7(a).\n"},{"id":"mapping--ogrl-bc-05-to-800-53-cp-7-c","source_ref":"control--ogrl-bc-05","target_ref":"requirement--nist-sp-800-53-r5-cp-7#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Applying the same security baseline to alternate locations satisfies CP-7(c)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7-1","slug":"cp-7-1","display_id":"CP-7(1)","name":"Separation from Primary Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-07(01)","statement":"an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats is identified.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7-2","slug":"cp-7-2","display_id":"CP-7(2)","name":"Accessibility","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-07(02).cp-07(02)[01]","statement":"potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster are identified;\n"},{"id":"cp-07(02).cp-07(02)[02]","statement":"explicit mitigation actions to address identified accessibility problems are outlined.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7-3","slug":"cp-7-3","display_id":"CP-7(3)","name":"Priority of Service","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-07(03)","statement":"alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7-4","slug":"cp-7-4","display_id":"CP-7(4)","name":"Preparation for Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prepare the alternate processing site so that the site can serve as the operational site supporting essential mission and business functions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-07(04)","statement":"the alternate processing site is prepared so that the site can serve as the operational site supporting essential mission and business functions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7-5","slug":"cp-7-5","display_id":"CP-7(5)","name":"Equivalent Information Security Safeguards","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cp-7-5_to_nist-sp-800-53-r5-cp-7","source_ref":"requirement--nist-sp-800-53-r5-cp-7-5","target_ref":"requirement--nist-sp-800-53-r5-cp-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-7-6","slug":"cp-7-6","display_id":"CP-7(6)","name":"Inability to Return to Primary Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Plan and prepare for circumstances that preclude returning to the primary processing site.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-07(06).cp-07(06)[01]","statement":"circumstances that preclude returning to the primary processing site are planned for;\n"},{"id":"cp-07(06).cp-07(06)[02]","statement":"circumstances that preclude returning to the primary processing site are prepared for.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-7-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-8","slug":"cp-8","display_id":"CP-8","name":"Telecommunications Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish alternate telecommunications services, including necessary agreements to permit the resumption of {{ cp_08_odp_01 }} for essential mission and business functions within {{ cp_08_odp_02 }} when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-08","statement":"alternate telecommunications services, including necessary agreements to permit the resumption of {{ cp_08_odp_01 }} , are established for essential mission and business functions within {{ cp_08_odp_02 }} when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-8-1","slug":"cp-8-1","display_id":"CP-8(1)","name":"Priority of Service Provisions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives); and\n"},{"id":"b","statement":"Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"primary telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed;\n"},{"id":"a-2","statement":"alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives) are developed;\n"},{"id":"b","statement":"Telecommunications Service Priority is requested for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-8-2","slug":"cp-8-2","display_id":"CP-8(2)","name":"Single Points of Failure","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Obtain alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-08(02)","statement":"alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services are obtained.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-8-3","slug":"cp-8-3","display_id":"CP-8(3)","name":"Separation of Primary and Alternate Providers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Obtain alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-08(03)","statement":"alternate telecommunications services from providers that are separated from primary service providers are obtained to reduce susceptibility to the same threats.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-8-4","slug":"cp-8-4","display_id":"CP-8(4)","name":"Provider Contingency Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require primary and alternate telecommunications service providers to have contingency plans;\n"},{"id":"b","statement":"Review provider contingency plans to ensure that the plans meet organizational contingency requirements; and\n"},{"id":"c","statement":"Obtain evidence of contingency testing and training by providers {{ cp_8_4_prm_1 }}.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"primary telecommunications service providers are required to have contingency plans;\n"},{"id":"a-2","statement":"alternate telecommunications service providers are required to have contingency plans;\n"},{"id":"b","statement":"provider contingency plans are reviewed to ensure that the plans meet organizational contingency requirements;\n"},{"id":"c-1","statement":"evidence of contingency testing by providers is obtained {{ cp_08_04_odp_01 }}."},{"id":"c-2","statement":"evidence of contingency training by providers is obtained {{ cp_08_04_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-8-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-8-5","slug":"cp-8-5","display_id":"CP-8(5)","name":"Alternate Telecommunication Service Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test alternate telecommunication services {{ cp_08_05_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-08(05)","statement":"alternate telecommunications services are tested {{ cp_08_05_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-8-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9","slug":"cp-9","display_id":"CP-9","name":"System Backup","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Conduct backups of user-level information contained in {{ cp_09_odp_01 }} {{ cp_09_odp_02 }};\n"},{"id":"b","statement":"Conduct backups of system-level information contained in the system {{ cp_09_odp_03 }};\n"},{"id":"c","statement":"Conduct backups of system documentation, including security- and privacy-related documentation {{ cp_09_odp_04 }} ; and\n"},{"id":"d","statement":"Protect the confidentiality, integrity, and availability of backup information."}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"backups of user-level information contained in {{ cp_09_odp_01 }} are conducted {{ cp_09_odp_02 }};\n"},{"id":"b","statement":"backups of system-level information contained in the system are conducted {{ cp_09_odp_03 }};\n"},{"id":"c","statement":"backups of system documentation, including security- and privacy-related documentation are conducted {{ cp_09_odp_04 }};\n"},{"id":"d-1","statement":"the confidentiality of backup information is protected;"},{"id":"d-2","statement":"the integrity of backup information is protected;"},{"id":"d-3","statement":"the availability of backup information is protected."}],"params_count":4,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-03-to-800-53-cp-9-a","source_ref":"control--ogrl-bc-03","target_ref":"requirement--nist-sp-800-53-r5-cp-9#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_09_odp_01":"backup_scope","cp_09_odp_02":"backup_frequency"},"summary":"Automated backups of production data stores at a defined frequency satisfy CP-9(a).\n"},{"id":"mapping--ogrl-bc-03-to-800-53-cp-9-b","source_ref":"control--ogrl-bc-03","target_ref":"requirement--nist-sp-800-53-r5-cp-9#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_09_odp_03":"backup_frequency"},"summary":"Backing up system configuration and state not held in version control at the same frequency satisfies CP-9(b).\n"},{"id":"mapping--ogrl-bc-03-to-800-53-cp-9-d","source_ref":"control--ogrl-bc-03","target_ref":"requirement--nist-sp-800-53-r5-cp-9#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Encryption, immutable isolated copies, and failure alerting protect the confidentiality, integrity, and availability of backups per CP-9(d).\n"},{"id":"mapping--ogrl-cr-05-to-800-53-cp-9","source_ref":"control--ogrl-cr-05","target_ref":"requirement--nist-sp-800-53-r5-cp-9","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Replicated copies preserve data availability, overlapping with backup objectives, but replication is not a substitute for point-in-time backups.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-1","slug":"cp-9-1","display_id":"CP-9(1)","name":"Testing for Reliability and Integrity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test backup information {{ cp_9_1_prm_1 }} to verify media reliability and information integrity.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-09(01).cp-09(01)[01]","statement":"backup information is tested {{ cp_09_01_odp_01 }} to verify media reliability;"},{"id":"cp-09(01).cp-09(01)[02]","statement":"backup information is tested {{ cp_09_01_odp_02 }} to verify information integrity.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-04-to-800-53-cp-9-1","source_ref":"control--ogrl-bc-04","target_ref":"requirement--nist-sp-800-53-r5-cp-9-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_9_1_prm_1":"restore_test_cadence"},"summary":"Scheduled restore tests with completeness and integrity checks verify backup reliability and integrity per CP-9(1).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-2","slug":"cp-9-2","display_id":"CP-9(2)","name":"Test Restoration Using Sampling","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use a sample of backup information in the restoration of selected system functions as part of contingency plan testing.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-09(02)","statement":"a sample of backup information in the restoration of selected system functions is used as part of contingency plan testing.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-3","slug":"cp-9-3","display_id":"CP-9(3)","name":"Separate Storage for Critical Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Store backup copies of {{ cp_09_03_odp }} in a separate facility or in a fire rated container that is not collocated with the operational system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-09(03)","statement":"backup copies of {{ cp_09_03_odp }} are stored in a separate facility or in a fire rated container that is not collocated with the operational system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-4","slug":"cp-9-4","display_id":"CP-9(4)","name":"Protection from Unauthorized Modification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cp-9-4_to_nist-sp-800-53-r5-cp-9","source_ref":"requirement--nist-sp-800-53-r5-cp-9-4","target_ref":"requirement--nist-sp-800-53-r5-cp-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-5","slug":"cp-9-5","display_id":"CP-9(5)","name":"Transfer to Alternate Storage Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Transfer system backup information to the alternate storage site {{ cp_9_5_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-09(05).cp-09(05)[01]","statement":"system backup information is transferred to the alternate storage site for {{ cp_09_05_odp_01 }};\n"},{"id":"cp-09(05).cp-09(05)[02]","statement":"system backup information is transferred to the alternate storage site {{ cp_09_05_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-6","slug":"cp-9-6","display_id":"CP-9(6)","name":"Redundant Secondary System","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Conduct system backup by maintaining a redundant secondary system that is not collocated with the primary system and that can be activated without loss of information or disruption to operations.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"cp-09(06).cp-09(06)[01]","statement":"system backup is conducted by maintaining a redundant secondary system that is not collocated with the primary system;\n"},{"id":"cp-09(06).cp-09(06)[02]","statement":"system backup is conducted by maintaining a redundant secondary system that can be activated without loss of information or disruption to operations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-7","slug":"cp-9-7","display_id":"CP-9(7)","name":"Dual Authorization for Deletion or Destruction","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce dual authorization for the deletion or destruction of {{ cp_09_07_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-09(07)","statement":"dual authorization for the deletion or destruction of {{ cp_09_07_odp }} is enforced.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-9-8","slug":"cp-9-8","display_id":"CP-9(8)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of {{ cp_09_08_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-09(08)","statement":"cryptographic mechanisms are implemented to prevent unauthorized disclosure and modification of {{ cp_09_08_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-9-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10","slug":"cp-10","display_id":"CP-10","name":"System Recovery and Reconstitution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide for the recovery and reconstitution of the system to a known state within {{ cp_10_prm_1 }} after a disruption, compromise, or failure.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"the recovery of the system to a known state is provided within {{ cp_10_odp_01 }} after a disruption, compromise, or failure;\n"},{"id":"_obj-2","statement":"a reconstitution of the system to a known state is provided within {{ cp_10_odp_02 }} after a disruption, compromise, or failure.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-06-to-800-53-cp-10","source_ref":"control--ogrl-bc-06","target_ref":"requirement--nist-sp-800-53-r5-cp-10","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"cp_10_prm_1":"recovery_time_objective"},"summary":"Recovering to a known-good state within defined recovery objectives satisfies CP-10.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10-1","slug":"cp-10-1","display_id":"CP-10(1)","name":"Contingency Plan Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cp-10-1_to_nist-sp-800-53-r5-cp-4","source_ref":"requirement--nist-sp-800-53-r5-cp-10-1","target_ref":"requirement--nist-sp-800-53-r5-cp-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10-2","slug":"cp-10-2","display_id":"CP-10(2)","name":"Transaction Recovery","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement transaction recovery for systems that are transaction-based.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-10(02)","statement":"transaction recovery is implemented for systems that are transaction-based."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10-3","slug":"cp-10-3","display_id":"CP-10(3)","name":"Compensating Security Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":"Addressed through tailoring.","citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10-4","slug":"cp-10-4","display_id":"CP-10(4)","name":"Restore Within Time Period","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability to restore system components within {{ cp_10_04_odp }} from configuration-controlled and integrity-protected information representing a known, operational state for the components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-10(04)","statement":"the capability to restore system components within {{ cp_10_04_odp }} from configuration-controlled and integrity-protected information representing a known, operational state for the components is provided.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10-5","slug":"cp-10-5","display_id":"CP-10(5)","name":"Failover Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-cp-10-5_to_nist-sp-800-53-r5-si-13","source_ref":"requirement--nist-sp-800-53-r5-cp-10-5","target_ref":"requirement--nist-sp-800-53-r5-si-13","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-10-6","slug":"cp-10-6","display_id":"CP-10(6)","name":"Component Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect system components used for recovery and reconstitution.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"cp-10(06)","statement":"system components used for recovery and reconstitution are protected."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-10-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-11","slug":"cp-11","display_id":"CP-11","name":"Alternate Communications Protocols","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide the capability to employ {{ cp_11_odp }} in support of maintaining continuity of operations.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the capability to employ {{ cp_11_odp }} are provided in support of maintaining continuity of operations.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-12","slug":"cp-12","display_id":"CP-12","name":"Safe Mode","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"When {{ cp_12_odp_02 }} are detected, enter a safe mode of operation with {{ cp_12_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a safe mode of operation is entered with {{ cp_12_odp_01 }} when {{ cp_12_odp_02 }} are detected.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-cp-13","slug":"cp-13","display_id":"CP-13","name":"Alternative Security Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ {{ cp_13_odp_01 }} for satisfying {{ cp_13_odp_02 }} when the primary means of implementing the security function is unavailable or compromised.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ cp_13_odp_01 }} are employed for satisfying {{ cp_13_odp_02 }} when the primary means of implementing the security function is unavailable or compromised.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/cp-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-1","slug":"ia-1","display_id":"IA-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ia_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ia_01_odp_03 }} identification and authentication policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the identification and authentication policy and the associated identification and authentication controls;\n"},{"id":"b","statement":"Designate an {{ ia_01_odp_04 }} to manage the development, documentation, and dissemination of the identification and authentication policy and procedures; and\n"},{"id":"c","statement":"Review and update the current identification and authentication:"},{"id":"c.1","statement":"Policy {{ ia_01_odp_05 }} and following {{ ia_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ia_01_odp_07 }} and following {{ ia_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"an identification and authentication policy is developed and documented;"},{"id":"a-2","statement":"the identification and authentication policy is disseminated to {{ ia_01_odp_01 }};\n"},{"id":"a-3","statement":"identification and authentication procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls are developed and documented;\n"},{"id":"a-4","statement":"the identification and authentication procedures are disseminated to {{ ia_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ ia_01_odp_03 }} identification and authentication policy addresses purpose;\n"},{"id":"a.1.a-2","statement":"the {{ ia_01_odp_03 }} identification and authentication policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2","slug":"ia-2","display_id":"IA-2","name":"Identification and Authentication (Organizational Users)","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"organizational users are uniquely identified and authenticated;"},{"id":"[02]","statement":"the unique identification of authenticated organizational users is associated with processes acting on behalf of those users.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-05-to-800-53-ia-2","source_ref":"control--ogrl-ac-05","target_ref":"requirement--nist-sp-800-53-r5-ia-2","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Universal MFA enforcement satisfies and strengthens organizational user authentication under IA-2.\n"},{"id":"mapping--ogrl-ac-13-to-800-53-ia-2","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Unique workforce identities authenticated through central SSO provide unique identification and authentication of organizational users.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-1","slug":"ia-2-1","display_id":"IA-2(1)","name":"Multi-factor Authentication to Privileged Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement multi-factor authentication for access to privileged accounts.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(01)","statement":"multi-factor authentication is implemented for access to privileged accounts."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-2","slug":"ia-2-2","display_id":"IA-2(2)","name":"Multi-factor Authentication to Non-privileged Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement multi-factor authentication for access to non-privileged accounts.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(02)","statement":"multi-factor authentication for access to non-privileged accounts is implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-3","slug":"ia-2-3","display_id":"IA-2(3)","name":"Local Access to Privileged Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-2-3_to_nist-sp-800-53-r5-ia-2-1","source_ref":"requirement--nist-sp-800-53-r5-ia-2-3","target_ref":"requirement--nist-sp-800-53-r5-ia-2-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-4","slug":"ia-2-4","display_id":"IA-2(4)","name":"Local Access to Non-privileged Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-2-4_to_nist-sp-800-53-r5-ia-2-2","source_ref":"requirement--nist-sp-800-53-r5-ia-2-4","target_ref":"requirement--nist-sp-800-53-r5-ia-2-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-5","slug":"ia-2-5","display_id":"IA-2(5)","name":"Individual Authentication with Group Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When shared accounts or authenticators are employed, require users to be individually authenticated before granting access to the shared accounts or resources.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(05)","statement":"users are required to be individually authenticated before granting access to the shared accounts or resources when shared accounts or authenticators are employed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-6","slug":"ia-2-6","display_id":"IA-2(6)","name":"Access to Accounts —separate Device","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement multi-factor authentication for {{ ia_02_06_odp_01 }} access to {{ ia_02_06_odp_02 }} such that:\n","citation":null,"parts":[{"id":"a","statement":"One of the factors is provided by a device separate from the system gaining access; and\n"},{"id":"b","statement":"The device meets {{ ia_02_06_odp_03 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"multi-factor authentication is implemented for {{ ia_02_06_odp_01 }} access to {{ ia_02_06_odp_02 }} such that one of the factors is provided by a device separate from the system gaining access;\n"},{"id":"b","statement":"multi-factor authentication is implemented for {{ ia_02_06_odp_01 }} access to {{ ia_02_06_odp_02 }} such that the device meets {{ ia_02_06_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-7","slug":"ia-2-7","display_id":"IA-2(7)","name":"Network Access to Non-privileged Accounts — Separate Device","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-2-7_to_nist-sp-800-53-r5-ia-2-6","source_ref":"requirement--nist-sp-800-53-r5-ia-2-7","target_ref":"requirement--nist-sp-800-53-r5-ia-2-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-8","slug":"ia-2-8","display_id":"IA-2(8)","name":"Access to Accounts — Replay Resistant","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement replay-resistant authentication mechanisms for access to {{ ia_02_08_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(08)","statement":"replay-resistant authentication mechanisms for access to {{ ia_02_08_odp }} are implemented.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-9","slug":"ia-2-9","display_id":"IA-2(9)","name":"Network Access to Non-privileged Accounts — Replay Resistant","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-2-9_to_nist-sp-800-53-r5-ia-2-8","source_ref":"requirement--nist-sp-800-53-r5-ia-2-9","target_ref":"requirement--nist-sp-800-53-r5-ia-2-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-10","slug":"ia-2-10","display_id":"IA-2(10)","name":"Single Sign-on","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide a single sign-on capability for {{ ia_02_10_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(10)","statement":"a single sign-on capability is provided for {{ ia_02_10_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-11","slug":"ia-2-11","display_id":"IA-2(11)","name":"Remote Access — Separate Device","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-2-11_to_nist-sp-800-53-r5-ia-2-6","source_ref":"requirement--nist-sp-800-53-r5-ia-2-11","target_ref":"requirement--nist-sp-800-53-r5-ia-2-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-12","slug":"ia-2-12","display_id":"IA-2(12)","name":"Acceptance of PIV Credentials","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Accept and electronically verify Personal Identity Verification-compliant credentials.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(12)","statement":"Personal Identity Verification-compliant credentials are accepted and electronically verified.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-2-13","slug":"ia-2-13","display_id":"IA-2(13)","name":"Out-of-band Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following out-of-band authentication mechanisms under {{ ia_02_13_odp_02 }}: {{ ia_02_13_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-02(13)","statement":"{{ ia_02_13_odp_01 }} mechanisms are implemented under {{ ia_02_13_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-2-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-3","slug":"ia-3","display_id":"IA-3","name":"Device Identification and Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Uniquely identify and authenticate {{ ia_03_odp_01 }} before establishing a {{ ia_03_odp_02 }} connection.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-03","statement":"{{ ia_03_odp_01 }} are uniquely identified and authenticated before establishing a {{ ia_03_odp_02 }} connection.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-3-1","slug":"ia-3-1","display_id":"IA-3(1)","name":"Cryptographic Bidirectional Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Authenticate {{ ia_03_01_odp_01 }} before establishing {{ ia_03_01_odp_02 }} connection using bidirectional authentication that is cryptographically based.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-03(01)","statement":"{{ ia_03_01_odp_01 }} are authenticated before establishing {{ ia_03_01_odp_02 }} connection using bidirectional authentication that is cryptographically based.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-3-2","slug":"ia-3-2","display_id":"IA-3(2)","name":"Cryptographic Bidirectional Network Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-3-2_to_nist-sp-800-53-r5-ia-3-1","source_ref":"requirement--nist-sp-800-53-r5-ia-3-2","target_ref":"requirement--nist-sp-800-53-r5-ia-3-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-3-3","slug":"ia-3-3","display_id":"IA-3(3)","name":"Dynamic Address Allocation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Where addresses are allocated dynamically, standardize dynamic address allocation lease information and the lease duration assigned to devices in accordance with {{ ia_3_3_prm_1 }} ; and\n"},{"id":"b","statement":"Audit lease information when assigned to a device."}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"dynamic address allocation lease information assigned to devices where addresses are allocated dynamically are standardized in accordance with {{ ia_03_03_odp_01 }};\n"},{"id":"a-2","statement":"dynamic address allocation lease duration assigned to devices where addresses are allocated dynamically are standardized in accordance with {{ ia_03_03_odp_02 }};\n"},{"id":"b","statement":"lease information is audited when assigned to a device."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-3-4","slug":"ia-3-4","display_id":"IA-3(4)","name":"Device Attestation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Handle device identification and authentication based on attestation by {{ ia_03_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-03(04)","statement":"device identification and authentication are handled based on attestation by {{ ia_03_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4","slug":"ia-4","display_id":"IA-4","name":"Identifier Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Manage system identifiers by:","citation":null,"parts":[{"id":"a","statement":"Receiving authorization from {{ ia_04_odp_01 }} to assign an individual, group, role, service, or device identifier;\n"},{"id":"b","statement":"Selecting an identifier that identifies an individual, group, role, service, or device;\n"},{"id":"c","statement":"Assigning the identifier to the intended individual, group, role, service, or device; and\n"},{"id":"d","statement":"Preventing reuse of identifiers for {{ ia_04_odp_02 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"system identifiers are managed by receiving authorization from {{ ia_04_odp_01 }} to assign to an individual, group, role, or device identifier;\n"},{"id":"b","statement":"system identifiers are managed by selecting an identifier that identifies an individual, group, role, service, or device;\n"},{"id":"c","statement":"system identifiers are managed by assigning the identifier to the intended individual, group, role, service, or device;\n"},{"id":"d","statement":"system identifiers are managed by preventing reuse of identifiers for {{ ia_04_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-13-to-800-53-ia-4-b","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-4#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Each identifier is selected to identify one specific individual.\n"},{"id":"mapping--ogrl-ac-13-to-800-53-ia-4-c","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-4#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Each unique identifier is assigned to the intended individual in the central identity provider.\n"},{"id":"mapping--ogrl-ac-13-to-800-53-ia-4-d","source_ref":"control--ogrl-ac-13","target_ref":"requirement--nist-sp-800-53-r5-ia-4#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ia_04_odp_02":"identifier_reuse_period"},"summary":"Retired identifiers are not reused for a defined period.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-1","slug":"ia-4-1","display_id":"IA-4(1)","name":"Prohibit Account Identifiers as Public Identifiers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-04(01)","statement":"the use of system account identifiers that are the same as public identifiers is prohibited for individual accounts.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-2","slug":"ia-4-2","display_id":"IA-4(2)","name":"Supervisor Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-4-2_to_nist-sp-800-53-r5-ia-12-1","source_ref":"requirement--nist-sp-800-53-r5-ia-4-2","target_ref":"requirement--nist-sp-800-53-r5-ia-12-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-3","slug":"ia-4-3","display_id":"IA-4(3)","name":"Multiple Forms of Certification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-4-3_to_nist-sp-800-53-r5-ia-12-2","source_ref":"requirement--nist-sp-800-53-r5-ia-4-3","target_ref":"requirement--nist-sp-800-53-r5-ia-12-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-4","slug":"ia-4-4","display_id":"IA-4(4)","name":"Identify User Status","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manage individual identifiers by uniquely identifying each individual as {{ ia_04_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-04(04)","statement":"individual identifiers are managed by uniquely identifying each individual as {{ ia_04_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-5","slug":"ia-4-5","display_id":"IA-4(5)","name":"Dynamic Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manage individual identifiers dynamically in accordance with {{ ia_04_05_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-04(05)","statement":"individual identifiers are dynamically managed in accordance with {{ ia_04_05_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-6","slug":"ia-4-6","display_id":"IA-4(6)","name":"Cross-organization Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate with the following external organizations for cross-organization management of identifiers: {{ ia_04_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-04(06)","statement":"cross-organization management of identifiers is coordinated with {{ ia_04_06_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-7","slug":"ia-4-7","display_id":"IA-4(7)","name":"In-person Registration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-4-7_to_nist-sp-800-53-r5-ia-12-4","source_ref":"requirement--nist-sp-800-53-r5-ia-4-7","target_ref":"requirement--nist-sp-800-53-r5-ia-12-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-8","slug":"ia-4-8","display_id":"IA-4(8)","name":"Pairwise Pseudonymous Identifiers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Generate pairwise pseudonymous identifiers.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-04(08)","statement":"pairwise pseudonymous identifiers are generated."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-4-9","slug":"ia-4-9","display_id":"IA-4(9)","name":"Attribute Maintenance and Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain the attributes for each uniquely identified individual, device, or service in {{ ia_04_09_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-04(09)","statement":"the attributes for each uniquely identified individual, device, or service are maintained in {{ ia_04_09_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-4-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5","slug":"ia-5","display_id":"IA-5","name":"Authenticator Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Manage system authenticators by:","citation":null,"parts":[{"id":"a","statement":"Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator;\n"},{"id":"b","statement":"Establishing initial authenticator content for any authenticators issued by the organization;\n"},{"id":"c","statement":"Ensuring that authenticators have sufficient strength of mechanism for their intended use;\n"},{"id":"d","statement":"Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators;\n"},{"id":"e","statement":"Changing default authenticators prior to first use;"},{"id":"f","statement":"Changing or refreshing authenticators {{ ia_05_odp_01 }} or when {{ ia_05_odp_02 }} occur;\n"},{"id":"g","statement":"Protecting authenticator content from unauthorized disclosure and modification;"},{"id":"h","statement":"Requiring individuals to take, and having devices implement, specific controls to protect authenticators; and\n"},{"id":"i","statement":"Changing authenticators for group or role accounts when membership to those accounts changes.\n"}],"objectives_count":10,"objectives_preview":[{"id":"a","statement":"system authenticators are managed through the verification of the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution;\n"},{"id":"b","statement":"system authenticators are managed through the establishment of initial authenticator content for any authenticators issued by the organization;\n"},{"id":"c","statement":"system authenticators are managed to ensure that authenticators have sufficient strength of mechanism for their intended use;\n"},{"id":"d","statement":"system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators;\n"},{"id":"e","statement":"system authenticators are managed through the change of default authenticators prior to first use;\n"},{"id":"f","statement":"system authenticators are managed through the change or refreshment of authenticators {{ ia_05_odp_01 }} or when {{ ia_05_odp_02 }} occur;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-06-to-800-53-ia-5-f","source_ref":"control--ogrl-ac-06","target_ref":"requirement--nist-sp-800-53-r5-ia-5#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ia_05_odp_01":"rotation_period","ia_05_odp_02":"revocation_triggers"},"summary":"Scheduled credential rotation and event-driven revocation directly satisfy NIST IA-5(f).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-1","slug":"ia-5-1","display_id":"IA-5(1)","name":"Password-based Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"For password-based authentication:","citation":null,"parts":[{"id":"a","statement":"Maintain a list of commonly-used, expected, or compromised passwords and update the list {{ ia_05_01_odp_01 }} and when organizational passwords are suspected to have been compromised directly or indirectly;\n"},{"id":"b","statement":"Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);\n"},{"id":"c","statement":"Transmit passwords only over cryptographically-protected channels;"},{"id":"d","statement":"Store passwords using an approved salted key derivation function, preferably using a keyed hash;\n"},{"id":"e","statement":"Require immediate selection of a new password upon account recovery;"},{"id":"f","statement":"Allow user selection of long passwords and passphrases, including spaces and all printable characters;\n"},{"id":"g","statement":"Employ automated tools to assist the user in selecting strong password authenticators; and\n"},{"id":"h","statement":"Enforce the following composition and complexity rules: {{ ia_05_01_odp_02 }}."}],"objectives_count":8,"objectives_preview":[{"id":"a","statement":"for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated {{ ia_05_01_odp_01 }} and when organizational passwords are suspected to have been compromised directly or indirectly;\n"},{"id":"b","statement":"for password-based authentication when passwords are created or updated by users, the passwords are verified not to be found on the list of commonly used, expected, or compromised passwords in IA-05(01)(a);\n"},{"id":"c","statement":"for password-based authentication, passwords are only transmitted over cryptographically protected channels;\n"},{"id":"d","statement":"for password-based authentication, passwords are stored using an approved salted key derivation function, preferably using a keyed hash;\n"},{"id":"e","statement":"for password-based authentication, immediate selection of a new password is required upon account recovery;\n"},{"id":"f","statement":"for password-based authentication, user selection of long passwords and passphrases is allowed, including spaces and all printable characters;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-14-to-800-53-ia-5-1","source_ref":"control--ogrl-ac-14","target_ref":"requirement--nist-sp-800-53-r5-ia-5-1","relationship":"subset-of","review_status":"reviewed","parameter_map":{"ia_05_01_odp_01":"blocklist_update_frequency","ia_05_01_odp_02":"password_composition_rules"},"summary":"Covers blocklist maintenance and checking, protected transmission and storage, reset on recovery, long passphrases, and composition rules; automated strength-assistance tooling is not required.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-2","slug":"ia-5-2","display_id":"IA-5(2)","name":"Public Key-based Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"For public key-based authentication:"},{"id":"a.1","statement":"Enforce authorized access to the corresponding private key; and"},{"id":"a.2","statement":"Map the authenticated identity to the account of the individual or group; and"},{"id":"b","statement":"When public key infrastructure (PKI) is used:"},{"id":"b.1","statement":"Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and\n"},{"id":"b.2","statement":"Implement a local cache of revocation data to support path discovery and validation.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a.1","statement":"authorized access to the corresponding private key is enforced for public key-based authentication;\n"},{"id":"a.2","statement":"the authenticated identity is mapped to the account of the individual or group for public key-based authentication;\n"},{"id":"b.1","statement":"when public key infrastructure (PKI) is used, certificates are validated by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information;\n"},{"id":"b.2","statement":"when public key infrastructure (PKI) is used, a local cache of revocation data is implemented to support path discovery and validation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-3","slug":"ia-5-3","display_id":"IA-5(3)","name":"In-person or Trusted External Party Registration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-5-3_to_nist-sp-800-53-r5-ia-12-4","source_ref":"requirement--nist-sp-800-53-r5-ia-5-3","target_ref":"requirement--nist-sp-800-53-r5-ia-12-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-4","slug":"ia-5-4","display_id":"IA-5(4)","name":"Automated Support for Password Strength Determination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-5-4_to_nist-sp-800-53-r5-ia-5-1","source_ref":"requirement--nist-sp-800-53-r5-ia-5-4","target_ref":"requirement--nist-sp-800-53-r5-ia-5-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-5","slug":"ia-5-5","display_id":"IA-5(5)","name":"Change Authenticators Prior to Delivery","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(05)","statement":"developers and installers of system components are required to provide unique authenticators or change default authenticators prior to delivery and installation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-6","slug":"ia-5-6","display_id":"IA-5(6)","name":"Protection of Authenticators","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(06)","statement":"authenticators are protected commensurate with the security category of the information to which use of the authenticator permits access.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-7","slug":"ia-5-7","display_id":"IA-5(7)","name":"No Embedded Unencrypted Static Authenticators","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(07)","statement":"unencrypted static authenticators are not embedded in applications or other forms of static storage.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-8","slug":"ia-5-8","display_id":"IA-5(8)","name":"Multiple System Accounts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ ia_05_08_odp }} to manage the risk of compromise due to individuals having accounts on multiple systems.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(08)","statement":"{{ ia_05_08_odp }} are implemented to manage the risk of compromise due to individuals having accounts on multiple systems.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-9","slug":"ia-5-9","display_id":"IA-5(9)","name":"Federated Credential Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use the following external organizations to federate credentials: {{ ia_05_09_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(09)","statement":"{{ ia_05_09_odp }} are used to federate credentials."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-10","slug":"ia-5-10","display_id":"IA-5(10)","name":"Dynamic Credential Binding","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Bind identities and authenticators dynamically using the following rules: {{ ia_05_10_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(10)","statement":"identities and authenticators are dynamically bound using {{ ia_05_10_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-11","slug":"ia-5-11","display_id":"IA-5(11)","name":"Hardware Token-based Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-5-11_to_nist-sp-800-53-r5-ia-2-1","source_ref":"requirement--nist-sp-800-53-r5-ia-5-11","target_ref":"requirement--nist-sp-800-53-r5-ia-2-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-ia-5-11_to_nist-sp-800-53-r5-ia-2-2","source_ref":"requirement--nist-sp-800-53-r5-ia-5-11","target_ref":"requirement--nist-sp-800-53-r5-ia-2-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-12","slug":"ia-5-12","display_id":"IA-5(12)","name":"Biometric Authentication Performance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements {{ ia_05_12_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(12)","statement":"mechanisms that satisfy {{ ia_05_12_odp }} are employed for biometric-based authentication.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-13","slug":"ia-5-13","display_id":"IA-5(13)","name":"Expiration of Cached Authenticators","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the use of cached authenticators after {{ ia_05_13_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(13)","statement":"the use of cached authenticators is prohibited after {{ ia_05_13_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-14","slug":"ia-5-14","display_id":"IA-5(14)","name":"Managing Content of PKI Trust Stores","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"For PKI-based authentication, employ an organization-wide methodology for managing the content of PKI trust stores installed across all platforms, including networks, operating systems, browsers, and applications.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(14)","statement":"an organization-wide methodology for managing the content of PKI trust stores is employed across all platforms, including networks, operating systems, browsers, and applications for PKI-based authentication.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-15","slug":"ia-5-15","display_id":"IA-5(15)","name":"GSA-approved Products and Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use only General Services Administration-approved products and services for identity, credential, and access management.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(15)","statement":"only General Services Administration-approved products and services are used for identity, credential, and access management.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-16","slug":"ia-5-16","display_id":"IA-5(16)","name":"In-person or Trusted External Party Authenticator Issuance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that the issuance of {{ ia_05_16_odp_01 }} be conducted {{ ia_05_16_odp_02 }} before {{ ia_05_16_odp_03 }} with authorization by {{ ia_05_16_odp_04 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(16)","statement":"the issuance of {{ ia_05_16_odp_01 }} is required to be conducted {{ ia_05_16_odp_02 }} before {{ ia_05_16_odp_03 }} with authorization by {{ ia_05_16_odp_04 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-17","slug":"ia-5-17","display_id":"IA-5(17)","name":"Presentation Attack Detection for Biometric Authenticators","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ presentation attack detection mechanisms for biometric-based authentication.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-05(17)","statement":"presentation attack detection mechanisms are employed for biometric-based authentication.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-5-18","slug":"ia-5-18","display_id":"IA-5(18)","name":"Password Managers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ {{ ia_05_18_odp_01 }} to generate and manage passwords; and"},{"id":"b","statement":"Protect the passwords using {{ ia_05_18_odp_02 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ ia_05_18_odp_01 }} are employed to generate and manage passwords;"},{"id":"b","statement":"the passwords are protected using {{ ia_05_18_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-5-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-6","slug":"ia-6","display_id":"IA-6","name":"Authentication Feedback","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-06","statement":"the feedback of authentication information is obscured during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-7","slug":"ia-7","display_id":"IA-7","name":"Cryptographic Module Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-07","statement":"mechanisms for authentication to a cryptographic module are implemented that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8","slug":"ia-8","display_id":"IA-8","name":"Identification and Authentication (Non-organizational Users)","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-08","statement":"non-organizational users or processes acting on behalf of non-organizational users are uniquely identified and authenticated.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-15-to-800-53-ia-8","source_ref":"control--ogrl-ac-15","target_ref":"requirement--nist-sp-800-53-r5-ia-8","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Individual customer accounts uniquely identify and authenticate non-organizational users, with added MFA, SSO, and recovery safeguards.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8-1","slug":"ia-8-1","display_id":"IA-8(1)","name":"Acceptance of PIV Credentials from Other Agencies","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Accept and electronically verify Personal Identity Verification-compliant credentials from other federal agencies.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ia-08(01).ia-08(01)[01]","statement":"Personal Identity Verification-compliant credentials from other federal agencies are accepted;\n"},{"id":"ia-08(01).ia-08(01)[02]","statement":"Personal Identity Verification-compliant credentials from other federal agencies are electronically verified.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8-2","slug":"ia-8-2","display_id":"IA-8(2)","name":"Acceptance of External Authenticators","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Accept only external authenticators that are NIST-compliant; and"},{"id":"b","statement":"Document and maintain a list of accepted external authenticators."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"only external authenticators that are NIST-compliant are accepted;"},{"id":"b-1","statement":"a list of accepted external authenticators is documented;"},{"id":"b-2","statement":"a list of accepted external authenticators is maintained."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8-3","slug":"ia-8-3","display_id":"IA-8(3)","name":"Use of FICAM-approved Products","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-8-3_to_nist-sp-800-53-r5-ia-8-2","source_ref":"requirement--nist-sp-800-53-r5-ia-8-3","target_ref":"requirement--nist-sp-800-53-r5-ia-8-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8-4","slug":"ia-8-4","display_id":"IA-8(4)","name":"Use of Defined Profiles","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Conform to the following profiles for identity management {{ ia_08_04_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-08(04)","statement":"there is conformance with {{ ia_08_04_odp }} for identity management."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8-5","slug":"ia-8-5","display_id":"IA-8(5)","name":"Acceptance of PIV-I Credentials","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Accept and verify federated or PKI credentials that meet {{ ia_08_05_odp }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ia-08(05).ia-08(05)[01]","statement":"federated or PKI credentials that meet {{ ia_08_05_odp }} are accepted;"},{"id":"ia-08(05).ia-08(05)[02]","statement":"federated or PKI credentials that meet {{ ia_08_05_odp }} are verified."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-8-6","slug":"ia-8-6","display_id":"IA-8(6)","name":"Disassociability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following measures to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties: {{ ia_08_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-08(06)","statement":"{{ ia_08_06_odp }} to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties are implemented.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-8-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-9","slug":"ia-9","display_id":"IA-9","name":"Service Identification and Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Uniquely identify and authenticate {{ ia_09_odp }} before establishing communications with devices, users, or other services or applications.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-09","statement":"{{ ia_09_odp }} are uniquely identified and authenticated before establishing communications with devices, users, or other services or applications.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-9-1","slug":"ia-9-1","display_id":"IA-9(1)","name":"Information Exchange","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-9-1_to_nist-sp-800-53-r5-ia-9","source_ref":"requirement--nist-sp-800-53-r5-ia-9-1","target_ref":"requirement--nist-sp-800-53-r5-ia-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-9-2","slug":"ia-9-2","display_id":"IA-9(2)","name":"Transmission of Decisions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ia-9-2_to_nist-sp-800-53-r5-ia-9","source_ref":"requirement--nist-sp-800-53-r5-ia-9-2","target_ref":"requirement--nist-sp-800-53-r5-ia-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-10","slug":"ia-10","display_id":"IA-10","name":"Adaptive Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require individuals accessing the system to employ {{ ia_10_odp_01 }} under specific {{ ia_10_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"individuals accessing the system are required to employ {{ ia_10_odp_01 }} under specific {{ ia_10_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-11","slug":"ia-11","display_id":"IA-11","name":"Re-authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require users to re-authenticate when {{ ia_11_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"users are required to re-authenticate when {{ ia_11_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12","slug":"ia-12","display_id":"IA-12","name":"Identity Proofing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines;\n"},{"id":"b","statement":"Resolve user identities to a unique individual; and"},{"id":"c","statement":"Collect, validate, and verify identity evidence."}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"users who require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines are identity proofed;\n"},{"id":"b","statement":"user identities are resolved to a unique individual;"},{"id":"c-1","statement":"identity evidence is collected;"},{"id":"c-2","statement":"identity evidence is validated;"},{"id":"c-3","statement":"identity evidence is verified."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12-1","slug":"ia-12-1","display_id":"IA-12(1)","name":"Supervisor Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that the registration process to receive an account for logical access includes supervisor or sponsor authorization.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-12(01)","statement":"the registration process to receive an account for logical access includes supervisor or sponsor authorization.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12-2","slug":"ia-12-2","display_id":"IA-12(2)","name":"Identity Evidence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require evidence of individual identification be presented to the registration authority.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-12(02)","statement":"evidence of individual identification is presented to the registration authority.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12-3","slug":"ia-12-3","display_id":"IA-12(3)","name":"Identity Evidence Validation and Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that the presented identity evidence be validated and verified through {{ ia_12_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-12(03)","statement":"the presented identity evidence is validated and verified through {{ ia_12_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12-4","slug":"ia-12-4","display_id":"IA-12(4)","name":"In-person Validation and Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that the validation and verification of identity evidence be conducted in person before a designated registration authority.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-12(04)","statement":"the validation and verification of identity evidence is conducted in person before a designated registration authority.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12-5","slug":"ia-12-5","display_id":"IA-12(5)","name":"Address Confirmation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that a {{ ia_12_05_odp }} be delivered through an out-of-band channel to verify the users address (physical or digital) of record.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-12(05)","statement":"a {{ ia_12_05_odp }} is delivered through an out-of-band channel to verify the user’s address (physical or digital) of record.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-12-6","slug":"ia-12-6","display_id":"IA-12(6)","name":"Accept Externally-proofed Identities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Accept externally-proofed identities at {{ ia_12_06_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ia-12(06)","statement":"externally proofed identities are accepted {{ ia_12_06_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-12-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-13","slug":"ia-13","display_id":"IA-13","name":"Identity Providers and Authorization Servers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ identity providers and authorization servers to manage user, device, and non-person entity (NPE) identities, attributes, and access rights supporting authentication and authorization decisions in accordance with {{ ia_13_odp_01 }} using {{ ia_13_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"_obj-1","statement":"identity providers are employed to manage user, device, and non-person entity (NPE) identities, attributes and access rights supporting authentication decisions in accordance with {{ ia_13_odp_02 }} using {{ ia_13_odp_02 }};\n"},{"id":"_obj-2","statement":"identity providers are employed to manage user, device, and non-person entity (NPE) identities, attributes and access rights supporting authorization decisions in accordance with {{ ia_13_odp_02 }} using {{ ia_13_odp_02 }};\n"},{"id":"_obj-3","statement":"authorization servers are employed to manage user, device, and non-person entity (NPE) identities, attributes and access rights supporting authentication decisions in accordance with {{ ia_13_odp_02 }} using {{ ia_13_odp_02 }};\n"},{"id":"_obj-4","statement":"authorization servers are employed to manage user, device, and non-person entity (NPE) identities, attributes and access rights supporting authorization decisions in accordance with {{ ia_13_odp_02 }} using {{ ia_13_odp_02 }};\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-13-1","slug":"ia-13-1","display_id":"IA-13(1)","name":"Protection of Cryptographic Keys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Cryptographic keys that protect access tokens are generated, managed, and protected from disclosure and misuse.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ia-13(01).ia-13(01)[01]","statement":"cryptographic keys that protect access tokens are generated;"},{"id":"ia-13(01).ia-13(01)[02]","statement":"cryptographic keys that protect access tokens are managed;"},{"id":"ia-13(01).ia-13(01)[03]","statement":"cryptographic keys that protect access tokens are protected from disclosure; and"},{"id":"ia-13(01).ia-13(01)[04]","statement":"cryptographic keys that protect access tokens are protected from disclosure and misuse\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-13-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-13-2","slug":"ia-13-2","display_id":"IA-13(2)","name":"Verification of Identity Assertions and Access Tokens","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"The source and integrity of identity assertions and access tokens are verified before granting access to system and information resources.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"ia-13(02).ia-13(02)[01]","statement":"the source of identity assertions is verified before granting access to system and information resources;\n"},{"id":"ia-13(02).ia-13(02)[02]","statement":"the source of access tokens is verified before granting access to system and information resources;\n"},{"id":"ia-13(02).ia-13(02)[03]","statement":"the integrity of identity assertions is verified before granting access to system and information resources;\n"},{"id":"ia-13(02).ia-13(02)[04]","statement":"the integrity of access tokens is verified before granting access to system and information resources\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-13-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ia-13-3","slug":"ia-13-3","display_id":"IA-13(3)","name":"Token Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"In accordance with {{ ia_13_odp_01 }}, assertions and access tokens are:","citation":null,"parts":[{"id":"a","statement":"generated;"},{"id":"b","statement":"issued;"},{"id":"c","statement":"refreshed;"},{"id":"d","statement":"revoked;"},{"id":"e","statement":"time-restricted; and"},{"id":"f","statement":"audience-restricted."}],"objectives_count":12,"objectives_preview":[{"id":"a-1","statement":"assertions are generated in accordance with {{ ia_13_odp_01 }};"},{"id":"a-2","statement":"access tokens are generated in accordance with {{ ia_13_odp_01 }};"},{"id":"b-1","statement":"assertions are issued in accordance with {{ ia_13_odp_01 }};"},{"id":"b-2","statement":"access tokens are issued in accordance with {{ ia_13_odp_01 }};"},{"id":"c-1","statement":"assertions are refreshed in accordance with {{ ia_13_odp_01 }};"},{"id":"c-2","statement":"access tokens are refreshed in accordance with {{ ia_13_odp_01 }};"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ia-13-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-1","slug":"ir-1","display_id":"IR-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ir_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ir_01_odp_03 }} incident response policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the incident response policy and the associated incident response controls;\n"},{"id":"b","statement":"Designate an {{ ir_01_odp_04 }} to manage the development, documentation, and dissemination of the incident response policy and procedures; and\n"},{"id":"c","statement":"Review and update the current incident response:"},{"id":"c.1","statement":"Policy {{ ir_01_odp_05 }} and following {{ ir_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ir_01_odp_07 }} and following {{ ir_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"an incident response policy is developed and documented;"},{"id":"a-2","statement":"the incident response policy is disseminated to {{ ir_01_odp_01 }};"},{"id":"a-3","statement":"incident response procedures to facilitate the implementation of the incident response policy and associated incident response controls are developed and documented;\n"},{"id":"a-4","statement":"the incident response procedures are disseminated to {{ ir_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ ir_01_odp_03 }} incident response policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ ir_01_odp_03 }} incident response policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-2","slug":"ir-2","display_id":"IR-2","name":"Incident Response Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide incident response training to system users consistent with assigned roles and responsibilities:\n"},{"id":"a.1","statement":"Within {{ ir_02_odp_01 }} of assuming an incident response role or responsibility or acquiring system access;\n"},{"id":"a.2","statement":"When required by system changes; and"},{"id":"a.3","statement":"{{ ir_02_odp_02 }} thereafter; and"},{"id":"b","statement":"Review and update incident response training content {{ ir_02_odp_03 }} and following {{ ir_02_odp_04 }}.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a.1","statement":"incident response training is provided to system users consistent with assigned roles and responsibilities within {{ ir_02_odp_01 }} of assuming an incident response role or responsibility or acquiring system access;\n"},{"id":"a.2","statement":"incident response training is provided to system users consistent with assigned roles and responsibilities when required by system changes;\n"},{"id":"a.3","statement":"incident response training is provided to system users consistent with assigned roles and responsibilities {{ ir_02_odp_02 }} thereafter;\n"},{"id":"b-1","statement":"incident response training content is reviewed and updated {{ ir_02_odp_03 }};"},{"id":"b-2","statement":"incident response training content is reviewed and updated following {{ ir_02_odp_04 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-2-1","slug":"ir-2-1","display_id":"IR-2(1)","name":"Simulated Events","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Incorporate simulated events into incident response training to facilitate the required response by personnel in crisis situations.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-02(01)","statement":"simulated events are incorporated into incident response training to facilitate the required response by personnel in crisis situations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-2-2","slug":"ir-2-2","display_id":"IR-2(2)","name":"Automated Training Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an incident response training environment using {{ ir_02_02_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-02(02)","statement":"an incident response training environment is provided using {{ ir_02_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-2-3","slug":"ir-2-3","display_id":"IR-2(3)","name":"Breach","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide incident response training on how to identify and respond to a breach, including the organization’s process for reporting a breach.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ir-02(03).ir-02(03)[01]","statement":"incident response training on how to identify and respond to a breach is provided;\n"},{"id":"ir-02(03).ir-02(03)[02]","statement":"incident response training on the organization’s process for reporting a breach is provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-3","slug":"ir-3","display_id":"IR-3","name":"Incident Response Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Test the effectiveness of the incident response capability for the system {{ ir_03_odp_01 }} using the following tests: {{ ir_03_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-03","statement":"the effectiveness of the incident response capability for the system is tested {{ ir_03_odp_01 }} using {{ ir_03_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-01-to-800-53-ir-3","source_ref":"control--ogrl-ir-01","target_ref":"requirement--nist-sp-800-53-r5-ir-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ir_03_odp_01":"ir_test_cadence","ir_03_odp_02":"ir_test_method"},"summary":"Scheduled tabletop exercises and drills directly satisfy NIST IR-3 incident response testing.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-3-1","slug":"ir-3-1","display_id":"IR-3(1)","name":"Automated Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test the incident response capability using {{ ir_03_01_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-03(01)","statement":"the incident response capability is tested using {{ ir_03_01_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-3-2","slug":"ir-3-2","display_id":"IR-3(2)","name":"Coordination with Related Plans","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate incident response testing with organizational elements responsible for related plans.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-03(02)","statement":"incident response testing is coordinated with organizational elements responsible for related plans.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-3-3","slug":"ir-3-3","display_id":"IR-3(3)","name":"Continuous Improvement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use qualitative and quantitative data from testing to:","citation":null,"parts":[{"id":"a","statement":"Determine the effectiveness of incident response processes;"},{"id":"b","statement":"Continuously improve incident response processes; and"},{"id":"c","statement":"Provide incident response measures and metrics that are accurate, consistent, and in a reproducible format.\n"}],"objectives_count":10,"objectives_preview":[{"id":"a-1","statement":"qualitative data from testing are used to determine the effectiveness of incident response processes;\n"},{"id":"a-2","statement":"quantitative data from testing are used to determine the effectiveness of incident response processes;\n"},{"id":"b-1","statement":"qualitative data from testing are used to continuously improve incident response processes;\n"},{"id":"b-2","statement":"quantitative data from testing are used to continuously improve incident response processes;\n"},{"id":"c-1","statement":"qualitative data from testing are used to provide incident response measures and metrics that are accurate;\n"},{"id":"c-2","statement":"quantitative data from testing are used to provide incident response measures and metrics that are accurate;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4","slug":"ir-4","display_id":"IR-4","name":"Incident Handling","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery;\n"},{"id":"b","statement":"Coordinate incident handling activities with contingency planning activities;"},{"id":"c","statement":"Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and\n"},{"id":"d","statement":"Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization.\n"}],"objectives_count":13,"objectives_preview":[{"id":"a-1","statement":"an incident handling capability for incidents is implemented that is consistent with the incident response plan;\n"},{"id":"a-2","statement":"the incident handling capability for incidents includes preparation;"},{"id":"a-3","statement":"the incident handling capability for incidents includes detection and analysis;"},{"id":"a-4","statement":"the incident handling capability for incidents includes containment;"},{"id":"a-5","statement":"the incident handling capability for incidents includes eradication;"},{"id":"a-6","statement":"the incident handling capability for incidents includes recovery;"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-02-to-800-53-ir-4-a","source_ref":"control--ogrl-ir-02","target_ref":"requirement--nist-sp-800-53-r5-ir-4#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Severity-based triage and plan-driven containment, eradication, and recovery implement the incident handling capability in IR-4(a).\n"},{"id":"mapping--ogrl-ir-02-to-800-53-ir-4-d","source_ref":"control--ogrl-ir-02","target_ref":"requirement--nist-sp-800-53-r5-ir-4#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A shared severity matrix and runbooks make incident handling consistent, contributing to the predictability IR-4(d) expects across the organization.\n"},{"id":"mapping--ogrl-ir-05-to-800-53-ir-4-c","source_ref":"control--ogrl-ir-05","target_ref":"requirement--nist-sp-800-53-r5-ir-4#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Post-incident reviews with tracked corrective actions feed lessons learned into procedures, training, and testing as IR-4(c) requires.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-1","slug":"ir-4-1","display_id":"IR-4(1)","name":"Automated Incident Handling Processes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Support the incident handling process using {{ ir_04_01_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(01)","statement":"the incident handling process is supported using {{ ir_04_01_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-2","slug":"ir-4-2","display_id":"IR-4(2)","name":"Dynamic Reconfiguration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include the following types of dynamic reconfiguration for {{ ir_04_02_odp_02 }} as part of the incident response capability: {{ ir_04_02_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(02)","statement":"{{ ir_04_02_odp_01 }} for {{ ir_04_02_odp_02 }} are included as part of the incident response capability.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-3","slug":"ir-4-3","display_id":"IR-4(3)","name":"Continuity of Operations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify {{ ir_04_03_odp_01 }} and take the following actions in response to those incidents to ensure continuation of organizational mission and business functions: {{ ir_04_03_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ir-04(03).ir-04(03)[01]","statement":"{{ ir_04_03_odp_01 }} are identified;"},{"id":"ir-04(03).ir-04(03)[02]","statement":"{{ ir_04_03_odp_02 }} are taken in response to those incidents (defined in IR-04(03)_ODP[01]) to ensure the continuation of organizational mission and business functions.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-4","slug":"ir-4-4","display_id":"IR-4(4)","name":"Information Correlation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(04)","statement":"incident information and individual incident responses are correlated to achieve an organization-wide perspective on incident awareness and response.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-5","slug":"ir-4-5","display_id":"IR-4(5)","name":"Automatic Disabling of System","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement a configurable capability to automatically disable the system if {{ ir_04_05_odp }} are detected.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(05)","statement":"a configurable capability is implemented to automatically disable the system if {{ ir_04_05_odp }} are detected.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-6","slug":"ir-4-6","display_id":"IR-4(6)","name":"Insider Threats","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement an incident handling capability for incidents involving insider threats.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(06)","statement":"an incident handling capability is implemented for incidents involving insider threats.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-7","slug":"ir-4-7","display_id":"IR-4(7)","name":"Insider Threats — Intra-organization Coordination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate an incident handling capability for insider threats that includes the following organizational entities {{ ir_04_07_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ir-04(07).ir-04(07)[01]","statement":"an incident handling capability is coordinated for insider threats;"},{"id":"ir-04(07).ir-04(07)[02]","statement":"the coordinated incident handling capability includes {{ ir_04_07_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-8","slug":"ir-4-8","display_id":"IR-4(8)","name":"Correlation with External Organizations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate with {{ ir_04_08_odp_01 }} to correlate and share {{ ir_04_08_odp_02 }} to achieve a cross-organization perspective on incident awareness and more effective incident responses.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(08)","statement":"there is coordination with {{ ir_04_08_odp_01 }} to correlate and share {{ ir_04_08_odp_02 }} to achieve a cross-organization perspective on incident awareness and more effective incident responses.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-9","slug":"ir-4-9","display_id":"IR-4(9)","name":"Dynamic Response Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ ir_04_09_odp }} to respond to incidents.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(09)","statement":"{{ ir_04_09_odp }} are employed to respond to incidents."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-10","slug":"ir-4-10","display_id":"IR-4(10)","name":"Supply Chain Coordination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Coordinate incident handling activities involving supply chain events with other organizations involved in the supply chain.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(10)","statement":"incident handling activities involving supply chain events are coordinated with other organizations involved in the supply chain.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-11","slug":"ir-4-11","display_id":"IR-4(11)","name":"Integrated Incident Response Team","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish and maintain an integrated incident response team that can be deployed to any location identified by the organization in {{ ir_04_11_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ir-04(11).ir-04(11)[01]","statement":"an integrated incident response team is established and maintained;"},{"id":"ir-04(11).ir-04(11)[02]","statement":"the integrated incident response team can be deployed to any location identified by the organization in {{ ir_04_11_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-12","slug":"ir-4-12","display_id":"IR-4(12)","name":"Malicious Code and Forensic Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Analyze malicious code and/or other residual artifacts remaining in the system after the incident.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ir-04(12).ir-04(12)[01]","statement":"malicious code remaining in the system is analyzed after the incident;"},{"id":"ir-04(12).ir-04(12)[02]","statement":"other residual artifacts remaining in the system (if any) are analyzed after the incident.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-13","slug":"ir-4-13","display_id":"IR-4(13)","name":"Behavior Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Analyze anomalous or suspected adversarial behavior in or related to {{ ir_04_13_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-04(13)","statement":"anomalous or suspected adversarial behavior in or related to {{ ir_04_13_odp }} are analyzed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-14","slug":"ir-4-14","display_id":"IR-4(14)","name":"Security Operations Center","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish and maintain a security operations center.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ir-04(14).ir-04(14)[01]","statement":"a security operations center is established;"},{"id":"ir-04(14).ir-04(14)[02]","statement":"a security operations center is maintained."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-4-15","slug":"ir-4-15","display_id":"IR-4(15)","name":"Public Relations and Reputation Repair","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Manage public relations associated with an incident; and"},{"id":"b","statement":"Employ measures to repair the reputation of the organization."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"public relations associated with an incident are managed;"},{"id":"b","statement":"measures are employed to repair the reputation of the organization."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-4-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-5","slug":"ir-5","display_id":"IR-5","name":"Incident Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Track and document incidents.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"incidents are tracked;"},{"id":"[02]","statement":"incidents are documented."}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-03-to-800-53-ir-5","source_ref":"control--ogrl-ir-03","target_ref":"requirement--nist-sp-800-53-r5-ir-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Recording every incident with required details through closure satisfies IR-5 incident tracking and documentation.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-5-1","slug":"ir-5-1","display_id":"IR-5(1)","name":"Automated Tracking, Data Collection, and Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Track incidents and collect and analyze incident information using {{ ir_5_1_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"ir-05(01).ir-05(01)[01]","statement":"incidents are tracked using {{ ir_05_01_odp_01 }};"},{"id":"ir-05(01).ir-05(01)[02]","statement":"incident information is collected using {{ ir_05_01_odp_02 }};"},{"id":"ir-05(01).ir-05(01)[03]","statement":"incident information is analyzed using {{ ir_05_01_odp_03 }}."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-6","slug":"ir-6","display_id":"IR-6","name":"Incident Reporting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require personnel to report suspected incidents to the organizational incident response capability within {{ ir_06_odp_01 }} ; and\n"},{"id":"b","statement":"Report incident information to {{ ir_06_odp_02 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"personnel is/are required to report suspected incidents to the organizational incident response capability within {{ ir_06_odp_01 }};\n"},{"id":"b","statement":"incident information is reported to {{ ir_06_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-04-to-800-53-ir-6-a","source_ref":"control--ogrl-ir-04","target_ref":"requirement--nist-sp-800-53-r5-ir-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ir_06_odp_01":"internal_report_window"},"summary":"Mandatory internal reporting of suspected incidents within a set window satisfies IR-6(a).\n"},{"id":"mapping--ogrl-ir-04-to-800-53-ir-6-b","source_ref":"control--ogrl-ir-04","target_ref":"requirement--nist-sp-800-53-r5-ir-6#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ir_06_odp_02":"external_notification_recipients"},"summary":"Reporting confirmed incidents to customers, regulators, and other required parties satisfies IR-6(b).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-6-1","slug":"ir-6-1","display_id":"IR-6(1)","name":"Automated Reporting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Report incidents using {{ ir_06_01_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-06(01)","statement":"incidents are reported using {{ ir_06_01_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-6-2","slug":"ir-6-2","display_id":"IR-6(2)","name":"Vulnerabilities Related to Incidents","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Report system vulnerabilities associated with reported incidents to {{ ir_06_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-06(02)","statement":"system vulnerabilities associated with reported incidents are reported to {{ ir_06_02_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-6-3","slug":"ir-6-3","display_id":"IR-6(3)","name":"Supply Chain Coordination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-06(03)","statement":"incident information is provided to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-7","slug":"ir-7","display_id":"IR-7","name":"Incident Response Assistance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide an incident response support resource, integral to the organizational incident response capability, that offers advice and assistance to users of the system for the handling and reporting of incidents.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"an incident response support resource, integral to the organizational incident response capability, is provided;\n"},{"id":"[02]","statement":"the incident response support resource offers advice and assistance to users of the system for the response and reporting of incidents.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-7-1","slug":"ir-7-1","display_id":"IR-7(1)","name":"Automation Support for Availability of Information and Support","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Increase the availability of incident response information and support using {{ ir_07_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-07(01)","statement":"the availability of incident response information and support is increased using {{ ir_07_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-7-2","slug":"ir-7-2","display_id":"IR-7(2)","name":"Coordination with External Providers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish a direct, cooperative relationship between its incident response capability and external providers of system protection capability; and\n"},{"id":"b","statement":"Identify organizational incident response team members to the external providers.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a direct, cooperative relationship is established between its incident response capability and external providers of the system protection capability;\n"},{"id":"b","statement":"organizational incident response team members are identified to the external providers.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-8","slug":"ir-8","display_id":"IR-8","name":"Incident Response Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop an incident response plan that:"},{"id":"a.1","statement":"Provides the organization with a roadmap for implementing its incident response capability;\n"},{"id":"a.2","statement":"Describes the structure and organization of the incident response capability;"},{"id":"a.3","statement":"Provides a high-level approach for how the incident response capability fits into the overall organization;\n"},{"id":"a.4","statement":"Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;\n"},{"id":"a.5","statement":"Defines reportable incidents;"},{"id":"a.6","statement":"Provides metrics for measuring the incident response capability within the organization;\n"},{"id":"a.7","statement":"Defines the resources and management support needed to effectively maintain and mature an incident response capability;\n"},{"id":"a.8","statement":"Addresses the sharing of incident information;"},{"id":"a.9","statement":"Is reviewed and approved by {{ ir_08_odp_01 }} {{ ir_08_odp_02 }} ; and"},{"id":"a.10","statement":"Explicitly designates responsibility for incident response to {{ ir_08_odp_03 }}.\n"},{"id":"b","statement":"Distribute copies of the incident response plan to {{ ir_08_odp_04 }};"},{"id":"c","statement":"Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing;\n"},{"id":"d","statement":"Communicate incident response plan changes to {{ ir_8_prm_5 }} ; and"},{"id":"e","statement":"Protect the incident response plan from unauthorized disclosure and modification.\n"}],"objectives_count":17,"objectives_preview":[{"id":"a.1","statement":"an incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability;\n"},{"id":"a.2","statement":"an incident response plan is developed that describes the structure and organization of the incident response capability;\n"},{"id":"a.3","statement":"an incident response plan is developed that provides a high-level approach for how the incident response capability fits into the overall organization;\n"},{"id":"a.4","statement":"an incident response plan is developed that meets the unique requirements of the organization with regard to mission, size, structure, and functions;\n"},{"id":"a.5","statement":"an incident response plan is developed that defines reportable incidents;"},{"id":"a.6","statement":"an incident response plan is developed that provides metrics for measuring the incident response capability within the organization;\n"}],"params_count":8,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-8-1","slug":"ir-8-1","display_id":"IR-8(1)","name":"Breaches","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include the following in the Incident Response Plan for breaches involving personally identifiable information:\n","citation":null,"parts":[{"id":"a","statement":"A process to determine if notice to individuals or other organizations, including oversight organizations, is needed;\n"},{"id":"b","statement":"An assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms; and\n"},{"id":"c","statement":"Identification of applicable privacy requirements."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the incident response plan for breaches involving personally identifiable information includes a process to determine if notice to individuals or other organizations, including oversight organizations, is needed;\n"},{"id":"b","statement":"the incident response plan for breaches involving personally identifiable information includes an assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms;\n"},{"id":"c","statement":"the incident response plan for breaches involving personally identifiable information includes the identification of applicable privacy requirements.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-06-to-800-53-ir-8-1","source_ref":"control--ogrl-ir-06","target_ref":"requirement--nist-sp-800-53-r5-ir-8-1","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"The documented breach procedure covers notification determination, harm assessment and mitigation, and applicable privacy requirements, and additionally requires executing notifications.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-9","slug":"ir-9","display_id":"IR-9","name":"Information Spillage Response","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Respond to information spills by:","citation":null,"parts":[{"id":"a","statement":"Assigning {{ ir_09_odp_01 }} with responsibility for responding to information spills;\n"},{"id":"b","statement":"Identifying the specific information involved in the system contamination;"},{"id":"c","statement":"Alerting {{ ir_09_odp_02 }} of the information spill using a method of communication not associated with the spill;\n"},{"id":"d","statement":"Isolating the contaminated system or system component;"},{"id":"e","statement":"Eradicating the information from the contaminated system or component;"},{"id":"f","statement":"Identifying other systems or system components that may have been subsequently contaminated; and\n"},{"id":"g","statement":"Performing the following additional actions: {{ ir_09_odp_03 }}."}],"objectives_count":7,"objectives_preview":[{"id":"a","statement":"{{ ir_09_odp_01 }} is/are assigned the responsibility to respond to information spills;\n"},{"id":"b","statement":"the specific information involved in the system contamination is identified in response to information spills;\n"},{"id":"c","statement":"{{ ir_09_odp_02 }} is/are alerted of the information spill using a method of communication not associated with the spill;\n"},{"id":"d","statement":"the contaminated system or system component is isolated in response to information spills;\n"},{"id":"e","statement":"the information is eradicated from the contaminated system or component in response to information spills;\n"},{"id":"f","statement":"other systems or system components that may have been subsequently contaminated are identified in response to information spills;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-9-1","slug":"ir-9-1","display_id":"IR-9(1)","name":"Responsible Personnel","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ir-9-1_to_nist-sp-800-53-r5-ir-9","source_ref":"requirement--nist-sp-800-53-r5-ir-9-1","target_ref":"requirement--nist-sp-800-53-r5-ir-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-9-2","slug":"ir-9-2","display_id":"IR-9(2)","name":"Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide information spillage response training {{ ir_09_02_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-09(02)","statement":"information spillage response training is provided {{ ir_09_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-9-3","slug":"ir-9-3","display_id":"IR-9(3)","name":"Post-spill Operations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following procedures to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions: {{ ir_09_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-09(03)","statement":"{{ ir_09_03_odp }} are implemented to ensure that organizational personnel impacted by information spills can continue to carry out assigned tasks while contaminated systems are undergoing corrective actions.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-9-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-9-4","slug":"ir-9-4","display_id":"IR-9(4)","name":"Exposure to Unauthorized Personnel","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following controls for personnel exposed to information not within assigned access authorizations: {{ ir_09_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ir-09(04)","statement":"{{ ir_09_04_odp }} are employed for personnel exposed to information not within assigned access authorizations.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-9-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ir-10","slug":"ir-10","display_id":"IR-10","name":"Integrated Information Security Analysis Team","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ir-10_to_nist-sp-800-53-r5-ir-4-11","source_ref":"requirement--nist-sp-800-53-r5-ir-10","target_ref":"requirement--nist-sp-800-53-r5-ir-4-11","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ir-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-1","slug":"ma-1","display_id":"MA-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ma_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ma_01_odp_03 }} maintenance policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the maintenance policy and the associated maintenance controls;\n"},{"id":"b","statement":"Designate an {{ ma_01_odp_04 }} to manage the development, documentation, and dissemination of the maintenance policy and procedures; and\n"},{"id":"c","statement":"Review and update the current maintenance:"},{"id":"c.1","statement":"Policy {{ ma_01_odp_05 }} and following {{ ma_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ma_01_odp_07 }} and following {{ ma_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a maintenance policy is developed and documented;"},{"id":"a-2","statement":"the maintenance policy is disseminated to {{ ma_01_odp_01 }};"},{"id":"a-3","statement":"maintenance procedures to facilitate the implementation of the maintenance policy and associated maintenance controls are developed and documented;\n"},{"id":"a-4","statement":"the maintenance procedures are disseminated to {{ ma_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ ma_01_odp_03 }} maintenance policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ ma_01_odp_03 }} maintenance policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-2","slug":"ma-2","display_id":"MA-2","name":"Controlled Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Schedule, document, and review records of maintenance, repair, and replacement on system components in accordance with manufacturer or vendor specifications and/or organizational requirements;\n"},{"id":"b","statement":"Approve and monitor all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location;\n"},{"id":"c","statement":"Require that {{ ma_02_odp_01 }} explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement;\n"},{"id":"d","statement":"Sanitize equipment to remove the following information from associated media prior to removal from organizational facilities for off-site maintenance, repair, or replacement: {{ ma_02_odp_02 }};\n"},{"id":"e","statement":"Check all potentially impacted controls to verify that the controls are still functioning properly following maintenance, repair, or replacement actions; and\n"},{"id":"f","statement":"Include the following information in organizational maintenance records: {{ ma_02_odp_03 }}.\n"}],"objectives_count":9,"objectives_preview":[{"id":"a-1","statement":"maintenance, repair, and replacement of system components are scheduled in accordance with manufacturer or vendor specifications and/or organizational requirements;\n"},{"id":"a-2","statement":"maintenance, repair, and replacement of system components are documented in accordance with manufacturer or vendor specifications and/or organizational requirements;\n"},{"id":"a-3","statement":"records of maintenance, repair, and replacement of system components are reviewed in accordance with manufacturer or vendor specifications and/or organizational requirements;\n"},{"id":"b-1","statement":"all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are approved;\n"},{"id":"b-2","statement":"all maintenance activities, whether performed on site or remotely and whether the system or system components are serviced on site or removed to another location, are monitored;\n"},{"id":"c","statement":"{{ ma_02_odp_01 }} is/are required to explicitly approve the removal of the system or system components from organizational facilities for off-site maintenance, repair, or replacement;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-a","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Scheduling maintenance to vendor specifications and reviewing records satisfies MA-2(a).\n"},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-b","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#b","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Approval of maintenance activities covers MA-2(b) except explicit monitoring of each activity.\n"},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-c","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ma_02_odp_01":"maintenance_approver"},"summary":"Required approval before off-site removal for service satisfies MA-2(c)."},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-e","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Post-maintenance verification of affected safeguards satisfies MA-2(e)."},{"id":"mapping--ogrl-ps-07-to-800-53-ma-2-f","source_ref":"control--ogrl-ps-07","target_ref":"requirement--nist-sp-800-53-r5-ma-2#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ma_02_odp_03":"maintenance_record_contents"},"summary":"Defined maintenance record contents satisfy MA-2(f)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-2-1","slug":"ma-2-1","display_id":"MA-2(1)","name":"Record Content","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ma-2-1_to_nist-sp-800-53-r5-ma-2","source_ref":"requirement--nist-sp-800-53-r5-ma-2-1","target_ref":"requirement--nist-sp-800-53-r5-ma-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-2-2","slug":"ma-2-2","display_id":"MA-2(2)","name":"Automated Maintenance Activities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Schedule, conduct, and document maintenance, repair, and replacement actions for the system using {{ ma_2_2_prm_1 }} ; and\n"},{"id":"b","statement":"Produce up-to date, accurate, and complete records of all maintenance, repair, and replacement actions requested, scheduled, in process, and completed.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"{{ ma_02_02_odp_01 }} are used to schedule maintenance, repair, and replacement actions for the system;\n"},{"id":"a-2","statement":"{{ ma_02_02_odp_02 }} are used to conduct maintenance, repair, and replacement actions for the system;\n"},{"id":"a-3","statement":"{{ ma_02_02_odp_03 }} are used to document maintenance, repair, and replacement actions for the system;\n"},{"id":"b-1","statement":"up-to date, accurate, and complete records of all maintenance actions requested, scheduled, in process, and completed are produced.\n"},{"id":"b-2","statement":"up-to date, accurate, and complete records of all repair actions requested, scheduled, in process, and completed are produced.\n"},{"id":"b-3","statement":"up-to date, accurate, and complete records of all replacement actions requested, scheduled, in process, and completed are produced.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3","slug":"ma-3","display_id":"MA-3","name":"Maintenance Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve, control, and monitor the use of system maintenance tools; and"},{"id":"b","statement":"Review previously approved system maintenance tools {{ ma_03_odp }}."}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"the use of system maintenance tools is approved;"},{"id":"a-2","statement":"the use of system maintenance tools is controlled;"},{"id":"a-3","statement":"the use of system maintenance tools is monitored;"},{"id":"b","statement":"previously approved system maintenance tools are reviewed {{ ma_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3-1","slug":"ma-3-1","display_id":"MA-3(1)","name":"Inspect Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-03(01)","statement":"maintenance tools used by maintenance personnel are inspected for improper or unauthorized modifications.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3-2","slug":"ma-3-2","display_id":"MA-3(2)","name":"Inspect Media","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Check media containing diagnostic and test programs for malicious code before the media are used in the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-03(02)","statement":"media containing diagnostic and test programs are checked for malicious code before the media are used in the system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3-3","slug":"ma-3-3","display_id":"MA-3(3)","name":"Prevent Unauthorized Removal","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent the removal of maintenance equipment containing organizational information by:\n","citation":null,"parts":[{"id":"a","statement":"Verifying that there is no organizational information contained on the equipment;\n"},{"id":"b","statement":"Sanitizing or destroying the equipment;"},{"id":"c","statement":"Retaining the equipment within the facility; or"},{"id":"d","statement":"Obtaining an exemption from {{ ma_03_03_odp }} explicitly authorizing removal of the equipment from the facility.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"the removal of maintenance equipment containing organizational information is prevented by verifying that there is no organizational information contained on the equipment; or\n"},{"id":"b","statement":"the removal of maintenance equipment containing organizational information is prevented by sanitizing or destroying the equipment; or\n"},{"id":"c","statement":"the removal of maintenance equipment containing organizational information is prevented by retaining the equipment within the facility; or\n"},{"id":"d","statement":"the removal of maintenance equipment containing organizational information is prevented by obtaining an exemption from {{ ma_03_03_odp }} explicitly authorizing removal of the equipment from the facility.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3-4","slug":"ma-3-4","display_id":"MA-3(4)","name":"Restricted Tool Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the use of maintenance tools to authorized personnel only.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-03(04)","statement":"the use of maintenance tools is restricted to authorized personnel only."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3-5","slug":"ma-3-5","display_id":"MA-3(5)","name":"Execution with Privilege","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Monitor the use of maintenance tools that execute with increased privilege.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-03(05)","statement":"the use of maintenance tools that execute with increased privilege is monitored."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-3-6","slug":"ma-3-6","display_id":"MA-3(6)","name":"Software Updates and Patches","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Inspect maintenance tools to ensure the latest software updates and patches are installed.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-03(06)","statement":"maintenance tools are inspected to ensure that the latest software updates and patches are installed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-3-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4","slug":"ma-4","display_id":"MA-4","name":"Nonlocal Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve and monitor nonlocal maintenance and diagnostic activities;"},{"id":"b","statement":"Allow the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the system;\n"},{"id":"c","statement":"Employ strong authentication in the establishment of nonlocal maintenance and diagnostic sessions;\n"},{"id":"d","statement":"Maintain records for nonlocal maintenance and diagnostic activities; and"},{"id":"e","statement":"Terminate session and network connections when nonlocal maintenance is completed.\n"}],"objectives_count":8,"objectives_preview":[{"id":"a-1","statement":"nonlocal maintenance and diagnostic activities are approved;"},{"id":"a-2","statement":"nonlocal maintenance and diagnostic activities are monitored;"},{"id":"b-1","statement":"the use of nonlocal maintenance and diagnostic tools are allowed only as consistent with organizational policy;\n"},{"id":"b-2","statement":"the use of nonlocal maintenance and diagnostic tools are documented in the security plan for the system;\n"},{"id":"c","statement":"strong authentication is employed in the establishment of nonlocal maintenance and diagnostic sessions;\n"},{"id":"d","statement":"records for nonlocal maintenance and diagnostic activities are maintained;"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-1","slug":"ma-4-1","display_id":"MA-4(1)","name":"Logging and Review","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Log {{ ma_4_1_prm_1 }} for nonlocal maintenance and diagnostic sessions; and"},{"id":"b","statement":"Review the audit records of the maintenance and diagnostic sessions to detect anomalous behavior.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"{{ ma_04_01_odp_01 }} are logged for nonlocal maintenance sessions;"},{"id":"a-2","statement":"{{ ma_04_01_odp_02 }} are logged for nonlocal diagnostic sessions;"},{"id":"b-1","statement":"the audit records of the maintenance sessions are reviewed to detect anomalous behavior;\n"},{"id":"b-2","statement":"the audit records of the diagnostic sessions are reviewed to detect anomalous behavior.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-2","slug":"ma-4-2","display_id":"MA-4(2)","name":"Document Nonlocal Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ma-4-2_to_nist-sp-800-53-r5-ma-1","source_ref":"requirement--nist-sp-800-53-r5-ma-4-2","target_ref":"requirement--nist-sp-800-53-r5-ma-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-ma-4-2_to_nist-sp-800-53-r5-ma-4","source_ref":"requirement--nist-sp-800-53-r5-ma-4-2","target_ref":"requirement--nist-sp-800-53-r5-ma-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-3","slug":"ma-4-3","display_id":"MA-4(3)","name":"Comparable Security and Sanitization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require that nonlocal maintenance and diagnostic services be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced; or\n"},{"id":"b","statement":"Remove the component to be serviced from the system prior to nonlocal maintenance or diagnostic services; sanitize the component (for organizational information); and after the service is performed, inspect and sanitize the component (for potentially malicious software) before reconnecting the component to the system.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"nonlocal maintenance services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced;\n"},{"id":"a-2","statement":"nonlocal diagnostic services are required to be performed from a system that implements a security capability comparable to the capability implemented on the system being serviced; or\n"},{"id":"b-1","statement":"the component to be serviced is removed from the system prior to nonlocal maintenance or diagnostic services;\n"},{"id":"b-2","statement":"the component to be serviced is sanitized (for organizational information);"},{"id":"b-3","statement":"the component is inspected and sanitized (for potentially malicious software) after the service is performed and before reconnecting the component to the system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-4","slug":"ma-4-4","display_id":"MA-4(4)","name":"Authentication and Separation of Maintenance Sessions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect nonlocal maintenance sessions by:","citation":null,"parts":[{"id":"a","statement":"Employing {{ ma_04_04_odp }} ; and"},{"id":"b","statement":"Separating the maintenance sessions from other network sessions with the system by either:\n"},{"id":"b.1","statement":"Physically separated communications paths; or"},{"id":"b.2","statement":"Logically separated communications paths."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"nonlocal maintenance sessions are protected by employing {{ ma_04_04_odp }};"},{"id":"b.1","statement":"nonlocal maintenance sessions are protected by separating maintenance sessions from other network sessions with the system by physically separated communication paths; or\n"},{"id":"b.2","statement":"nonlocal maintenance sessions are protected by logically separated communication paths.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-5","slug":"ma-4-5","display_id":"MA-4(5)","name":"Approvals and Notifications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require the approval of each nonlocal maintenance session by {{ ma_04_05_odp_01 }} ; and\n"},{"id":"b","statement":"Notify the following personnel or roles of the date and time of planned nonlocal maintenance: {{ ma_04_05_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the approval of each nonlocal maintenance session is required by {{ ma_04_05_odp_01 }};\n"},{"id":"b","statement":"{{ ma_04_05_odp_02 }} is/are notified of the date and time of planned nonlocal maintenance.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-6","slug":"ma-4-6","display_id":"MA-4(6)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications: {{ ma_04_06_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ma-04(06).ma-04(06)[01]","statement":"{{ ma_04_06_odp }} are implemented to protect the integrity of nonlocal maintenance and diagnostic communications;\n"},{"id":"ma-04(06).ma-04(06)[02]","statement":"{{ ma_04_06_odp }} are implemented to protect the confidentiality of nonlocal maintenance and diagnostic communications.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-4-7","slug":"ma-4-7","display_id":"MA-4(7)","name":"Disconnect Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify session and network connection termination after the completion of nonlocal maintenance and diagnostic sessions.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ma-04(07).ma-04(07)[01]","statement":"session connection termination is verified after the completion of nonlocal maintenance and diagnostic sessions;\n"},{"id":"ma-04(07).ma-04(07)[02]","statement":"network connection termination is verified after the completion of nonlocal maintenance and diagnostic sessions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-4-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-5","slug":"ma-5","display_id":"MA-5","name":"Maintenance Personnel","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish a process for maintenance personnel authorization and maintain a list of authorized maintenance organizations or personnel;\n"},{"id":"b","statement":"Verify that non-escorted personnel performing maintenance on the system possess the required access authorizations; and\n"},{"id":"c","statement":"Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"a process for maintenance personnel authorization is established;"},{"id":"a-2","statement":"a list of authorized maintenance organizations or personnel is maintained;"},{"id":"b","statement":"non-escorted personnel performing maintenance on the system possess the required access authorizations;\n"},{"id":"c","statement":"organizational personnel with required access authorizations and technical competence is/are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-5-1","slug":"ma-5-1","display_id":"MA-5(1)","name":"Individuals Without Appropriate Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:\n"},{"id":"a.1","statement":"Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified; and\n"},{"id":"a.2","statement":"Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and\n"},{"id":"b","statement":"Develop and implement {{ ma_05_01_odp }} in the event a system component cannot be sanitized, removed, or disconnected from the system.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a.1","statement":"procedures for the use of maintenance personnel who lack appropriate security clearances or are not U.S. citizens are implemented and include approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified escorting and supervising maintenance personnel without the needed access authorization during the performance of maintenance and diagnostic activities;\n"},{"id":"a.2","statement":"procedures for the use of maintenance personnel who lack appropriate security clearances or are not U.S. citizens are implemented and include all volatile information storage components within the system being sanitized and all non-volatile storage media being removed or physically disconnected from the system and secured prior to initiating maintenance or diagnostic activities;\n"},{"id":"b","statement":"{{ ma_05_01_odp }} are developed and implemented in the event that a system cannot be sanitized, removed, or disconnected from the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-5-2","slug":"ma-5-2","display_id":"MA-5(2)","name":"Security Clearances for Classified Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances and formal access approvals for at least the highest classification level and for compartments of information on the system.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ma-05(02).ma-05(02)[01]","statement":"personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess security clearances for at least the highest classification level and for compartments of information on the system;\n"},{"id":"ma-05(02).ma-05(02)[02]","statement":"personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information possess formal access approvals for at least the highest classification level and for compartments of information on the system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-5-3","slug":"ma-5-3","display_id":"MA-5(3)","name":"Citizenship Requirements for Classified Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are U.S. citizens.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-05(03)","statement":"personnel performing maintenance and diagnostic activities on a system processing, storing, or transmitting classified information are U.S. citizens.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-5-4","slug":"ma-5-4","display_id":"MA-5(4)","name":"Foreign Nationals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure that:","citation":null,"parts":[{"id":"a","statement":"Foreign nationals with appropriate security clearances are used to conduct maintenance and diagnostic activities on classified systems only when the systems are jointly owned and operated by the United States and foreign allied governments, or owned and operated solely by foreign allied governments; and\n"},{"id":"b","statement":"Approvals, consents, and detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"foreign nationals with appropriate security clearances are used to conduct maintenance and diagnostic activities on classified systems only when the systems are jointly owned and operated by the United States and foreign allied governments or owned and operated solely by foreign allied governments;\n"},{"id":"b-1","statement":"approvals regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements;\n"},{"id":"b-2","statement":"consents regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements;\n"},{"id":"b-3","statement":"detailed operational conditions regarding the use of foreign nationals to conduct maintenance and diagnostic activities on classified systems are fully documented within Memoranda of Agreements.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-5-5","slug":"ma-5-5","display_id":"MA-5(5)","name":"Non-system Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure that non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system, have required access authorizations.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-05(05)","statement":"non-escorted personnel performing maintenance activities not directly associated with the system but in the physical proximity of the system have required access authorizations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-5-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-6","slug":"ma-6","display_id":"MA-6","name":"Timely Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Obtain maintenance support and/or spare parts for {{ ma_06_odp_01 }} within {{ ma_06_odp_02 }} of failure.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-06","statement":"maintenance support and/or spare parts are obtained for {{ ma_06_odp_01 }} within {{ ma_06_odp_02 }} of failure.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-6-1","slug":"ma-6-1","display_id":"MA-6(1)","name":"Preventive Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform preventive maintenance on {{ ma_06_01_odp_01 }} at {{ ma_06_01_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-06(01)","statement":"preventive maintenance is performed on {{ ma_06_01_odp_01 }} at {{ ma_06_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-6-2","slug":"ma-6-2","display_id":"MA-6(2)","name":"Predictive Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform predictive maintenance on {{ ma_06_02_odp_01 }} at {{ ma_06_02_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-06(02)","statement":"predictive maintenance is performed on {{ ma_06_02_odp_01 }} at {{ ma_06_02_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-6-3","slug":"ma-6-3","display_id":"MA-6(3)","name":"Automated Support for Predictive Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Transfer predictive maintenance data to a maintenance management system using {{ ma_06_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-06(03)","statement":"predictive maintenance data is transferred to a maintenance management system using {{ ma_06_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ma-7","slug":"ma-7","display_id":"MA-7","name":"Field Maintenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Restrict or prohibit field maintenance on {{ ma_07_odp_01 }} to {{ ma_07_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ma-07","statement":"field maintenance on {{ ma_07_odp_01 }} are restricted or prohibited to {{ ma_07_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ma-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-1","slug":"mp-1","display_id":"MP-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ mp_1_prm_1 }}:"},{"id":"a.1","statement":"{{ mp_01_odp_03 }} media protection policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the media protection policy and the associated media protection controls;\n"},{"id":"b","statement":"Designate an {{ mp_01_odp_04 }} to manage the development, documentation, and dissemination of the media protection policy and procedures; and\n"},{"id":"c","statement":"Review and update the current media protection:"},{"id":"c.1","statement":"Policy {{ mp_01_odp_05 }} and following {{ mp_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ mp_01_odp_07 }} and following {{ mp_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a media protection policy is developed and documented;"},{"id":"a-2","statement":"the media protection policy is disseminated to {{ mp_01_odp_01 }};"},{"id":"a-3","statement":"media protection procedures to facilitate the implementation of the media protection policy and associated media protection controls are developed and documented;\n"},{"id":"a-4","statement":"the media protection procedures are disseminated to {{ mp_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ mp_01_odp_03 }} media protection policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ mp_01_odp_03 }} media protection policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-2","slug":"mp-2","display_id":"MP-2","name":"Media Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Restrict access to {{ mp_2_prm_1 }} to {{ mp_2_prm_2 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"access to {{ mp_02_odp_01 }} is restricted to {{ mp_02_odp_02 }};"},{"id":"[02]","statement":"access to {{ mp_02_odp_03 }} is restricted to {{ mp_02_odp_04 }}."}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-2-1","slug":"mp-2-1","display_id":"MP-2(1)","name":"Automated Restricted Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-2-1_to_nist-sp-800-53-r5-mp-4-2","source_ref":"requirement--nist-sp-800-53-r5-mp-2-1","target_ref":"requirement--nist-sp-800-53-r5-mp-4-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-2-2","slug":"mp-2-2","display_id":"MP-2(2)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-2-2_to_nist-sp-800-53-r5-sc-28-1","source_ref":"requirement--nist-sp-800-53-r5-mp-2-2","target_ref":"requirement--nist-sp-800-53-r5-sc-28-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-3","slug":"mp-3","display_id":"MP-3","name":"Media Marking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and\n"},{"id":"b","statement":"Exempt {{ mp_03_odp_01 }} from marking if the media remain within {{ mp_03_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"system media is marked to indicate distribution limitations, handling caveats, and applicable security markings (if any) of the information;\n"},{"id":"b","statement":"{{ mp_03_odp_01 }} remain within {{ mp_03_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-4","slug":"mp-4","display_id":"MP-4","name":"Media Storage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Physically control and securely store {{ mp_4_prm_1 }} within {{ mp_4_prm_2 }} ; and\n"},{"id":"b","statement":"Protect system media types defined in MP-4a until the media are destroyed or sanitized using approved equipment, techniques, and procedures.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"{{ mp_04_odp_01 }} are physically controlled;"},{"id":"a-2","statement":"{{ mp_04_odp_02 }} are physically controlled;"},{"id":"a-3","statement":"{{ mp_04_odp_03 }} are securely stored within {{ mp_04_odp_05 }};"},{"id":"a-4","statement":"{{ mp_04_odp_04 }} are securely stored within {{ mp_04_odp_06 }};"},{"id":"b","statement":"system media types (defined in MP-04_ODP[01], MP-04_ODP[02], MP-04_ODP[03], MP-04_ODP[04]) are protected until the media are destroyed or sanitized using approved equipment, techniques, and procedures.\n"}],"params_count":8,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-4-1","slug":"mp-4-1","display_id":"MP-4(1)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-4-1_to_nist-sp-800-53-r5-sc-28-1","source_ref":"requirement--nist-sp-800-53-r5-mp-4-1","target_ref":"requirement--nist-sp-800-53-r5-sc-28-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-4-2","slug":"mp-4-2","display_id":"MP-4(2)","name":"Automated Restricted Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict access to media storage areas and log access attempts and access granted using {{ mp_4_2_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"mp-04(02).mp-04(02)[01]","statement":"access to media storage areas is restricted using {{ mp_04_02_odp_01 }};"},{"id":"mp-04(02).mp-04(02)[02]","statement":"access attempts to media storage areas are logged using {{ mp_04_02_odp_02 }};"},{"id":"mp-04(02).mp-04(02)[03]","statement":"access granted to media storage areas is logged using {{ mp_04_02_odp_03 }}."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-5","slug":"mp-5","display_id":"MP-5","name":"Media Transport","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Protect and control {{ mp_05_odp_01 }} during transport outside of controlled areas using {{ mp_5_prm_2 }};\n"},{"id":"b","statement":"Maintain accountability for system media during transport outside of controlled areas;\n"},{"id":"c","statement":"Document activities associated with the transport of system media; and"},{"id":"d","statement":"Restrict the activities associated with the transport of system media to authorized personnel.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"{{ mp_05_odp_01 }} are protected during transport outside of controlled areas using {{ mp_05_odp_02 }};\n"},{"id":"a-2","statement":"{{ mp_05_odp_01 }} are controlled during transport outside of controlled areas using {{ mp_05_odp_03 }};\n"},{"id":"b","statement":"accountability for system media is maintained during transport outside of controlled areas;\n"},{"id":"c","statement":"activities associated with the transport of system media are documented;"},{"id":"d-1","statement":"personnel authorized to conduct media transport activities is/are identified;"},{"id":"d-2","statement":"activities associated with the transport of system media are restricted to identified authorized personnel.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-5-1","slug":"mp-5-1","display_id":"MP-5(1)","name":"Protection Outside of Controlled Areas","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-5-1_to_nist-sp-800-53-r5-mp-5","source_ref":"requirement--nist-sp-800-53-r5-mp-5-1","target_ref":"requirement--nist-sp-800-53-r5-mp-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-5-2","slug":"mp-5-2","display_id":"MP-5(2)","name":"Documentation of Activities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-5-2_to_nist-sp-800-53-r5-mp-5","source_ref":"requirement--nist-sp-800-53-r5-mp-5-2","target_ref":"requirement--nist-sp-800-53-r5-mp-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-5-3","slug":"mp-5-3","display_id":"MP-5(3)","name":"Custodians","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ an identified custodian during transport of system media outside of controlled areas.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"mp-05(03).mp-05(03)[01]","statement":"a custodian to transport system media outside of controlled areas is identified;"},{"id":"mp-05(03).mp-05(03)[02]","statement":"the identified custodian is employed during the transport of system media outside of controlled areas.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-5-4","slug":"mp-5-4","display_id":"MP-5(4)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-5-4_to_nist-sp-800-53-r5-sc-28-1","source_ref":"requirement--nist-sp-800-53-r5-mp-5-4","target_ref":"requirement--nist-sp-800-53-r5-sc-28-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6","slug":"mp-6","display_id":"MP-6","name":"Media Sanitization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Sanitize {{ mp_6_prm_1 }} prior to disposal, release out of organizational control, or release for reuse using {{ mp_6_prm_2 }} ; and\n"},{"id":"b","statement":"Employ sanitization mechanisms with the strength and integrity commensurate with the security category or classification of the information.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"{{ mp_06_odp_01 }} is sanitized using {{ mp_06_odp_04 }} prior to disposal;"},{"id":"a-2","statement":"{{ mp_06_odp_02 }} is sanitized using {{ mp_06_odp_05 }} prior to release from organizational control;\n"},{"id":"a-3","statement":"{{ mp_06_odp_03 }} is sanitized using {{ mp_06_odp_06 }} prior to release for reuse;\n"},{"id":"b","statement":"sanitization mechanisms with strength and integrity commensurate with the security category or classification of the information are employed.\n"}],"params_count":8,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-04-to-800-53-mp-6-a","source_ref":"control--ogrl-cr-04","target_ref":"requirement--nist-sp-800-53-r5-mp-6#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"mp_6_prm_1":"media_scope","mp_6_prm_2":"sanitization_methods"},"summary":"Sanitizing defined media with defined techniques before disposal, reuse, or release satisfies MP-6(a).\n"},{"id":"mapping--ogrl-cr-04-to-800-53-mp-6-b","source_ref":"control--ogrl-cr-04","target_ref":"requirement--nist-sp-800-53-r5-mp-6#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Using purge or destroy techniques aligned to SP 800-88 supports sanitization strength commensurate with data sensitivity, without formal categorization-based selection.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-1","slug":"mp-6-1","display_id":"MP-6(1)","name":"Review, Approve, Track, Document, and Verify","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review, approve, track, document, and verify media sanitization and disposal actions.\n","citation":null,"parts":[],"objectives_count":5,"objectives_preview":[{"id":"mp-06(01).mp-06(01)[01]","statement":"media sanitization and disposal actions are reviewed;"},{"id":"mp-06(01).mp-06(01)[02]","statement":"media sanitization and disposal actions are approved;"},{"id":"mp-06(01).mp-06(01)[03]","statement":"media sanitization and disposal actions are tracked;"},{"id":"mp-06(01).mp-06(01)[04]","statement":"media sanitization and disposal actions are documented;"},{"id":"mp-06(01).mp-06(01)[05]","statement":"media sanitization and disposal actions are verified."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-2","slug":"mp-6-2","display_id":"MP-6(2)","name":"Equipment Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test sanitization equipment and procedures {{ mp_6_2_prm_1 }} to ensure that the intended sanitization is being achieved.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"mp-06(02).mp-06(02)[01]","statement":"sanitization equipment is tested {{ mp_06_02_odp_01 }} to ensure that the intended sanitization is being achieved;\n"},{"id":"mp-06(02).mp-06(02)[02]","statement":"sanitization procedures are tested {{ mp_06_02_odp_02 }} to ensure that the intended sanitization is being achieved.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-3","slug":"mp-6-3","display_id":"MP-6(3)","name":"Nondestructive Techniques","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Apply nondestructive sanitization techniques to portable storage devices prior to connecting such devices to the system under the following circumstances: {{ mp_06_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"mp-06(03)","statement":"non-destructive sanitization techniques are applied to portable storage devices prior to connecting such devices to the system under {{ mp_06_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-4","slug":"mp-6-4","display_id":"MP-6(4)","name":"Controlled Unclassified Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-6-4_to_nist-sp-800-53-r5-mp-6","source_ref":"requirement--nist-sp-800-53-r5-mp-6-4","target_ref":"requirement--nist-sp-800-53-r5-mp-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-5","slug":"mp-6-5","display_id":"MP-6(5)","name":"Classified Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-6-5_to_nist-sp-800-53-r5-mp-6","source_ref":"requirement--nist-sp-800-53-r5-mp-6-5","target_ref":"requirement--nist-sp-800-53-r5-mp-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-6","slug":"mp-6-6","display_id":"MP-6(6)","name":"Media Destruction","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-6-6_to_nist-sp-800-53-r5-mp-6","source_ref":"requirement--nist-sp-800-53-r5-mp-6-6","target_ref":"requirement--nist-sp-800-53-r5-mp-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-7","slug":"mp-6-7","display_id":"MP-6(7)","name":"Dual Authorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce dual authorization for the sanitization of {{ mp_06_07_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"mp-06(07)","statement":"dual authorization for sanitization of {{ mp_06_07_odp }} is enforced."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-6-8","slug":"mp-6-8","display_id":"MP-6(8)","name":"Remote Purging or Wiping of Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability to purge or wipe information from {{ mp_06_08_odp_01 }} {{ mp_06_08_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"mp-06(08)","statement":"the capability to purge or wipe information from {{ mp_06_08_odp_01 }} {{ mp_06_08_odp_02 }} is provided.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-6-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-7","slug":"mp-7","display_id":"MP-7","name":"Media Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"{{ mp_07_odp_02 }} the use of {{ mp_07_odp_01 }} on {{ mp_07_odp_03 }} using {{ mp_07_odp_04 }} ; and\n"},{"id":"b","statement":"Prohibit the use of portable storage devices in organizational systems when such devices have no identifiable owner.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the use of {{ mp_07_odp_01 }} is {{ mp_07_odp_02 }} on {{ mp_07_odp_03 }} using {{ mp_07_odp_04 }};\n"},{"id":"b","statement":"the use of portable storage devices in organizational systems is prohibited when such devices have no identifiable owner.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-7-1","slug":"mp-7-1","display_id":"MP-7(1)","name":"Prohibit Use Without Owner","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-mp-7-1_to_nist-sp-800-53-r5-mp-7","source_ref":"requirement--nist-sp-800-53-r5-mp-7-1","target_ref":"requirement--nist-sp-800-53-r5-mp-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-7-2","slug":"mp-7-2","display_id":"MP-7(2)","name":"Prohibit Use of Sanitization-resistant Media","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the use of sanitization-resistant media in organizational systems.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"mp-07(02).mp-07(02)[01]","statement":"sanitization-resistant media is identified;"},{"id":"mp-07(02).mp-07(02)[02]","statement":"the use of sanitization-resistant media in organizational systems is prohibited."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-8","slug":"mp-8","display_id":"MP-8","name":"Media Downgrading","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish {{ mp_08_odp_01 }} that includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information;\n"},{"id":"b","statement":"Verify that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed and the access authorizations of the potential recipients of the downgraded information;\n"},{"id":"c","statement":"Identify {{ mp_08_odp_02 }} ; and"},{"id":"d","statement":"Downgrade the identified system media using the established process."}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"a {{ mp_08_odp_01 }} is established;"},{"id":"a-2","statement":"the {{ mp_08_odp_01 }} includes employing downgrading mechanisms with strength and integrity commensurate with the security category or classification of the information;\n"},{"id":"b-1","statement":"there is verification that the system media downgrading process is commensurate with the security category and/or classification level of the information to be removed;\n"},{"id":"b-2","statement":"there is verification that the system media downgrading process is commensurate with the access authorizations of the potential recipients of the downgraded information;\n"},{"id":"c","statement":"{{ mp_08_odp_02 }} is identified;"},{"id":"d","statement":"the identified system media is downgraded using the {{ mp_08_odp_01 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-8-1","slug":"mp-8-1","display_id":"MP-8(1)","name":"Documentation of Process","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Document system media downgrading actions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"mp-08(01)","statement":"system media downgrading actions are documented."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-8-2","slug":"mp-8-2","display_id":"MP-8(2)","name":"Equipment Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test downgrading equipment and procedures {{ mp_8_2_prm_1 }} to ensure that downgrading actions are being achieved.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"mp-08(02).mp-08(02)[01]","statement":"downgrading equipment is tested {{ mp_08_02_odp_01 }} to ensure that downgrading actions are being achieved;\n"},{"id":"mp-08(02).mp-08(02)[02]","statement":"downgrading procedures are tested {{ mp_08_02_odp_02 }} to ensure that downgrading actions are being achieved.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-8-3","slug":"mp-8-3","display_id":"MP-8(3)","name":"Controlled Unclassified Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Downgrade system media containing controlled unclassified information prior to public release.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"mp-08(03).mp-08(03)[01]","statement":"system media containing controlled unclassified information is identified;"},{"id":"mp-08(03).mp-08(03)[02]","statement":"system media containing controlled unclassified information is downgraded prior to public release.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-mp-8-4","slug":"mp-8-4","display_id":"MP-8(4)","name":"Classified Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Downgrade system media containing classified information prior to release to individuals without required access authorizations.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"mp-08(04).mp-08(04)[01]","statement":"system media containing classified information is identified;"},{"id":"mp-08(04).mp-08(04)[02]","statement":"system media containing classified information is downgraded prior to release to individuals without required access authorizations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/mp-8-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-1","slug":"pe-1","display_id":"PE-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ pe_1_prm_1 }}:"},{"id":"a.1","statement":"{{ pe_01_odp_03 }} physical and environmental protection policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the physical and environmental protection policy and the associated physical and environmental protection controls;\n"},{"id":"b","statement":"Designate an {{ pe_01_odp_04 }} to manage the development, documentation, and dissemination of the physical and environmental protection policy and procedures; and\n"},{"id":"c","statement":"Review and update the current physical and environmental protection:"},{"id":"c.1","statement":"Policy {{ pe_01_odp_05 }} and following {{ pe_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ pe_01_odp_07 }} and following {{ pe_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a physical and environmental protection policy is developed and documented;"},{"id":"a-2","statement":"the physical and environmental protection policy is disseminated to {{ pe_01_odp_01 }};\n"},{"id":"a-3","statement":"physical and environmental protection procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls are developed and documented;\n"},{"id":"a-4","statement":"the physical and environmental protection procedures are disseminated to {{ pe_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ pe_01_odp_03 }} physical and environmental protection policy addresses purpose;\n"},{"id":"a.1.a-2","statement":"the {{ pe_01_odp_03 }} physical and environmental protection policy addresses scope;\n"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-2","slug":"pe-2","display_id":"PE-2","name":"Physical Access Authorizations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, approve, and maintain a list of individuals with authorized access to the facility where the system resides;\n"},{"id":"b","statement":"Issue authorization credentials for facility access;"},{"id":"c","statement":"Review the access list detailing authorized facility access by individuals {{ pe_02_odp }} ; and\n"},{"id":"d","statement":"Remove individuals from the facility access list when access is no longer required.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"a list of individuals with authorized access to the facility where the system resides has been developed;\n"},{"id":"a-2","statement":"the list of individuals with authorized access to the facility where the system resides has been approved;\n"},{"id":"a-3","statement":"the list of individuals with authorized access to the facility where the system resides has been maintained;\n"},{"id":"b","statement":"authorization credentials are issued for facility access;"},{"id":"c","statement":"the access list detailing authorized facility access by individuals is reviewed {{ pe_02_odp }};\n"},{"id":"d","statement":"individuals are removed from the facility access list when access is no longer required.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-01-to-800-53-pe-2","source_ref":"control--ogrl-ps-01","target_ref":"requirement--nist-sp-800-53-r5-pe-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_02_odp":"access_review_cadence"},"summary":"Approved access list, credential issuance, periodic review, and timely removal cover all of PE-2.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-2-1","slug":"pe-2-1","display_id":"PE-2(1)","name":"Access by Position or Role","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Authorize physical access to the facility where the system resides based on position or role.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-02(01)","statement":"physical access to the facility where the system resides is authorized based on position or role.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-2-2","slug":"pe-2-2","display_id":"PE-2(2)","name":"Two Forms of Identification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require two forms of identification from the following forms of identification for visitor access to the facility where the system resides: {{ pe_02_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-02(02)","statement":"two forms of identification are required from {{ pe_02_02_odp }} for visitor access to the facility where the system resides.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-2-3","slug":"pe-2-3","display_id":"PE-2(3)","name":"Restrict Unescorted Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict unescorted access to the facility where the system resides to personnel with {{ pe_02_03_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-02(03)","statement":"unescorted access to the facility where the system resides is restricted to personnel with {{ pe_02_03_odp_01 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3","slug":"pe-3","display_id":"PE-3","name":"Physical Access Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Enforce physical access authorizations at {{ pe_03_odp_01 }} by:"},{"id":"a.1","statement":"Verifying individual access authorizations before granting access to the facility; and\n"},{"id":"a.2","statement":"Controlling ingress and egress to the facility using {{ pe_03_odp_02 }};"},{"id":"b","statement":"Maintain physical access audit logs for {{ pe_03_odp_04 }};"},{"id":"c","statement":"Control access to areas within the facility designated as publicly accessible by implementing the following controls: {{ pe_03_odp_05 }};\n"},{"id":"d","statement":"Escort visitors and control visitor activity {{ pe_03_odp_06 }};"},{"id":"e","statement":"Secure keys, combinations, and other physical access devices;"},{"id":"f","statement":"Inventory {{ pe_03_odp_07 }} every {{ pe_03_odp_08 }} ; and"},{"id":"g","statement":"Change combinations and keys {{ pe_3_prm_9 }} and/or when keys are lost, combinations are compromised, or when individuals possessing the keys or combinations are transferred or terminated.\n"}],"objectives_count":12,"objectives_preview":[{"id":"a.1","statement":"physical access authorizations are enforced at {{ pe_03_odp_01 }} by verifying individual access authorizations before granting access to the facility;\n"},{"id":"a.2","statement":"physical access authorizations are enforced at {{ pe_03_odp_01 }} by controlling ingress and egress to the facility using {{ pe_03_odp_02 }};\n"},{"id":"b","statement":"physical access audit logs are maintained for {{ pe_03_odp_04 }};"},{"id":"c","statement":"access to areas within the facility designated as publicly accessible are maintained by implementing {{ pe_03_odp_05 }};\n"},{"id":"d-1","statement":"visitors are escorted;"},{"id":"d-2","statement":"visitor activity is controlled {{ pe_03_odp_06 }};"}],"params_count":11,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-a","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_03_odp_02":"entry_control_mechanism"},"summary":"Badge or lock enforcement at every entry and exit point satisfies PE-3(a)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-b","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Retained electronic entry logs at controlled entry points satisfy PE-3(b)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-e","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Securing unissued keys, badges, and combinations satisfies PE-3(e)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-f","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#f","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_03_odp_08":"access_device_inventory_cadence"},"summary":"Periodic inventory of physical access devices satisfies PE-3(f)."},{"id":"mapping--ogrl-ps-02-to-800-53-pe-3-g","source_ref":"control--ogrl-ps-02","target_ref":"requirement--nist-sp-800-53-r5-pe-3#g","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Event-triggered rekeying covers PE-3(g) except the periodic change cadence."},{"id":"mapping--ogrl-ps-03-to-800-53-pe-3-d","source_ref":"control--ogrl-ps-03","target_ref":"requirement--nist-sp-800-53-r5-pe-3#d","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Escorting visitors in non-public areas addresses PE-3(d) without broader visitor activity controls.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-1","slug":"pe-3-1","display_id":"PE-3(1)","name":"System Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce physical access authorizations to the system in addition to the physical access controls for the facility at {{ pe_03_01_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-03(01).pe-03(01)[01]","statement":"physical access authorizations to the system are enforced;"},{"id":"2","statement":"physical access controls are enforced for the facility at {{ pe_03_01_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-2","slug":"pe-3-2","display_id":"PE-3(2)","name":"Facility and Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform security checks {{ pe_03_02_odp }} at the physical perimeter of the facility or system for exfiltration of information or removal of system components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-03(02)","statement":"security checks are performed {{ pe_03_02_odp }} at the physical perimeter of the facility or system for exfiltration of information or removal of system components.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-3","slug":"pe-3-3","display_id":"PE-3(3)","name":"Continuous Guards","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ guards to control {{ pe_03_03_odp }} to the facility where the system resides 24 hours per day, 7 days per week.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-03(03)","statement":"guards are employed to control {{ pe_03_03_odp }} to the facility where the system resides 24 hours per day, 7 days per week.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-4","slug":"pe-3-4","display_id":"PE-3(4)","name":"Lockable Casings","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use lockable physical casings to protect {{ pe_03_04_odp }} from unauthorized physical access.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-03(04)","statement":"lockable physical casings are used to protect {{ pe_03_04_odp }} from unauthorized access.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-5","slug":"pe-3-5","display_id":"PE-3(5)","name":"Tamper Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ pe_03_05_odp_01 }} to {{ pe_03_05_odp_02 }} physical tampering or alteration of {{ pe_03_05_odp_03 }} within the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-03(05)","statement":"{{ pe_03_05_odp_01 }} are employed to {{ pe_03_05_odp_02 }} physical tampering or alteration of {{ pe_03_05_odp_03 }} within the system.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-6","slug":"pe-3-6","display_id":"PE-3(6)","name":"Facility Penetration Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-3-6_to_nist-sp-800-53-r5-ca-8","source_ref":"requirement--nist-sp-800-53-r5-pe-3-6","target_ref":"requirement--nist-sp-800-53-r5-ca-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-7","slug":"pe-3-7","display_id":"PE-3(7)","name":"Physical Barriers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit access using physical barriers.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-03(07)","statement":"physical barriers are used to limit access."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-3-8","slug":"pe-3-8","display_id":"PE-3(8)","name":"Access Control Vestibules","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ access control vestibules at {{ pe_03_08_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-03(08)","statement":"access control vestibules are employed at {{ pe_03_08_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-3-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-4","slug":"pe-4","display_id":"PE-4","name":"Access Control for Transmission","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Control physical access to {{ pe_04_odp_01 }} within organizational facilities using {{ pe_04_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-04","statement":"physical access to {{ pe_04_odp_01 }} within organizational facilities is controlled using {{ pe_04_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-5","slug":"pe-5","display_id":"PE-5","name":"Access Control for Output Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Control physical access to output from {{ pe_05_odp }} to prevent unauthorized individuals from obtaining the output.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-05","statement":"physical access to output from {{ pe_05_odp }} is controlled to prevent unauthorized individuals from obtaining the output.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-5-1","slug":"pe-5-1","display_id":"PE-5(1)","name":"Access to Output by Authorized Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-5-1_to_nist-sp-800-53-r5-pe-5","source_ref":"requirement--nist-sp-800-53-r5-pe-5-1","target_ref":"requirement--nist-sp-800-53-r5-pe-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-5-2","slug":"pe-5-2","display_id":"PE-5(2)","name":"Link to Individual Identity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Link individual identity to receipt of output from output devices.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-05(02)","statement":"individual identity is linked to the receipt of output from output devices."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-5-3","slug":"pe-5-3","display_id":"PE-5(3)","name":"Marking Output Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-5-3_to_nist-sp-800-53-r5-pe-22","source_ref":"requirement--nist-sp-800-53-r5-pe-5-3","target_ref":"requirement--nist-sp-800-53-r5-pe-22","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-6","slug":"pe-6","display_id":"PE-6","name":"Monitoring Physical Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor physical access to the facility where the system resides to detect and respond to physical security incidents;\n"},{"id":"b","statement":"Review physical access logs {{ pe_06_odp_01 }} and upon occurrence of {{ pe_06_odp_02 }} ; and\n"},{"id":"c","statement":"Coordinate results of reviews and investigations with the organizational incident response capability.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"physical access to the facility where the system resides is monitored to detect and respond to physical security incidents;\n"},{"id":"b-1","statement":"physical access logs are reviewed {{ pe_06_odp_01 }};"},{"id":"b-2","statement":"physical access logs are reviewed upon occurrence of {{ pe_06_odp_02 }};"},{"id":"c-1","statement":"results of reviews are coordinated with organizational incident response capabilities;\n"},{"id":"c-2","statement":"results of investigations are coordinated with organizational incident response capabilities.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-04-to-800-53-pe-6","source_ref":"control--ogrl-ps-04","target_ref":"requirement--nist-sp-800-53-r5-pe-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_06_odp_01":"access_log_review_cadence","pe_06_odp_02":"access_log_review_triggers"},"summary":"Entry-point monitoring, scheduled and triggered log reviews, and incident escalation cover PE-6.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-6-1","slug":"pe-6-1","display_id":"PE-6(1)","name":"Intrusion Alarms and Surveillance Equipment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Monitor physical access to the facility where the system resides using physical intrusion alarms and surveillance equipment.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-06(01).pe-06(01)[01]","statement":"physical access to the facility where the system resides is monitored using physical intrusion alarms;\n"},{"id":"pe-06(01).pe-06(01)[02]","statement":"physical access to the facility where the system resides is monitored using physical surveillance equipment.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-6-2","slug":"pe-6-2","display_id":"PE-6(2)","name":"Automated Intrusion Recognition and Responses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Recognize {{ pe_06_02_odp_01 }} and initiate {{ pe_06_02_odp_02 }} using {{ pe_06_02_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-06(02).pe-06(02)[01]","statement":"{{ pe_06_02_odp_01 }} are recognized;"},{"id":"pe-06(02).pe-06(02)[02]","statement":"{{ pe_06_02_odp_02 }} are initiated using {{ pe_06_02_odp_03 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-6-3","slug":"pe-6-3","display_id":"PE-6(3)","name":"Video Surveillance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ video surveillance of {{ pe_06_03_odp_01 }};"},{"id":"b","statement":"Review video recordings {{ pe_06_03_odp_02 }} ; and"},{"id":"c","statement":"Retain video recordings for {{ pe_06_03_odp_03 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"video surveillance of {{ pe_06_03_odp_01 }} is employed;"},{"id":"b","statement":"video recordings are reviewed {{ pe_06_03_odp_02 }};"},{"id":"c","statement":"video recordings are retained for {{ pe_06_03_odp_03 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-6-4","slug":"pe-6-4","display_id":"PE-6(4)","name":"Monitoring Physical Access to Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Monitor physical access to the system in addition to the physical access monitoring of the facility at {{ pe_06_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-06(04)","statement":"physical access to the system is monitored in addition to the physical access monitoring of the facility at {{ pe_06_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-6-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-7","slug":"pe-7","display_id":"PE-7","name":"Visitor Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-7_to_nist-sp-800-53-r5-pe-2","source_ref":"requirement--nist-sp-800-53-r5-pe-7","target_ref":"requirement--nist-sp-800-53-r5-pe-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-pe-7_to_nist-sp-800-53-r5-pe-3","source_ref":"requirement--nist-sp-800-53-r5-pe-7","target_ref":"requirement--nist-sp-800-53-r5-pe-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-8","slug":"pe-8","display_id":"PE-8","name":"Visitor Access Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Maintain visitor access records to the facility where the system resides for {{ pe_08_odp_01 }};\n"},{"id":"b","statement":"Review visitor access records {{ pe_08_odp_02 }} ; and"},{"id":"c","statement":"Report anomalies in visitor access records to {{ pe_08_odp_03 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"visitor access records for the facility where the system resides are maintained for {{ pe_08_odp_01 }};\n"},{"id":"b","statement":"visitor access records are reviewed {{ pe_08_odp_02 }};"},{"id":"c","statement":"visitor access records anomalies are reported to {{ pe_08_odp_03 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-03-to-800-53-pe-8","source_ref":"control--ogrl-ps-03","target_ref":"requirement--nist-sp-800-53-r5-pe-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_08_odp_01":"visitor_record_retention","pe_08_odp_02":"visitor_review_cadence","pe_08_odp_03":"visitor_anomaly_recipient"},"summary":"Visitor logging, retention, periodic review, and anomaly reporting cover PE-8."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-8-1","slug":"pe-8-1","display_id":"PE-8(1)","name":"Automated Records Maintenance and Review","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain and review visitor access records using {{ pe_8_1_prm_1 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-08(01).pe-08(01)[01]","statement":"visitor access records are maintained using {{ pe_08_01_odp_01 }};"},{"id":"pe-08(01).pe-08(01)[02]","statement":"visitor access records are reviewed using {{ pe_08_01_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-8-2","slug":"pe-8-2","display_id":"PE-8(2)","name":"Physical Access Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-8-2_to_nist-sp-800-53-r5-pe-2","source_ref":"requirement--nist-sp-800-53-r5-pe-8-2","target_ref":"requirement--nist-sp-800-53-r5-pe-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-8-3","slug":"pe-8-3","display_id":"PE-8(3)","name":"Limit Personally Identifiable Information Elements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit personally identifiable information contained in visitor access records to the following elements identified in the privacy risk assessment: {{ pe_08_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-08(03)","statement":"personally identifiable information contained in visitor access records is limited to {{ pe_08_03_odp }} identified in the privacy risk assessment.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-9","slug":"pe-9","display_id":"PE-9","name":"Power Equipment and Cabling","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect power equipment and power cabling for the system from damage and destruction.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"power equipment for the system is protected from damage and destruction;"},{"id":"[02]","statement":"power cabling for the system is protected from damage and destruction."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-9-1","slug":"pe-9-1","display_id":"PE-9(1)","name":"Redundant Cabling","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ redundant power cabling paths that are physically separated by {{ pe_09_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-09(01)","statement":"redundant power cabling paths that are physically separated by {{ pe_09_01_odp }} are employed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-9-2","slug":"pe-9-2","display_id":"PE-9(2)","name":"Automatic Voltage Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automatic voltage controls for {{ pe_09_02_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-09(02)","statement":"automatic voltage controls for {{ pe_09_02_odp }} are employed."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-10","slug":"pe-10","display_id":"PE-10","name":"Emergency Shutoff","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide the capability of shutting off power to {{ pe_10_odp_01 }} in emergency situations;\n"},{"id":"b","statement":"Place emergency shutoff switches or devices in {{ pe_10_odp_02 }} to facilitate access for authorized personnel; and\n"},{"id":"c","statement":"Protect emergency power shutoff capability from unauthorized activation."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the capability to shut off power to {{ pe_10_odp_01 }} in emergency situations is provided;\n"},{"id":"b","statement":"emergency shutoff switches or devices are placed in {{ pe_10_odp_02 }} to facilitate access for authorized personnel;\n"},{"id":"c","statement":"the emergency power shutoff capability is protected from unauthorized activation.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-10-1","slug":"pe-10-1","display_id":"PE-10(1)","name":"Accidental and Unauthorized Activation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-10-1_to_nist-sp-800-53-r5-pe-10","source_ref":"requirement--nist-sp-800-53-r5-pe-10-1","target_ref":"requirement--nist-sp-800-53-r5-pe-10","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-10-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-11","slug":"pe-11","display_id":"PE-11","name":"Emergency Power","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide an uninterruptible power supply to facilitate {{ pe_11_odp }} in the event of a primary power source loss.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"an uninterruptible power supply is provided to facilitate {{ pe_11_odp }} in the event of a primary power source loss.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-05-to-800-53-pe-11","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-11","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_11_odp":"ups_capability"},"summary":"Providing a UPS sized for the defined capability satisfies PE-11."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-11-1","slug":"pe-11-1","display_id":"PE-11(1)","name":"Alternate Power Supply — Minimal Operational Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an alternate power supply for the system that is activated {{ pe_11_01_odp }} and that can maintain minimally required operational capability in the event of an extended loss of the primary power source.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-11(01).pe-11(01)[01]","statement":"an alternate power supply provided for the system is activated {{ pe_11_01_odp }};\n"},{"id":"pe-11(01).pe-11(01)[02]","statement":"the alternate power supply provided for the system can maintain minimally required operational capability in the event of an extended loss of the primary power source.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-11-2","slug":"pe-11-2","display_id":"PE-11(2)","name":"Alternate Power Supply — Self-contained","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an alternate power supply for the system that is activated {{ pe_11_02_odp_01 }} and that is:\n","citation":null,"parts":[{"id":"a","statement":"Self-contained;"},{"id":"b","statement":"Not reliant on external power generation; and"},{"id":"c","statement":"Capable of maintaining {{ pe_11_02_odp_02 }} in the event of an extended loss of the primary power source.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the alternate power supply provided for the system is self-contained;"},{"id":"b","statement":"the alternate power supply provided for the system is not reliant on external power generation;\n"},{"id":"c","statement":"the alternate power supply provided for the system is capable of maintaining {{ pe_11_02_odp_02 }} in the event of an extended loss of the primary power source.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-11-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-12","slug":"pe-12","display_id":"PE-12","name":"Emergency Lighting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ and maintain automatic emergency lighting for the system that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes within the facility.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"_obj-1","statement":"automatic emergency lighting that activates in the event of a power outage or disruption is employed for the system;\n"},{"id":"_obj-2","statement":"automatic emergency lighting that activates in the event of a power outage or disruption is maintained for the system;\n"},{"id":"_obj-3","statement":"automatic emergency lighting for the system covers emergency exits within the facility;\n"},{"id":"_obj-4","statement":"automatic emergency lighting for the system covers evacuation routes within the facility.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-12-1","slug":"pe-12-1","display_id":"PE-12(1)","name":"Essential Mission and Business Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide emergency lighting for all areas within the facility supporting essential mission and business functions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-12(01)","statement":"emergency lighting is provided for all areas within the facility supporting essential mission and business functions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-13","slug":"pe-13","display_id":"PE-13","name":"Fire Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ and maintain fire detection and suppression systems that are supported by an independent energy source.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"_obj-1","statement":"fire detection systems are employed;"},{"id":"_obj-2","statement":"employed fire detection systems are supported by an independent energy source;"},{"id":"_obj-3","statement":"employed fire detection systems are maintained;"},{"id":"_obj-4","statement":"fire suppression systems are employed;"},{"id":"_obj-5","statement":"employed fire suppression systems are supported by an independent energy source;"},{"id":"_obj-6","statement":"employed fire suppression systems are maintained."}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-05-to-800-53-pe-13","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-13","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Fire detection and suppression with independent power satisfies PE-13."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-13-1","slug":"pe-13-1","display_id":"PE-13(1)","name":"Detection Systems — Automatic Activation and Notification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ fire detection systems that activate automatically and notify {{ pe_13_01_odp_01 }} and {{ pe_13_01_odp_02 }} in the event of a fire.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"pe-13(01).pe-13(01)[01]","statement":"fire detection systems that activate automatically are employed in the event of a fire;\n"},{"id":"pe-13(01).pe-13(01)[02]","statement":"fire detection systems that notify {{ pe_13_01_odp_01 }} automatically are employed in the event of a fire;\n"},{"id":"pe-13(01).pe-13(01)[03]","statement":"fire detection systems that notify {{ pe_13_01_odp_02 }} automatically are employed in the event of a fire.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-13-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-13-2","slug":"pe-13-2","display_id":"PE-13(2)","name":"Suppression Systems — Automatic Activation and Notification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ fire suppression systems that activate automatically and notify {{ pe_13_02_odp_01 }} and {{ pe_13_02_odp_02 }} ; and\n"},{"id":"b","statement":"Employ an automatic fire suppression capability when the facility is not staffed on a continuous basis.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"fire suppression systems that activate automatically are employed;"},{"id":"a-2","statement":"fire suppression systems that notify {{ pe_13_02_odp_01 }} automatically are employed;\n"},{"id":"a-3","statement":"fire suppression systems that notify {{ pe_13_02_odp_02 }} automatically are employed;\n"},{"id":"b","statement":"an automatic fire suppression capability is employed when the facility is not staffed on a continuous basis.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-13-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-13-3","slug":"pe-13-3","display_id":"PE-13(3)","name":"Automatic Fire Suppression","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-13-3_to_nist-sp-800-53-r5-pe-13-2","source_ref":"requirement--nist-sp-800-53-r5-pe-13-3","target_ref":"requirement--nist-sp-800-53-r5-pe-13-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-13-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-13-4","slug":"pe-13-4","display_id":"PE-13(4)","name":"Inspections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure that the facility undergoes {{ pe_13_04_odp_01 }} fire protection inspections by authorized and qualified inspectors and identified deficiencies are resolved within {{ pe_13_04_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-13(04).pe-13(04)[01]","statement":"the facility undergoes fire protection inspections {{ pe_13_04_odp_01 }} by authorized and qualified inspectors;\n"},{"id":"pe-13(04).pe-13(04)[02]","statement":"the identified deficiencies from fire protection inspections are resolved within {{ pe_13_04_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-13-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-14","slug":"pe-14","display_id":"PE-14","name":"Environmental Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Maintain {{ pe_14_odp_01 }} levels within the facility where the system resides at {{ pe_14_odp_03 }} ; and\n"},{"id":"b","statement":"Monitor environmental control levels {{ pe_14_odp_04 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ pe_14_odp_01 }} levels are maintained at {{ pe_14_odp_03 }} within the facility where the system resides;\n"},{"id":"b","statement":"environmental control levels are monitored {{ pe_14_odp_04 }}."}],"params_count":4,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-05-to-800-53-pe-14","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-14","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_14_odp_01":"environmental_factors","pe_14_odp_03":"environmental_ranges","pe_14_odp_04":"environmental_monitoring_cadence"},"summary":"Maintaining and monitoring environmental conditions within defined ranges satisfies PE-14.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-14-1","slug":"pe-14-1","display_id":"PE-14(1)","name":"Automatic Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following automatic environmental controls in the facility to prevent fluctuations potentially harmful to the system: {{ pe_14_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pe-14(01)","statement":"{{ pe_14_01_odp }} are employed in the facility to prevent fluctuations that are potentially harmful to the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-14-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-14-2","slug":"pe-14-2","display_id":"PE-14(2)","name":"Monitoring with Alarms and Notifications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ environmental control monitoring that provides an alarm or notification of changes potentially harmful to personnel or equipment to {{ pe_14_02_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-14(02).pe-14(02)[01]","statement":"environmental control monitoring is employed;"},{"id":"pe-14(02).pe-14(02)[02]","statement":"the environmental control monitoring capability provides an alarm or notification to {{ pe_14_02_odp }} when changes are potentially harmful to personnel or equipment.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-14-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-15","slug":"pe-15","display_id":"PE-15","name":"Water Damage Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect the system from damage resulting from water leakage by providing master shutoff or isolation valves that are accessible, working properly, and known to key personnel.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"_obj-1","statement":"the system is protected from damage resulting from water leakage by providing master shutoff or isolation valves;\n"},{"id":"_obj-2","statement":"the master shutoff or isolation valves are accessible;"},{"id":"_obj-3","statement":"the master shutoff or isolation valves are working properly;"},{"id":"_obj-4","statement":"the master shutoff or isolation valves are known to key personnel."}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-05-to-800-53-pe-15","source_ref":"control--ogrl-ps-05","target_ref":"requirement--nist-sp-800-53-r5-pe-15","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Accessible, working, known master water shutoff valves satisfy PE-15."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-15-1","slug":"pe-15-1","display_id":"PE-15(1)","name":"Automation Support","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Detect the presence of water near the system and alert {{ pe_15_01_odp_01 }} using {{ pe_15_01_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"pe-15(01).pe-15(01)[01]","statement":"the presence of water near the system can be detected automatically;"},{"id":"pe-15(01).pe-15(01)[02]","statement":"{{ pe_15_01_odp_01 }} is/are alerted using {{ pe_15_01_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-15-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-16","slug":"pe-16","display_id":"PE-16","name":"Delivery and Removal","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Authorize and control {{ pe_16_prm_1 }} entering and exiting the facility; and"},{"id":"b","statement":"Maintain records of the system components."}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"{{ pe_16_odp_01 }} are authorized when entering the facility;"},{"id":"a-2","statement":"{{ pe_16_odp_01 }} are controlled when entering the facility;"},{"id":"a-3","statement":"{{ pe_16_odp_02 }} are authorized when exiting the facility;"},{"id":"a-4","statement":"{{ pe_16_odp_02 }} are controlled when exiting the facility;"},{"id":"b","statement":"records of the system components are maintained."}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-06-to-800-53-pe-16","source_ref":"control--ogrl-ps-06","target_ref":"requirement--nist-sp-800-53-r5-pe-16","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pe_16_prm_1":"controlled_component_types"},"summary":"Authorizing and recording component movements in and out of facilities covers PE-16.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-17","slug":"pe-17","display_id":"PE-17","name":"Alternate Work Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine and document the {{ pe_17_odp_01 }} allowed for use by employees;"},{"id":"b","statement":"Employ the following controls at alternate work sites: {{ pe_17_odp_02 }};"},{"id":"c","statement":"Assess the effectiveness of controls at alternate work sites; and"},{"id":"d","statement":"Provide a means for employees to communicate with information security and privacy personnel in case of incidents.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"{{ pe_17_odp_01 }} are determined and documented;"},{"id":"b","statement":"{{ pe_17_odp_02 }} are employed at alternate work sites;"},{"id":"c","statement":"the effectiveness of controls at alternate work sites is assessed;"},{"id":"d","statement":"a means for employees to communicate with information security and privacy personnel in case of incidents is provided.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-18","slug":"pe-18","display_id":"PE-18","name":"Location of System Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Position system components within the facility to minimize potential damage from {{ pe_18_odp }} and to minimize the opportunity for unauthorized access.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"system components are positioned within the facility to minimize potential damage from {{ pe_18_odp }} and to minimize the opportunity for unauthorized access.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-18-1","slug":"pe-18-1","display_id":"PE-18(1)","name":"Facility Site","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pe-18-1_to_nist-sp-800-53-r5-pe-23","source_ref":"requirement--nist-sp-800-53-r5-pe-18-1","target_ref":"requirement--nist-sp-800-53-r5-pe-23","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-18-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-19","slug":"pe-19","display_id":"PE-19","name":"Information Leakage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect the system from information leakage due to electromagnetic signals emanations.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the system is protected from information leakage due to electromagnetic signal emanations.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-19-1","slug":"pe-19-1","display_id":"PE-19(1)","name":"National Emissions Policies and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect system components, associated data communications, and networks in accordance with national Emissions Security policies and procedures based on the security category or classification of the information.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"pe-19(01).pe-19(01)[01]","statement":"system components are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information;\n"},{"id":"pe-19(01).pe-19(01)[02]","statement":"associated data communications are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information;\n"},{"id":"pe-19(01).pe-19(01)[03]","statement":"networks are protected in accordance with national emissions security policies and procedures based on the security category or classification of the information.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-19-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-20","slug":"pe-20","display_id":"PE-20","name":"Asset Monitoring and Tracking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ {{ pe_20_odp_01 }} to track and monitor the location and movement of {{ pe_20_odp_02 }} within {{ pe_20_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ pe_20_odp_01 }} are employed to track and monitor the location and movement of {{ pe_20_odp_02 }} within {{ pe_20_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-21","slug":"pe-21","display_id":"PE-21","name":"Electromagnetic Pulse Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ {{ pe_21_odp_01 }} against electromagnetic pulse damage for {{ pe_21_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ pe_21_odp_01 }} are employed against electromagnetic pulse damage for {{ pe_21_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-22","slug":"pe-22","display_id":"PE-22","name":"Component Marking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Mark {{ pe_22_odp }} indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ pe_22_odp }} are marked indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-pe-23","slug":"pe-23","display_id":"PE-23","name":"Facility Location","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Plan the location or site of the facility where the system resides considering physical and environmental hazards; and\n"},{"id":"b","statement":"For existing facilities, consider the physical and environmental hazards in the organizational risk management strategy.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the location or site of the facility where the system resides is planned considering physical and environmental hazards;\n"},{"id":"b","statement":"for existing facilities, physical and environmental hazards are considered in the organizational risk management strategy.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pe-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-1","slug":"pl-1","display_id":"PL-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ pl_1_prm_1 }}:"},{"id":"a.1","statement":"{{ pl_01_odp_03 }} planning policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the planning policy and the associated planning controls;\n"},{"id":"b","statement":"Designate an {{ pl_01_odp_04 }} to manage the development, documentation, and dissemination of the planning policy and procedures; and\n"},{"id":"c","statement":"Review and update the current planning:"},{"id":"c.1","statement":"Policy {{ pl_01_odp_05 }} and following {{ pl_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ pl_01_odp_07 }} and following {{ pl_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a planning policy is developed and documented."},{"id":"a-2","statement":"the planning policy is disseminated to {{ pl_01_odp_01 }};"},{"id":"a-3","statement":"planning procedures to facilitate the implementation of the planning policy and associated planning controls are developed and documented;\n"},{"id":"a-4","statement":"the planning procedures are disseminated to {{ pl_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ pl_01_odp_03 }} planning policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ pl_01_odp_03 }} planning policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-2","slug":"pl-2","display_id":"PL-2","name":"System Security and Privacy Plans","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop security and privacy plans for the system that:"},{"id":"a.1","statement":"Are consistent with the organization’s enterprise architecture;"},{"id":"a.2","statement":"Explicitly define the constituent system components;"},{"id":"a.3","statement":"Describe the operational context of the system in terms of mission and business processes;\n"},{"id":"a.4","statement":"Identify the individuals that fulfill system roles and responsibilities;"},{"id":"a.5","statement":"Identify the information types processed, stored, and transmitted by the system;"},{"id":"a.6","statement":"Provide the security categorization of the system, including supporting rationale;\n"},{"id":"a.7","statement":"Describe any specific threats to the system that are of concern to the organization;\n"},{"id":"a.8","statement":"Provide the results of a privacy risk assessment for systems processing personally identifiable information;\n"},{"id":"a.9","statement":"Describe the operational environment for the system and any dependencies on or connections to other systems or system components;\n"},{"id":"a.10","statement":"Provide an overview of the security and privacy requirements for the system;"},{"id":"a.11","statement":"Identify any relevant control baselines or overlays, if applicable;"},{"id":"a.12","statement":"Describe the controls in place or planned for meeting the security and privacy requirements, including a rationale for any tailoring decisions;\n"},{"id":"a.13","statement":"Include risk determinations for security and privacy architecture and design decisions;\n"},{"id":"a.14","statement":"Include security- and privacy-related activities affecting the system that require planning and coordination with {{ pl_02_odp_01 }} ; and\n"},{"id":"a.15","statement":"Are reviewed and approved by the authorizing official or designated representative prior to plan implementation.\n"},{"id":"b","statement":"Distribute copies of the plans and communicate subsequent changes to the plans to {{ pl_02_odp_02 }};\n"},{"id":"c","statement":"Review the plans {{ pl_02_odp_03 }};"},{"id":"d","statement":"Update the plans to address changes to the system and environment of operation or problems identified during plan implementation or control assessments; and\n"},{"id":"e","statement":"Protect the plans from unauthorized disclosure and modification."}],"objectives_count":38,"objectives_preview":[{"id":"a.1-1","statement":"a security plan for the system is developed that is consistent with the organization’s enterprise architecture;\n"},{"id":"a.1-2","statement":"a privacy plan for the system is developed that is consistent with the organization’s enterprise architecture;\n"},{"id":"a.2-1","statement":"a security plan for the system is developed that explicitly defines the constituent system components;\n"},{"id":"a.2-2","statement":"a privacy plan for the system is developed that explicitly defines the constituent system components;\n"},{"id":"a.3-1","statement":"a security plan for the system is developed that describes the operational context of the system in terms of mission and business processes;\n"},{"id":"a.3-2","statement":"a privacy plan for the system is developed that describes the operational context of the system in terms of mission and business processes;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-a","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#a","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Covers components, operational context, roles, information types, dependencies, and controls; security categorization, privacy risk results, and design risk determinations are not required.\n"},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-b","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pl_02_odp_02":"plan_distribution"},"summary":"Distribution of the description and its changes to named recipients meets the plan distribution requirement.\n"},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-c","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pl_02_odp_03":"plan_review_frequency"},"summary":"Periodic review of the system description meets the plan review requirement."},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-d","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Updating on significant change or assessment findings meets the plan update requirement.\n"},{"id":"mapping--ogrl-gv-08-to-800-53-pl-2-e","source_ref":"control--ogrl-gv-08","target_ref":"requirement--nist-sp-800-53-r5-pl-2#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Restricting modification to owners protects the plan from unauthorized change; disclosure protection relies on repository access controls.\n"},{"id":"mapping--ogrl-sd-05-to-800-53-pl-2-a-5","source_ref":"control--ogrl-sd-05","target_ref":"requirement--nist-sp-800-53-r5-pl-2#a.5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Data definitions identify the information types a system processes, loosely overlapping PL-2(a)(5).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-2-1","slug":"pl-2-1","display_id":"PL-2(1)","name":"Concept of Operations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pl-2-1_to_nist-sp-800-53-r5-pl-7","source_ref":"requirement--nist-sp-800-53-r5-pl-2-1","target_ref":"requirement--nist-sp-800-53-r5-pl-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-2-2","slug":"pl-2-2","display_id":"PL-2(2)","name":"Functional Architecture","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pl-2-2_to_nist-sp-800-53-r5-pl-8","source_ref":"requirement--nist-sp-800-53-r5-pl-2-2","target_ref":"requirement--nist-sp-800-53-r5-pl-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-2-3","slug":"pl-2-3","display_id":"PL-2(3)","name":"Plan and Coordinate with Other Organizational Entities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pl-2-3_to_nist-sp-800-53-r5-pl-2","source_ref":"requirement--nist-sp-800-53-r5-pl-2-3","target_ref":"requirement--nist-sp-800-53-r5-pl-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-3","slug":"pl-3","display_id":"PL-3","name":"System Security Plan Update","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pl-3_to_nist-sp-800-53-r5-pl-2","source_ref":"requirement--nist-sp-800-53-r5-pl-3","target_ref":"requirement--nist-sp-800-53-r5-pl-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-4","slug":"pl-4","display_id":"PL-4","name":"Rules of Behavior","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish and provide to individuals requiring access to the system, the rules that describe their responsibilities and expected behavior for information and system usage, security, and privacy;\n"},{"id":"b","statement":"Receive a documented acknowledgment from such individuals, indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to information and the system;\n"},{"id":"c","statement":"Review and update the rules of behavior {{ pl_04_odp_01 }} ; and"},{"id":"d","statement":"Require individuals who have acknowledged a previous version of the rules of behavior to read and re-acknowledge {{ pl_04_odp_02 }}.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are established for individuals requiring access to the system;\n"},{"id":"a-2","statement":"rules that describe responsibilities and expected behavior for information and system usage, security, and privacy are provided to individuals requiring access to the system;\n"},{"id":"b","statement":"before authorizing access to information and the system, a documented acknowledgement from such individuals indicating that they have read, understand, and agree to abide by the rules of behavior is received;\n"},{"id":"c","statement":"rules of behavior are reviewed and updated {{ pl_04_odp_01 }};"},{"id":"d","statement":"individuals who have acknowledged a previous version of the rules of behavior are required to read and reacknowledge {{ pl_04_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-09-to-800-53-pl-4","source_ref":"control--ogrl-gv-09","target_ref":"requirement--nist-sp-800-53-r5-pl-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pl_04_odp_01":"aup_review_frequency","pl_04_odp_03":"reacknowledgment_frequency"},"summary":"Published rules, acknowledgment before access, periodic review, and periodic or revision-driven re-acknowledgment together cover every part of rules of behavior.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-4-1","slug":"pl-4-1","display_id":"PL-4(1)","name":"Social Media and External Site/Application Usage Restrictions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include in the rules of behavior, restrictions on:","citation":null,"parts":[{"id":"a","statement":"Use of social media, social networking sites, and external sites/applications;"},{"id":"b","statement":"Posting organizational information on public websites; and"},{"id":"c","statement":"Use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the rules of behavior include restrictions on the use of social media, social networking sites, and external sites/applications;\n"},{"id":"b","statement":"the rules of behavior include restrictions on posting organizational information on public websites;\n"},{"id":"c","statement":"the rules of behavior include restrictions on the use of organization-provided identifiers (e.g., email addresses) and authentication secrets (e.g., passwords) for creating accounts on external sites/applications.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-5","slug":"pl-5","display_id":"PL-5","name":"Privacy Impact Assessment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pl-5_to_nist-sp-800-53-r5-ra-8","source_ref":"requirement--nist-sp-800-53-r5-pl-5","target_ref":"requirement--nist-sp-800-53-r5-ra-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-6","slug":"pl-6","display_id":"PL-6","name":"Security-related Activity Planning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-pl-6_to_nist-sp-800-53-r5-pl-2","source_ref":"requirement--nist-sp-800-53-r5-pl-6","target_ref":"requirement--nist-sp-800-53-r5-pl-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-7","slug":"pl-7","display_id":"PL-7","name":"Concept of Operations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy; and\n"},{"id":"b","statement":"Review and update the CONOPS {{ pl_07_odp }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a CONOPS for the system describing how the organization intends to operate the system from the perspective of information security and privacy is developed;\n"},{"id":"b","statement":"the CONOPS is reviewed and updated {{ pl_07_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-8","slug":"pl-8","display_id":"PL-8","name":"Security and Privacy Architectures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop security and privacy architectures for the system that:"},{"id":"a.1","statement":"Describe the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;\n"},{"id":"a.2","statement":"Describe the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;\n"},{"id":"a.3","statement":"Describe how the architectures are integrated into and support the enterprise architecture; and\n"},{"id":"a.4","statement":"Describe any assumptions about, and dependencies on, external systems and services;\n"},{"id":"b","statement":"Review and update the architectures {{ pl_08_odp }} to reflect changes in the enterprise architecture; and\n"},{"id":"c","statement":"Reflect planned architecture changes in security and privacy plans, Concept of Operations (CONOPS), criticality analysis, organizational procedures, and procurements and acquisitions.\n"}],"objectives_count":13,"objectives_preview":[{"id":"a.1","statement":"a security architecture for the system describes the requirements and approach to be taken for protecting the confidentiality, integrity, and availability of organizational information;\n"},{"id":"a.2","statement":"a privacy architecture describes the requirements and approach to be taken for processing personally identifiable information to minimize privacy risk to individuals;\n"},{"id":"a.3-1","statement":"a security architecture for the system describes how the architecture is integrated into and supports the enterprise architecture;\n"},{"id":"a.3-2","statement":"a privacy architecture for the system describes how the architecture is integrated into and supports the enterprise architecture;\n"},{"id":"a.4-1","statement":"a security architecture for the system describes any assumptions about and dependencies on external systems and services;\n"},{"id":"a.4-2","statement":"a privacy architecture for the system describes any assumptions about and dependencies on external systems and services;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-8-1","slug":"pl-8-1","display_id":"PL-8(1)","name":"Defense in Depth","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Design the security and privacy architectures for the system using a defense-in-depth approach that:\n","citation":null,"parts":[{"id":"a","statement":"Allocates {{ pl_08_01_odp_01 }} to {{ pl_08_01_odp_02 }} ; and"},{"id":"b","statement":"Ensures that the allocated controls operate in a coordinated and mutually reinforcing manner.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"the security architecture for the system is designed using a defense-in-depth approach that allocates {{ pl_08_01_odp_01 }} to {{ pl_08_01_odp_02 }};\n"},{"id":"a-2","statement":"the privacy architecture for the system is designed using a defense-in-depth approach that allocates {{ pl_08_01_odp_01 }} to {{ pl_08_01_odp_02 }};\n"},{"id":"b-1","statement":"the security architecture for the system is designed using a defense-in-depth approach that ensures the allocated controls operate in a coordinated and mutually reinforcing manner;\n"},{"id":"b-2","statement":"the privacy architecture for the system is designed using a defense-in-depth approach that ensures the allocated controls operate in a coordinated and mutually reinforcing manner.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-8-2","slug":"pl-8-2","display_id":"PL-8(2)","name":"Supplier Diversity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that {{ pl_08_02_odp_01 }} allocated to {{ pl_08_02_odp_02 }} are obtained from different suppliers.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pl-08(02)","statement":"{{ pl_08_02_odp_01 }} that are allocated to {{ pl_08_02_odp_02 }} are required to be obtained from different suppliers.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-9","slug":"pl-9","display_id":"PL-9","name":"Central Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Centrally manage {{ pl_09_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pl-09","statement":"{{ pl_09_odp }} are centrally managed."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-10","slug":"pl-10","display_id":"PL-10","name":"Baseline Selection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Select a control baseline for the system.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a control baseline for the system is selected."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-pl-11","slug":"pl-11","display_id":"PL-11","name":"Baseline Tailoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Tailor the selected control baseline by applying specified tailoring actions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the selected control baseline is tailored by applying specified tailoring actions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pl-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-1","slug":"pm-1","display_id":"PM-1","name":"Information Security Program Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and disseminate an organization-wide information security program plan that:\n"},{"id":"a.1","statement":"Provides an overview of the requirements for the security program and a description of the security program management controls and common controls in place or planned for meeting those requirements;\n"},{"id":"a.2","statement":"Includes the identification and assignment of roles, responsibilities, management commitment, coordination among organizational entities, and compliance;\n"},{"id":"a.3","statement":"Reflects the coordination among organizational entities responsible for information security; and\n"},{"id":"a.4","statement":"Is approved by a senior official with responsibility and accountability for the risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation;\n"},{"id":"b","statement":"Review and update the organization-wide information security program plan {{ pm_01_odp_01 }} and following {{ pm_01_odp_02 }} ; and\n"},{"id":"c","statement":"Protect the information security program plan from unauthorized disclosure and modification.\n"}],"objectives_count":16,"objectives_preview":[{"id":"a-1","statement":"an organization-wide information security program plan is developed;"},{"id":"a-2","statement":"the information security program plan is disseminated;"},{"id":"a.1-1","statement":"the information security program plan provides an overview of the requirements for the security program;\n"},{"id":"a.1-2","statement":"the information security program plan provides a description of the security program management controls in place or planned for meeting those requirements;\n"},{"id":"a.1-3","statement":"the information security program plan provides a description of the common controls in place or planned for meeting those requirements;\n"},{"id":"a.2-1","statement":"the information security program plan includes the identification and assignment of roles;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-01-to-800-53-pm-1-a","source_ref":"control--ogrl-gv-01","target_ref":"requirement--nist-sp-800-53-r5-pm-1#a","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"The approved policy set serves as the program plan and assigns roles, but does not itself describe every program management and common control.\n"},{"id":"mapping--ogrl-gv-01-to-800-53-pm-1-b","source_ref":"control--ogrl-gv-01","target_ref":"requirement--nist-sp-800-53-r5-pm-1#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_01_odp_01":"policy_review_frequency","pm_01_odp_02":"policy_review_triggers"},"summary":"Scheduled and event-driven policy review and update fulfils the plan review requirement.\n"},{"id":"mapping--ogrl-gv-01-to-800-53-pm-1-c","source_ref":"control--ogrl-gv-01","target_ref":"requirement--nist-sp-800-53-r5-pm-1#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Restricting policy modification to owners in a controlled repository protects the plan from unauthorized change.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-2","slug":"pm-2","display_id":"PM-2","name":"Information Security Program Leadership Role","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Appoint a senior agency information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program.\n","citation":null,"parts":[],"objectives_count":5,"objectives_preview":[{"id":"[01]","statement":"a senior agency information security officer is appointed;"},{"id":"[02]","statement":"the senior agency information security officer is provided with the mission and resources to coordinate an organization-wide information security program;\n"},{"id":"[03]","statement":"the senior agency information security officer is provided with the mission and resources to develop an organization-wide information security program;\n"},{"id":"[04]","statement":"the senior agency information security officer is provided with the mission and resources to implement an organization-wide information security program;\n"},{"id":"[05]","statement":"the senior agency information security officer is provided with the mission and resources to maintain an organization-wide information security program.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-02-to-800-53-pm-2","source_ref":"control--ogrl-gv-02","target_ref":"requirement--nist-sp-800-53-r5-pm-2","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Written designation of an accountable security leader with authority and resources covers the appointment requirement; documented reporting lines add scope.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-3","slug":"pm-3","display_id":"PM-3","name":"Information Security and Privacy Resources","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Include the resources needed to implement the information security and privacy programs in capital planning and investment requests and document all exceptions to this requirement;\n"},{"id":"b","statement":"Prepare documentation required for addressing information security and privacy programs in capital planning and investment requests in accordance with applicable laws, executive orders, directives, policies, regulations, standards; and\n"},{"id":"c","statement":"Make available for expenditure, the planned information security and privacy resources.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"the resources needed to implement the information security program are included in capital planning and investment requests, and all exceptions are documented;\n"},{"id":"a-2","statement":"the resources needed to implement the privacy program are included in capital planning and investment requests, and all exceptions are documented;\n"},{"id":"b-1","statement":"the documentation required for addressing the information security program in capital planning and investment requests is prepared in accordance with applicable laws, executive orders, directives, policies, regulations, standards;\n"},{"id":"b-2","statement":"the documentation required for addressing the privacy program in capital planning and investment requests is prepared in accordance with applicable laws, executive orders, directives, policies, regulations, standards;\n"},{"id":"c-1","statement":"information security resources are made available for expenditure as planned;"},{"id":"c-2","statement":"privacy resources are made available for expenditure as planned."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-4","slug":"pm-4","display_id":"PM-4","name":"Plan of Action and Milestones Process","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement a process to ensure that plans of action and milestones for the information security, privacy, and supply chain risk management programs and associated organizational systems:\n"},{"id":"a.1","statement":"Are developed and maintained;"},{"id":"a.2","statement":"Document the remedial information security, privacy, and supply chain risk management actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation; and\n"},{"id":"a.3","statement":"Are reported in accordance with established reporting requirements."},{"id":"b","statement":"Review plans of action and milestones for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.\n"}],"objectives_count":14,"objectives_preview":[{"id":"a.1-1","statement":"a process to ensure that plans of action and milestones for the information security program and associated organizational systems are developed;\n"},{"id":"a.1-2","statement":"a process to ensure that plans of action and milestones for the information security program and associated organizational systems are maintained;\n"},{"id":"a.1-3","statement":"a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are developed;\n"},{"id":"a.1-4","statement":"a process to ensure that plans of action and milestones for the privacy program and associated organizational systems are maintained;\n"},{"id":"a.1-5","statement":"a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are developed;\n"},{"id":"a.1-6","statement":"a process to ensure that plans of action and milestones for the supply chain risk management program and associated organizational systems are maintained;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-5","slug":"pm-5","display_id":"PM-5","name":"System Inventory","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop and update {{ pm_05_odp }} an inventory of organizational systems.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"an inventory of organizational systems is developed;"},{"id":"[02]","statement":"the inventory of organizational systems is updated {{ pm_05_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-5-1","slug":"pm-5-1","display_id":"PM-5(1)","name":"Inventory of Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish, maintain, and update {{ pm_05_01_odp }} an inventory of all systems, applications, and projects that process personally identifiable information.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"pm-05(01).pm-05(01)[01]","statement":"an inventory of all systems, applications, and projects that process personally identifiable information is established;\n"},{"id":"pm-05(01).pm-05(01)[02]","statement":"an inventory of all systems, applications, and projects that process personally identifiable information is maintained;\n"},{"id":"pm-05(01).pm-05(01)[03]","statement":"an inventory of all systems, applications, and projects that process personally identifiable information is updated {{ pm_05_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-05-to-800-53-pm-5-1","source_ref":"control--ogrl-pr-05","target_ref":"requirement--nist-sp-800-53-r5-pm-5-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_05_01_odp":"pii_inventory_review_cadence"},"summary":"A maintained and periodically reviewed inventory of PII-processing systems satisfies PM-5(1).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-6","slug":"pm-6","display_id":"PM-6","name":"Measures of Performance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop, monitor, and report on the results of information security and privacy measures of performance.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"[01]","statement":"information security measures of performance are developed;"},{"id":"[02]","statement":"information security measures of performance are monitored;"},{"id":"[03]","statement":"the results of information security measures of performance are reported;"},{"id":"[04]","statement":"privacy measures of performance are developed;"},{"id":"[05]","statement":"privacy measures of performance are monitored;"},{"id":"[06]","statement":"the results of privacy measures of performance are reported."}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-06-to-800-53-pm-6","source_ref":"control--ogrl-gv-06","target_ref":"requirement--nist-sp-800-53-r5-pm-6","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Developing, monitoring, and reporting security metrics meets the security half of this requirement; privacy measures are not covered.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-7","slug":"pm-7","display_id":"PM-7","name":"Enterprise Architecture","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop and maintain an enterprise architecture with consideration for information security, privacy, and the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"[01]","statement":"an enterprise architecture is developed with consideration for information security;\n"},{"id":"[02]","statement":"an enterprise architecture is maintained with consideration for information security;\n"},{"id":"[03]","statement":"an enterprise architecture is developed with consideration for privacy;"},{"id":"[04]","statement":"an enterprise architecture is maintained with consideration for privacy;"},{"id":"[05]","statement":"an enterprise architecture is developed with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation;\n"},{"id":"[06]","statement":"an enterprise architecture is maintained with consideration for the resulting risk to organizational operations and assets, individuals, other organizations, and the Nation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-7-1","slug":"pm-7-1","display_id":"PM-7(1)","name":"Offloading","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Offload {{ pm_07_01_odp }} to other systems, system components, or an external provider.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pm-07(01)","statement":"{{ pm_07_01_odp }} are offloaded to other systems, system components, or an external provider.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-8","slug":"pm-8","display_id":"PM-8","name":"Critical Infrastructure Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Address information security and privacy issues in the development, documentation, and updating of a critical infrastructure and key resources protection plan.\n","citation":null,"parts":[],"objectives_count":6,"objectives_preview":[{"id":"[01]","statement":"information security issues are addressed in the development of a critical infrastructure and key resources protection plan;\n"},{"id":"[02]","statement":"information security issues are addressed in the documentation of a critical infrastructure and key resources protection plan;\n"},{"id":"[03]","statement":"information security issues are addressed in the update of a critical infrastructure and key resources protection plan;\n"},{"id":"[04]","statement":"privacy issues are addressed in the development of a critical infrastructure and key resources protection plan;\n"},{"id":"[05]","statement":"privacy issues are addressed in the documentation of a critical infrastructure and key resources protection plan;\n"},{"id":"[06]","statement":"privacy issues are addressed in the update of a critical infrastructure and key resources protection plan.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-9","slug":"pm-9","display_id":"PM-9","name":"Risk Management Strategy","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develops a comprehensive strategy to manage:"},{"id":"a.1","statement":"Security risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of organizational systems; and\n"},{"id":"a.2","statement":"Privacy risk to individuals resulting from the authorized processing of personally identifiable information;\n"},{"id":"b","statement":"Implement the risk management strategy consistently across the organization; and"},{"id":"c","statement":"Review and update the risk management strategy {{ pm_09_odp }} or as required, to address organizational changes.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a.1","statement":"a comprehensive strategy is developed to manage security risk to organizational operations and assets, individuals, other organizations, and the Nation associated with the operation and use of organizational systems;\n"},{"id":"a.2","statement":"a comprehensive strategy is developed to manage privacy risk to individuals resulting from the authorized processing of personally identifiable information;\n"},{"id":"b","statement":"the risk management strategy is implemented consistently across the organization;\n"},{"id":"c","statement":"the risk management strategy is reviewed and updated {{ pm_09_odp }} or as required to address organizational changes.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-rm-01-to-800-53-pm-9-a-1","source_ref":"control--ogrl-rm-01","target_ref":"requirement--nist-sp-800-53-r5-pm-9#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The approved methodology is the organization's strategy for managing security risk.\n"},{"id":"mapping--ogrl-rm-01-to-800-53-pm-9-c","source_ref":"control--ogrl-rm-01","target_ref":"requirement--nist-sp-800-53-r5-pm-9#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_09_odp":"strategy_review_frequency"},"summary":"Periodic and change-driven review of the methodology meets the strategy review requirement.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-10","slug":"pm-10","display_id":"PM-10","name":"Authorization Process","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Manage the security and privacy state of organizational systems and the environments in which those systems operate through authorization processes;\n"},{"id":"b","statement":"Designate individuals to fulfill specific roles and responsibilities within the organizational risk management process; and\n"},{"id":"c","statement":"Integrate the authorization processes into an organization-wide risk management program.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"the security state of organizational systems and the environments in which those systems operate are managed through authorization processes;\n"},{"id":"a-2","statement":"the privacy state of organizational systems and the environments in which those systems operate are managed through authorization processes;\n"},{"id":"b","statement":"individuals are designated to fulfill specific roles and responsibilities within the organizational risk management process;\n"},{"id":"c","statement":"the authorization processes are integrated into an organization-wide risk management program.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-11","slug":"pm-11","display_id":"PM-11","name":"Mission and Business Process Definition","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Define organizational mission and business processes with consideration for information security and privacy and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation; and\n"},{"id":"b","statement":"Determine information protection and personally identifiable information processing needs arising from the defined mission and business processes; and\n"},{"id":"c","statement":"Review and revise the mission and business processes {{ pm_11_odp }}."}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"organizational mission and business processes are defined with consideration for information security;\n"},{"id":"a-2","statement":"organizational mission and business processes are defined with consideration for privacy;\n"},{"id":"a-3","statement":"organizational mission and business processes are defined with consideration for the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation;\n"},{"id":"b-1","statement":"information protection needs arising from the defined mission and business processes are determined;\n"},{"id":"b-2","statement":"personally identifiable information processing needs arising from the defined mission and business processes are determined;\n"},{"id":"c","statement":"the mission and business processes are reviewed and revised {{ pm_11_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-12","slug":"pm-12","display_id":"PM-12","name":"Insider Threat Program","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement an insider threat program that includes a cross-discipline insider threat incident handling team.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"an insider threat program that includes a cross-discipline insider threat incident handling team is implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-13","slug":"pm-13","display_id":"PM-13","name":"Security and Privacy Workforce","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish a security and privacy workforce development and improvement program.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"a security workforce development and improvement program is established;"},{"id":"_obj-2","statement":"a privacy workforce development and improvement program is established."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-14","slug":"pm-14","display_id":"PM-14","name":"Testing, Training, and Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement a process for ensuring that organizational plans for conducting security and privacy testing, training, and monitoring activities associated with organizational systems:\n"},{"id":"a.1","statement":"Are developed and maintained; and"},{"id":"a.2","statement":"Continue to be executed; and"},{"id":"b","statement":"Review testing, training, and monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.\n"}],"objectives_count":12,"objectives_preview":[{"id":"a.1-1","statement":"a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are developed;\n"},{"id":"a.1-2","statement":"a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems are maintained;\n"},{"id":"a.1-3","statement":"a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are developed;\n"},{"id":"a.1-4","statement":"a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems are maintained;\n"},{"id":"a.2-1","statement":"a process is implemented for ensuring that organizational plans for conducting security testing, training, and monitoring activities associated with organizational systems continue to be executed;\n"},{"id":"a.2-2","statement":"a process is implemented for ensuring that organizational plans for conducting privacy testing, training, and monitoring activities associated with organizational systems continue to be executed;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-15","slug":"pm-15","display_id":"PM-15","name":"Security and Privacy Groups and Associations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish and institutionalize contact with selected groups and associations within the security and privacy communities:\n","citation":null,"parts":[{"id":"a","statement":"To facilitate ongoing security and privacy education and training for organizational personnel;\n"},{"id":"b","statement":"To maintain currency with recommended security and privacy practices, techniques, and technologies; and\n"},{"id":"c","statement":"To share current security and privacy information, including threats, vulnerabilities, and incidents.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"contact is established and institutionalized with selected groups and associations within the security community to facilitate ongoing security education and training for organizational personnel;\n"},{"id":"a-2","statement":"contact is established and institutionalized with selected groups and associations within the privacy community to facilitate ongoing privacy education and training for organizational personnel;\n"},{"id":"b-1","statement":"contact is established and institutionalized with selected groups and associations within the security community to maintain currency with recommended security practices, techniques, and technologies;\n"},{"id":"b-2","statement":"contact is established and institutionalized with selected groups and associations within the privacy community to maintain currency with recommended privacy practices, techniques, and technologies;\n"},{"id":"c-1","statement":"contact is established and institutionalized with selected groups and associations within the security community to share current security information, including threats, vulnerabilities, and incidents;\n"},{"id":"c-2","statement":"contact is established and institutionalized with selected groups and associations within the privacy community to share current privacy information, including threats, vulnerabilities, and incidents.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-16","slug":"pm-16","display_id":"PM-16","name":"Threat Awareness Program","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a threat awareness program that includes a cross-organization information-sharing capability for threat intelligence is implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-16-1","slug":"pm-16-1","display_id":"PM-16(1)","name":"Automated Means for Sharing Threat Intelligence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automated mechanisms to maximize the effectiveness of sharing threat intelligence information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pm-16(01)","statement":"automated mechanisms are employed to maximize the effectiveness of sharing threat intelligence information.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-16-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-17","slug":"pm-17","display_id":"PM-17","name":"Protecting Controlled Unclassified Information on External Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish policy and procedures to ensure that requirements for the protection of controlled unclassified information that is processed, stored or transmitted on external systems, are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards; and\n"},{"id":"b","statement":"Review and update the policy and procedures {{ pm_17_prm_1 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"policy is established to ensure that requirements for the protection of controlled unclassified information that is processed, stored, or transmitted on external systems are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards;\n"},{"id":"a-2","statement":"procedures are established to ensure that requirements for the protection of controlled unclassified information that is processed, stored, or transmitted on external systems are implemented in accordance with applicable laws, executive orders, directives, policies, regulations, and standards;\n"},{"id":"b-1","statement":"policy is reviewed and updated {{ pm_17_odp_01 }};"},{"id":"b-2","statement":"procedures are reviewed and updated {{ pm_17_odp_02 }}"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-18","slug":"pm-18","display_id":"PM-18","name":"Privacy Program Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and disseminate an organization-wide privacy program plan that provides an overview of the agency’s privacy program, and:\n"},{"id":"a.1","statement":"Includes a description of the structure of the privacy program and the resources dedicated to the privacy program;\n"},{"id":"a.2","statement":"Provides an overview of the requirements for the privacy program and a description of the privacy program management controls and common controls in place or planned for meeting those requirements;\n"},{"id":"a.3","statement":"Includes the role of the senior agency official for privacy and the identification and assignment of roles of other privacy officials and staff and their responsibilities;\n"},{"id":"a.4","statement":"Describes management commitment, compliance, and the strategic goals and objectives of the privacy program;\n"},{"id":"a.5","statement":"Reflects coordination among organizational entities responsible for the different aspects of privacy; and\n"},{"id":"a.6","statement":"Is approved by a senior official with responsibility and accountability for the privacy risk being incurred to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation; and\n"},{"id":"b","statement":"Update the plan {{ pm_18_odp }} and to address changes in federal privacy laws and policy and organizational changes and problems identified during plan implementation or privacy control assessments.\n"}],"objectives_count":18,"objectives_preview":[{"id":"a-1","statement":"an organization-wide privacy program plan that provides an overview of the agency’s privacy program is developed;\n"},{"id":"a.1-1","statement":"the privacy program plan includes a description of the structure of the privacy program;\n"},{"id":"a.1-2","statement":"the privacy program plan includes a description of the resources dedicated to the privacy program;\n"},{"id":"a.2-1","statement":"the privacy program plan provides an overview of the requirements for the privacy program;\n"},{"id":"a.2-2","statement":"the privacy program plan provides a description of the privacy program management controls in place or planned for meeting the requirements of the privacy program;\n"},{"id":"a.2-3","statement":"the privacy program plan provides a description of common controls in place or planned for meeting the requirements of the privacy program;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-19","slug":"pm-19","display_id":"PM-19","name":"Privacy Program Leadership Role","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Appoint a senior agency official for privacy with the authority, mission, accountability, and resources to coordinate, develop, and implement, applicable privacy requirements and manage privacy risks through the organization-wide privacy program.\n","citation":null,"parts":[],"objectives_count":5,"objectives_preview":[{"id":"_obj-1","statement":"a senior agency official for privacy with authority, mission, accountability, and resources is appointed;\n"},{"id":"_obj-2","statement":"the senior agency official for privacy coordinates applicable privacy requirements;\n"},{"id":"_obj-3","statement":"the senior agency official for privacy develops applicable privacy requirements;"},{"id":"_obj-4","statement":"the senior agency official for privacy implements applicable privacy requirements;\n"},{"id":"_obj-5","statement":"the senior agency official for privacy manages privacy risks through the organization-wide privacy program.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-11-to-800-53-pm-19","source_ref":"control--ogrl-pr-11","target_ref":"requirement--nist-sp-800-53-r5-pm-19","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Designating an accountable privacy lead for complaints is a narrow part of the privacy leadership role in PM-19.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-20","slug":"pm-20","display_id":"PM-20","name":"Dissemination of Privacy Program Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Maintain a central resource webpage on the organization’s principal public website that serves as a central source of information about the organization’s privacy program and that:\n","citation":null,"parts":[{"id":"a","statement":"Ensures that the public has access to information about organizational privacy activities and can communicate with its senior agency official for privacy;\n"},{"id":"b","statement":"Ensures that organizational privacy practices and reports are publicly available; and\n"},{"id":"c","statement":"Employs publicly facing email addresses and/or phone lines to enable the public to provide feedback and/or direct questions to privacy offices regarding privacy practices.\n"}],"objectives_count":7,"objectives_preview":[{"id":"_obj-1","statement":"a central resource webpage is maintained on the organization’s principal public website;\n"},{"id":"_obj-2","statement":"the webpage serves as a central source of information about the organization’s privacy program;\n"},{"id":"a-1","statement":"the webpage ensures that the public has access to information about organizational privacy activities;\n"},{"id":"a-2","statement":"the webpage ensures that the public can communicate with its senior agency official for privacy;\n"},{"id":"b-1","statement":"the webpage ensures that organizational privacy practices are publicly available;\n"},{"id":"b-2","statement":"the webpage ensures that organizational privacy reports are publicly available;"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-20-1","slug":"pm-20-1","display_id":"PM-20(1)","name":"Privacy Policies on Websites, Applications, and Digital Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Develop and post privacy policies on all external-facing websites, mobile applications, and other digital services, that:\n","citation":null,"parts":[{"id":"a","statement":"Are written in plain language and organized in a way that is easy to understand and navigate;\n"},{"id":"b","statement":"Provide information needed by the public to make an informed decision about whether and how to interact with the organization; and\n"},{"id":"c","statement":"Are updated whenever the organization makes a substantive change to the practices it describes and includes a time/date stamp to inform the public of the date of the most recent changes.\n"}],"objectives_count":9,"objectives_preview":[{"id":"pm-20(01).pm-20(01)[01]","statement":"privacy policies are developed and posted on all external-facing websites;"},{"id":"pm-20(01).pm-20(01)[02]","statement":"privacy policies are developed and posted on all mobile applications;"},{"id":"pm-20(01).pm-20(01)[03]","statement":"privacy policies are developed and posted on all other digital services;"},{"id":"a-1","statement":"the privacy policies are written in plain language;"},{"id":"a-2","statement":"the privacy policies are organized in a way that is easy to understand and navigate;\n"},{"id":"b-1","statement":"the privacy policies provide the information needed by the public to make an informed decision about whether to interact with the organization;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-20-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-21","slug":"pm-21","display_id":"PM-21","name":"Accounting of Disclosures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and maintain an accurate accounting of disclosures of personally identifiable information, including:\n"},{"id":"a.1","statement":"Date, nature, and purpose of each disclosure; and"},{"id":"a.2","statement":"Name and address, or other contact information of the individual or organization to which the disclosure was made;\n"},{"id":"b","statement":"Retain the accounting of disclosures for the length of the time the personally identifiable information is maintained or five years after the disclosure is made, whichever is longer; and\n"},{"id":"c","statement":"Make the accounting of disclosures available to the individual to whom the personally identifiable information relates upon request.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a.1-1","statement":"the accounting includes the date of each disclosure;"},{"id":"a.1-2","statement":"the accounting includes the nature of each disclosure;"},{"id":"a.1-3","statement":"the accounting includes the purpose of each disclosure;"},{"id":"a.2-1","statement":"the accounting includes the name of the individual or organization to whom the disclosure was made;\n"},{"id":"a.2-2","statement":"the accounting includes the address or other contact information of the individual or organization to whom the disclosure was made;\n"},{"id":"b","statement":"the accounting of disclosures is retained for the length of time that the personally identifiable information is maintained or five years after the disclosure is made, whichever is longer;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-09-to-800-53-pm-21","source_ref":"control--ogrl-pr-09","target_ref":"requirement--nist-sp-800-53-r5-pm-21","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Recording disclosure details, retaining them, and providing them on request covers PM-21.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-22","slug":"pm-22","display_id":"PM-22","name":"Personally Identifiable Information Quality Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop and document organization-wide policies and procedures for:","citation":null,"parts":[{"id":"a","statement":"Reviewing for the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle;\n"},{"id":"b","statement":"Correcting or deleting inaccurate or outdated personally identifiable information;\n"},{"id":"c","statement":"Disseminating notice of corrected or deleted personally identifiable information to individuals or other appropriate entities; and\n"},{"id":"d","statement":"Appeals of adverse decisions on correction or deletion requests."}],"objectives_count":16,"objectives_preview":[{"id":"_obj-1","statement":"organization-wide policies for personally identifiable information quality management are developed and documented;\n"},{"id":"_obj-2","statement":"organization-wide procedures for personally identifiable information quality management are developed and documented;\n"},{"id":"a-1","statement":"the policies address reviewing the accuracy of personally identifiable information across the information life cycle;\n"},{"id":"a-2","statement":"the policies address reviewing the relevance of personally identifiable information across the information life cycle;\n"},{"id":"a-3","statement":"the policies address reviewing the timeliness of personally identifiable information across the information life cycle;\n"},{"id":"a-4","statement":"the policies address reviewing the completeness of personally identifiable information across the information life cycle;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-23","slug":"pm-23","display_id":"PM-23","name":"Data Governance Body","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish a Data Governance Body consisting of {{ pm_23_odp_01 }} with {{ pm_23_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a Data Governance Body consisting of {{ pm_23_odp_01 }} with {{ pm_23_odp_02 }} is established.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-24","slug":"pm-24","display_id":"PM-24","name":"Data Integrity Board","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish a Data Integrity Board to:","citation":null,"parts":[{"id":"a","statement":"Review proposals to conduct or participate in a matching program; and"},{"id":"b","statement":"Conduct an annual review of all matching programs in which the agency has participated.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the Data Integrity Board reviews proposals to conduct or participate in a matching program;\n"},{"id":"b","statement":"the Data Integrity Board conducts an annual review of all matching programs in which the agency has participated.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-25","slug":"pm-25","display_id":"PM-25","name":"Minimization of Personally Identifiable Information Used in Testing, Training, and Research\n","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and implement policies and procedures that address the use of personally identifiable information for internal testing, training, and research;\n"},{"id":"b","statement":"Limit or minimize the amount of personally identifiable information used for internal testing, training, and research purposes;\n"},{"id":"c","statement":"Authorize the use of personally identifiable information when such information is required for internal testing, training, and research; and\n"},{"id":"d","statement":"Review and update policies and procedures {{ pm_25_prm_1 }}."}],"objectives_count":22,"objectives_preview":[{"id":"a-1","statement":"policies that address the use of personally identifiable information for internal testing are developed and documented;\n"},{"id":"a-2","statement":"policies that address the use of personally identifiable information for internal training are developed and documented;\n"},{"id":"a-3","statement":"policies that address the use of personally identifiable information for internal research are developed and documented;\n"},{"id":"a-4","statement":"procedures that address the use of personally identifiable information for internal testing are developed and documented;\n"},{"id":"a-5","statement":"procedures that address the use of personally identifiable information for internal training are developed and documented;\n"},{"id":"a-6","statement":"procedures that address the use of personally identifiable information for internal research are developed and documented;\n"}],"params_count":5,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-26","slug":"pm-26","display_id":"PM-26","name":"Complaint Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement a process for receiving and responding to complaints, concerns, or questions from individuals about the organizational security and privacy practices that includes:\n","citation":null,"parts":[{"id":"a","statement":"Mechanisms that are easy to use and readily accessible by the public;"},{"id":"b","statement":"All information necessary for successfully filing complaints;"},{"id":"c","statement":"Tracking mechanisms to ensure all complaints received are reviewed and addressed within {{ pm_26_prm_1 }};\n"},{"id":"d","statement":"Acknowledgement of receipt of complaints, concerns, or questions from individuals within {{ pm_26_odp_03 }} ; and\n"},{"id":"e","statement":"Response to complaints, concerns, or questions from individuals within {{ pm_26_odp_04 }}.\n"}],"objectives_count":9,"objectives_preview":[{"id":"_obj-1","statement":"a process for receiving complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented;\n"},{"id":"_obj-2","statement":"a process for responding to complaints, concerns, or questions from individuals about organizational security and privacy practices is implemented;\n"},{"id":"a-1","statement":"the complaint management process includes mechanisms that are easy to use by the public;\n"},{"id":"a-2","statement":"the complaint management process includes mechanisms that are readily accessible by the public;\n"},{"id":"b","statement":"the complaint management process includes all information necessary for successfully filing complaints;\n"},{"id":"c-1","statement":"the complaint management process includes tracking mechanisms to ensure that all complaints are reviewed within {{ pm_26_odp_01 }};\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-11-to-800-53-pm-26","source_ref":"control--ogrl-pr-11","target_ref":"requirement--nist-sp-800-53-r5-pm-26","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pm_26_odp_03":"complaint_acknowledgement_sla","pm_26_odp_04":"complaint_response_sla","pm_26_prm_1":"complaint_resolution_sla"},"summary":"Published channels, filing information, tracking, and acknowledgement, response, and resolution timelines cover PM-26.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-26.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-27","slug":"pm-27","display_id":"PM-27","name":"Privacy Reporting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop {{ pm_27_odp_01 }} and disseminate to:"},{"id":"a.1","statement":"{{ pm_27_odp_02 }} to demonstrate accountability with statutory, regulatory, and policy privacy mandates; and\n"},{"id":"a.2","statement":"{{ pm_27_odp_03 }} and other personnel with responsibility for monitoring privacy program compliance; and\n"},{"id":"b","statement":"Review and update privacy reports {{ pm_27_odp_04 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a.1","statement":"the privacy reports are disseminated to {{ pm_27_odp_02 }} to demonstrate accountability with statutory, regulatory, and policy privacy mandates;\n"},{"id":"a.2-1","statement":"the privacy reports are disseminated to {{ pm_27_odp_03 }};"},{"id":"a.2-2","statement":"the privacy reports are disseminated to other personnel responsible for monitoring privacy program compliance;\n"},{"id":"b","statement":"the privacy reports are reviewed and updated {{ pm_27_odp_04 }}."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-27.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-28","slug":"pm-28","display_id":"PM-28","name":"Risk Framing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify and document:"},{"id":"a.1","statement":"Assumptions affecting risk assessments, risk responses, and risk monitoring;"},{"id":"a.2","statement":"Constraints affecting risk assessments, risk responses, and risk monitoring;"},{"id":"a.3","statement":"Priorities and trade-offs considered by the organization for managing risk; and"},{"id":"a.4","statement":"Organizational risk tolerance;"},{"id":"b","statement":"Distribute the results of risk framing activities to {{ pm_28_odp_01 }} ; and"},{"id":"c","statement":"Review and update risk framing considerations {{ pm_28_odp_02 }}."}],"objectives_count":11,"objectives_preview":[{"id":"a.1-1","statement":"assumptions affecting risk assessments are identified and documented;"},{"id":"a.1-2","statement":"assumptions affecting risk responses are identified and documented;"},{"id":"a.1-3","statement":"assumptions affecting risk monitoring are identified and documented;"},{"id":"a.2-1","statement":"constraints affecting risk assessments are identified and documented;"},{"id":"a.2-2","statement":"constraints affecting risk responses are identified and documented;"},{"id":"a.2-3","statement":"constraints affecting risk monitoring are identified and documented;"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-28.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-29","slug":"pm-29","display_id":"PM-29","name":"Risk Management Program Leadership Roles","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Appoint a Senior Accountable Official for Risk Management to align organizational information security and privacy management processes with strategic, operational, and budgetary planning processes; and\n"},{"id":"b","statement":"Establish a Risk Executive (function) to view and analyze risk from an organization-wide perspective and ensure management of risk is consistent across the organization.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"a Senior Accountable Official for Risk Management is appointed;"},{"id":"a-2","statement":"a Senior Accountable Official for Risk Management aligns information security and privacy management processes with strategic, operational, and budgetary planning processes;\n"},{"id":"b-1","statement":"a Risk Executive (function) is established;"},{"id":"b-2","statement":"a Risk Executive (function) views and analyzes risk from an organization-wide perspective;\n"},{"id":"b-3","statement":"a Risk Executive (function) ensures that the management of risk is consistent across the organization.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-29.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-30","slug":"pm-30","display_id":"PM-30","name":"Supply Chain Risk Management Strategy","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop an organization-wide strategy for managing supply chain risks associated with the development, acquisition, maintenance, and disposal of systems, system components, and system services;\n"},{"id":"b","statement":"Implement the supply chain risk management strategy consistently across the organization; and\n"},{"id":"c","statement":"Review and update the supply chain risk management strategy on {{ pm_30_odp }} or as required, to address organizational changes.\n"}],"objectives_count":15,"objectives_preview":[{"id":"a-1","statement":"an organization-wide strategy for managing supply chain risks is developed;"},{"id":"a-2","statement":"the supply chain risk management strategy addresses risks associated with the development of systems;\n"},{"id":"a-3","statement":"the supply chain risk management strategy addresses risks associated with the development of system components;\n"},{"id":"a-4","statement":"the supply chain risk management strategy addresses risks associated with the development of system services;\n"},{"id":"a-5","statement":"the supply chain risk management strategy addresses risks associated with the acquisition of systems;\n"},{"id":"a-6","statement":"the supply chain risk management strategy addresses risks associated with the acquisition of system components;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-30.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-30-1","slug":"pm-30-1","display_id":"PM-30(1)","name":"Suppliers of Critical or Mission-essential Items","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify, prioritize, and assess suppliers of critical or mission-essential technologies, products, and services.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"pm-30(01).pm-30(01)[01]","statement":"suppliers of critical or mission-essential technologies, products, and services are identified;\n"},{"id":"pm-30(01).pm-30(01)[02]","statement":"suppliers of critical or mission-essential technologies, products, and services are prioritized;\n"},{"id":"pm-30(01).pm-30(01)[03]","statement":"suppliers of critical or mission-essential technologies, products, and services are assessed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-30-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-31","slug":"pm-31","display_id":"PM-31","name":"Continuous Monitoring Strategy","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include:\n","citation":null,"parts":[{"id":"a","statement":"Establishing the following organization-wide metrics to be monitored: {{ pm_31_odp_01 }};\n"},{"id":"b","statement":"Establishing {{ pm_31_odp_02 }} and {{ pm_31_odp_03 }} for control effectiveness;\n"},{"id":"c","statement":"Ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy;\n"},{"id":"d","statement":"Correlation and analysis of information generated by control assessments and monitoring;\n"},{"id":"e","statement":"Response actions to address results of the analysis of control assessment and monitoring information; and\n"},{"id":"f","statement":"Reporting the security and privacy status of organizational systems to {{ pm_31_prm_4 }} {{ pm_31_prm_5 }}.\n"}],"objectives_count":10,"objectives_preview":[{"id":"a","statement":"continuous monitoring programs are implemented that include establishing {{ pm_31_odp_01 }} to be monitored;\n"},{"id":"b-1","statement":"continuous monitoring programs are implemented that establish {{ pm_31_odp_02 }} for monitoring;\n"},{"id":"b-2","statement":"continuous monitoring programs are implemented that establish {{ pm_31_odp_03 }} for assessment of control effectiveness;\n"},{"id":"c","statement":"continuous monitoring programs are implemented that include monitoring {{ pm_31_odp_01 }} on an ongoing basis in accordance with the continuous monitoring strategy;\n"},{"id":"d-1","statement":"continuous monitoring programs are implemented that include correlating information generated by control assessments and monitoring;\n"},{"id":"d-2","statement":"continuous monitoring programs are implemented that include analyzing information generated by control assessments and monitoring;\n"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-31.yaml"},{"id":"requirement--nist-sp-800-53-r5-pm-32","slug":"pm-32","display_id":"PM-32","name":"Purposing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Analyze {{ pm_32_odp }} supporting mission essential services or functions to ensure that the information resources are being used consistent with their intended purpose.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ pm_32_odp }} supporting mission-essential services or functions are analyzed to ensure that the information resources are being used in a manner that is consistent with their intended purpose.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pm-32.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-1","slug":"ps-1","display_id":"PS-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ps_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ps_01_odp_03 }} personnel security policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the personnel security policy and the associated personnel security controls;\n"},{"id":"b","statement":"Designate an {{ ps_01_odp_04 }} to manage the development, documentation, and dissemination of the personnel security policy and procedures; and\n"},{"id":"c","statement":"Review and update the current personnel security:"},{"id":"c.1","statement":"Policy {{ ps_01_odp_05 }} and following {{ ps_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ps_01_odp_07 }} and following {{ ps_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a personnel security policy is developed and documented;"},{"id":"a-2","statement":"the personnel security policy is disseminated to {{ ps_01_odp_01 }};"},{"id":"a-3","statement":"personnel security procedures to facilitate the implementation of the personnel security policy and associated personnel security controls are developed and documented;\n"},{"id":"a-4","statement":"the personnel security procedures are disseminated to {{ ps_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ ps_01_odp_03 }} personnel security policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ ps_01_odp_03 }} personnel security policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-2","slug":"ps-2","display_id":"PS-2","name":"Position Risk Designation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Assign a risk designation to all organizational positions;"},{"id":"b","statement":"Establish screening criteria for individuals filling those positions; and"},{"id":"c","statement":"Review and update position risk designations {{ ps_02_odp }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"a risk designation is assigned to all organizational positions;"},{"id":"b","statement":"screening criteria are established for individuals filling organizational positions;\n"},{"id":"c","statement":"position risk designations are reviewed and updated {{ ps_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-3","slug":"ps-3","display_id":"PS-3","name":"Personnel Screening","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Screen individuals prior to authorizing access to the system; and"},{"id":"b","statement":"Rescreen individuals in accordance with {{ ps_3_prm_1 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"individuals are screened prior to authorizing access to the system;"},{"id":"b-1","statement":"individuals are rescreened in accordance with {{ ps_03_odp_01 }};"},{"id":"b-2","statement":"where rescreening is so indicated, individuals are rescreened {{ ps_03_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-01-to-800-53-ps-3","source_ref":"control--ogrl-hr-01","target_ref":"requirement--nist-sp-800-53-r5-ps-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_03_odp_01":"rescreening_conditions"},"summary":"Screening before access plus condition-based rescreening covers both parts of PS-3.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-3-1","slug":"ps-3-1","display_id":"PS-3(1)","name":"Classified Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that individuals accessing a system processing, storing, or transmitting classified information are cleared and indoctrinated to the highest classification level of the information to which they have access on the system.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ps-03(01).ps-03(01)[01]","statement":"individuals accessing a system processing, storing, or transmitting classified information are cleared;\n"},{"id":"ps-03(01).ps-03(01)[02]","statement":"individuals accessing a system processing, storing, or transmitting classified information are indoctrinated to the highest classification level of the information to which they have access on the system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-3-2","slug":"ps-3-2","display_id":"PS-3(2)","name":"Formal Indoctrination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that individuals accessing a system processing, storing, or transmitting types of classified information that require formal indoctrination, are formally indoctrinated for all the relevant types of information to which they have access on the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ps-03(02)","statement":"individuals accessing a system processing, storing, or transmitting types of classified information that require formal indoctrination are formally indoctrinated for all of the relevant types of information to which they have access on the system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-3-3","slug":"ps-3-3","display_id":"PS-3(3)","name":"Information Requiring Special Protective Measures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection:\n","citation":null,"parts":[{"id":"a","statement":"Have valid access authorizations that are demonstrated by assigned official government duties; and\n"},{"id":"b","statement":"Satisfy {{ ps_03_03_odp }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"individuals accessing a system processing, storing, or transmitting information requiring special protection have valid access authorizations that are demonstrated by assigned official government duties;\n"},{"id":"b","statement":"individuals accessing a system processing, storing, or transmitting information requiring special protection satisfy {{ ps_03_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-3-4","slug":"ps-3-4","display_id":"PS-3(4)","name":"Citizenship Requirements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that individuals accessing a system processing, storing, or transmitting {{ ps_03_04_odp_01 }} meet {{ ps_03_04_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ps-03(04)","statement":"individuals accessing a system processing, storing, or transmitting {{ ps_03_04_odp_01 }} meet {{ ps_03_04_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-4","slug":"ps-4","display_id":"PS-4","name":"Personnel Termination","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Upon termination of individual employment:","citation":null,"parts":[{"id":"a","statement":"Disable system access within {{ ps_04_odp_01 }};"},{"id":"b","statement":"Terminate or revoke any authenticators and credentials associated with the individual;\n"},{"id":"c","statement":"Conduct exit interviews that include a discussion of {{ ps_04_odp_02 }};"},{"id":"d","statement":"Retrieve all security-related organizational system-related property; and"},{"id":"e","statement":"Retain access to organizational information and systems formerly controlled by terminated individual.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"upon termination of individual employment, system access is disabled within {{ ps_04_odp_01 }};\n"},{"id":"b","statement":"upon termination of individual employment, any authenticators and credentials are terminated or revoked;\n"},{"id":"c","statement":"upon termination of individual employment, exit interviews that include a discussion of {{ ps_04_odp_02 }} are conducted;\n"},{"id":"d","statement":"upon termination of individual employment, all security-related organizational system-related property is retrieved;\n"},{"id":"e","statement":"upon termination of individual employment, access to organizational information and systems formerly controlled by the terminated individual are retained.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-02-to-800-53-ps-4","source_ref":"control--ogrl-hr-02","target_ref":"requirement--nist-sp-800-53-r5-ps-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_04_odp_01":"access_disable_sla","ps_04_odp_02":"exit_briefing_topics"},"summary":"The offboarding checklist covers access disablement, credential revocation, exit briefing, property recovery, and retained data access required by PS-4.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-4-1","slug":"ps-4-1","display_id":"PS-4(1)","name":"Post-employment Requirements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Notify terminated individuals of applicable, legally binding post-employment requirements for the protection of organizational information; and\n"},{"id":"b","statement":"Require terminated individuals to sign an acknowledgment of post-employment requirements as part of the organizational termination process.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"terminated individuals are notified of applicable, legally binding post-employment requirements for the protection of organizational information;\n"},{"id":"b","statement":"terminated individuals are required to sign an acknowledgement of post-employment requirements as part of the organizational termination process.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-4-2","slug":"ps-4-2","display_id":"PS-4(2)","name":"Automated Actions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use {{ ps_04_02_odp_01 }} to {{ ps_04_02_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ps-04(02)","statement":"{{ ps_04_02_odp_01 }} are used to {{ ps_04_02_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-5","slug":"ps-5","display_id":"PS-5","name":"Personnel Transfer","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Review and confirm ongoing operational need for current logical and physical access authorizations to systems and facilities when individuals are reassigned or transferred to other positions within the organization;\n"},{"id":"b","statement":"Initiate {{ ps_05_odp_01 }} within {{ ps_05_odp_02 }};"},{"id":"c","statement":"Modify access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and\n"},{"id":"d","statement":"Notify {{ ps_05_odp_03 }} within {{ ps_05_odp_04 }}."}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"the ongoing operational need for current logical and physical access authorizations to systems and facilities are reviewed and confirmed when individuals are reassigned or transferred to other positions within the organization;\n"},{"id":"b","statement":"{{ ps_05_odp_01 }} are initiated within {{ ps_05_odp_02 }};"},{"id":"c","statement":"access authorization is modified as needed to correspond with any changes in operational need due to reassignment or transfer;\n"},{"id":"d","statement":"{{ ps_05_odp_03 }} are notified within {{ ps_05_odp_04 }}."}],"params_count":4,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-02-to-800-53-ps-5-a","source_ref":"control--ogrl-hr-02","target_ref":"requirement--nist-sp-800-53-r5-ps-5#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The transfer access review confirms continued need for existing access when personnel change roles.\n"},{"id":"mapping--ogrl-hr-02-to-800-53-ps-5-c","source_ref":"control--ogrl-hr-02","target_ref":"requirement--nist-sp-800-53-r5-ps-5#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Adjusting access to match the new role after a transfer is the modification PS-5(c) calls for.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-6","slug":"ps-6","display_id":"PS-6","name":"Access Agreements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and document access agreements for organizational systems;"},{"id":"b","statement":"Review and update the access agreements {{ ps_06_odp_01 }} ; and"},{"id":"c","statement":"Verify that individuals requiring access to organizational information and systems:\n"},{"id":"c.1","statement":"Sign appropriate access agreements prior to being granted access; and"},{"id":"c.2","statement":"Re-sign access agreements to maintain access to organizational systems when access agreements have been updated or {{ ps_06_odp_02 }}.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"access agreements are developed and documented for organizational systems;"},{"id":"b","statement":"the access agreements are reviewed and updated {{ ps_06_odp_01 }};"},{"id":"c.1","statement":"individuals requiring access to organizational information and systems sign appropriate access agreements prior to being granted access;\n"},{"id":"c.2","statement":"individuals requiring access to organizational information and systems re-sign access agreements to maintain access to organizational systems when access agreements have been updated or {{ ps_06_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-03-to-800-53-ps-6","source_ref":"control--ogrl-hr-03","target_ref":"requirement--nist-sp-800-53-r5-ps-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_06_odp_01":"agreement_review_frequency","ps_06_odp_02":"reacknowledgement_frequency"},"summary":"Documented agreements signed before access, periodically reviewed, and re-signed on change or cadence satisfy PS-6.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-6-1","slug":"ps-6-1","display_id":"PS-6(1)","name":"Information Requiring Special Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ps-6-1_to_nist-sp-800-53-r5-ps-3","source_ref":"requirement--nist-sp-800-53-r5-ps-6-1","target_ref":"requirement--nist-sp-800-53-r5-ps-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-6-2","slug":"ps-6-2","display_id":"PS-6(2)","name":"Classified Information Requiring Special Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that access to classified information requiring special protection is granted only to individuals who:\n","citation":null,"parts":[{"id":"a","statement":"Have a valid access authorization that is demonstrated by assigned official government duties;\n"},{"id":"b","statement":"Satisfy associated personnel security criteria; and"},{"id":"c","statement":"Have read, understood, and signed a nondisclosure agreement."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"access to classified information requiring special protection is granted only to individuals who have a valid access authorization that is demonstrated by assigned official government duties;\n"},{"id":"b","statement":"access to classified information requiring special protection is granted only to individuals who satisfy associated personnel security criteria;\n"},{"id":"c","statement":"access to classified information requiring special protection is granted only to individuals who have read, understood, and signed a non-disclosure agreement.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-6-3","slug":"ps-6-3","display_id":"PS-6(3)","name":"Post-employment Requirements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Notify individuals of applicable, legally binding post-employment requirements for protection of organizational information; and\n"},{"id":"b","statement":"Require individuals to sign an acknowledgment of these requirements, if applicable, as part of granting initial access to covered information.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"individuals are notified of applicable, legally binding post-employment requirements for the protection of organizational information;\n"},{"id":"b","statement":"individuals are required to sign an acknowledgement of applicable, legally binding post-employment requirements as part of being granted initial access to covered information.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-7","slug":"ps-7","display_id":"PS-7","name":"External Personnel Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish personnel security requirements, including security roles and responsibilities for external providers;\n"},{"id":"b","statement":"Require external providers to comply with personnel security policies and procedures established by the organization;\n"},{"id":"c","statement":"Document personnel security requirements;"},{"id":"d","statement":"Require external providers to notify {{ ps_07_odp_01 }} of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges, or who have system privileges within {{ ps_07_odp_02 }} ; and\n"},{"id":"e","statement":"Monitor provider compliance with personnel security requirements."}],"objectives_count":5,"objectives_preview":[{"id":"a","statement":"personnel security requirements are established, including security roles and responsibilities for external providers;\n"},{"id":"b","statement":"external providers are required to comply with personnel security policies and procedures established by the organization;\n"},{"id":"c","statement":"personnel security requirements are documented;"},{"id":"d","statement":"external providers are required to notify {{ ps_07_odp_01 }} of any personnel transfers or terminations of external personnel who possess organizational credentials and/or badges or who have system privileges within {{ ps_07_odp_02 }};\n"},{"id":"e","statement":"provider compliance with personnel security requirements is monitored."}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-04-to-800-53-ps-7","source_ref":"control--ogrl-hr-04","target_ref":"requirement--nist-sp-800-53-r5-ps-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_07_odp_01":"notification_recipient","ps_07_odp_02":"notification_window"},"summary":"Contractual personnel security requirements, change notifications, and compliance verification cover each part of PS-7.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-8","slug":"ps-8","display_id":"PS-8","name":"Personnel Sanctions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ a formal sanctions process for individuals failing to comply with established information security and privacy policies and procedures; and\n"},{"id":"b","statement":"Notify {{ ps_08_odp_01 }} within {{ ps_08_odp_02 }} when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a formal sanctions process is employed for individuals failing to comply with established information security and privacy policies and procedures;\n"},{"id":"b","statement":"{{ ps_08_odp_01 }} is/are notified within {{ ps_08_odp_02 }} when a formal employee sanctions process is initiated, identifying the individual sanctioned and the reason for the sanction.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-05-to-800-53-ps-8","source_ref":"control--ogrl-hr-05","target_ref":"requirement--nist-sp-800-53-r5-ps-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ps_08_odp_01":"sanction_notification_recipient","ps_08_odp_02":"sanction_notification_window"},"summary":"A formal sanctions process with timely notification of designated roles satisfies both parts of PS-8.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ps-9","slug":"ps-9","display_id":"PS-9","name":"Position Descriptions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Incorporate security and privacy roles and responsibilities into organizational position descriptions.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"security roles and responsibilities are incorporated into organizational position descriptions;\n"},{"id":"[02]","statement":"privacy roles and responsibilities are incorporated into organizational position descriptions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-06-to-800-53-ps-9","source_ref":"control--ogrl-hr-06","target_ref":"requirement--nist-sp-800-53-r5-ps-9","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"The control incorporates security and privacy responsibilities into position descriptions as PS-9 requires and adds periodic review.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ps-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-1","slug":"pt-1","display_id":"PT-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ pt_1_prm_1 }}:"},{"id":"a.1","statement":"{{ pt_01_odp_03 }} personally identifiable information processing and transparency policy that:\n"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and the associated personally identifiable information processing and transparency controls;\n"},{"id":"b","statement":"Designate an {{ pt_01_odp_04 }} to manage the development, documentation, and dissemination of the personally identifiable information processing and transparency policy and procedures; and\n"},{"id":"c","statement":"Review and update the current personally identifiable information processing and transparency:\n"},{"id":"c.1","statement":"Policy {{ pt_01_odp_05 }} and following {{ pt_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ pt_01_odp_07 }} and following {{ pt_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a personally identifiable information processing and transparency policy is developed and documented;\n"},{"id":"a-2","statement":"the personally identifiable information processing and transparency policy is disseminated to {{ pt_01_odp_01 }};\n"},{"id":"a-3","statement":"personally identifiable information processing and transparency procedures to facilitate the implementation of the personally identifiable information processing and transparency policy and associated personally identifiable information processing and transparency controls are developed and documented;\n"},{"id":"a-4","statement":"the personally identifiable information processing and transparency procedures are disseminated to {{ pt_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ pt_01_odp_03 }} personally identifiable information processing and transparency policy addresses purpose;\n"},{"id":"a.1.a-2","statement":"the {{ pt_01_odp_03 }} personally identifiable information processing and transparency policy addresses scope;\n"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-2","slug":"pt-2","display_id":"PT-2","name":"Authority to Process Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine and document the {{ pt_02_odp_01 }} that permits the {{ pt_02_odp_02 }} of personally identifiable information; and\n"},{"id":"b","statement":"Restrict the {{ pt_02_odp_03 }} of personally identifiable information to only that which is authorized.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the {{ pt_02_odp_01 }} that permits the {{ pt_02_odp_02 }} of personally identifiable information is determined and documented;\n"},{"id":"b","statement":"the {{ pt_02_odp_03 }} of personally identifiable information is restricted to only that which is authorized.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-03-to-800-53-pt-2","source_ref":"control--ogrl-pr-03","target_ref":"requirement--nist-sp-800-53-r5-pt-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Documenting legal authority per activity and restricting processing to it addresses PT-2.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-2-1","slug":"pt-2-1","display_id":"PT-2(1)","name":"Data Tagging","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Attach data tags containing {{ pt_02_01_odp_01 }} to {{ pt_02_01_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-02(01)","statement":"data tags containing {{ pt_02_01_odp_01 }} are attached to {{ pt_02_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-2-2","slug":"pt-2-2","display_id":"PT-2(2)","name":"Automation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manage enforcement of the authorized processing of personally identifiable information using {{ pt_02_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-02(02)","statement":"enforcement of the authorized processing of personally identifiable information is managed using {{ pt_02_02_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-3","slug":"pt-3","display_id":"PT-3","name":"Personally Identifiable Information Processing Purposes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify and document the {{ pt_03_odp_01 }} for processing personally identifiable information;\n"},{"id":"b","statement":"Describe the purpose(s) in the public privacy notices and policies of the organization;\n"},{"id":"c","statement":"Restrict the {{ pt_03_odp_02 }} of personally identifiable information to only that which is compatible with the identified purpose(s); and\n"},{"id":"d","statement":"Monitor changes in processing personally identifiable information and implement {{ pt_03_odp_03 }} to ensure that any changes are made in accordance with {{ pt_03_odp_04 }}.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"the {{ pt_03_odp_01 }} for processing personally identifiable information is/are identified and documented;\n"},{"id":"b-1","statement":"the purpose(s) is/are described in the public privacy notices of the organization;\n"},{"id":"b-2","statement":"the purpose(s) is/are described in the policies of the organization;"},{"id":"c","statement":"the {{ pt_03_odp_02 }} of personally identifiable information are restricted to only that which is compatible with the identified purpose(s);\n"},{"id":"d-1","statement":"changes in the processing of personally identifiable information are monitored;"},{"id":"d-2","statement":"{{ pt_03_odp_03 }} are implemented to ensure that any changes are made in accordance with {{ pt_03_odp_04 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-03-to-800-53-pt-3","source_ref":"control--ogrl-pr-03","target_ref":"requirement--nist-sp-800-53-r5-pt-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pt_03_odp_03":"purpose_change_review"},"summary":"Documenting purposes, reflecting them in the notice, restricting use, and reviewing changes covers PT-3.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-3-1","slug":"pt-3-1","display_id":"PT-3(1)","name":"Data Tagging","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Attach data tags containing the following purposes to {{ pt_03_01_odp_02 }}: {{ pt_03_01_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-03(01)","statement":"data tags containing {{ pt_03_01_odp_01 }} are attached to {{ pt_03_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-3-2","slug":"pt-3-2","display_id":"PT-3(2)","name":"Automation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Track processing purposes of personally identifiable information using {{ pt_03_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-03(02)","statement":"the processing purposes of personally identifiable information are tracked using {{ pt_03_02_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-4","slug":"pt-4","display_id":"PT-4","name":"Consent","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement {{ pt_04_odp }} for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals’ informed decision-making.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-04","statement":"the {{ pt_04_odp }} are implemented for individuals to consent to the processing of their personally identifiable information prior to its collection that facilitate individuals’ informed decision-making.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-02-to-800-53-pt-4","source_ref":"control--ogrl-pr-02","target_ref":"requirement--nist-sp-800-53-r5-pt-4","relationship":"superset-of","review_status":"reviewed","parameter_map":{"pt_04_odp":"consent_mechanism"},"summary":"Pre-collection consent mechanisms satisfy PT-4; the control adds consent records and withdrawal handling.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-4-1","slug":"pt-4-1","display_id":"PT-4(1)","name":"Tailored Consent","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ pt_04_01_odp }} to allow individuals to tailor processing permissions to selected elements of personally identifiable information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-04(01)","statement":"{{ pt_04_01_odp }} are provided to allow individuals to tailor processing permissions to selected elements of personally identifiable information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-4-2","slug":"pt-4-2","display_id":"PT-4(2)","name":"Just-in-time Consent","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Present {{ pt_04_02_odp_01 }} to individuals at {{ pt_04_02_odp_02 }} and in conjunction with {{ pt_04_02_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-04(02)","statement":"{{ pt_04_02_odp_01 }} are presented to individuals {{ pt_04_02_odp_02 }} and in conjunction with {{ pt_04_02_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-4-3","slug":"pt-4-3","display_id":"PT-4(3)","name":"Revocation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ pt_04_03_odp }} for individuals to revoke consent to the processing of their personally identifiable information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-04(03)","statement":"the {{ pt_04_03_odp }} are implemented for individuals to revoke consent to the processing of their personally identifiable information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-5","slug":"pt-5","display_id":"PT-5","name":"Privacy Notice","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Provide notice to individuals about the processing of personally identifiable information that:\n","citation":null,"parts":[{"id":"a","statement":"Is available to individuals upon first interacting with an organization, and subsequently at {{ pt_05_odp_01 }};\n"},{"id":"b","statement":"Is clear and easy-to-understand, expressing information about personally identifiable information processing in plain language;\n"},{"id":"c","statement":"Identifies the authority that authorizes the processing of personally identifiable information;\n"},{"id":"d","statement":"Identifies the purposes for which personally identifiable information is to be processed; and\n"},{"id":"e","statement":"Includes {{ pt_05_odp_02 }}."}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"a notice to individuals about the processing of personally identifiable information is provided such that the notice is available to individuals upon first interacting with an organization;\n"},{"id":"a-2","statement":"a notice to individuals about the processing of personally identifiable information is provided such that the notice is subsequently available to individuals {{ pt_05_odp_01 }};\n"},{"id":"b","statement":"a notice to individuals about the processing of personally identifiable information is provided that is clear, easy-to-understand, and expresses information about personally identifiable information processing in plain language;\n"},{"id":"c","statement":"a notice to individuals about the processing of personally identifiable information that identifies the authority that authorizes the processing of personally identifiable information is provided;\n"},{"id":"d","statement":"a notice to individuals about the processing of personally identifiable information that identifies the purpose for which personally identifiable information is to be processed is provided;\n"},{"id":"e","statement":"a notice to individuals about the processing of personally identifiable information which includes {{ pt_05_odp_02 }} is provided.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-01-to-800-53-pt-5","source_ref":"control--ogrl-pr-01","target_ref":"requirement--nist-sp-800-53-r5-pt-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"pt_05_odp_02":"notice_contents"},"summary":"A plain-language notice available at first collection stating purposes, legal basis, and defined contents covers PT-5.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-5-1","slug":"pt-5-1","display_id":"PT-5(1)","name":"Just-in-time Notice","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Present notice of personally identifiable information processing to individuals at a time and location where the individual provides personally identifiable information or in conjunction with a data action, or {{ pt_05_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-05(01)","statement":"a notice of personally identifiable information processing is presented to individuals at a time and location where the individual provides personally identifiable information, in conjunction with a data action, or {{ pt_05_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-5-2","slug":"pt-5-2","display_id":"PT-5(2)","name":"Privacy Act Statements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include Privacy Act statements on forms that collect information that will be maintained in a Privacy Act system of records, or provide Privacy Act statements on separate forms that can be retained by individuals.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-05(02)","statement":"Privacy Act statements are included on forms that collect information that will be maintained in a Privacy Act system of records, or Privacy Act statements are provided on separate forms that can be retained by individuals.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-6","slug":"pt-6","display_id":"PT-6","name":"System of Records Notice","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"For systems that process information that will be maintained in a Privacy Act system of records:\n","citation":null,"parts":[{"id":"a","statement":"Draft system of records notices in accordance with OMB guidance and submit new and significantly modified system of records notices to the OMB and appropriate congressional committees for advance review;\n"},{"id":"b","statement":"Publish system of records notices in the Federal Register; and"},{"id":"c","statement":"Keep system of records notices accurate, up-to-date, and scoped in accordance with policy.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"system of records notices are drafted in accordance with OMB guidance for systems that process information that will be maintained in a Privacy Act system of records;\n"},{"id":"a-2","statement":"new and significantly modified system of records notices are submitted to the OMB and appropriate congressional committees for advance review for systems that process information that will be maintained in a Privacy Act system of records;\n"},{"id":"b","statement":"system of records notices are published in the Federal Register for systems that process information that will be maintained in a Privacy Act system of records;\n"},{"id":"c","statement":"system of records notices are kept accurate, up-to-date, and scoped in accordance with policy for systems that process information that will be maintained in a Privacy Act system of records.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-6-1","slug":"pt-6-1","display_id":"PT-6(1)","name":"Routine Uses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review all routine uses published in the system of records notice at {{ pt_06_01_odp }} to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-06(01)","statement":"all routine uses published in the system of records notice are reviewed {{ pt_06_01_odp }} to ensure continued accuracy, and to ensure that routine uses continue to be compatible with the purpose for which the information was collected.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-6-2","slug":"pt-6-2","display_id":"PT-6(2)","name":"Exemption Rules","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review all Privacy Act exemptions claimed for the system of records at {{ pt_06_02_odp }} to ensure they remain appropriate and necessary in accordance with law, that they have been promulgated as regulations, and that they are accurately described in the system of records notice.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"pt-06(02).pt-06(02)[01]","statement":"all Privacy Act exemptions claimed for the system of records are reviewed {{ pt_06_02_odp }} to ensure that they remain appropriate and necessary in accordance with law;\n"},{"id":"pt-06(02).pt-06(02)[02]","statement":"all Privacy Act exemptions claimed for the system of records are reviewed {{ pt_06_02_odp }} to ensure that they have been promulgated as regulations;\n"},{"id":"pt-06(02).pt-06(02)[03]","statement":"all Privacy Act exemptions claimed for the system of records are reviewed {{ pt_06_02_odp }} to ensure that they are accurately described in the system of records notice.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-7","slug":"pt-7","display_id":"PT-7","name":"Specific Categories of Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Apply {{ pt_07_odp }} for specific categories of personally identifiable information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-07","statement":"{{ pt_07_odp }} are applied for specific categories of personally identifiable information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-7-1","slug":"pt-7-1","display_id":"PT-7(1)","name":"Social Security Numbers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"When a system processes Social Security numbers:","citation":null,"parts":[{"id":"a","statement":"Eliminate unnecessary collection, maintenance, and use of Social Security numbers, and explore alternatives to their use as a personal identifier;\n"},{"id":"b","statement":"Do not deny any individual any right, benefit, or privilege provided by law because of such individual’s refusal to disclose his or her Social Security number; and\n"},{"id":"c","statement":"Inform any individual who is asked to disclose his or her Social Security number whether that disclosure is mandatory or voluntary, by what statutory or other authority such number is solicited, and what uses will be made of it.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"when a system processes Social Security numbers, the unnecessary collection, maintenance, and use of Social Security numbers are eliminated;\n"},{"id":"a-2","statement":"when a system processes Social Security numbers, alternatives to the use of Social Security Numbers as a personal identifier are explored;\n"},{"id":"b","statement":"when a system processes Social Security numbers, individual rights, benefits, or privileges provided by law are not denied because of an individual’s refusal to disclose their Social Security number;\n"},{"id":"c-1","statement":"when a system processes Social Security numbers, any individual who is asked to disclose their Social Security number is informed whether that disclosure is mandatory or voluntary, by what statutory or other authority such number is solicited, and what uses will be made of it;\n"},{"id":"c-2","statement":"when a system processes Social Security numbers, any individual who is asked to disclose their Social Security number is informed by what statutory or other authority the number is solicited;\n"},{"id":"c-3","statement":"when a system processes Social Security numbers, any individual who is asked to disclose their Social Security number is informed what uses will be made of it.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-7-2","slug":"pt-7-2","display_id":"PT-7(2)","name":"First Amendment Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the processing of information describing how any individual exercises rights guaranteed by the First Amendment unless expressly authorized by statute or by the individual or unless pertinent to and within the scope of an authorized law enforcement activity.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"pt-07(02)","statement":"the processing of information describing how any individual exercises rights guaranteed by the First Amendment is prohibited unless expressly authorized by statute or by the individual or unless pertinent to and within the scope of an authorized law enforcement activity.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-pt-8","slug":"pt-8","display_id":"PT-8","name":"Computer Matching Requirements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"When a system or organization processes information for the purpose of conducting a matching program:\n","citation":null,"parts":[{"id":"a","statement":"Obtain approval from the Data Integrity Board to conduct the matching program;"},{"id":"b","statement":"Develop and enter into a computer matching agreement;"},{"id":"c","statement":"Publish a matching notice in the Federal Register;"},{"id":"d","statement":"Independently verify the information produced by the matching program before taking adverse action against an individual, if required; and\n"},{"id":"e","statement":"Provide individuals with notice and an opportunity to contest the findings before taking adverse action against an individual.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a","statement":"approval to conduct the matching program is obtained from the Data Integrity Board when a system or organization processes information for the purpose of conducting a matching program;\n"},{"id":"b-1","statement":"a computer matching agreement is developed when a system or organization processes information for the purpose of conducting a matching program;\n"},{"id":"b-2","statement":"a computer matching agreement is entered into when a system or organization processes information for the purpose of conducting a matching program;\n"},{"id":"c","statement":"a matching notice is published in the Federal Register when a system or organization processes information for the purpose of conducting a matching program;\n"},{"id":"d","statement":"the information produced by the matching program is independently verified before taking adverse action against an individual, if required, when a system or organization processes information for the purpose of conducting a matching program;\n"},{"id":"e-1","statement":"individuals are provided with notice when a system or organization processes information for the purpose of conducting a matching program;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/pt-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-1","slug":"ra-1","display_id":"RA-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ ra_1_prm_1 }}:"},{"id":"a.1","statement":"{{ ra_01_odp_03 }} risk assessment policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the risk assessment policy and the associated risk assessment controls;\n"},{"id":"b","statement":"Designate an {{ ra_01_odp_04 }} to manage the development, documentation, and dissemination of the risk assessment policy and procedures; and\n"},{"id":"c","statement":"Review and update the current risk assessment:"},{"id":"c.1","statement":"Policy {{ ra_01_odp_05 }} and following {{ ra_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ ra_01_odp_07 }} and following {{ ra_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a risk assessment policy is developed and documented;"},{"id":"a-2","statement":"the risk assessment policy is disseminated to {{ ra_01_odp_01 }};"},{"id":"a-3","statement":"risk assessment procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls are developed and documented;\n"},{"id":"a-4","statement":"the risk assessment procedures are disseminated to {{ ra_01_odp_02 }};"},{"id":"a.1.a-1","statement":"the {{ ra_01_odp_03 }} risk assessment policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ ra_01_odp_03 }} risk assessment policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-2","slug":"ra-2","display_id":"RA-2","name":"Security Categorization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Categorize the system and information it processes, stores, and transmits;"},{"id":"b","statement":"Document the security categorization results, including supporting rationale, in the security plan for the system; and\n"},{"id":"c","statement":"Verify that the authorizing official or authorizing official designated representative reviews and approves the security categorization decision.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the system and the information it processes, stores, and transmits are categorized;\n"},{"id":"b","statement":"the security categorization results, including supporting rationale, are documented in the security plan for the system;\n"},{"id":"c","statement":"the authorizing official or authorizing official designated representative reviews and approves the security categorization decision.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-am-02-to-800-53-ra-2","source_ref":"control--ogrl-am-02","target_ref":"requirement--nist-sp-800-53-r5-ra-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Classifying information and data stores overlaps with system and information categorization; impact-level categorization and authorizing official approval are not provided.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-2-1","slug":"ra-2-1","display_id":"RA-2(1)","name":"Impact-level Prioritization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Conduct an impact-level prioritization of organizational systems to obtain additional granularity on system impact levels.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-02(01)","statement":"an impact-level prioritization of organizational systems is conducted to obtain additional granularity on system impact levels.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-3","slug":"ra-3","display_id":"RA-3","name":"Risk Assessment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Conduct a risk assessment, including:"},{"id":"a.1","statement":"Identifying threats to and vulnerabilities in the system;"},{"id":"a.2","statement":"Determining the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system, the information it processes, stores, or transmits, and any related information; and\n"},{"id":"a.3","statement":"Determining the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information;\n"},{"id":"b","statement":"Integrate risk assessment results and risk management decisions from the organization and mission or business process perspectives with system-level risk assessments;\n"},{"id":"c","statement":"Document risk assessment results in {{ ra_03_odp_01 }};"},{"id":"d","statement":"Review risk assessment results {{ ra_03_odp_03 }};"},{"id":"e","statement":"Disseminate risk assessment results to {{ ra_03_odp_04 }} ; and"},{"id":"f","statement":"Update the risk assessment {{ ra_03_odp_05 }} or when there are significant changes to the system, its environment of operation, or other conditions that may impact the security or privacy state of the system.\n"}],"objectives_count":8,"objectives_preview":[{"id":"a.1","statement":"a risk assessment is conducted to identify threats to and vulnerabilities in the system;\n"},{"id":"a.2","statement":"a risk assessment is conducted to determine the likelihood and magnitude of harm from unauthorized access, use, disclosure, disruption, modification, or destruction of the system; the information it processes, stores, or transmits; and any related information;\n"},{"id":"a.3","statement":"a risk assessment is conducted to determine the likelihood and impact of adverse effects on individuals arising from the processing of personally identifiable information;\n"},{"id":"b","statement":"risk assessment results and risk management decisions from the organization and mission or business process perspectives are integrated with system-level risk assessments;\n"},{"id":"c","statement":"risk assessment results are documented in {{ ra_03_odp_01 }};"},{"id":"d","statement":"risk assessment results are reviewed {{ ra_03_odp_03 }};"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-a-1","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The assessment identifies threats to and vulnerabilities in the system."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-a-2","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#a.2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Likelihood and impact ratings determine the likelihood and magnitude of harm."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-c","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_03_odp_02":"risk_register"},"summary":"Results are documented in the risk register."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-e","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_03_odp_04":"results_audience"},"summary":"Results are communicated to named recipients."},{"id":"mapping--ogrl-rm-02-to-800-53-ra-3-f","source_ref":"control--ogrl-rm-02","target_ref":"requirement--nist-sp-800-53-r5-ra-3#f","relationship":"subset-of","review_status":"reviewed","parameter_map":{"ra_03_odp_05":"risk_assessment_frequency"},"summary":"Covers the periodic update; change-driven updates are handled by significant change risk evaluation.\n"},{"id":"mapping--ogrl-rm-03-to-800-53-ra-3-a-1","source_ref":"control--ogrl-rm-03","target_ref":"requirement--nist-sp-800-53-r5-ra-3#a.1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Fraud and insider-misuse scenarios are one category of threat identified in a system risk assessment.\n"},{"id":"mapping--ogrl-rm-05-to-800-53-ra-3-f","source_ref":"control--ogrl-rm-05","target_ref":"requirement--nist-sp-800-53-r5-ra-3#f","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Covers the change-driven update of the risk assessment; periodic updates are covered by periodic risk assessment.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-3-1","slug":"ra-3-1","display_id":"RA-3(1)","name":"Supply Chain Risk Assessment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Assess supply chain risks associated with {{ ra_03_01_odp_01 }} ; and"},{"id":"b","statement":"Update the supply chain risk assessment {{ ra_03_01_odp_02 }} , when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"supply chain risks associated with {{ ra_03_01_odp_01 }} are assessed;"},{"id":"b","statement":"the supply chain risk assessment is updated {{ ra_03_01_odp_02 }} , when there are significant changes to the relevant supply chain, or when changes to the system, environments of operation, or other conditions may necessitate a change in the supply chain.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-3-2","slug":"ra-3-2","display_id":"RA-3(2)","name":"Use of All-source Intelligence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use all-source intelligence to assist in the analysis of risk.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-03(02)","statement":"all-source intelligence is used to assist in the analysis of risk."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-3-3","slug":"ra-3-3","display_id":"RA-3(3)","name":"Dynamic Threat Awareness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Determine the current cyber threat environment on an ongoing basis using {{ ra_03_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-03(03)","statement":"the current cyber threat environment is determined on an ongoing basis using {{ ra_03_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-3-4","slug":"ra-3-4","display_id":"RA-3(4)","name":"Predictive Cyber Analytics","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following advanced automation and analytics capabilities to predict and identify risks to {{ ra_03_04_odp_02 }}: {{ ra_3_4_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ra-03(04).ra-03(04)[01]","statement":"{{ ra_03_04_odp_01 }} are employed to predict and identify risks to {{ ra_03_04_odp_02 }};\n"},{"id":"ra-03(04).ra-03(04)[02]","statement":"{{ ra_03_04_odp_03 }} are employed to predict and identify risks to {{ ra_03_04_odp_02 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-4","slug":"ra-4","display_id":"RA-4","name":"Risk Assessment Update","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ra-4_to_nist-sp-800-53-r5-ra-3","source_ref":"requirement--nist-sp-800-53-r5-ra-4","target_ref":"requirement--nist-sp-800-53-r5-ra-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5","slug":"ra-5","display_id":"RA-5","name":"Vulnerability Monitoring and Scanning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor and scan for vulnerabilities in the system and hosted applications {{ ra_5_prm_1 }} and when new vulnerabilities potentially affecting the system are identified and reported;\n"},{"id":"b","statement":"Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for:\n"},{"id":"b.1","statement":"Enumerating platforms, software flaws, and improper configurations;"},{"id":"b.2","statement":"Formatting checklists and test procedures; and"},{"id":"b.3","statement":"Measuring vulnerability impact;"},{"id":"c","statement":"Analyze vulnerability scan reports and results from vulnerability monitoring;"},{"id":"d","statement":"Remediate legitimate vulnerabilities {{ ra_05_odp_03 }} in accordance with an organizational assessment of risk;\n"},{"id":"e","statement":"Share information obtained from the vulnerability monitoring process and control assessments with {{ ra_05_odp_04 }} to help eliminate similar vulnerabilities in other systems; and\n"},{"id":"f","statement":"Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned.\n"}],"objectives_count":9,"objectives_preview":[{"id":"a-1","statement":"systems and hosted applications are monitored for vulnerabilities {{ ra_05_odp_01 }} and when new vulnerabilities potentially affecting the system are identified and reported;\n"},{"id":"a-2","statement":"systems and hosted applications are scanned for vulnerabilities {{ ra_05_odp_02 }} and when new vulnerabilities potentially affecting the system are identified and reported;\n"},{"id":"b.1","statement":"vulnerability monitoring tools and techniques are employed to automate parts of the vulnerability management process by using standards for enumerating platforms, software flaws, and improper configurations;\n"},{"id":"b.2","statement":"vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for formatting checklists and test procedures;\n"},{"id":"b.3","statement":"vulnerability monitoring tools and techniques are employed to facilitate interoperability among tools and to automate parts of the vulnerability management process by using standards for measuring vulnerability impact;\n"},{"id":"c","statement":"vulnerability scan reports and results from vulnerability monitoring are analyzed;\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-vm-01-to-800-53-ra-5-a","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-53-r5-ra-5#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_5_prm_1":"scan_cadence"},"summary":"Scheduled infrastructure and release vulnerability scanning satisfies NIST RA-5(a).\n"},{"id":"mapping--ogrl-vm-01-to-800-53-ra-5-d","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-53-r5-ra-5#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_05_odp_03":"remediation_sla"},"summary":"Risk-based vulnerability remediation SLAs directly satisfy NIST RA-5(d)."},{"id":"mapping--ogrl-vm-01-to-800-53-ra-5-e","source_ref":"control--ogrl-vm-01","target_ref":"requirement--nist-sp-800-53-r5-ra-5#e","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"ra_05_odp_04":"advisory_audience"},"summary":"Sharing vulnerability advisories with service owners satisfies NIST RA-5(e)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-1","slug":"ra-5-1","display_id":"RA-5(1)","name":"Update Tool Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ra-5-1_to_nist-sp-800-53-r5-ra-5","source_ref":"requirement--nist-sp-800-53-r5-ra-5-1","target_ref":"requirement--nist-sp-800-53-r5-ra-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-2","slug":"ra-5-2","display_id":"RA-5(2)","name":"Update Vulnerabilities to Be Scanned","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Update the system vulnerabilities to be scanned {{ ra_05_02_odp_01 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(02)","statement":"the system vulnerabilities to be scanned are updated {{ ra_05_02_odp_01 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-3","slug":"ra-5-3","display_id":"RA-5(3)","name":"Breadth and Depth of Coverage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Define the breadth and depth of vulnerability scanning coverage.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(03)","statement":"the breadth and depth of vulnerability scanning coverage are defined."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-4","slug":"ra-5-4","display_id":"RA-5(4)","name":"Discoverable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Determine information about the system that is discoverable and take {{ ra_05_04_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"ra-05(04).ra-05(04)[01]","statement":"information about the system is discoverable;"},{"id":"ra-05(04).ra-05(04)[02]","statement":"{{ ra_05_04_odp }} are taken when information about the system is confirmed as discoverable.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-5","slug":"ra-5-5","display_id":"RA-5(5)","name":"Privileged Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement privileged access authorization to {{ ra_05_05_odp_01 }} for {{ ra_05_05_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(05)","statement":"privileged access authorization is implemented to {{ ra_05_05_odp_01 }} for {{ ra_05_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-6","slug":"ra-5-6","display_id":"RA-5(6)","name":"Automated Trend Analyses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Compare the results of multiple vulnerability scans using {{ ra_05_06_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(06)","statement":"the results of multiple vulnerability scans are compared using {{ ra_05_06_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-7","slug":"ra-5-7","display_id":"RA-5(7)","name":"Automated Detection and Notification of Unauthorized Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ra-5-7_to_nist-sp-800-53-r5-cm-8","source_ref":"requirement--nist-sp-800-53-r5-ra-5-7","target_ref":"requirement--nist-sp-800-53-r5-cm-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-8","slug":"ra-5-8","display_id":"RA-5(8)","name":"Review Historic Audit Logs","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review historic audit logs to determine if a vulnerability identified in a {{ ra_05_08_odp_01 }} has been previously exploited within an {{ ra_05_08_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(08)","statement":"historic audit logs are reviewed to determine if a vulnerability identified in a {{ ra_05_08_odp_01 }} has been previously exploited within {{ ra_05_08_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-9","slug":"ra-5-9","display_id":"RA-5(9)","name":"Penetration Testing and Analyses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-ra-5-9_to_nist-sp-800-53-r5-ca-8","source_ref":"requirement--nist-sp-800-53-r5-ra-5-9","target_ref":"requirement--nist-sp-800-53-r5-ca-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-10","slug":"ra-5-10","display_id":"RA-5(10)","name":"Correlate Scanning Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correlate the output from vulnerability scanning tools to determine the presence of multi-vulnerability and multi-hop attack vectors.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(10)","statement":"the output from vulnerability scanning tools is correlated to determine the presence of multi-vulnerability and multi-hop attack vectors.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-5-11","slug":"ra-5-11","display_id":"RA-5(11)","name":"Public Disclosure Program","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-05(11)","statement":"a public reporting channel is established for receiving reports of vulnerabilities in organizational systems and system components.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-5-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-6","slug":"ra-6","display_id":"RA-6","name":"Technical Surveillance Countermeasures Survey","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ a technical surveillance countermeasures survey at {{ ra_06_odp_01 }} {{ ra_06_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-06","statement":"a technical surveillance countermeasures survey is employed at {{ ra_06_odp_01 }} {{ ra_06_odp_02 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-7","slug":"ra-7","display_id":"RA-7","name":"Risk Response","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Respond to findings from security and privacy assessments, monitoring, and audits in accordance with organizational risk tolerance.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"[01]","statement":"findings from security assessments are responded to in accordance with organizational risk tolerance;\n"},{"id":"[02]","statement":"findings from privacy assessments are responded to in accordance with organizational risk tolerance;\n"},{"id":"[03]","statement":"findings from monitoring are responded to in accordance with organizational risk tolerance;\n"},{"id":"[04]","statement":"findings from audits are responded to in accordance with organizational risk tolerance.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-rm-04-to-800-53-ra-7","source_ref":"control--ogrl-rm-04","target_ref":"requirement--nist-sp-800-53-r5-ra-7","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Responds to risk assessment results in line with risk tolerance; responses to audit and monitoring findings are covered by deficiency tracking.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-8","slug":"ra-8","display_id":"RA-8","name":"Privacy Impact Assessments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Conduct privacy impact assessments for systems, programs, or other activities before:\n","citation":null,"parts":[{"id":"a","statement":"Developing or procuring information technology that processes personally identifiable information; and\n"},{"id":"b","statement":"Initiating a new collection of personally identifiable information that:"},{"id":"b.1","statement":"Will be processed using information technology; and"},{"id":"b.2","statement":"Includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more individuals, other than agencies, instrumentalities, or employees of the federal government.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"privacy impact assessments are conducted for systems, programs, or other activities before developing or procuring information technology that processes personally identifiable information;\n"},{"id":"b-1","statement":"privacy impact assessments are conducted for systems, programs, or other activities before initiating a collection of personally identifiable information that will be processed using information technology;\n"},{"id":"b-2","statement":"privacy impact assessments are conducted for systems, programs, or other activities before initiating a collection of personally identifiable information that includes personally identifiable information permitting the physical or virtual (online) contacting of a specific individual, if identical questions have been posed to, or identical reporting requirements imposed on, ten or more individuals, other than agencies, instrumentalities, or employees of the federal government.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-9","slug":"ra-9","display_id":"RA-9","name":"Criticality Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Identify critical system components and functions by performing a criticality analysis for {{ ra_09_odp_01 }} at {{ ra_09_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"ra-09","statement":"critical system components and functions are identified by performing a criticality analysis for {{ ra_09_odp_01 }} at {{ ra_09_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-07-to-800-53-ra-9","source_ref":"control--ogrl-bc-07","target_ref":"requirement--nist-sp-800-53-r5-ra-9","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Rating the criticality of supporting systems and dependencies overlaps criticality analysis, though not performed at system development decision points.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-ra-10","slug":"ra-10","display_id":"RA-10","name":"Threat Hunting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish and maintain a cyber threat hunting capability to:"},{"id":"a.1","statement":"Search for indicators of compromise in organizational systems; and"},{"id":"a.2","statement":"Detect, track, and disrupt threats that evade existing controls; and"},{"id":"b","statement":"Employ the threat hunting capability {{ ra_10_odp }}."}],"objectives_count":3,"objectives_preview":[{"id":"a.1","statement":"a cyber threat capability is established and maintained to search for indicators of compromise in organizational systems;\n"},{"id":"a.2","statement":"a cyber threat capability is established and maintained to detect, track, and disrupt threats that evade existing controls;\n"},{"id":"b","statement":"the threat hunting capability is employed {{ ra_10_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/ra-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-1","slug":"sa-1","display_id":"SA-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ sa_1_prm_1 }}:"},{"id":"a.1","statement":"{{ sa_01_odp_03 }} system and services acquisition policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls;\n"},{"id":"b","statement":"Designate an {{ sa_01_odp_04 }} to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and\n"},{"id":"c","statement":"Review and update the current system and services acquisition:"},{"id":"c.1","statement":"Policy {{ sa_01_odp_05 }} and following {{ sa_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ sa_01_odp_07 }} and following {{ sa_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a system and services acquisition policy is developed and documented;"},{"id":"a-2","statement":"the system and services acquisition policy is disseminated to {{ sa_01_odp_01 }};\n"},{"id":"a-3","statement":"system and services acquisition procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls are developed and documented;\n"},{"id":"a-4","statement":"the system and services acquisition procedures are disseminated to {{ sa_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ sa_01_odp_03 }} system and services acquisition policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ sa_01_odp_03 }} system and services acquisition policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-2","slug":"sa-2","display_id":"SA-2","name":"Allocation of Resources","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine the high-level information security and privacy requirements for the system or system service in mission and business process planning;\n"},{"id":"b","statement":"Determine, document, and allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process; and\n"},{"id":"c","statement":"Establish a discrete line item for information security and privacy in organizational programming and budgeting documentation.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"the high-level information security requirements for the system or system service are determined in mission and business process planning;\n"},{"id":"a-2","statement":"the high-level privacy requirements for the system or system service are determined in mission and business process planning;\n"},{"id":"b-1","statement":"the resources required to protect the system or system service are determined and documented as part of the organizational capital planning and investment control process;\n"},{"id":"b-2","statement":"the resources required to protect the system or system service are allocated as part of the organizational capital planning and investment control process;\n"},{"id":"c-1","statement":"a discrete line item for information security is established in organizational programming and budgeting documentation;\n"},{"id":"c-2","statement":"a discrete line item for privacy is established in organizational programming and budgeting documentation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-3","slug":"sa-3","display_id":"SA-3","name":"System Development Life Cycle","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Acquire, develop, and manage the system using {{ sa_03_odp }} that incorporates information security and privacy considerations;\n"},{"id":"b","statement":"Define and document information security and privacy roles and responsibilities throughout the system development life cycle;\n"},{"id":"c","statement":"Identify individuals having information security and privacy roles and responsibilities; and\n"},{"id":"d","statement":"Integrate the organizational information security and privacy risk management process into system development life cycle activities.\n"}],"objectives_count":8,"objectives_preview":[{"id":"a-1","statement":"the system is acquired, developed, and managed using {{ sa_03_odp }} that incorporates information security considerations;\n"},{"id":"a-2","statement":"the system is acquired, developed, and managed using {{ sa_03_odp }} that incorporates privacy considerations;\n"},{"id":"b-1","statement":"information security roles and responsibilities are defined and documented throughout the system development life cycle;\n"},{"id":"b-2","statement":"privacy roles and responsibilities are defined and documented throughout the system development life cycle;\n"},{"id":"c-1","statement":"individuals with information security roles and responsibilities are identified;"},{"id":"c-2","statement":"individuals with privacy roles and responsibilities are identified;"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-01-to-800-53-sa-3-a","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-3#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"A documented SDLC with security activities in each phase satisfies SA-3(a)."},{"id":"mapping--ogrl-sd-01-to-800-53-sa-3-b","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-3#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"The SDLC assigns security responsibilities to named roles, addressing SA-3(b)."},{"id":"mapping--ogrl-sd-01-to-800-53-sa-3-d","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-3#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Threat modeling integrates risk analysis into development, partly addressing SA-3(d).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-3-1","slug":"sa-3-1","display_id":"SA-3(1)","name":"Manage Preproduction Environment","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect system preproduction environments commensurate with risk throughout the system development life cycle for the system, system component, or system service.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-03(01)","statement":"system pre-production environments are protected commensurate with risk throughout the system development life cycle for the system, system component, or system service.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-3-2","slug":"sa-3-2","display_id":"SA-3(2)","name":"Use of Live or Operational Data","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Approve, document, and control the use of live data in preproduction environments for the system, system component, or system service; and\n"},{"id":"b","statement":"Protect preproduction environments for the system, system component, or system service at the same impact or classification level as any live data in use within the preproduction environments.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"the use of live data in pre-production environments is approved for the system, system component, or system service;\n"},{"id":"a-2","statement":"the use of live data in pre-production environments is documented for the system, system component, or system service;\n"},{"id":"a-3","statement":"the use of live data in pre-production environments is controlled for the system, system component, or system service;\n"},{"id":"b","statement":"pre-production environments for the system, system component, or system service are protected at the same impact or classification level as any live data in use within the pre-production environments.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-3-3","slug":"sa-3-3","display_id":"SA-3(3)","name":"Technology Refresh","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Plan for and implement a technology refresh schedule for the system throughout the system development life cycle.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-03(03).sa-03(03)[01]","statement":"a technology refresh schedule is planned for the system throughout the system development life cycle;\n"},{"id":"sa-03(03).sa-03(03)[02]","statement":"a technology refresh schedule is implemented for the system throughout the system development life cycle.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4","slug":"sa-4","display_id":"SA-4","name":"Acquisition Process","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Include the following requirements, descriptions, and criteria, explicitly or by reference, using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service:\n","citation":null,"parts":[{"id":"a","statement":"Security and privacy functional requirements;"},{"id":"b","statement":"Strength of mechanism requirements;"},{"id":"c","statement":"Security and privacy assurance requirements;"},{"id":"d","statement":"Controls needed to satisfy the security and privacy requirements."},{"id":"e","statement":"Security and privacy documentation requirements;"},{"id":"f","statement":"Requirements for protecting security and privacy documentation;"},{"id":"g","statement":"Description of the system development environment and environment in which the system is intended to operate;\n"},{"id":"h","statement":"Allocation of responsibility or identification of parties responsible for information security, privacy, and supply chain risk management; and\n"},{"id":"i","statement":"Acceptance criteria."}],"objectives_count":16,"objectives_preview":[{"id":"a-1","statement":"security functional requirements, descriptions, and criteria are included explicitly or by reference using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service;\n"},{"id":"a-2","statement":"privacy functional requirements, descriptions, and criteria are included explicitly or by reference using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service;\n"},{"id":"b","statement":"strength of mechanism requirements, descriptions, and criteria are included explicitly or by reference using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service;\n"},{"id":"c-1","statement":"security assurance requirements, descriptions, and criteria are included explicitly or by reference using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service;\n"},{"id":"c-2","statement":"privacy assurance requirements, descriptions, and criteria are included explicitly or by reference using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service;\n"},{"id":"d-1","statement":"controls needed to satisfy the security requirements, descriptions, and criteria are included explicitly or by reference using {{ sa_04_odp_01 }} in the acquisition contract for the system, system component, or system service;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-03-to-800-53-sa-4","source_ref":"control--ogrl-tp-03","target_ref":"requirement--nist-sp-800-53-r5-sa-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Contractual security, privacy, and responsibility-allocation terms overlap SA-4 acquisition requirements, which also address system development and assurance criteria not covered here.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-1","slug":"sa-4-1","display_id":"SA-4(1)","name":"Functional Properties of Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-04(01)","statement":"the developer of the system, system component, or system service is required to provide a description of the functional properties of the controls to be implemented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-2","slug":"sa-4-2","display_id":"SA-4(2)","name":"Design and Implementation Information for Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: {{ sa_04_02_odp_01 }} at {{ sa_04_02_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-04(02)","statement":"the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using {{ sa_04_02_odp_01 }} at {{ sa_04_02_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-3","slug":"sa-4-3","display_id":"SA-4(3)","name":"Development Methods, Techniques, and Practices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes:\n","citation":null,"parts":[{"id":"a","statement":"{{ sa_04_03_odp_01 }};"},{"id":"b","statement":"{{ sa_04_03_odp_02 }} ; and"},{"id":"c","statement":"{{ sa_04_03_odp_05 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes {{ sa_04_03_odp_01 }};\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes {{ sa_04_03_odp_02 }};\n"},{"id":"c","statement":"the developer of the system, system component, or system service is required to demonstrate the use of a system development life cycle process that includes {{ sa_04_03_odp_05 }}.\n"}],"params_count":8,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-4","slug":"sa-4-4","display_id":"SA-4(4)","name":"Assignment of Components to Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-4-4_to_nist-sp-800-53-r5-cm-8-9","source_ref":"requirement--nist-sp-800-53-r5-sa-4-4","target_ref":"requirement--nist-sp-800-53-r5-cm-8-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-5","slug":"sa-4-5","display_id":"SA-4(5)","name":"System, Component, and Service Configurations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Deliver the system, component, or service with {{ sa_04_05_odp }} implemented; and\n"},{"id":"b","statement":"Use the configurations as the default for any subsequent system, component, or service reinstallation or upgrade.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to deliver the system, component, or service with {{ sa_04_05_odp }} implemented;\n"},{"id":"b","statement":"the configurations are used as the default for any subsequent system, component, or service reinstallation or upgrade.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-6","slug":"sa-4-6","display_id":"SA-4(6)","name":"Use of Information Assurance Products","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ only government off-the-shelf or commercial off-the-shelf information assurance and information assurance-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted; and\n"},{"id":"b","statement":"Ensure that these products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"only government off-the-shelf or commercial off-the-shelf information assurance and information assurance-enabled information technology products that compose an NSA-approved solution to protect classified information when the networks used to transmit the information are at a lower classification level than the information being transmitted are employed;\n"},{"id":"b","statement":"these products have been evaluated and/or validated by NSA or in accordance with NSA-approved procedures.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-7","slug":"sa-4-7","display_id":"SA-4(7)","name":"NIAP-approved Protection Profiles","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Limit the use of commercially provided information assurance and information assurance-enabled information technology products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists; and\n"},{"id":"b","statement":"Require, if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that the cryptographic module is FIPS-validated or NSA-approved.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the use of commercially provided information assurance and information assurance-enabled information technology products is limited to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile for a specific technology type, if such a profile exists;\n"},{"id":"b","statement":"if no NIAP-approved Protection Profile exists for a specific technology type but a commercially provided information technology product relies on cryptographic functionality to enforce its security policy, that cryptographic module is required to be FIPS-validated or NSA-approved.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-8","slug":"sa-4-8","display_id":"SA-4(8)","name":"Continuous Monitoring Plan for Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to produce a plan for continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-04(08)","statement":"the developer of the system, system component, or system service is required to produce a plan for the continuous monitoring of control effectiveness that is consistent with the continuous monitoring program of the organization.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-9","slug":"sa-4-9","display_id":"SA-4(9)","name":"Functions, Ports, Protocols, and Services in Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to identify the functions, ports, protocols, and services intended for organizational use.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"sa-04(09).sa-04(09)[01]","statement":"the developer of the system, system component, or system service is required to identify the functions intended for organizational use;\n"},{"id":"sa-04(09).sa-04(09)[02]","statement":"the developer of the system, system component, or system service is required to identify the ports intended for organizational use;\n"},{"id":"sa-04(09).sa-04(09)[03]","statement":"the developer of the system, system component, or system service is required to identify the protocols intended for organizational use;\n"},{"id":"sa-04(09).sa-04(09)[04]","statement":"the developer of the system, system component, or system service is required to identify the services intended for organizational use.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-10","slug":"sa-4-10","display_id":"SA-4(10)","name":"Use of Approved PIV Products","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-04(10)","statement":"only information technology products on the FIPS 201-approved products list for the Personal Identity Verification (PIV) capability implemented within organizational systems are employed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-11","slug":"sa-4-11","display_id":"SA-4(11)","name":"System of Records","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Include {{ sa_04_11_odp }} in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-04(11)","statement":"{{ sa_04_11_odp }} are defined in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-4-12","slug":"sa-4-12","display_id":"SA-4(12)","name":"Data Ownership","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Include organizational data ownership requirements in the acquisition contract; and\n"},{"id":"b","statement":"Require all data to be removed from the contractor’s system and returned to the organization within {{ sa_04_12_odp }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"organizational data ownership requirements are included in the acquisition contract;\n"},{"id":"b","statement":"all data to be removed from the contractor’s system and returned to the organization is required within {{ sa_04_12_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-4-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-5","slug":"sa-5","display_id":"SA-5","name":"System Documentation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Obtain or develop administrator documentation for the system, system component, or system service that describes:\n"},{"id":"a.1","statement":"Secure configuration, installation, and operation of the system, component, or service;\n"},{"id":"a.2","statement":"Effective use and maintenance of security and privacy functions and mechanisms; and\n"},{"id":"a.3","statement":"Known vulnerabilities regarding configuration and use of administrative or privileged functions;\n"},{"id":"b","statement":"Obtain or develop user documentation for the system, system component, or system service that describes:\n"},{"id":"b.1","statement":"User-accessible security and privacy functions and mechanisms and how to effectively use those functions and mechanisms;\n"},{"id":"b.2","statement":"Methods for user interaction, which enables individuals to use the system, component, or service in a more secure manner and protect individual privacy; and\n"},{"id":"b.3","statement":"User responsibilities in maintaining the security of the system, component, or service and privacy of individuals;\n"},{"id":"c","statement":"Document attempts to obtain system, system component, or system service documentation when such documentation is either unavailable or nonexistent and take {{ sa_05_odp_01 }} in response; and\n"},{"id":"d","statement":"Distribute documentation to {{ sa_05_odp_02 }}."}],"objectives_count":20,"objectives_preview":[{"id":"a.1-1","statement":"administrator documentation for the system, system component, or system service that describes the secure configuration of the system, component, or service is obtained or developed;\n"},{"id":"a.1-2","statement":"administrator documentation for the system, system component, or system service that describes the secure installation of the system, component, or service is obtained or developed;\n"},{"id":"a.1-3","statement":"administrator documentation for the system, system component, or system service that describes the secure operation of the system, component, or service is obtained or developed;\n"},{"id":"a.2-1","statement":"administrator documentation for the system, system component, or system service that describes the effective use of security functions and mechanisms is obtained or developed;\n"},{"id":"a.2-2","statement":"administrator documentation for the system, system component, or system service that describes the effective maintenance of security functions and mechanisms is obtained or developed;\n"},{"id":"a.2-3","statement":"administrator documentation for the system, system component, or system service that describes the effective use of privacy functions and mechanisms is obtained or developed;\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-05-to-800-53-sa-5-d","source_ref":"control--ogrl-sd-05","target_ref":"requirement--nist-sp-800-53-r5-sa-5#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"sa_05_odp_02":"spec_audience"},"summary":"Processing specifications are distributed to defined audiences, overlapping SA-5(d) distribution of system documentation.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-5-1","slug":"sa-5-1","display_id":"SA-5(1)","name":"Functional Properties of Security Controls","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-5-1_to_nist-sp-800-53-r5-sa-4-1","source_ref":"requirement--nist-sp-800-53-r5-sa-5-1","target_ref":"requirement--nist-sp-800-53-r5-sa-4-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-5-2","slug":"sa-5-2","display_id":"SA-5(2)","name":"Security-relevant External System Interfaces","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-5-2_to_nist-sp-800-53-r5-sa-4-2","source_ref":"requirement--nist-sp-800-53-r5-sa-5-2","target_ref":"requirement--nist-sp-800-53-r5-sa-4-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-5-3","slug":"sa-5-3","display_id":"SA-5(3)","name":"High-level Design","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-5-3_to_nist-sp-800-53-r5-sa-4-2","source_ref":"requirement--nist-sp-800-53-r5-sa-5-3","target_ref":"requirement--nist-sp-800-53-r5-sa-4-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-5-4","slug":"sa-5-4","display_id":"SA-5(4)","name":"Low-level Design","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-5-4_to_nist-sp-800-53-r5-sa-4-2","source_ref":"requirement--nist-sp-800-53-r5-sa-5-4","target_ref":"requirement--nist-sp-800-53-r5-sa-4-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-5-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-5-5","slug":"sa-5-5","display_id":"SA-5(5)","name":"Source Code","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-5-5_to_nist-sp-800-53-r5-sa-4-2","source_ref":"requirement--nist-sp-800-53-r5-sa-5-5","target_ref":"requirement--nist-sp-800-53-r5-sa-4-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-5-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-6","slug":"sa-6","display_id":"SA-6","name":"Software Usage Restrictions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-6_to_nist-sp-800-53-r5-cm-10","source_ref":"requirement--nist-sp-800-53-r5-sa-6","target_ref":"requirement--nist-sp-800-53-r5-cm-10","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sa-6_to_nist-sp-800-53-r5-si-7","source_ref":"requirement--nist-sp-800-53-r5-sa-6","target_ref":"requirement--nist-sp-800-53-r5-si-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-7","slug":"sa-7","display_id":"SA-7","name":"User-installed Software","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-7_to_nist-sp-800-53-r5-cm-11","source_ref":"requirement--nist-sp-800-53-r5-sa-7","target_ref":"requirement--nist-sp-800-53-r5-cm-11","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sa-7_to_nist-sp-800-53-r5-si-7","source_ref":"requirement--nist-sp-800-53-r5-sa-7","target_ref":"requirement--nist-sp-800-53-r5-si-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8","slug":"sa-8","display_id":"SA-8","name":"Security and Privacy Engineering Principles","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Apply the following systems security and privacy engineering principles in the specification, design, development, implementation, and modification of the system and system components: {{ sa_8_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":10,"objectives_preview":[{"id":"[01]","statement":"{{ sa_08_odp_01 }} are applied in the specification of the system and system components;\n"},{"id":"[02]","statement":"{{ sa_08_odp_01 }} are applied in the design of the system and system components;\n"},{"id":"[03]","statement":"{{ sa_08_odp_01 }} are applied in the development of the system and system components;\n"},{"id":"[04]","statement":"{{ sa_08_odp_01 }} are applied in the implementation of the system and system components;\n"},{"id":"[05]","statement":"{{ sa_08_odp_01 }} are applied in the modification of the system and system components;\n"},{"id":"[06]","statement":"{{ sa_08_odp_02 }} are applied in the specification of the system and system components;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-01-to-800-53-sa-8","source_ref":"control--ogrl-sd-01","target_ref":"requirement--nist-sp-800-53-r5-sa-8","relationship":"intersects-with","review_status":"reviewed","parameter_map":{"sa_8_prm_1":"secure_design_principles"},"summary":"The SDLC names secure design principles to apply, supplying the SA-8 principles; application across all lifecycle stages is broader.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-1","slug":"sa-8-1","display_id":"SA-8(1)","name":"Clear Abstractions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of clear abstractions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(01)","statement":"the security design principle of clear abstractions is implemented."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-2","slug":"sa-8-2","display_id":"SA-8(2)","name":"Least Common Mechanism","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of least common mechanism in {{ sa_08_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(02)","statement":"{{ sa_08_02_odp }} implement the security design principle of least common mechanism.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-3","slug":"sa-8-3","display_id":"SA-8(3)","name":"Modularity and Layering","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principles of modularity and layering in {{ sa_8_3_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-08(03).sa-08(03)[01]","statement":"{{ sa_08_03_odp_01 }} implement the security design principle of modularity;"},{"id":"sa-08(03).sa-08(03)[02]","statement":"{{ sa_08_03_odp_02 }} implement the security design principle of layering."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-4","slug":"sa-8-4","display_id":"SA-8(4)","name":"Partially Ordered Dependencies","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of partially ordered dependencies in {{ sa_08_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(04)","statement":"{{ sa_08_04_odp }} implement the security design principle of partially ordered dependencies.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-5","slug":"sa-8-5","display_id":"SA-8(5)","name":"Efficiently Mediated Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of efficiently mediated access in {{ sa_08_05_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(05)","statement":"{{ sa_08_05_odp }} implement the security design principle of efficiently mediated access.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-6","slug":"sa-8-6","display_id":"SA-8(6)","name":"Minimized Sharing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of minimized sharing in {{ sa_08_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(06)","statement":"{{ sa_08_06_odp }} implement the security design principle of minimized sharing."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-7","slug":"sa-8-7","display_id":"SA-8(7)","name":"Reduced Complexity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of reduced complexity in {{ sa_08_07_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(07)","statement":"{{ sa_08_07_odp }} implement the security design principle of reduced complexity.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-8","slug":"sa-8-8","display_id":"SA-8(8)","name":"Secure Evolvability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of secure evolvability in {{ sa_08_08_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(08)","statement":"{{ sa_08_08_odp }} implement the security design principle of secure evolvability.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-9","slug":"sa-8-9","display_id":"SA-8(9)","name":"Trusted Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of trusted components in {{ sa_08_09_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(09)","statement":"{{ sa_08_09_odp }} implement the security design principle of trusted components.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-10","slug":"sa-8-10","display_id":"SA-8(10)","name":"Hierarchical Trust","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of hierarchical trust in {{ sa_08_10_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(10)","statement":"{{ sa_08_10_odp }} implement the security design principle of hierarchical trust.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-11","slug":"sa-8-11","display_id":"SA-8(11)","name":"Inverse Modification Threshold","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of inverse modification threshold in {{ sa_08_11_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(11)","statement":"{{ sa_08_11_odp }} implement the security design principle of inverse modification threshold.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-12","slug":"sa-8-12","display_id":"SA-8(12)","name":"Hierarchical Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of hierarchical protection in {{ sa_08_12_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(12)","statement":"{{ sa_08_12_odp }} implement the security design principle of hierarchical protection.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-13","slug":"sa-8-13","display_id":"SA-8(13)","name":"Minimized Security Elements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of minimized security elements in {{ sa_08_13_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(13)","statement":"{{ sa_08_13_odp }} implement the security design principle of minimized security elements.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-14","slug":"sa-8-14","display_id":"SA-8(14)","name":"Least Privilege","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of least privilege in {{ sa_08_14_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(14)","statement":"{{ sa_08_14_odp }} implement the security design principle of least privilege."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-15","slug":"sa-8-15","display_id":"SA-8(15)","name":"Predicate Permission","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of predicate permission in {{ sa_08_15_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(15)","statement":"{{ sa_08_15_odp }} implement the security design principle of predicate permission.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-16","slug":"sa-8-16","display_id":"SA-8(16)","name":"Self-reliant Trustworthiness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of self-reliant trustworthiness in {{ sa_08_16_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(16)","statement":"{{ sa_08_16_odp }} implement the security design principle of self-reliant trustworthiness.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-17","slug":"sa-8-17","display_id":"SA-8(17)","name":"Secure Distributed Composition","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of secure distributed composition in {{ sa_08_17_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(17)","statement":"{{ sa_08_17_odp }} implement the security design principle of secure distributed composition.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-18","slug":"sa-8-18","display_id":"SA-8(18)","name":"Trusted Communications Channels","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of trusted communications channels in {{ sa_08_18_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(18)","statement":"{{ sa_08_18_odp }} implement the security design principle of trusted communications channels.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-19","slug":"sa-8-19","display_id":"SA-8(19)","name":"Continuous Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of continuous protection in {{ sa_08_19_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(19)","statement":"{{ sa_08_19_odp }} implement the security design principle of continuous protection.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-20","slug":"sa-8-20","display_id":"SA-8(20)","name":"Secure Metadata Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of secure metadata management in {{ sa_08_20_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(20)","statement":"{{ sa_08_20_odp }} implement the security design principle of secure metadata management.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-21","slug":"sa-8-21","display_id":"SA-8(21)","name":"Self-analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of self-analysis in {{ sa_08_21_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(21)","statement":"{{ sa_08_21_odp }} implement the security design principle of self-analysis."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-22","slug":"sa-8-22","display_id":"SA-8(22)","name":"Accountability and Traceability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of accountability and traceability in {{ sa_8_22_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-08(22).sa-08(22)[01]","statement":"{{ sa_08_22_odp_01 }} implement the security design principle of accountability;"},{"id":"sa-08(22).sa-08(22)[02]","statement":"{{ sa_08_22_odp_02 }} implement the security design principle of traceability."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-23","slug":"sa-8-23","display_id":"SA-8(23)","name":"Secure Defaults","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of secure defaults in {{ sa_08_23_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(23)","statement":"{{ sa_08_23_odp }} implement the security design principle of secure defaults."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-24","slug":"sa-8-24","display_id":"SA-8(24)","name":"Secure Failure and Recovery","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of secure failure and recovery in {{ sa_8_24_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-08(24).sa-08(24)[01]","statement":"{{ sa_08_24_odp_01 }} implement the security design principle of secure failure;"},{"id":"sa-08(24).sa-08(24)[02]","statement":"{{ sa_08_24_odp_02 }} implement the security design principle of secure recovery.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-25","slug":"sa-8-25","display_id":"SA-8(25)","name":"Economic Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of economic security in {{ sa_08_25_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(25)","statement":"{{ sa_08_25_odp }} implement the security design principle of economic security."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-26","slug":"sa-8-26","display_id":"SA-8(26)","name":"Performance Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of performance security in {{ sa_08_26_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(26)","statement":"{{ sa_08_26_odp }} implement the security design principle of performance security.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-26.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-27","slug":"sa-8-27","display_id":"SA-8(27)","name":"Human Factored Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of human factored security in {{ sa_08_27_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(27)","statement":"{{ sa_08_27_odp }} implement the security design principle of human factored security.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-27.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-28","slug":"sa-8-28","display_id":"SA-8(28)","name":"Acceptable Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of acceptable security in {{ sa_08_28_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(28)","statement":"{{ sa_08_28_odp }} implement the security design principle of acceptable security.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-28.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-29","slug":"sa-8-29","display_id":"SA-8(29)","name":"Repeatable and Documented Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of repeatable and documented procedures in {{ sa_08_29_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(29)","statement":"{{ sa_08_29_odp }} implement the security design principle of repeatable and documented procedures.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-29.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-30","slug":"sa-8-30","display_id":"SA-8(30)","name":"Procedural Rigor","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of procedural rigor in {{ sa_08_30_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(30)","statement":"{{ sa_08_30_odp }} implement the security design principle of procedural rigor."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-30.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-31","slug":"sa-8-31","display_id":"SA-8(31)","name":"Secure System Modification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of secure system modification in {{ sa_08_31_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(31)","statement":"{{ sa_08_31_odp }} implement the security design principle of secure system modification.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-31.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-32","slug":"sa-8-32","display_id":"SA-8(32)","name":"Sufficient Documentation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the security design principle of sufficient documentation in {{ sa_08_32_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(32)","statement":"{{ sa_08_32_odp }} implement the security design principle of sufficient documentation.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-32.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-8-33","slug":"sa-8-33","display_id":"SA-8(33)","name":"Minimization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the privacy principle of minimization using {{ sa_08_33_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-08(33)","statement":"the privacy principle of minimization is implemented using {{ sa_08_33_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-8-33.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9","slug":"sa-9","display_id":"SA-9","name":"External System Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require that providers of external system services comply with organizational security and privacy requirements and employ the following controls: {{ sa_09_odp_01 }};\n"},{"id":"b","statement":"Define and document organizational oversight and user roles and responsibilities with regard to external system services; and\n"},{"id":"c","statement":"Employ the following processes, methods, and techniques to monitor control compliance by external service providers on an ongoing basis: {{ sa_09_odp_02 }}.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"providers of external system services comply with organizational security requirements;\n"},{"id":"a-2","statement":"providers of external system services comply with organizational privacy requirements;\n"},{"id":"a-3","statement":"providers of external system services employ {{ sa_09_odp_01 }};"},{"id":"b-1","statement":"organizational oversight with regard to external system services are defined and documented;\n"},{"id":"b-2","statement":"user roles and responsibilities with regard to external system services are defined and documented;\n"},{"id":"c","statement":"{{ sa_09_odp_02 }} are employed to monitor control compliance by external service providers on an ongoing basis.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-01-to-800-53-sa-9-b","source_ref":"control--ogrl-tp-01","target_ref":"requirement--nist-sp-800-53-r5-sa-9#b","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Assigning an internal owner to each external service documents oversight responsibility; broader user roles and responsibilities are not addressed.\n"},{"id":"mapping--ogrl-tp-04-to-800-53-sa-9-c","source_ref":"control--ogrl-tp-04","target_ref":"requirement--nist-sp-800-53-r5-sa-9#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sa_09_odp_02":"assurance_evidence"},"summary":"Periodic review of vendor assurance reports is the method used to monitor provider control compliance on an ongoing basis.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-1","slug":"sa-9-1","display_id":"SA-9(1)","name":"Risk Assessments and Organizational Approvals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Conduct an organizational assessment of risk prior to the acquisition or outsourcing of information security services; and\n"},{"id":"b","statement":"Verify that the acquisition or outsourcing of dedicated information security services is approved by {{ sa_09_01_odp }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"an organizational assessment of risk is conducted prior to the acquisition or outsourcing of information security services;\n"},{"id":"b","statement":"{{ sa_09_01_odp }} approve the acquisition or outsourcing of dedicated information security services.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-2","slug":"sa-9-2","display_id":"SA-9(2)","name":"Identification of Functions, Ports, Protocols, and Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require providers of the following external system services to identify the functions, ports, protocols, and other services required for the use of such services: {{ sa_09_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-09(02)","statement":"providers of {{ sa_09_02_odp }} are required to identify the functions, ports, protocols, and other services required for the use of such services.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-3","slug":"sa-9-3","display_id":"SA-9(3)","name":"Establish and Maintain Trust Relationship with Providers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish, document, and maintain trust relationships with external service providers based on the following requirements, properties, factors, or conditions: {{ sa_9_3_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"sa-09(03).sa-09(03)[01]","statement":"trust relationships with external service provides based on {{ sa_09_03_odp_01 }} are established and documented;\n"},{"id":"sa-09(03).sa-09(03)[02]","statement":"trust relationships with external service provides based on {{ sa_09_03_odp_01 }} are maintained;\n"},{"id":"sa-09(03).sa-09(03)[03]","statement":"trust relationships with external service provides based on {{ sa_09_03_odp_02 }} are established and documented;\n"},{"id":"sa-09(03).sa-09(03)[04]","statement":"trust relationships with external service provides based on {{ sa_09_03_odp_02 }} are maintained.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-4","slug":"sa-9-4","display_id":"SA-9(4)","name":"Consistent Interests of Consumers and Providers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Take the following actions to verify that the interests of {{ sa_09_04_odp_01 }} are consistent with and reflect organizational interests: {{ sa_09_04_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-09(04)","statement":"{{ sa_09_04_odp_02 }} are taken to verify that the interests of {{ sa_09_04_odp_01 }} are consistent with and reflect organizational interests.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-5","slug":"sa-9-5","display_id":"SA-9(5)","name":"Processing, Storage, and Service Location","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the location of {{ sa_09_05_odp_01 }} to {{ sa_09_05_odp_02 }} based on {{ sa_09_05_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-09(05)","statement":"based on {{ sa_09_05_odp_03 }}, {{ sa_09_05_odp_01 }} is/are restricted to {{ sa_09_05_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-6","slug":"sa-9-6","display_id":"SA-9(6)","name":"Organization-controlled Cryptographic Keys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain exclusive control of cryptographic keys for encrypted material stored or transmitted through an external system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-09(06)","statement":"exclusive control of cryptographic keys is maintained for encrypted material stored or transmitted through an external system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-7","slug":"sa-9-7","display_id":"SA-9(7)","name":"Organization-controlled Integrity Checking","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability to check the integrity of information while it resides in the external system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-09(07)","statement":"the capability is provided to check the integrity of information while it resides in the external system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-9-8","slug":"sa-9-8","display_id":"SA-9(8)","name":"Processing and Storage Location — U.S. Jurisdiction","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the geographic location of information processing and data storage to facilities located within in the legal jurisdictional boundary of the United States.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-09(08)","statement":"the geographic location of information processing and data storage is restricted to facilities located within the legal jurisdictional boundary of the United States.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-9-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10","slug":"sa-10","display_id":"SA-10","name":"Developer Configuration Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Perform configuration management during system, component, or service {{ sa_10_odp_01 }};\n"},{"id":"b","statement":"Document, manage, and control the integrity of changes to {{ sa_10_odp_02 }};"},{"id":"c","statement":"Implement only organization-approved changes to the system, component, or service;\n"},{"id":"d","statement":"Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and\n"},{"id":"e","statement":"Track security flaws and flaw resolution within the system, component, or service and report findings to {{ sa_10_odp_03 }}.\n"}],"objectives_count":11,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to perform configuration management during system, component, or service {{ sa_10_odp_01 }};\n"},{"id":"b-1","statement":"the developer of the system, system component, or system service is required to document the integrity of changes to {{ sa_10_odp_02 }};\n"},{"id":"b-2","statement":"the developer of the system, system component, or system service is required to manage the integrity of changes to {{ sa_10_odp_02 }};\n"},{"id":"b-3","statement":"the developer of the system, system component, or system service is required to control the integrity of changes to {{ sa_10_odp_02 }};\n"},{"id":"c","statement":"the developer of the system, system component, or system service is required to implement only organization-approved changes to the system, component, or service;\n"},{"id":"d-1","statement":"the developer of the system, system component, or system service is required to document approved changes to the system, component, or service;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-04-to-800-53-sa-10-b","source_ref":"control--ogrl-sd-04","target_ref":"requirement--nist-sp-800-53-r5-sa-10#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sa_10_odp_02":"versioned_assets"},"summary":"Versioning all production assets and protecting branches controls the integrity of changes to configuration items per SA-10(b).\n"},{"id":"mapping--ogrl-sd-04-to-800-53-sa-10-c","source_ref":"control--ogrl-sd-04","target_ref":"requirement--nist-sp-800-53-r5-sa-10#c","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Branch protection ensures only approved pull requests enter release branches, partly enforcing SA-10(c).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-1","slug":"sa-10-1","display_id":"SA-10(1)","name":"Software and Firmware Integrity Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to enable integrity verification of software and firmware components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-10(01)","statement":"the developer of the system, system component, or system service is required to enable integrity verification of software and firmware components.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-2","slug":"sa-10-2","display_id":"SA-10(2)","name":"Alternative Configuration Management Processes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an alternate configuration management process using organizational personnel in the absence of a dedicated developer configuration management team.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-10(02)","statement":"an alternate configuration management process has been provided using organizational personnel in the absence of a dedicated developer configuration management team.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-3","slug":"sa-10-3","display_id":"SA-10(3)","name":"Hardware Integrity Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to enable integrity verification of hardware components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-10(03)","statement":"the developer of the system, system component, or system service is required to enable integrity verification of hardware components.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-4","slug":"sa-10-4","display_id":"SA-10(4)","name":"Trusted Generation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to employ tools for comparing newly generated versions of security-relevant hardware descriptions, source code, and object code with previous versions.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"sa-10(04).sa-10(04)[01]","statement":"the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of security-relevant hardware descriptions with previous versions;\n"},{"id":"sa-10(04).sa-10(04)[02]","statement":"the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of source code with previous versions;\n"},{"id":"sa-10(04).sa-10(04)[03]","statement":"the developer of the system, system component, or system service is required to employ tools for comparing newly generated versions of object code with previous versions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-5","slug":"sa-10-5","display_id":"SA-10(5)","name":"Mapping Integrity for Version Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-10(05)","statement":"the developer of the system, system component, or system service is required to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-6","slug":"sa-10-6","display_id":"SA-10(6)","name":"Trusted Distribution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-10(06)","statement":"the developer of the system, system component, or system service is required to execute procedures for ensuring that security-relevant hardware, software, and firmware updates distributed to the organization are exactly as specified by the master copies.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-10-7","slug":"sa-10-7","display_id":"SA-10(7)","name":"Security and Privacy Representatives","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require {{ sa_10_7_prm_1 }} to be included in the {{ sa_10_7_prm_2 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-10(07).sa-10(07)[01]","statement":"{{ sa_10_07_odp_01 }} are required to be included in the {{ sa_10_07_odp_03 }};"},{"id":"sa-10(07).sa-10(07)[02]","statement":"{{ sa_10_07_odp_02 }} are required to be included in the {{ sa_10_07_odp_04 }}."}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-10-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11","slug":"sa-11","display_id":"SA-11","name":"Developer Testing and Evaluation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to:\n","citation":null,"parts":[{"id":"a","statement":"Develop and implement a plan for ongoing security and privacy control assessments;\n"},{"id":"b","statement":"Perform {{ sa_11_odp_01 }} testing/evaluation {{ sa_11_odp_02 }} at {{ sa_11_odp_03 }};\n"},{"id":"c","statement":"Produce evidence of the execution of the assessment plan and the results of the testing and evaluation;\n"},{"id":"d","statement":"Implement a verifiable flaw remediation process; and"},{"id":"e","statement":"Correct flaws identified during testing and evaluation."}],"objectives_count":9,"objectives_preview":[{"id":"a-1","statement":"the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments;\n"},{"id":"a-2","statement":"the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments;\n"},{"id":"a-3","statement":"the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments;\n"},{"id":"a-4","statement":"the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments;\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to perform {{ sa_11_odp_01 }} testing/evaluation {{ sa_11_odp_02 }} at {{ sa_11_odp_03 }};\n"},{"id":"c-1","statement":"the developer of the system, system component, or system service is required at all post-design stages of the system development life cycle to produce evidence of the execution of the assessment plan;\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-1","slug":"sa-11-1","display_id":"SA-11(1)","name":"Static Code Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of the analysis.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-11(01).sa-11(01)[01]","statement":"the developer of the system, system component, or system service is required to employ static code analysis tools to identify common flaws;\n"},{"id":"sa-11(01).sa-11(01)[02]","statement":"the developer of the system, system component, or system service is required to employ static code analysis tools to document the results of the analysis.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-03-to-800-53-sa-11-1","source_ref":"control--ogrl-sd-03","target_ref":"requirement--nist-sp-800-53-r5-sa-11-1","relationship":"superset-of","review_status":"reviewed","parameter_map":null,"summary":"Static analysis on every pull request with retained results meets SA-11(1), with secret and dependency scanning added.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-2","slug":"sa-11-2","display_id":"SA-11(2)","name":"Threat Modeling and Vulnerability Analyses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and evaluation of the system, component, or service that:\n","citation":null,"parts":[{"id":"a","statement":"Uses the following contextual information: {{ sa_11_02_odp_01 }};"},{"id":"b","statement":"Employs the following tools and methods: {{ sa_11_02_odp_02 }};"},{"id":"c","statement":"Conducts the modeling and analyses at the following level of rigor: {{ sa_11_2_prm_3 }} ; and\n"},{"id":"d","statement":"Produces evidence that meets the following acceptance criteria: {{ sa_11_2_prm_4 }}.\n"}],"objectives_count":14,"objectives_preview":[{"id":"a-1","statement":"the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses {{ sa_11_02_odp_01 }};\n"},{"id":"a-2","statement":"the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that uses {{ sa_11_02_odp_01 }};\n"},{"id":"a-3","statement":"the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that uses {{ sa_11_02_odp_01 }};\n"},{"id":"a-4","statement":"the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that uses {{ sa_11_02_odp_01 }};\n"},{"id":"b-1","statement":"the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that employs {{ sa_11_02_odp_02 }};\n"},{"id":"b-2","statement":"the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that employs {{ sa_11_02_odp_02 }};\n"}],"params_count":8,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-3","slug":"sa-11-3","display_id":"SA-11(3)","name":"Independent Verification of Assessment Plans and Evidence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require an independent agent satisfying {{ sa_11_03_odp }} to verify the correct implementation of the developer security and privacy assessment plans and the evidence produced during testing and evaluation; and\n"},{"id":"b","statement":"Verify that the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"an independent agent is required to satisfy {{ sa_11_03_odp }} to verify the correct implementation of the developer security assessment plan and the evidence produced during testing and evaluation;\n"},{"id":"a-2","statement":"an independent agent is required to satisfy {{ sa_11_03_odp }} to verify the correct implementation of the developer privacy assessment plan and the evidence produced during testing and evaluation;\n"},{"id":"b","statement":"the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-4","slug":"sa-11-4","display_id":"SA-11(4)","name":"Manual Code Reviews","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to perform a manual code review of {{ sa_11_04_odp_01 }} using the following processes, procedures, and/or techniques: {{ sa_11_04_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-11(04)","statement":"the developer of the system, system component, or system service is required to perform a manual code review of {{ sa_11_04_odp_01 }} using {{ sa_11_04_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-02-to-800-53-sa-11-4","source_ref":"control--ogrl-sd-02","target_ref":"requirement--nist-sp-800-53-r5-sa-11-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sa_11_04_odp_01":"security_sensitive_code","sa_11_04_odp_02":"code_review_techniques"},"summary":"Checklist-driven manual review of designated security-sensitive code satisfies SA-11(4).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-5","slug":"sa-11-5","display_id":"SA-11(5)","name":"Penetration Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to perform penetration testing:\n","citation":null,"parts":[{"id":"a","statement":"At the following level of rigor: {{ sa_11_5_prm_1 }} ; and"},{"id":"b","statement":"Under the following constraints: {{ sa_11_05_odp_03 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: {{ sa_11_05_odp_01 }};\n"},{"id":"a-2","statement":"the developer of the system, system component, or system service is required to perform penetration testing at the following level of rigor: {{ sa_11_05_odp_02 }};\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to perform penetration testing under {{ sa_11_05_odp_03 }}.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-6","slug":"sa-11-6","display_id":"SA-11(6)","name":"Attack Surface Reviews","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to perform attack surface reviews.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-11(06)","statement":"the developer of the system, system component, or system service is required to perform attack surface reviews.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-7","slug":"sa-11-7","display_id":"SA-11(7)","name":"Verify Scope of Testing and Evaluation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to verify that the scope of testing and evaluation provides complete coverage of the required controls at the following level of rigor: {{ sa_11_7_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-11(07).sa-11(07)[01]","statement":"the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at {{ sa_11_07_odp_01 }};\n"},{"id":"sa-11(07).sa-11(07)[02]","statement":"the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls at {{ sa_11_07_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-8","slug":"sa-11-8","display_id":"SA-11(8)","name":"Dynamic Code Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-11(08).sa-11(08)[01]","statement":"the developer of the system, system component, or system service is required to employ dynamic code analysis tools to identify common flaws;\n"},{"id":"sa-11(08).sa-11(08)[02]","statement":"the developer of the system, system component, or system service is required to document the results of the analysis.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-11-9","slug":"sa-11-9","display_id":"SA-11(9)","name":"Interactive Application Security Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws and document the results.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-11(09).sa-11(09)[01]","statement":"the developer of the system, system component, or system service is required to employ interactive application security testing tools to identify flaws;\n"},{"id":"sa-11(09).sa-11(09)[02]","statement":"the developer of the system, system component, or system service is required to document the results of flaw identification.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-11-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12","slug":"sa-12","display_id":"SA-12","name":"Supply Chain Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-1","slug":"sa-12-1","display_id":"SA-12(1)","name":"Acquisition Strategies / Tools / Methods","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-1_to_nist-sp-800-53-r5-sr-5","source_ref":"requirement--nist-sp-800-53-r5-sa-12-1","target_ref":"requirement--nist-sp-800-53-r5-sr-5","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-2","slug":"sa-12-2","display_id":"SA-12(2)","name":"Supplier Reviews","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-2_to_nist-sp-800-53-r5-sr-6","source_ref":"requirement--nist-sp-800-53-r5-sa-12-2","target_ref":"requirement--nist-sp-800-53-r5-sr-6","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-3","slug":"sa-12-3","display_id":"SA-12(3)","name":"Trusted Shipping and Warehousing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-3_to_nist-sp-800-53-r5-sr-3","source_ref":"requirement--nist-sp-800-53-r5-sa-12-3","target_ref":"requirement--nist-sp-800-53-r5-sr-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-4","slug":"sa-12-4","display_id":"SA-12(4)","name":"Diversity of Suppliers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-4_to_nist-sp-800-53-r5-sr-3-1","source_ref":"requirement--nist-sp-800-53-r5-sa-12-4","target_ref":"requirement--nist-sp-800-53-r5-sr-3-1","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-5","slug":"sa-12-5","display_id":"SA-12(5)","name":"Limitation of Harm","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-5_to_nist-sp-800-53-r5-sr-3-2","source_ref":"requirement--nist-sp-800-53-r5-sa-12-5","target_ref":"requirement--nist-sp-800-53-r5-sr-3-2","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-6","slug":"sa-12-6","display_id":"SA-12(6)","name":"Minimizing Procurement Time","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-6_to_nist-sp-800-53-r5-sr-5-1","source_ref":"requirement--nist-sp-800-53-r5-sa-12-6","target_ref":"requirement--nist-sp-800-53-r5-sr-5-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-7","slug":"sa-12-7","display_id":"SA-12(7)","name":"Assessments Prior to Selection / Acceptance / Update","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-7_to_nist-sp-800-53-r5-sr-5-2","source_ref":"requirement--nist-sp-800-53-r5-sa-12-7","target_ref":"requirement--nist-sp-800-53-r5-sr-5-2","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-8","slug":"sa-12-8","display_id":"SA-12(8)","name":"Use of All-source Intelligence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-8_to_nist-sp-800-53-r5-ra-3-2","source_ref":"requirement--nist-sp-800-53-r5-sa-12-8","target_ref":"requirement--nist-sp-800-53-r5-ra-3-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-9","slug":"sa-12-9","display_id":"SA-12(9)","name":"Operations Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-9_to_nist-sp-800-53-r5-sr-7","source_ref":"requirement--nist-sp-800-53-r5-sa-12-9","target_ref":"requirement--nist-sp-800-53-r5-sr-7","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-10","slug":"sa-12-10","display_id":"SA-12(10)","name":"Validate as Genuine and Not Altered","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-10_to_nist-sp-800-53-r5-sr-4-3","source_ref":"requirement--nist-sp-800-53-r5-sa-12-10","target_ref":"requirement--nist-sp-800-53-r5-sr-4-3","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-11","slug":"sa-12-11","display_id":"SA-12(11)","name":"Penetration Testing / Analysis of Elements, Processes, and Actors","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-11_to_nist-sp-800-53-r5-sr-6-1","source_ref":"requirement--nist-sp-800-53-r5-sa-12-11","target_ref":"requirement--nist-sp-800-53-r5-sr-6-1","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-12","slug":"sa-12-12","display_id":"SA-12(12)","name":"Inter-organizational Agreements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-12_to_nist-sp-800-53-r5-sr-8","source_ref":"requirement--nist-sp-800-53-r5-sa-12-12","target_ref":"requirement--nist-sp-800-53-r5-sr-8","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-13","slug":"sa-12-13","display_id":"SA-12(13)","name":"Critical Information System Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-13_to_nist-sp-800-53-r5-ma-6","source_ref":"requirement--nist-sp-800-53-r5-sa-12-13","target_ref":"requirement--nist-sp-800-53-r5-ma-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sa-12-13_to_nist-sp-800-53-r5-ra-9","source_ref":"requirement--nist-sp-800-53-r5-sa-12-13","target_ref":"requirement--nist-sp-800-53-r5-ra-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-14","slug":"sa-12-14","display_id":"SA-12(14)","name":"Identity and Traceability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-14_to_nist-sp-800-53-r5-sr-4-1","source_ref":"requirement--nist-sp-800-53-r5-sa-12-14","target_ref":"requirement--nist-sp-800-53-r5-sr-4-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sa-12-14_to_nist-sp-800-53-r5-sr-4-2","source_ref":"requirement--nist-sp-800-53-r5-sa-12-14","target_ref":"requirement--nist-sp-800-53-r5-sr-4-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-12-15","slug":"sa-12-15","display_id":"SA-12(15)","name":"Processes to Address Weaknesses or Deficiencies","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-12-15_to_nist-sp-800-53-r5-sr-3","source_ref":"requirement--nist-sp-800-53-r5-sa-12-15","target_ref":"requirement--nist-sp-800-53-r5-sr-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-12-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-13","slug":"sa-13","display_id":"SA-13","name":"Trustworthiness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-13_to_nist-sp-800-53-r5-sa-8","source_ref":"requirement--nist-sp-800-53-r5-sa-13","target_ref":"requirement--nist-sp-800-53-r5-sa-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-14","slug":"sa-14","display_id":"SA-14","name":"Criticality Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-14_to_nist-sp-800-53-r5-ra-9","source_ref":"requirement--nist-sp-800-53-r5-sa-14","target_ref":"requirement--nist-sp-800-53-r5-ra-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-14-1","slug":"sa-14-1","display_id":"SA-14(1)","name":"Critical Components with No Viable Alternative Sourcing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-14-1_to_nist-sp-800-53-r5-sa-20","source_ref":"requirement--nist-sp-800-53-r5-sa-14-1","target_ref":"requirement--nist-sp-800-53-r5-sa-20","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-14-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15","slug":"sa-15","display_id":"SA-15","name":"Development Process, Standards, and Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Require the developer of the system, system component, or system service to follow a documented development process that:\n"},{"id":"a.1","statement":"Explicitly addresses security and privacy requirements;"},{"id":"a.2","statement":"Identifies the standards and tools used in the development process;"},{"id":"a.3","statement":"Documents the specific tool options and tool configurations used in the development process; and\n"},{"id":"a.4","statement":"Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and\n"},{"id":"b","statement":"Review the development process, standards, tools, tool options, and tool configurations {{ sa_15_odp_01 }} to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: {{ sa_15_prm_2 }}.\n"}],"objectives_count":9,"objectives_preview":[{"id":"a.1-1","statement":"the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses security requirements;\n"},{"id":"a.1-2","statement":"the developer of the system, system component, or system service is required to follow a documented development process that explicitly addresses privacy requirements;\n"},{"id":"a.2-1","statement":"the developer of the system, system component, or system service is required to follow a documented development process that identifies the standards used in the development process;\n"},{"id":"a.2-2","statement":"the developer of the system, system component, or system service is required to follow a documented development process that identifies the tools used in the development process;\n"},{"id":"a.3-1","statement":"the developer of the system, system component, or system service is required to follow a documented development process that documents the specific tool used in the development process;\n"},{"id":"a.3-2","statement":"the developer of the system, system component, or system service is required to follow a documented development process that documents the specific tool configurations used in the development process;\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-1","slug":"sa-15-1","display_id":"SA-15(1)","name":"Quality Metrics","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Define quality metrics at the beginning of the development process; and"},{"id":"b","statement":"Provide evidence of meeting the quality metrics {{ sa_15_01_odp_01 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to define quality metrics at the beginning of the development process;\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to provide evidence of meeting the quality metrics {{ sa_15_01_odp_01 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-2","slug":"sa-15-2","display_id":"SA-15(2)","name":"Security and Privacy Tracking Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to select and employ security and privacy tracking tools for use during the development process.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-15(02).sa-15(02)[01]","statement":"the developer of the system, system component, or system service is required to select and employ security tracking tools for use during the development process;\n"},{"id":"sa-15(02).sa-15(02)[02]","statement":"the developer of the system, system component, or system service is required to select and employ privacy tracking tools for use during the development process.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-3","slug":"sa-15-3","display_id":"SA-15(3)","name":"Criticality Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to perform a criticality analysis:\n","citation":null,"parts":[{"id":"a","statement":"At the following decision points in the system development life cycle: {{ sa_15_03_odp_01 }} ; and\n"},{"id":"b","statement":"At the following level of rigor: {{ sa_15_3_prm_2 }}."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to perform a criticality analysis at {{ sa_15_03_odp_01 }} in the system development life cycle;\n"},{"id":"b-1","statement":"the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: {{ sa_15_03_odp_02 }};\n"},{"id":"b-2","statement":"the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: {{ sa_15_03_odp_03 }} .\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-4","slug":"sa-15-4","display_id":"SA-15(4)","name":"Threat Modeling and Vulnerability Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-15-4_to_nist-sp-800-53-r5-sa-11-2","source_ref":"requirement--nist-sp-800-53-r5-sa-15-4","target_ref":"requirement--nist-sp-800-53-r5-sa-11-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-5","slug":"sa-15-5","display_id":"SA-15(5)","name":"Attack Surface Reduction","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to reduce attack surfaces to {{ sa_15_05_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-15(05)","statement":"the developer of the system, system component, or system service is required to reduce attack surfaces to {{ sa_15_05_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-6","slug":"sa-15-6","display_id":"SA-15(6)","name":"Continuous Improvement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to implement an explicit process to continuously improve the development process.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-15(06)","statement":"the developer of the system, system component, or system service is required to implement an explicit process to continuously improve the development process.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-7","slug":"sa-15-7","display_id":"SA-15(7)","name":"Automated Vulnerability Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service {{ sa_15_07_odp_01 }} to:\n","citation":null,"parts":[{"id":"a","statement":"Perform an automated vulnerability analysis using {{ sa_15_07_odp_02 }};"},{"id":"b","statement":"Determine the exploitation potential for discovered vulnerabilities;"},{"id":"c","statement":"Determine potential risk mitigations for delivered vulnerabilities; and"},{"id":"d","statement":"Deliver the outputs of the tools and results of the analysis to {{ sa_15_07_odp_03 }}.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to perform automated vulnerability analysis {{ sa_15_07_odp_01 }} using {{ sa_15_07_odp_02 }};\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to determine the exploitation potential for discovered vulnerabilities {{ sa_15_07_odp_01 }};\n"},{"id":"c","statement":"the developer of the system, system component, or system service is required to determine potential risk mitigations {{ sa_15_07_odp_01 }} for delivered vulnerabilities;\n"},{"id":"d","statement":"the developer of the system, system component, or system service is required to deliver the outputs of the tools and results of the analysis {{ sa_15_07_odp_01 }} to {{ sa_15_07_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-8","slug":"sa-15-8","display_id":"SA-15(8)","name":"Reuse of Threat and Vulnerability Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to use threat modeling and vulnerability analyses from similar systems, components, or services to inform the current development process.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sa-15(08).sa-15(08)[01]","statement":"the developer of the system, system component, or system service is required to use threat modeling from similar systems, components, or services to inform the current development process;\n"},{"id":"sa-15(08).sa-15(08)[02]","statement":"the developer of the system, system component, or system service is required to use vulnerability analyses from similar systems, components, or services to inform the current development process.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-9","slug":"sa-15-9","display_id":"SA-15(9)","name":"Use of Live Data","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-15-9_to_nist-sp-800-53-r5-sa-3-2","source_ref":"requirement--nist-sp-800-53-r5-sa-15-9","target_ref":"requirement--nist-sp-800-53-r5-sa-3-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-10","slug":"sa-15-10","display_id":"SA-15(10)","name":"Incident Response Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to provide, implement, and test an incident response plan.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"_obj-1","statement":"the developer of the system, system component, or system service is required to provide an incident response plan;\n"},{"id":"_obj-2","statement":"the developer of the system, system component, or system service is required to implement an incident response plan;\n"},{"id":"_obj-3","statement":"the developer of the system, system component, or system service is required to test an incident response plan.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-11","slug":"sa-15-11","display_id":"SA-15(11)","name":"Archive System or Component","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the developer of the system or system component is required to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-12","slug":"sa-15-12","display_id":"SA-15(12)","name":"Minimize Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the developer of the system or system component is required to minimize the use of personally identifiable information in development and test environments.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-15-13","slug":"sa-15-13","display_id":"SA-15(13)","name":"Logging Syntax","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to use {{ sa_15_13_odp_01 }} to log {{ sa_15_13_odp_02 }} at {{ sa_15_13_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"Determine if:\n\nthe developer of the system, system component, or system service uses {{ sa_15_13_odp_01 }} to log {{ sa_15_13_odp_02 }} at {{ sa_15_13_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-15-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-16","slug":"sa-16","display_id":"SA-16","name":"Developer-provided Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to provide the following training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms: {{ sa_16_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the developer of the system, system component, or system service is required to provide {{ sa_16_odp }} on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17","slug":"sa-17","display_id":"SA-17","name":"Developer Security and Privacy Architecture and Design","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that:\n","citation":null,"parts":[{"id":"a","statement":"Is consistent with the organization’s security and privacy architecture that is an integral part the organization’s enterprise architecture;\n"},{"id":"b","statement":"Accurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and\n"},{"id":"c","statement":"Expresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to protection.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"the developer of the system, system component, or system service is required to produce a design specification and security architecture that are consistent with the organization’s security architecture, which is an integral part the organization’s enterprise architecture;\n"},{"id":"a-2","statement":"the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that are consistent with the organization’s privacy architecture, which is an integral part the organization’s enterprise architecture;\n"},{"id":"b-1","statement":"the developer of the system, system component, or system service is required to produce a design specification and security architecture that accurately and completely describe the required security functionality and the allocation of controls among physical and logical components;\n"},{"id":"b-2","statement":"the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that accurately and completely describe the required privacy functionality and the allocation of controls among physical and logical components;\n"},{"id":"c-1","statement":"the developer of the system, system component, or system service is required to produce a design specification and security architecture that express how individual security functions, mechanisms, and services work together to provide required security capabilities and a unified approach to protection;\n"},{"id":"c-2","statement":"the developer of the system, system component, or system service is required to produce a design specification and privacy architecture that express how individual privacy functions, mechanisms, and services work together to provide required privacy capabilities and a unified approach to protection.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-1","slug":"sa-17-1","display_id":"SA-17(1)","name":"Formal Policy Model","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Produce, as an integral part of the development process, a formal policy model describing the {{ sa_17_1_prm_1 }} to be enforced; and\n"},{"id":"b","statement":"Prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security and privacy policy when implemented.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the {{ sa_17_01_odp_01 }} to be enforced;\n"},{"id":"a-2","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the {{ sa_17_01_odp_02 }} to be enforced;\n"},{"id":"b-1","statement":"the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented;\n"},{"id":"b-2","statement":"the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational privacy policy when implemented.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-2","slug":"sa-17-2","display_id":"SA-17(2)","name":"Security-relevant Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Define security-relevant hardware, software, and firmware; and"},{"id":"b","statement":"Provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"the developer of the system, system component, or system service is required to define security-relevant hardware;\n"},{"id":"a-2","statement":"the developer of the system, system component, or system service is required to define security-relevant software;\n"},{"id":"a-3","statement":"the developer of the system, system component, or system service is required to define security-relevant firmware;\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-3","slug":"sa-17-3","display_id":"SA-17(3)","name":"Formal Correspondence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Produce, as an integral part of the development process, a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions, error messages, and effects;\n"},{"id":"b","statement":"Show via proof to the extent feasible with additional informal demonstration as necessary, that the formal top-level specification is consistent with the formal policy model;\n"},{"id":"c","statement":"Show via informal demonstration, that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;\n"},{"id":"d","statement":"Show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware; and\n"},{"id":"e","statement":"Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the formal top-level specification but strictly internal to the security-relevant hardware, software, and firmware.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a-1","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions;\n"},{"id":"a-2","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages;\n"},{"id":"a-3","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects;\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to show proof that the formal top-level specification is consistent with the formal policy model to the extent feasible with additional informal demonstration as necessary;\n"},{"id":"c","statement":"the developer of the system, system component, or system service is required to show via informal demonstration that the formal top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;\n"},{"id":"d","statement":"the developer of the system, system component, or system service is required to show that the formal top-level specification is an accurate description of the implemented security-relevant hardware, software, and firmware;\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-4","slug":"sa-17-4","display_id":"SA-17(4)","name":"Informal Correspondence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Produce, as an integral part of the development process, an informal descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions, error messages, and effects;\n"},{"id":"b","statement":"Show via {{ sa_17_04_odp }} that the descriptive top-level specification is consistent with the formal policy model;\n"},{"id":"c","statement":"Show via informal demonstration, that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;\n"},{"id":"d","statement":"Show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware; and\n"},{"id":"e","statement":"Describe the security-relevant hardware, software, and firmware mechanisms not addressed in the descriptive top-level specification but strictly internal to the security-relevant hardware, software, and firmware.\n"}],"objectives_count":7,"objectives_preview":[{"id":"a-1","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of exceptions;\n"},{"id":"a-2","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of error messages;\n"},{"id":"a-3","statement":"as an integral part of the development process, the developer of the system, system component, or system service is required to produce an informal, descriptive top-level specification that specifies the interfaces to security-relevant hardware, software, and firmware in terms of effects;\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to show via {{ sa_17_04_odp }} that the descriptive top-level specification is consistent with the formal policy model;\n"},{"id":"c","statement":"the developer of the system, system component, or system service is required to show via informal demonstration that the descriptive top-level specification completely covers the interfaces to security-relevant hardware, software, and firmware;\n"},{"id":"d","statement":"the developer of the system, system component, or system service is required to show that the descriptive top-level specification is an accurate description of the interfaces to security-relevant hardware, software, and firmware;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-5","slug":"sa-17-5","display_id":"SA-17(5)","name":"Conceptually Simple Design","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to:","citation":null,"parts":[{"id":"a","statement":"Design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics; and\n"},{"id":"b","statement":"Internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the developer of the system, system component, or system service is required to design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics;\n"},{"id":"b","statement":"the developer of the system, system component, or system service is required to internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-6","slug":"sa-17-6","display_id":"SA-17(6)","name":"Structure for Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to structure security-relevant hardware, software, and firmware to facilitate testing.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-17(06)","statement":"the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate testing.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-7","slug":"sa-17-7","display_id":"SA-17(7)","name":"Structure for Least Privilege","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require the developer of the system, system component, or system service to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-17(07)","statement":"the developer of the system, system component, or system service is required to structure security-relevant hardware, software, and firmware to facilitate controlling access with least privilege.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-8","slug":"sa-17-8","display_id":"SA-17(8)","name":"Orchestration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Design {{ sa_17_08_odp_01 }} with coordinated behavior to implement the following capabilities: {{ sa_17_08_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-17(08)","statement":"{{ sa_17_08_odp_01 }} are designed with coordinated behavior to implement {{ sa_17_08_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-17-9","slug":"sa-17-9","display_id":"SA-17(9)","name":"Design Diversity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use different designs for {{ sa_17_09_odp }} to satisfy a common set of requirements or to provide equivalent functionality.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sa-17(09)","statement":"different designs are used for {{ sa_17_09_odp }} to satisfy a common set of requirements or to provide equivalent functionality.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-17-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-18","slug":"sa-18","display_id":"SA-18","name":"Tamper Resistance and Detection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-18_to_nist-sp-800-53-r5-sr-9","source_ref":"requirement--nist-sp-800-53-r5-sa-18","target_ref":"requirement--nist-sp-800-53-r5-sr-9","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-18-1","slug":"sa-18-1","display_id":"SA-18(1)","name":"Multiple Phases of System Development Life Cycle","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-18-1_to_nist-sp-800-53-r5-sr-9-1","source_ref":"requirement--nist-sp-800-53-r5-sa-18-1","target_ref":"requirement--nist-sp-800-53-r5-sr-9-1","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-18-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-18-2","slug":"sa-18-2","display_id":"SA-18(2)","name":"Inspection of Systems or Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-18-2_to_nist-sp-800-53-r5-sr-10","source_ref":"requirement--nist-sp-800-53-r5-sa-18-2","target_ref":"requirement--nist-sp-800-53-r5-sr-10","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-18-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-19","slug":"sa-19","display_id":"SA-19","name":"Component Authenticity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-19_to_nist-sp-800-53-r5-sr-11","source_ref":"requirement--nist-sp-800-53-r5-sa-19","target_ref":"requirement--nist-sp-800-53-r5-sr-11","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-19-1","slug":"sa-19-1","display_id":"SA-19(1)","name":"Anti-counterfeit Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-19-1_to_nist-sp-800-53-r5-sr-11-1","source_ref":"requirement--nist-sp-800-53-r5-sa-19-1","target_ref":"requirement--nist-sp-800-53-r5-sr-11-1","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-19-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-19-2","slug":"sa-19-2","display_id":"SA-19(2)","name":"Configuration Control for Component Service and Repair","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-19-2_to_nist-sp-800-53-r5-sr-11-2","source_ref":"requirement--nist-sp-800-53-r5-sa-19-2","target_ref":"requirement--nist-sp-800-53-r5-sr-11-2","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-19-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-19-3","slug":"sa-19-3","display_id":"SA-19(3)","name":"Component Disposal","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-19-3_to_nist-sp-800-53-r5-sr-12","source_ref":"requirement--nist-sp-800-53-r5-sa-19-3","target_ref":"requirement--nist-sp-800-53-r5-sr-12","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-19-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-19-4","slug":"sa-19-4","display_id":"SA-19(4)","name":"Anti-counterfeit Scanning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-19-4_to_nist-sp-800-53-r5-sr-11-3","source_ref":"requirement--nist-sp-800-53-r5-sa-19-4","target_ref":"requirement--nist-sp-800-53-r5-sr-11-3","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-19-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-20","slug":"sa-20","display_id":"SA-20","name":"Customized Development of Critical Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Reimplement or custom develop the following critical system components: {{ sa_20_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sa_20_odp }} are reimplemented or custom-developed."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-21","slug":"sa-21","display_id":"SA-21","name":"Developer Screening","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Require that the developer of {{ sa_21_odp_01 }}:","citation":null,"parts":[{"id":"a","statement":"Has appropriate access authorizations as determined by assigned {{ sa_21_odp_02 }} ; and\n"},{"id":"b","statement":"Satisfies the following additional personnel screening criteria: {{ sa_21_odp_03 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the developer of {{ sa_21_odp_01 }} is required to have appropriate access authorizations as determined by assigned {{ sa_21_odp_02 }};\n"},{"id":"b","statement":"the developer of {{ sa_21_odp_01 }} is required to satisfy {{ sa_21_odp_03 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-21-1","slug":"sa-21-1","display_id":"SA-21(1)","name":"Validation of Screening","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-21-1_to_nist-sp-800-53-r5-sa-21","source_ref":"requirement--nist-sp-800-53-r5-sa-21-1","target_ref":"requirement--nist-sp-800-53-r5-sa-21","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-21-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-22","slug":"sa-22","display_id":"SA-22","name":"Unsupported System Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or\n"},{"id":"b","statement":"Provide the following options for alternative sources for continued support for unsupported components {{ sa_22_odp_01 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"system components are replaced when support for the components is no longer available from the developer, vendor, or manufacturer;\n"},{"id":"b","statement":"{{ sa_22_odp_01 }} provide options for alternative sources for continued support for unsupported components.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-22-1","slug":"sa-22-1","display_id":"SA-22(1)","name":"Alternative Sources for Continued Support","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sa-22-1_to_nist-sp-800-53-r5-sa-22","source_ref":"requirement--nist-sp-800-53-r5-sa-22-1","target_ref":"requirement--nist-sp-800-53-r5-sa-22","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-22-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-23","slug":"sa-23","display_id":"SA-23","name":"Specialization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ {{ sa_23_odp_01 }} on {{ sa_23_odp_02 }} supporting mission essential services or functions to increase the trustworthiness in those systems or components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sa_23_odp_01 }} is employed on {{ sa_23_odp_02 }} supporting essential services or functions to increase the trustworthiness in those systems or components.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-sa-24","slug":"sa-24","display_id":"SA-24","name":"Design For Cyber Resiliency","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Design organizational systems, system components, or system services to achieve cyber resiliency by:\n"},{"id":"a.1","statement":"Defining the following cyber resiliency goals: {{ sa_24_odp_01 }}."},{"id":"a.2","statement":"Defining the following cyber resiliency objectives: {{ sa_24_odp_02 }}."},{"id":"a.3","statement":"Defining the following cyber resiliency techniques: {{ sa_24_odp_03 }}."},{"id":"a.4","statement":"Defining the following cyber resiliency implementation approaches: {{ sa_24_odp_04 }}.\n"},{"id":"a.5","statement":"Defining the following cyber resiliency design principles: {{ sa_24_odp_05 }}."},{"id":"b","statement":"Implement the selected cyber resiliency goals, objectives, techniques, implementation approaches, and design principles as part of an organizational risk management process or systems security engineering process.\n"}],"objectives_count":15,"objectives_preview":[{"id":"a.1","statement":"organizational systems, system components, or system services achieve cyber resiliency through {{ sa_24_odp_01 }};\n"},{"id":"a.2","statement":"organizational systems, system components, or system services achieve cyber resiliency through {{ sa_24_odp_02 }};\n"},{"id":"a.3","statement":"organizational systems, system components, or system services achieve cyber resiliency through {{ sa_24_odp_03 }};\n"},{"id":"a.4","statement":"organizational systems, system components, or system services achieve cyber resiliency through {{ sa_24_odp_04 }};\n"},{"id":"a-5","statement":"organizational systems, system components, or system services achieve cyber resiliency through {{ sa_24_odp_05 }};\n"},{"id":"b-1","statement":"selected cyber resiliency goals are implemented as part of an organizational risk management process of systems security engineering process;\n"}],"params_count":5,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sa-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-1","slug":"sc-1","display_id":"SC-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ sc_1_prm_1 }}:"},{"id":"a.1","statement":"{{ sc_01_odp_03 }} system and communications protection policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls;\n"},{"id":"b","statement":"Designate an {{ sc_01_odp_04 }} to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and\n"},{"id":"c","statement":"Review and update the current system and communications protection:"},{"id":"c.1","statement":"Policy {{ sc_01_odp_05 }} and following {{ sc_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ sc_01_odp_07 }} and following {{ sc_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a system and communications protection policy is developed and documented;"},{"id":"a-2","statement":"the system and communications protection policy is disseminated to {{ sc_01_odp_01 }};\n"},{"id":"a-3","statement":"system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls are developed and documented;\n"},{"id":"a-4","statement":"the system and communications protection procedures are disseminated to {{ sc_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ sc_01_odp_03 }} system and communications protection policy addresses purpose;\n"},{"id":"a.1.a-2","statement":"the {{ sc_01_odp_03 }} system and communications protection policy addresses scope;\n"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-2","slug":"sc-2","display_id":"SC-2","name":"Separation of System and User Functionality","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Separate user functionality, including user interface services, from system management functionality.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-02","statement":"user functionality, including user interface services, is separated from system management functionality.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-2-1","slug":"sc-2-1","display_id":"SC-2(1)","name":"Interfaces for Non-privileged Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent the presentation of system management functionality at interfaces to non-privileged users.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-02(01)","statement":"the presentation of system management functionality is prevented at interfaces to non-privileged users.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-2-2","slug":"sc-2-2","display_id":"SC-2(2)","name":"Disassociability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Store state information from applications and software separately.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-02(02)","statement":"state information is stored separately from applications and software."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-3","slug":"sc-3","display_id":"SC-3","name":"Security Function Isolation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Isolate security functions from nonsecurity functions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-03","statement":"security functions are isolated from non-security functions."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-3-1","slug":"sc-3-1","display_id":"SC-3(1)","name":"Hardware Separation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ hardware separation mechanisms to implement security function isolation.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-03(01)","statement":"hardware separation mechanisms are employed to implement security function isolation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-3-2","slug":"sc-3-2","display_id":"SC-3(2)","name":"Access and Flow Control Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Isolate security functions enforcing access and information flow control from nonsecurity functions and from other security functions.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"sc-03(02).sc-03(02)[01]","statement":"security functions enforcing access control are isolated from non-security functions;\n"},{"id":"sc-03(02).sc-03(02)[02]","statement":"security functions enforcing access control are isolated from other security functions;\n"},{"id":"sc-03(02).sc-03(02)[03]","statement":"security functions enforcing information flow control are isolated from non-security functions;\n"},{"id":"sc-03(02).sc-03(02)[04]","statement":"security functions enforcing information flow control are isolated from other security functions.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-3-3","slug":"sc-3-3","display_id":"SC-3(3)","name":"Minimize Nonsecurity Functionality","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Minimize the number of nonsecurity functions included within the isolation boundary containing security functions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-03(03)","statement":"the number of non-security functions included within the isolation boundary containing security functions is minimized.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-3-4","slug":"sc-3-4","display_id":"SC-3(4)","name":"Module Coupling and Cohesiveness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-03(04).sc-03(04)[01]","statement":"security functions are implemented as largely independent modules that maximize internal cohesiveness within modules;\n"},{"id":"sc-03(04).sc-03(04)[02]","statement":"security functions are implemented as largely independent modules that minimize coupling between modules.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-3-5","slug":"sc-3-5","display_id":"SC-3(5)","name":"Layered Structures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-03(05)","statement":"security functions are implemented as a layered structure, minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-4","slug":"sc-4","display_id":"SC-4","name":"Information in Shared System Resources","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Prevent unauthorized and unintended information transfer via shared system resources.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"[01]","statement":"unauthorized information transfer via shared system resources is prevented;"},{"id":"[02]","statement":"unintended information transfer via shared system resources is prevented."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-4-1","slug":"sc-4-1","display_id":"SC-4(1)","name":"Security Levels","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-4-1_to_nist-sp-800-53-r5-sc-4","source_ref":"requirement--nist-sp-800-53-r5-sc-4-1","target_ref":"requirement--nist-sp-800-53-r5-sc-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-4-2","slug":"sc-4-2","display_id":"SC-4(2)","name":"Multilevel or Periods Processing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent unauthorized information transfer via shared resources in accordance with {{ sc_04_02_odp }} when system processing explicitly switches between different information classification levels or security categories.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-04(02)","statement":"unauthorized information transfer via shared resources is prevented in accordance with {{ sc_04_02_odp }} when system processing explicitly switches between different information classification levels or security categories.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-5","slug":"sc-5","display_id":"SC-5","name":"Denial-of-service Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"{{ sc_05_odp_02 }} the effects of the following types of denial-of-service events: {{ sc_05_odp_01 }} ; and\n"},{"id":"b","statement":"Employ the following controls to achieve the denial-of-service objective: {{ sc_05_odp_03 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the effects of {{ sc_05_odp_01 }} are {{ sc_05_odp_02 }};"},{"id":"b","statement":"{{ sc_05_odp_03 }} are employed to achieve the denial-of-service protection objective.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-09-to-800-53-sc-5","source_ref":"control--ogrl-bc-09","target_ref":"requirement--nist-sp-800-53-r5-sc-5","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sc_05_odp_01":"dos_event_types","sc_05_odp_03":"dos_protections"},"summary":"Layered denial-of-service mitigations for defined attack types satisfy SC-5."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-5-1","slug":"sc-5-1","display_id":"SC-5(1)","name":"Restrict Ability to Attack Other Systems","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the ability of individuals to launch the following denial-of-service attacks against other systems: {{ sc_05_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-05(01)","statement":"the ability of individuals to launch {{ sc_05_01_odp }} against other systems is restricted.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-5-2","slug":"sc-5-2","display_id":"SC-5(2)","name":"Capacity, Bandwidth, and Redundancy","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manage capacity, bandwidth, or other redundancy to limit the effects of information flooding denial-of-service attacks.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-05(02)","statement":"capacity, bandwidth, or other redundancies to limit the effects of information flooding denial-of-service attacks are managed.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-5-3","slug":"sc-5-3","display_id":"SC-5(3)","name":"Detection and Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ the following monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system: {{ sc_05_03_odp_01 }} ; and\n"},{"id":"b","statement":"Monitor the following system resources to determine if sufficient resources exist to prevent effective denial-of-service attacks: {{ sc_05_03_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ sc_05_03_odp_01 }} are employed to detect indicators of denial-of-service attacks against or launched from the system;\n"},{"id":"b","statement":"{{ sc_05_03_odp_02 }} are monitored to determine if sufficient resources exist to prevent effective denial-of-service attacks.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-5-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-6","slug":"sc-6","display_id":"SC-6","name":"Resource Availability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect the availability of resources by allocating {{ sc_06_odp_01 }} by {{ sc_06_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-06","statement":"the availability of resources is protected by allocating {{ sc_06_odp_01 }} by {{ sc_06_odp_02 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7","slug":"sc-7","display_id":"SC-7","name":"Boundary Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system;\n"},{"id":"b","statement":"Implement subnetworks for publicly accessible system components that are {{ sc_07_odp }} separated from internal organizational networks; and\n"},{"id":"c","statement":"Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"communications at external managed interfaces to the system are monitored;"},{"id":"a-2","statement":"communications at external managed interfaces to the system are controlled;"},{"id":"a-3","statement":"communications at key internal managed interfaces within the system are monitored;\n"},{"id":"a-4","statement":"communications at key internal managed interfaces within the system are controlled;\n"},{"id":"b","statement":"subnetworks for publicly accessible system components are {{ sc_07_odp }} separated from internal organizational networks;\n"},{"id":"c","statement":"external networks or systems are only connected to through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-1","slug":"sc-7-1","display_id":"SC-7(1)","name":"Physically Separated Subnetworks","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-7-1_to_nist-sp-800-53-r5-sc-7","source_ref":"requirement--nist-sp-800-53-r5-sc-7-1","target_ref":"requirement--nist-sp-800-53-r5-sc-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-2","slug":"sc-7-2","display_id":"SC-7(2)","name":"Public Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-7-2_to_nist-sp-800-53-r5-sc-7","source_ref":"requirement--nist-sp-800-53-r5-sc-7-2","target_ref":"requirement--nist-sp-800-53-r5-sc-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-3","slug":"sc-7-3","display_id":"SC-7(3)","name":"Access Points","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit the number of external network connections to the system.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(03)","statement":"the number of external network connections to the system is limited."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-4","slug":"sc-7-4","display_id":"SC-7(4)","name":"External Telecommunications Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement a managed interface for each external telecommunication service;"},{"id":"b","statement":"Establish a traffic flow policy for each managed interface;"},{"id":"c","statement":"Protect the confidentiality and integrity of the information being transmitted across each interface;\n"},{"id":"d","statement":"Document each exception to the traffic flow policy with a supporting mission or business need and duration of that need;\n"},{"id":"e","statement":"Review exceptions to the traffic flow policy {{ sc_07_04_odp }} and remove exceptions that are no longer supported by an explicit mission or business need;\n"},{"id":"f","statement":"Prevent unauthorized exchange of control plane traffic with external networks;"},{"id":"g","statement":"Publish information to enable remote networks to detect unauthorized control plane traffic from internal networks; and\n"},{"id":"h","statement":"Filter unauthorized control plane traffic from external networks."}],"objectives_count":10,"objectives_preview":[{"id":"a","statement":"a managed interface is implemented for each external telecommunication service;"},{"id":"b","statement":"a traffic flow policy is established for each managed interface;"},{"id":"c-1","statement":"the confidentiality of the information being transmitted across each interface is protected;\n"},{"id":"c-2","statement":"the integrity of the information being transmitted across each interface is protected;\n"},{"id":"d","statement":"each exception to the traffic flow policy is documented with a supporting mission or business need and duration of that need;\n"},{"id":"e-1","statement":"exceptions to the traffic flow policy are reviewed {{ sc_07_04_odp }};"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-5","slug":"sc-7-5","display_id":"SC-7(5)","name":"Deny by Default — Allow by Exception","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Deny network communications traffic by default and allow network communications traffic by exception {{ sc_07_05_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-07(05).sc-07(05)[01]","statement":"network communications traffic is denied by default {{ sc_07_05_odp_01 }};"},{"id":"sc-07(05).sc-07(05)[02]","statement":"network communications traffic is allowed by exception {{ sc_07_05_odp_01 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-6","slug":"sc-7-6","display_id":"SC-7(6)","name":"Response to Recognized Failures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-7-6_to_nist-sp-800-53-r5-sc-7-18","source_ref":"requirement--nist-sp-800-53-r5-sc-7-6","target_ref":"requirement--nist-sp-800-53-r5-sc-7-18","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-7","slug":"sc-7-7","display_id":"SC-7(7)","name":"Split Tunneling for Remote Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent split tunneling for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using {{ sc_07_07_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(07)","statement":"split tunneling is prevented for remote devices connecting to organizational systems unless the split tunnel is securely provisioned using {{ sc_07_07_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-8","slug":"sc-7-8","display_id":"SC-7(8)","name":"Route Traffic to Authenticated Proxy Servers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Route {{ sc_07_08_odp_01 }} to {{ sc_07_08_odp_02 }} through authenticated proxy servers at managed interfaces.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(08)","statement":"{{ sc_07_08_odp_01 }} is routed to {{ sc_07_08_odp_02 }} through authenticated proxy servers at managed interfaces.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-9","slug":"sc-7-9","display_id":"SC-7(9)","name":"Restrict Threatening Outgoing Communications Traffic","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Detect and deny outgoing communications traffic posing a threat to external systems; and\n"},{"id":"b","statement":"Audit the identity of internal users associated with denied communications."}],"objectives_count":3,"objectives_preview":[{"id":"a-1","statement":"outgoing communications traffic posing a threat to external systems is detected;"},{"id":"a-2","statement":"outgoing communications traffic posing a threat to external systems is denied;"},{"id":"b","statement":"the identity of internal users associated with denied communications is audited."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-10","slug":"sc-7-10","display_id":"SC-7(10)","name":"Prevent Exfiltration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prevent the exfiltration of information; and"},{"id":"b","statement":"Conduct exfiltration tests {{ sc_07_10_odp }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the exfiltration of information is prevented;"},{"id":"b","statement":"exfiltration tests are conducted {{ sc_07_10_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-11","slug":"sc-7-11","display_id":"SC-7(11)","name":"Restrict Incoming Communications Traffic","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Only allow incoming communications from {{ sc_07_11_odp_01 }} to be routed to {{ sc_07_11_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(11)","statement":"only incoming communications from {{ sc_07_11_odp_01 }} are allowed to be routed to {{ sc_07_11_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-12","slug":"sc-7-12","display_id":"SC-7(12)","name":"Host-based Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ sc_07_12_odp_01 }} at {{ sc_07_12_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(12)","statement":"{{ sc_07_12_odp_01 }} are implemented at {{ sc_07_12_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-13","slug":"sc-7-13","display_id":"SC-7(13)","name":"Isolation of Security Tools, Mechanisms, and Support Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Isolate {{ sc_07_13_odp }} from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(13)","statement":"{{ sc_07_13_odp }} are isolated from other internal system components by implementing physically separate subnetworks with managed interfaces to other components of the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-14","slug":"sc-7-14","display_id":"SC-7(14)","name":"Protect Against Unauthorized Physical Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect against unauthorized physical connections at {{ sc_07_14_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(14)","statement":"{{ sc_07_14_odp }} are protected against unauthorized physical connections."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-15","slug":"sc-7-15","display_id":"SC-7(15)","name":"Networked Privileged Accesses","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Route networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-07(15).sc-07(15)[01]","statement":"networked, privileged accesses are routed through a dedicated, managed interface for purposes of access control;\n"},{"id":"sc-07(15).sc-07(15)[02]","statement":"networked, privileged accesses are routed through a dedicated, managed interface for purposes of auditing.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-16","slug":"sc-7-16","display_id":"SC-7(16)","name":"Prevent Discovery of System Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent the discovery of specific system components that represent a managed interface.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(16)","statement":"the discovery of specific system components that represent a managed interface is prevented.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-17","slug":"sc-7-17","display_id":"SC-7(17)","name":"Automated Enforcement of Protocol Formats","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Enforce adherence to protocol formats.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(17)","statement":"adherence to protocol formats is enforced."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-18","slug":"sc-7-18","display_id":"SC-7(18)","name":"Fail Secure","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(18)","statement":"systems are prevented from entering unsecure states in the event of an operational failure of a boundary protection device.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-19","slug":"sc-7-19","display_id":"SC-7(19)","name":"Block Communication from Non-organizationally Configured Hosts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Block inbound and outbound communications traffic between {{ sc_07_19_odp }} that are independently configured by end users and external service providers.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-07(19).sc-07(19)[01]","statement":"inbound communications traffic is blocked between {{ sc_07_19_odp }} that are independently configured by end users and external service providers;\n"},{"id":"sc-07(19).sc-07(19)[02]","statement":"outbound communications traffic is blocked between {{ sc_07_19_odp }} that are independently configured by end users and external service providers.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-20","slug":"sc-7-20","display_id":"SC-7(20)","name":"Dynamic Isolation and Segregation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide the capability to dynamically isolate {{ sc_07_20_odp }} from other system components.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(20)","statement":"the capability to dynamically isolate {{ sc_07_20_odp }} from other system components is provided.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-21","slug":"sc-7-21","display_id":"SC-7(21)","name":"Isolation of System Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ boundary protection mechanisms to isolate {{ sc_07_21_odp_01 }} supporting {{ sc_07_21_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(21)","statement":"boundary protection mechanisms are employed to isolate {{ sc_07_21_odp_01 }} supporting {{ sc_07_21_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-22","slug":"sc-7-22","display_id":"SC-7(22)","name":"Separate Subnets for Connecting to Different Security Domains","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement separate network addresses to connect to systems in different security domains.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(22)","statement":"separate network addresses are implemented to connect to systems in different security domains.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-23","slug":"sc-7-23","display_id":"SC-7(23)","name":"Disable Sender Feedback on Protocol Validation Failure","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Disable feedback to senders on protocol format validation failure.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(23)","statement":"feedback to senders is disabled on protocol format validation failure."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-24","slug":"sc-7-24","display_id":"SC-7(24)","name":"Personally Identifiable Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"For systems that process personally identifiable information:","citation":null,"parts":[{"id":"a","statement":"Apply the following processing rules to data elements of personally identifiable information: {{ sc_07_24_odp }};\n"},{"id":"b","statement":"Monitor for permitted processing at the external interfaces to the system and at key internal boundaries within the system;\n"},{"id":"c","statement":"Document each processing exception; and"},{"id":"d","statement":"Review and remove exceptions that are no longer supported."}],"objectives_count":6,"objectives_preview":[{"id":"a","statement":"{{ sc_07_24_odp }} are applied to data elements of personally identifiable information on systems that process personally identifiable information;\n"},{"id":"b-1","statement":"permitted processing is monitored at the external interfaces to the systems that process personally identifiable information;\n"},{"id":"b-2","statement":"permitted processing is monitored at key internal boundaries within the systems that process personally identifiable information;\n"},{"id":"c","statement":"each processing exception is documented for systems that process personally identifiable information;\n"},{"id":"d-1","statement":"exceptions for systems that process personally identifiable information are reviewed;\n"},{"id":"d-2","statement":"exceptions for systems that process personally identifiable information that are no longer supported are removed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-25","slug":"sc-7-25","display_id":"SC-7(25)","name":"Unclassified National Security System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the direct connection of {{ sc_07_25_odp_01 }} to an external network without the use of {{ sc_07_25_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(25)","statement":"the direct connection of {{ sc_07_25_odp_01 }} to an external network without the use of {{ sc_07_25_odp_02 }} is prohibited.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-26","slug":"sc-7-26","display_id":"SC-7(26)","name":"Classified National Security System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the direct connection of a classified national security system to an external network without the use of {{ sc_07_26_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(26)","statement":"the direct connection of classified national security system to an external network without the use of a {{ sc_07_26_odp }} is prohibited.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-26.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-27","slug":"sc-7-27","display_id":"SC-7(27)","name":"Unclassified Non-national Security System Connections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the direct connection of {{ sc_07_27_odp_01 }} to an external network without the use of {{ sc_07_27_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(27)","statement":"the direct connection of {{ sc_07_27_odp_01 }} to an external network without the use of a {{ sc_07_27_odp_02 }} is prohibited.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-27.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-28","slug":"sc-7-28","display_id":"SC-7(28)","name":"Connections to Public Networks","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit the direct connection of {{ sc_07_28_odp }} to a public network.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(28)","statement":"the direct connection of the {{ sc_07_28_odp }} to a public network is prohibited.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-28.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-7-29","slug":"sc-7-29","display_id":"SC-7(29)","name":"Separate Subnets to Isolate Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ sc_07_29_odp_01 }} separate subnetworks to isolate the following critical system components and functions: {{ sc_07_29_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-07(29)","statement":"subnetworks are separated {{ sc_07_29_odp_01 }} to isolate {{ sc_07_29_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-7-29.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-8","slug":"sc-8","display_id":"SC-8","name":"Transmission Confidentiality and Integrity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect the {{ sc_08_odp }} of transmitted information.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-08","statement":"the {{ sc_08_odp }} of transmitted information is/are protected."}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-01-to-800-53-sc-8","source_ref":"control--ogrl-cr-01","target_ref":"requirement--nist-sp-800-53-r5-sc-8","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Enforcing modern TLS protects confidentiality and integrity of transmitted information per SC-8.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-8-1","slug":"sc-8-1","display_id":"SC-8(1)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to {{ sc_08_01_odp }} during transmission.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-08(01)","statement":"cryptographic mechanisms are implemented to {{ sc_08_01_odp }} during transmission.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-8-2","slug":"sc-8-2","display_id":"SC-8(2)","name":"Pre- and Post-transmission Handling","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain the {{ sc_08_02_odp }} of information during preparation for transmission and during reception.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-08(02).sc-08(02)[01]","statement":"information {{ sc_08_02_odp }} is/are maintained during preparation for transmission;\n"},{"id":"sc-08(02).sc-08(02)[02]","statement":"information {{ sc_08_02_odp }} is/are maintained during reception."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-8-3","slug":"sc-8-3","display_id":"SC-8(3)","name":"Cryptographic Protection for Message Externals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to protect message externals unless otherwise protected by {{ sc_08_03_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-08(03)","statement":"cryptographic mechanisms are implemented to protect message externals unless otherwise protected by {{ sc_08_03_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-8-4","slug":"sc-8-4","display_id":"SC-8(4)","name":"Conceal or Randomize Communications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by {{ sc_08_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-08(04)","statement":"cryptographic mechanisms are implemented to conceal or randomize communication patterns unless otherwise protected by {{ sc_08_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-8-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-8-5","slug":"sc-8-5","display_id":"SC-8(5)","name":"Protected Distribution System","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ sc_08_05_odp_01 }} to {{ sc_08_05_odp_02 }} during transmission.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-08(05)","statement":"the {{ sc_08_05_odp_01 }} is implemented to {{ sc_08_05_odp_02 }} during transmission.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-8-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-9","slug":"sc-9","display_id":"SC-9","name":"Transmission Confidentiality","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-9_to_nist-sp-800-53-r5-sc-8","source_ref":"requirement--nist-sp-800-53-r5-sc-9","target_ref":"requirement--nist-sp-800-53-r5-sc-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-10","slug":"sc-10","display_id":"SC-10","name":"Network Disconnect","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Terminate the network connection associated with a communications session at the end of the session or after {{ sc_10_odp }} of inactivity.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the network connection associated with a communication session is terminated at the end of the session or after {{ sc_10_odp }} of inactivity.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-11","slug":"sc-11","display_id":"SC-11","name":"Trusted Path","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide a {{ sc_11_odp_01 }} isolated trusted communications path for communications between the user and the trusted components of the system; and\n"},{"id":"b","statement":"Permit users to invoke the trusted communications path for communications between the user and the following security functions of the system, including at a minimum, authentication and re-authentication: {{ sc_11_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a {{ sc_11_odp_01 }} isolated trusted communication path is provided for communications between the user and the trusted components of the system;\n"},{"id":"b","statement":"users are permitted to invoke the trusted communication path for communications between the user and the {{ sc_11_odp_02 }} of the system, including authentication and re-authentication, at a minimum.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-11-1","slug":"sc-11-1","display_id":"SC-11(1)","name":"Irrefutable Communications Path","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide a trusted communications path that is irrefutably distinguishable from other communications paths; and\n"},{"id":"b","statement":"Initiate the trusted communications path for communications between the {{ sc_11_01_odp }} of the system and the user.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a trusted communication path that is irrefutably distinguishable from other communication paths is provided;\n"},{"id":"b","statement":"the trusted communication path for communications between the {{ sc_11_01_odp }} of the system and the user is initiated.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12","slug":"sc-12","display_id":"SC-12","name":"Cryptographic Key Establishment and Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: {{ sc_12_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"cryptographic keys are established when cryptography is employed within the system in accordance with {{ sc_12_odp }};\n"},{"id":"_obj-2","statement":"cryptographic keys are managed when cryptography is employed within the system in accordance with {{ sc_12_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-02-to-800-53-sc-12","source_ref":"control--ogrl-cr-02","target_ref":"requirement--nist-sp-800-53-r5-sc-12","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Centralized key generation, storage, access restriction, rotation, and logging establish and manage keys as SC-12 requires.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12-1","slug":"sc-12-1","display_id":"SC-12(1)","name":"Availability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain availability of information in the event of the loss of cryptographic keys by users.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-12(01)","statement":"information availability is maintained in the event of the loss of cryptographic keys by users.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12-2","slug":"sc-12-2","display_id":"SC-12(2)","name":"Symmetric Keys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Produce, control, and distribute symmetric cryptographic keys using {{ sc_12_02_odp }} key management technology and processes.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"sc-12(02).sc-12(02)[01]","statement":"symmetric cryptographic keys are produced using {{ sc_12_02_odp }} key management technology and processes;\n"},{"id":"sc-12(02).sc-12(02)[02]","statement":"symmetric cryptographic keys are controlled using {{ sc_12_02_odp }} key management technology and processes;\n"},{"id":"sc-12(02).sc-12(02)[03]","statement":"symmetric cryptographic keys are distributed using {{ sc_12_02_odp }} key management technology and processes.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12-3","slug":"sc-12-3","display_id":"SC-12(3)","name":"Asymmetric Keys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Produce, control, and distribute asymmetric cryptographic keys using {{ sc_12_03_odp }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"sc-12(03).sc-12(03)[01]","statement":"asymmetric cryptographic keys are produced using {{ sc_12_03_odp }};"},{"id":"sc-12(03).sc-12(03)[02]","statement":"asymmetric cryptographic keys are controlled using {{ sc_12_03_odp }};"},{"id":"sc-12(03).sc-12(03)[03]","statement":"asymmetric cryptographic keys are distributed using {{ sc_12_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12-4","slug":"sc-12-4","display_id":"SC-12(4)","name":"PKI Certificates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-12-4_to_nist-sp-800-53-r5-sc-12-3","source_ref":"requirement--nist-sp-800-53-r5-sc-12-4","target_ref":"requirement--nist-sp-800-53-r5-sc-12-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12-5","slug":"sc-12-5","display_id":"SC-12(5)","name":"PKI Certificates / Hardware Tokens","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-12-5_to_nist-sp-800-53-r5-sc-12-3","source_ref":"requirement--nist-sp-800-53-r5-sc-12-5","target_ref":"requirement--nist-sp-800-53-r5-sc-12-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-12-6","slug":"sc-12-6","display_id":"SC-12(6)","name":"Physical Control of Keys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain physical control of cryptographic keys when stored information is encrypted by external service providers.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-12(06)","statement":"physical control of cryptographic keys is maintained when stored information is encrypted by external service providers.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-12-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-13","slug":"sc-13","display_id":"SC-13","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine the {{ sc_13_odp_01 }} ; and"},{"id":"b","statement":"Implement the following types of cryptography required for each specified cryptographic use: {{ sc_13_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ sc_13_odp_01 }} are identified;"},{"id":"b","statement":"{{ sc_13_odp_02 }} for each specified cryptographic use (defined in SC-13_ODP[01]) are implemented.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-13-1","slug":"sc-13-1","display_id":"SC-13(1)","name":"FIPS-validated Cryptography","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-13-1_to_nist-sp-800-53-r5-sc-13","source_ref":"requirement--nist-sp-800-53-r5-sc-13-1","target_ref":"requirement--nist-sp-800-53-r5-sc-13","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-13-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-13-2","slug":"sc-13-2","display_id":"SC-13(2)","name":"NSA-approved Cryptography","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-13-2_to_nist-sp-800-53-r5-sc-13","source_ref":"requirement--nist-sp-800-53-r5-sc-13-2","target_ref":"requirement--nist-sp-800-53-r5-sc-13","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-13-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-13-3","slug":"sc-13-3","display_id":"SC-13(3)","name":"Individuals Without Formal Access Approvals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-13-3_to_nist-sp-800-53-r5-sc-13","source_ref":"requirement--nist-sp-800-53-r5-sc-13-3","target_ref":"requirement--nist-sp-800-53-r5-sc-13","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-13-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-13-4","slug":"sc-13-4","display_id":"SC-13(4)","name":"Digital Signatures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-13-4_to_nist-sp-800-53-r5-sc-13","source_ref":"requirement--nist-sp-800-53-r5-sc-13-4","target_ref":"requirement--nist-sp-800-53-r5-sc-13","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-13-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-14","slug":"sc-14","display_id":"SC-14","name":"Public Access Protections","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-ac-2","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-ac-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-ac-3","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-ac-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-ac-5","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-ac-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-ac-6","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-ac-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-si-10","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-si-10","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-si-3","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-si-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-si-4","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-si-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-si-5","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-si-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-sc-14_to_nist-sp-800-53-r5-si-7","source_ref":"requirement--nist-sp-800-53-r5-sc-14","target_ref":"requirement--nist-sp-800-53-r5-si-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-15","slug":"sc-15","display_id":"SC-15","name":"Collaborative Computing Devices and Applications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prohibit remote activation of collaborative computing devices and applications with the following exceptions: {{ sc_15_odp }} ; and\n"},{"id":"b","statement":"Provide an explicit indication of use to users physically present at the devices.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"remote activation of collaborative computing devices and applications is prohibited except {{ sc_15_odp }};\n"},{"id":"b","statement":"an explicit indication of use is provided to users physically present at the devices.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-15-1","slug":"sc-15-1","display_id":"SC-15(1)","name":"Physical or Logical Disconnect","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ sc_15_01_odp }} disconnect of collaborative computing devices in a manner that supports ease of use.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-15(01)","statement":"the {{ sc_15_01_odp }} disconnect of collaborative computing devices is/are provided in a manner that supports ease of use.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-15-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-15-2","slug":"sc-15-2","display_id":"SC-15(2)","name":"Blocking Inbound and Outbound Communications Traffic","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-15-2_to_nist-sp-800-53-r5-sc-7","source_ref":"requirement--nist-sp-800-53-r5-sc-15-2","target_ref":"requirement--nist-sp-800-53-r5-sc-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-15-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-15-3","slug":"sc-15-3","display_id":"SC-15(3)","name":"Disabling and Removal in Secure Work Areas","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Disable or remove collaborative computing devices and applications from {{ sc_15_03_odp_01 }} in {{ sc_15_03_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-15(03)","statement":"collaborative computing devices and applications are disabled or removed from {{ sc_15_03_odp_01 }} in {{ sc_15_03_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-15-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-15-4","slug":"sc-15-4","display_id":"SC-15(4)","name":"Explicitly Indicate Current Participants","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide an explicit indication of current participants in {{ sc_15_04_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-15(04)","statement":"an explicit indication of current participants in {{ sc_15_04_odp }} is provided.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-15-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-16","slug":"sc-16","display_id":"SC-16","name":"Transmission of Security and Privacy Attributes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Associate {{ sc_16_prm_1 }} with information exchanged between systems and between system components.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"_obj-1","statement":"{{ sc_16_odp_01 }} are associated with information exchanged between systems;"},{"id":"_obj-2","statement":"{{ sc_16_odp_01 }} are associated with information exchanged between system components;\n"},{"id":"_obj-3","statement":"{{ sc_16_odp_02 }} are associated with information exchanged between systems;"},{"id":"_obj-4","statement":"{{ sc_16_odp_02 }} are associated with information exchanged between system components.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-16-1","slug":"sc-16-1","display_id":"SC-16(1)","name":"Integrity Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify the integrity of transmitted security and privacy attributes.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-16(01).sc-16(01)[01]","statement":"the integrity of transmitted security attributes is verified;"},{"id":"sc-16(01).sc-16(01)[02]","statement":"the integrity of transmitted privacy attributes is verified."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-16-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-16-2","slug":"sc-16-2","display_id":"SC-16(2)","name":"Anti-spoofing Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement anti-spoofing mechanisms to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-16(02)","statement":"anti-spoofing mechanisms are implemented to prevent adversaries from falsifying the security attributes indicating the successful application of the security process.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-16-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-16-3","slug":"sc-16-3","display_id":"SC-16(3)","name":"Cryptographic Binding","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ sc_16_03_odp }} to bind security and privacy attributes to transmitted information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-16(03)","statement":"{{ sc_16_03_odp }} are implemented to bind security and privacy attributes to transmitted information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-16-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-17","slug":"sc-17","display_id":"SC-17","name":"Public Key Infrastructure Certificates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Issue public key certificates under an {{ sc_17_odp }} or obtain public key certificates from an approved service provider; and\n"},{"id":"b","statement":"Include only approved trust anchors in trust stores or certificate stores managed by the organization.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"public key certificates are issued under {{ sc_17_odp }} , or public key certificates are obtained from an approved service provider;\n"},{"id":"b","statement":"only approved trust anchors are included in trust stores or certificate stores managed by the organization.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-18","slug":"sc-18","display_id":"SC-18","name":"Mobile Code","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Define acceptable and unacceptable mobile code and mobile code technologies; and"},{"id":"b","statement":"Authorize, monitor, and control the use of mobile code within the system."}],"objectives_count":7,"objectives_preview":[{"id":"a-1","statement":"acceptable mobile code is defined;"},{"id":"a-2","statement":"unacceptable mobile code is defined;"},{"id":"a-3","statement":"acceptable mobile code technologies are defined;"},{"id":"a-4","statement":"unacceptable mobile code technologies are defined;"},{"id":"b-1","statement":"the use of mobile code is authorized within the system;"},{"id":"b-2","statement":"the use of mobile code is monitored within the system;"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-18-1","slug":"sc-18-1","display_id":"SC-18(1)","name":"Identify Unacceptable Code and Take Corrective Actions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Identify {{ sc_18_01_odp_01 }} and take {{ sc_18_01_odp_02 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-18(01).sc-18(01)[01]","statement":"{{ sc_18_01_odp_01 }} is identified;"},{"id":"sc-18(01).sc-18(01)[02]","statement":"{{ sc_18_01_odp_02 }} are taken if unacceptable mobile code is identified."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-18-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-18-2","slug":"sc-18-2","display_id":"SC-18(2)","name":"Acquisition, Development, and Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that the acquisition, development, and use of mobile code to be deployed in the system meets {{ sc_18_02_odp }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"sc-18(02).sc-18(02)[01]","statement":"the acquisition of mobile code to be deployed in the system meets {{ sc_18_02_odp }};\n"},{"id":"sc-18(02).sc-18(02)[02]","statement":"the development of mobile code to be deployed in the system meets {{ sc_18_02_odp }};\n"},{"id":"sc-18(02).sc-18(02)[03]","statement":"the use of mobile code to be deployed in the system meets {{ sc_18_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-18-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-18-3","slug":"sc-18-3","display_id":"SC-18(3)","name":"Prevent Downloading and Execution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent the download and execution of {{ sc_18_03_odp }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-18(03).sc-18(03)[01]","statement":"the download of {{ sc_18_03_odp }} is prevented;"},{"id":"sc-18(03).sc-18(03)[02]","statement":"the execution of {{ sc_18_03_odp }} is prevented."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-18-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-18-4","slug":"sc-18-4","display_id":"SC-18(4)","name":"Prevent Automatic Execution","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent the automatic execution of mobile code in {{ sc_18_04_odp_01 }} and enforce {{ sc_18_04_odp_02 }} prior to executing the code.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-18(04).sc-18(04)[01]","statement":"the automatic execution of mobile code in {{ sc_18_04_odp_01 }} is prevented;"},{"id":"sc-18(04).sc-18(04)[02]","statement":"{{ sc_18_04_odp_02 }} are enforced prior to executing mobile code."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-18-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-18-5","slug":"sc-18-5","display_id":"SC-18(5)","name":"Allow Execution Only in Confined Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Allow execution of permitted mobile code only in confined virtual machine environments.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-18(05)","statement":"execution of permitted mobile code is allowed only in confined virtual machine environments.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-18-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-19","slug":"sc-19","display_id":"SC-19","name":"Voice Over Internet Protocol","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":"Technology-specific; addressed as any other technology or protocol.","citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-20","slug":"sc-20","display_id":"SC-20","name":"Secure Name/Address Resolution Service (Authoritative Source)","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and\n"},{"id":"b","statement":"Provide the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;\n"},{"id":"a-2","statement":"integrity verification artifacts are provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;\n"},{"id":"b-1","statement":"the means to indicate the security status of child zones (and if the child supports secure resolution services) is provided when operating as part of a distributed, hierarchical namespace;\n"},{"id":"b-2","statement":"the means to enable verification of a chain of trust among parent and child domains when operating as part of a distributed, hierarchical namespace is provided.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-20-1","slug":"sc-20-1","display_id":"SC-20(1)","name":"Child Subspaces","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-20-1_to_nist-sp-800-53-r5-sc-20","source_ref":"requirement--nist-sp-800-53-r5-sc-20-1","target_ref":"requirement--nist-sp-800-53-r5-sc-20","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-20-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-20-2","slug":"sc-20-2","display_id":"SC-20(2)","name":"Data Origin and Integrity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide data origin and integrity protection artifacts for internal name/address resolution queries.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-20(02).sc-20(02)[01]","statement":"data origin artifacts are provided for internal name/address resolution queries;"},{"id":"sc-20(02).sc-20(02)[02]","statement":"integrity protection artifacts are provided for internal name/address resolution queries.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-20-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-21","slug":"sc-21","display_id":"SC-21","name":"Secure Name/Address Resolution Service (Recursive or Caching Resolver)","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"_obj-1","statement":"data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources;\n"},{"id":"_obj-2","statement":"data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources;\n"},{"id":"_obj-3","statement":"data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources;\n"},{"id":"_obj-4","statement":"data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-21-1","slug":"sc-21-1","display_id":"SC-21(1)","name":"Data Origin and Integrity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-21-1_to_nist-sp-800-53-r5-sc-21","source_ref":"requirement--nist-sp-800-53-r5-sc-21-1","target_ref":"requirement--nist-sp-800-53-r5-sc-21","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-21-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-22","slug":"sc-22","display_id":"SC-22","name":"Architecture and Provisioning for Name/Address Resolution Service","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"_obj-1","statement":"the systems that collectively provide name/address resolution services for an organization are fault-tolerant;\n"},{"id":"_obj-2","statement":"the systems that collectively provide name/address resolution services for an organization implement internal role separation;\n"},{"id":"_obj-3","statement":"the systems that collectively provide name/address resolution services for an organization implement external role separation.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-23","slug":"sc-23","display_id":"SC-23","name":"Session Authenticity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect the authenticity of communications sessions.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the authenticity of communication sessions is protected."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-23-1","slug":"sc-23-1","display_id":"SC-23(1)","name":"Invalidate Session Identifiers at Logout","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Invalidate session identifiers upon user logout or other session termination.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-23(01)","statement":"session identifiers are invalidated upon user logout or other session termination.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-23-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-23-2","slug":"sc-23-2","display_id":"SC-23(2)","name":"User-initiated Logouts and Message Displays","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-23-2_to_nist-sp-800-53-r5-ac-12-1","source_ref":"requirement--nist-sp-800-53-r5-sc-23-2","target_ref":"requirement--nist-sp-800-53-r5-ac-12-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-23-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-23-3","slug":"sc-23-3","display_id":"SC-23(3)","name":"Unique System-generated Session Identifiers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Generate a unique session identifier for each session with {{ sc_23_03_odp }} and recognize only session identifiers that are system-generated.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-23(03).sc-23(03)[01]","statement":"a unique session identifier is generated for each session with {{ sc_23_03_odp }};\n"},{"id":"sc-23(03).sc-23(03)[02]","statement":"only system-generated session identifiers are recognized."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-23-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-23-4","slug":"sc-23-4","display_id":"SC-23(4)","name":"Unique Session Identifiers with Randomization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-23-4_to_nist-sp-800-53-r5-sc-23-3","source_ref":"requirement--nist-sp-800-53-r5-sc-23-4","target_ref":"requirement--nist-sp-800-53-r5-sc-23-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-23-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-23-5","slug":"sc-23-5","display_id":"SC-23(5)","name":"Allowed Certificate Authorities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Only allow the use of {{ sc_23_05_odp }} for verification of the establishment of protected sessions.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-23(05)","statement":"only the use of {{ sc_23_05_odp }} for verification of the establishment of protected sessions is allowed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-23-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-24","slug":"sc-24","display_id":"SC-24","name":"Fail in Known State","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Fail to a {{ sc_24_odp_02 }} for the following failures on the indicated components while preserving {{ sc_24_odp_03 }} in failure: {{ sc_24_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_24_odp_01 }} fail to a {{ sc_24_odp_02 }} while preserving {{ sc_24_odp_03 }} in failure.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-25","slug":"sc-25","display_id":"SC-25","name":"Thin Nodes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ minimal functionality and information storage on the following system components: {{ sc_25_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"minimal functionality for {{ sc_25_odp }} is employed;"},{"id":"_obj-2","statement":"minimal information storage on {{ sc_25_odp }} is allocated."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-26","slug":"sc-26","display_id":"SC-26","name":"Decoys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"_obj-1","statement":"components within organizational systems specifically designed to be the target of malicious attacks are included to detect such attacks;\n"},{"id":"_obj-2","statement":"components within organizational systems specifically designed to be the target of malicious attacks are included to deflect such attacks;\n"},{"id":"_obj-3","statement":"components within organizational systems specifically designed to be the target of malicious attacks are included to analyze such attacks.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-26.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-26-1","slug":"sc-26-1","display_id":"SC-26(1)","name":"Detection of Malicious Code","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-26-1_to_nist-sp-800-53-r5-sc-35","source_ref":"requirement--nist-sp-800-53-r5-sc-26-1","target_ref":"requirement--nist-sp-800-53-r5-sc-35","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-26-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-27","slug":"sc-27","display_id":"SC-27","name":"Platform-independent Applications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Include within organizational systems the following platform independent applications: {{ sc_27_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_27_odp }} are included within organizational systems."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-27.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-28","slug":"sc-28","display_id":"SC-28","name":"Protection of Information at Rest","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect the {{ sc_28_odp_01 }} of the following information at rest: {{ sc_28_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the {{ sc_28_odp_01 }} of {{ sc_28_odp_02 }} is/are protected."}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-01-to-800-53-sc-28","source_ref":"control--ogrl-cr-01","target_ref":"requirement--nist-sp-800-53-r5-sc-28","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"sc_28_odp_02":"protected_data_scope"},"summary":"Enforcing AES-256 encryption at rest with managed keys protects stored data per SC-28.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-28.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-28-1","slug":"sc-28-1","display_id":"SC-28(1)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on {{ sc_28_01_odp_02 }}: {{ sc_28_01_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-28(01).sc-28(01)[01]","statement":"cryptographic mechanisms are implemented to prevent unauthorized disclosure of {{ sc_28_01_odp_01 }} at rest on {{ sc_28_01_odp_02 }};\n"},{"id":"sc-28(01).sc-28(01)[02]","statement":"cryptographic mechanisms are implemented to prevent unauthorized modification of {{ sc_28_01_odp_01 }} at rest on {{ sc_28_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-28-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-28-2","slug":"sc-28-2","display_id":"SC-28(2)","name":"Offline Storage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Remove the following information from online storage and store offline in a secure location: {{ sc_28_02_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-28(02).sc-28(02)[01]","statement":"{{ sc_28_02_odp }} is removed from online storage;"},{"id":"sc-28(02).sc-28(02)[02]","statement":"{{ sc_28_02_odp }} is stored offline in a secure location."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-28-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-28-3","slug":"sc-28-3","display_id":"SC-28(3)","name":"Cryptographic Keys","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide protected storage for cryptographic keys {{ sc_28_03_odp_01 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-28(03)","statement":"protected storage for cryptographic keys is provided using {{ sc_28_03_odp_01 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-28-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-29","slug":"sc-29","display_id":"SC-29","name":"Heterogeneity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ a diverse set of information technologies for the following system components in the implementation of the system: {{ sc_29_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a diverse set of information technologies is employed for {{ sc_29_odp }} in the implementation of the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-29.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-29-1","slug":"sc-29-1","display_id":"SC-29(1)","name":"Virtualization Techniques","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ virtualization techniques to support the deployment of a diversity of operating systems and applications that are changed {{ sc_29_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-29(01)","statement":"virtualization techniques are employed to support the deployment of a diverse range of operating systems and applications that are changed {{ sc_29_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-29-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-30","slug":"sc-30","display_id":"SC-30","name":"Concealment and Misdirection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ the following concealment and misdirection techniques for {{ sc_30_odp_02 }} at {{ sc_30_odp_03 }} to confuse and mislead adversaries: {{ sc_30_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_30_odp_01 }} are employed for {{ sc_30_odp_02 }} for {{ sc_30_odp_03 }} to confuse and mislead adversaries.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-30.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-30-1","slug":"sc-30-1","display_id":"SC-30(1)","name":"Virtualization Techniques","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-30-1_to_nist-sp-800-53-r5-sc-29-1","source_ref":"requirement--nist-sp-800-53-r5-sc-30-1","target_ref":"requirement--nist-sp-800-53-r5-sc-29-1","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-30-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-30-2","slug":"sc-30-2","display_id":"SC-30(2)","name":"Randomness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ sc_30_02_odp }} to introduce randomness into organizational operations and assets.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-30(02)","statement":"{{ sc_30_02_odp }} are employed to introduce randomness into organizational operations and assets.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-30-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-30-3","slug":"sc-30-3","display_id":"SC-30(3)","name":"Change Processing and Storage Locations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Change the location of {{ sc_30_03_odp_01 }} {{ sc_30_03_odp_02 }}].","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-30(03)","statement":"the location of {{ sc_30_03_odp_01 }} is changed {{ sc_30_03_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-30-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-30-4","slug":"sc-30-4","display_id":"SC-30(4)","name":"Misleading Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ realistic, but misleading information in {{ sc_30_04_odp }} about its security state or posture.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-30(04)","statement":"realistic but misleading information about the security state or posture of {{ sc_30_04_odp }} is employed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-30-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-30-5","slug":"sc-30-5","display_id":"SC-30(5)","name":"Concealment of System Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following techniques to hide or conceal {{ sc_30_05_odp_02 }}: {{ sc_30_05_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-30(05)","statement":"{{ sc_30_05_odp_01 }} are employed to hide or conceal {{ sc_30_05_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-30-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-31","slug":"sc-31","display_id":"SC-31","name":"Covert Channel Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Perform a covert channel analysis to identify those aspects of communications within the system that are potential avenues for covert {{ sc_31_odp }} channels; and\n"},{"id":"b","statement":"Estimate the maximum bandwidth of those channels."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a covert channel analysis is performed to identify those aspects of communications within the system that are potential avenues for covert {{ sc_31_odp }} channels;\n"},{"id":"b","statement":"the maximum bandwidth of those channels is estimated."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-31.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-31-1","slug":"sc-31-1","display_id":"SC-31(1)","name":"Test Covert Channels for Exploitability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test a subset of the identified covert channels to determine the channels that are exploitable.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-31(01)","statement":"a subset of the identified covert channels is tested to determine the channels that are exploitable.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-31-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-31-2","slug":"sc-31-2","display_id":"SC-31(2)","name":"Maximum Bandwidth","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Reduce the maximum bandwidth for identified covert {{ sc_31_02_odp_01 }} channels to {{ sc_31_02_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-31(02)","statement":"the maximum bandwidth for identified covert {{ sc_31_02_odp_01 }} channels is reduced to {{ sc_31_02_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-31-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-31-3","slug":"sc-31-3","display_id":"SC-31(3)","name":"Measure Bandwidth in Operational Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Measure the bandwidth of {{ sc_31_03_odp }} in the operational environment of the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-31(03)","statement":"the bandwidth of {{ sc_31_03_odp }} is measured in the operational environment of the system.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-31-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-32","slug":"sc-32","display_id":"SC-32","name":"System Partitioning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Partition the system into {{ sc_32_odp_01 }} residing in separate {{ sc_32_odp_02 }} domains or environments based on {{ sc_32_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the system is partitioned into {{ sc_32_odp_01 }} residing in separate {{ sc_32_odp_02 }} domains or environments based on {{ sc_32_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-32.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-32-1","slug":"sc-32-1","display_id":"SC-32(1)","name":"Separate Physical Domains for Privileged Functions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Partition privileged functions into separate physical domains.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-32(01)","statement":"privileged functions are partitioned into separate physical domains."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-32-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-33","slug":"sc-33","display_id":"SC-33","name":"Transmission Preparation Integrity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-33_to_nist-sp-800-53-r5-sc-8","source_ref":"requirement--nist-sp-800-53-r5-sc-33","target_ref":"requirement--nist-sp-800-53-r5-sc-8","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-33.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-34","slug":"sc-34","display_id":"SC-34","name":"Non-modifiable Executable Programs","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"For {{ sc_34_odp_01 }} , load and execute:","citation":null,"parts":[{"id":"a","statement":"The operating environment from hardware-enforced, read-only media; and"},{"id":"b","statement":"The following applications from hardware-enforced, read-only media: {{ sc_34_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the operating environment for {{ sc_34_odp_01 }} is loaded and executed from hardware-enforced, read-only media;\n"},{"id":"b","statement":"{{ sc_34_odp_02 }} for {{ sc_34_odp_01 }} are loaded and executed from hardware-enforced, read-only media.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-34.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-34-1","slug":"sc-34-1","display_id":"SC-34(1)","name":"No Writable Storage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ sc_34_01_odp }} with no writeable storage that is persistent across component restart or power on/off.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-34(01)","statement":"{{ sc_34_01_odp }} are employed with no writeable storage that is persistent across component restart or power on/off.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-34-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-34-2","slug":"sc-34-2","display_id":"SC-34(2)","name":"Integrity Protection on Read-only Media","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Protect the integrity of information prior to storage on read-only media and control the media after such information has been recorded onto the media.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sc-34(02).sc-34(02)[01]","statement":"the integrity of information is protected prior to storage on read-only media;"},{"id":"sc-34(02).sc-34(02)[02]","statement":"the media is controlled after such information has been recorded onto the media;"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-34-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-34-3","slug":"sc-34-3","display_id":"SC-34(3)","name":"Hardware-based Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-34-3_to_nist-sp-800-53-r5-sc-51","source_ref":"requirement--nist-sp-800-53-r5-sc-34-3","target_ref":"requirement--nist-sp-800-53-r5-sc-51","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-34-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-35","slug":"sc-35","display_id":"SC-35","name":"External Malicious Code Identification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Include system components that proactively seek to identify network-based malicious code or malicious websites.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"system components that proactively seek to identify network-based malicious code or malicious websites are included.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-35.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-36","slug":"sc-36","display_id":"SC-36","name":"Distributed Processing and Storage","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Distribute the following processing and storage components across multiple {{ sc_36_prm_1 }}: {{ sc_36_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"{{ sc_36_odp_01 }} are distributed across {{ sc_36_odp_02 }};"},{"id":"_obj-2","statement":"{{ sc_36_odp_03 }} are distributed across {{ sc_36_odp_04 }}."}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-36.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-36-1","slug":"sc-36-1","display_id":"SC-36(1)","name":"Polling Techniques","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ polling techniques to identify potential faults, errors, or compromises to the following processing and storage components: {{ sc_36_01_odp_01 }} ; and\n"},{"id":"b","statement":"Take the following actions in response to identified faults, errors, or compromises: {{ sc_36_01_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"polling techniques are employed to identify potential faults, errors, or compromises to {{ sc_36_01_odp_01 }};\n"},{"id":"b","statement":"{{ sc_36_01_odp_02 }} are taken in response to identified faults, errors, or compromise.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-36-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-36-2","slug":"sc-36-2","display_id":"SC-36(2)","name":"Synchronization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Synchronize the following duplicate systems or system components: {{ sc_36_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-36(02)","statement":"{{ sc_36_02_odp }} are synchronized."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-36-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-37","slug":"sc-37","display_id":"SC-37","name":"Out-of-band Channels","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ the following out-of-band channels for the physical delivery or electronic transmission of {{ sc_37_odp_02 }} to {{ sc_37_odp_03 }}: {{ sc_37_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_37_odp_01 }} are employed for the physical delivery or electronic transmission of {{ sc_37_odp_02 }} to {{ sc_37_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-37.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-37-1","slug":"sc-37-1","display_id":"SC-37(1)","name":"Ensure Delivery and Transmission","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ sc_37_01_odp_01 }} to ensure that only {{ sc_37_01_odp_02 }} receive the following information, system components, or devices: {{ sc_37_01_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-37(01)","statement":"{{ sc_37_01_odp_01 }} are employed to ensure that only {{ sc_37_01_odp_02 }} receive {{ sc_37_01_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-37-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-38","slug":"sc-38","display_id":"SC-38","name":"Operations Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ the following operations security controls to protect key organizational information throughout the system development life cycle: {{ sc_38_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_38_odp }} are employed to protect key organizational information throughout the system development life cycle.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-38.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-39","slug":"sc-39","display_id":"SC-39","name":"Process Isolation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Maintain a separate execution domain for each executing system process.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a separate execution domain is maintained for each executing system process."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-39.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-39-1","slug":"sc-39-1","display_id":"SC-39(1)","name":"Hardware Separation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement hardware separation mechanisms to facilitate process isolation.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-39(01)","statement":"hardware separation is implemented to facilitate process isolation."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-39-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-39-2","slug":"sc-39-2","display_id":"SC-39(2)","name":"Separate Execution Domain Per Thread","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain a separate execution domain for each thread in {{ sc_39_02_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-39(02)","statement":"a separate execution domain is maintained for each thread in {{ sc_39_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-39-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-40","slug":"sc-40","display_id":"SC-40","name":"Wireless Link Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Protect external and internal {{ sc_40_prm_1 }} from the following signal parameter attacks: {{ sc_40_prm_2 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"external {{ sc_40_odp_01 }} are protected from {{ sc_40_odp_02 }}."},{"id":"_obj-2","statement":"internal {{ sc_40_odp_03 }} are protected from {{ sc_40_odp_04 }}."}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-40.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-40-1","slug":"sc-40-1","display_id":"SC-40(1)","name":"Electromagnetic Interference","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms that achieve {{ sc_40_01_odp }} against the effects of intentional electromagnetic interference.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-40(01)","statement":"cryptographic mechanisms that achieve {{ sc_40_01_odp }} against the effects of intentional electromagnetic interference are implemented.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-40-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-40-2","slug":"sc-40-2","display_id":"SC-40(2)","name":"Reduce Detection Potential","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to reduce the detection potential of wireless links to {{ sc_40_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-40(02)","statement":"cryptographic mechanisms to reduce the detection potential of wireless links to {{ sc_40_02_odp }} are implemented.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-40-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-40-3","slug":"sc-40-3","display_id":"SC-40(3)","name":"Imitative or Manipulative Communications Deception","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-40(03)","statement":"cryptographic mechanisms are implemented to identify and reject wireless transmissions that are deliberate attempts to achieve imitative or manipulative communications deception based on signal parameters.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-40-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-40-4","slug":"sc-40-4","display_id":"SC-40(4)","name":"Signal Parameter Identification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to prevent the identification of {{ sc_40_04_odp }} by using the transmitter signal parameters.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-40(04)","statement":"cryptographic mechanisms are implemented to prevent the identification of {{ sc_40_04_odp }} by using the transmitter signal parameters.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-40-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-41","slug":"sc-41","display_id":"SC-41","name":"Port and I/O Device Access","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"{{ sc_41_odp_02 }} disable or remove {{ sc_41_odp_01 }} on the following systems or system components: {{ sc_41_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_41_odp_01 }} are {{ sc_41_odp_02 }} disabled or removed on {{ sc_41_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-41.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-42","slug":"sc-42","display_id":"SC-42","name":"Sensor Capability and Data","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Prohibit {{ sc_42_odp_01 }} ; and"},{"id":"b","statement":"Provide an explicit indication of sensor use to {{ sc_42_odp_05 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ sc_42_odp_01 }} is/are prohibited;"},{"id":"b","statement":"an explicit indication of sensor use is provided to {{ sc_42_odp_05 }}."}],"params_count":5,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-42.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-42-1","slug":"sc-42-1","display_id":"SC-42(1)","name":"Reporting to Authorized Individuals or Roles","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that the system is configured so that data or information collected by the {{ sc_42_01_odp }} is only reported to authorized individuals or roles.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-42(01)","statement":"the system is configured so that data or information collected by the {{ sc_42_01_odp }} is only reported to authorized individuals or roles.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-42-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-42-2","slug":"sc-42-2","display_id":"SC-42(2)","name":"Authorized Use","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following measures so that data or information collected by {{ sc_42_01_odp }} is only used for authorized purposes: {{ sc_42_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-42(02)","statement":"{{ sc_42_02_odp }} are employed so that data or information collected by {{ sc_42_01_odp }} is only used for authorized purposes.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-42-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-42-3","slug":"sc-42-3","display_id":"SC-42(3)","name":"Prohibit Use of Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-sc-42-3_to_nist-sp-800-53-r5-sc-42","source_ref":"requirement--nist-sp-800-53-r5-sc-42-3","target_ref":"requirement--nist-sp-800-53-r5-sc-42","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-42-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-42-4","slug":"sc-42-4","display_id":"SC-42(4)","name":"Notice of Collection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following measures to facilitate an individual’s awareness that personally identifiable information is being collected by {{ sc_42_04_odp_02 }}: {{ sc_42_04_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-42(04)","statement":"{{ sc_42_04_odp_01 }} are employed to facilitate an individual’s awareness that personally identifiable information is being collected by {{ sc_42_04_odp_02 }}\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-42-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-42-5","slug":"sc-42-5","display_id":"SC-42(5)","name":"Collection Minimization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ sc_42_05_odp }} that are configured to minimize the collection of information about individuals that is not needed.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-42(05)","statement":"the {{ sc_42_05_odp }} configured to minimize the collection of information about individuals that is not needed are employed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-42-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-43","slug":"sc-43","display_id":"SC-43","name":"Usage Restrictions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish usage restrictions and implementation guidelines for the following system components: {{ sc_43_odp }} ; and\n"},{"id":"b","statement":"Authorize, monitor, and control the use of such components within the system."}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"usage restrictions and implementation guidelines are established for {{ sc_43_odp }};\n"},{"id":"b-1","statement":"the use of {{ sc_43_odp }} is authorized within the system;"},{"id":"b-2","statement":"the use of {{ sc_43_odp }} is monitored within the system;"},{"id":"b-3","statement":"the use of {{ sc_43_odp }} is controlled within the system."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-43.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-44","slug":"sc-44","display_id":"SC-44","name":"Detonation Chambers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ a detonation chamber capability within {{ sc_44_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a detonation chamber capability is employed within the {{ sc_44_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-44.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-45","slug":"sc-45","display_id":"SC-45","name":"System Time Synchronization","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Synchronize system clocks within and between systems and system components.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"system clocks are synchronized within and between systems and system components."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-45.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-45-1","slug":"sc-45-1","display_id":"SC-45(1)","name":"Synchronization with Authoritative Time Source","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Compare the internal system clocks {{ sc_45_01_odp_01 }} with {{ sc_45_01_odp_02 }} ; and\n"},{"id":"b","statement":"Synchronize the internal system clocks to the authoritative time source when the time difference is greater than {{ sc_45_01_odp_03 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the internal system clocks are compared {{ sc_45_01_odp_01 }} with {{ sc_45_01_odp_02 }};\n"},{"id":"b","statement":"the internal system clocks are synchronized with the authoritative time source when the time difference is greater than {{ sc_45_01_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-45-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-45-2","slug":"sc-45-2","display_id":"SC-45(2)","name":"Secondary Authoritative Time Source","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify a secondary authoritative time source that is in a different geographic region than the primary authoritative time source; and\n"},{"id":"b","statement":"Synchronize the internal system clocks to the secondary authoritative time source if the primary authoritative time source is unavailable.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"a secondary authoritative time source is identified that is in a different geographic region than the primary authoritative time source;\n"},{"id":"b","statement":"the internal system clocks are synchronized to the secondary authoritative time source if the primary authoritative time source is unavailable.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-45-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-46","slug":"sc-46","display_id":"SC-46","name":"Cross Domain Policy Enforcement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement a policy enforcement mechanism {{ sc_46_odp }} between the physical and/or network interfaces for the connecting security domains.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"a policy enforcement mechanism is {{ sc_46_odp }} implemented between the physical and/or network interfaces for the connecting security domains.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-46.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-47","slug":"sc-47","display_id":"SC-47","name":"Alternate Communications Paths","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish {{ sc_47_odp }} for system operations organizational command and control.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_47_odp }} are established for system operations and operational command and control.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-47.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-48","slug":"sc-48","display_id":"SC-48","name":"Sensor Relocation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Relocate {{ sc_48_odp_01 }} to {{ sc_48_odp_02 }} under the following conditions or circumstances: {{ sc_48_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sc_48_odp_01 }} are relocated to {{ sc_48_odp_02 }} under {{ sc_48_odp_03 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-48.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-48-1","slug":"sc-48-1","display_id":"SC-48(1)","name":"Dynamic Relocation of Sensors or Monitoring Capabilities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Dynamically relocate {{ sc_48_01_odp_01 }} to {{ sc_48_01_odp_02 }} under the following conditions or circumstances: {{ sc_48_01_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sc-48(01)","statement":"{{ sc_48_01_odp_01 }} are dynamically relocated to {{ sc_48_01_odp_02 }} under {{ sc_48_01_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-48-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-49","slug":"sc-49","display_id":"SC-49","name":"Hardware-enforced Separation and Policy Enforcement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement hardware-enforced separation and policy enforcement mechanisms between {{ sc_49_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"hardware-enforced separation and policy enforcement mechanisms are implemented between {{ sc_49_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-49.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-50","slug":"sc-50","display_id":"SC-50","name":"Software-enforced Separation and Policy Enforcement","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement software-enforced separation and policy enforcement mechanisms between {{ sc_50_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"software-enforced separation and policy enforcement mechanisms are implemented between {{ sc_50_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-50.yaml"},{"id":"requirement--nist-sp-800-53-r5-sc-51","slug":"sc-51","display_id":"SC-51","name":"Hardware-based Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ hardware-based, write-protect for {{ sc_51_odp_01 }} ; and"},{"id":"b","statement":"Implement specific procedures for {{ sc_51_odp_02 }} to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"hardware-based write-protect for {{ sc_51_odp_01 }} is employed;"},{"id":"b-1","statement":"specific procedures are implemented for {{ sc_51_odp_02 }} to manually disable hardware write-protect for firmware modifications;\n"},{"id":"b-2","statement":"specific procedures are implemented for {{ sc_51_odp_02 }} to re-enable the write-protect prior to returning to operational mode.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sc-51.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-1","slug":"si-1","display_id":"SI-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ si_1_prm_1 }}:"},{"id":"a.1","statement":"{{ si_01_odp_03 }} system and information integrity policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls;\n"},{"id":"b","statement":"Designate an {{ si_01_odp_04 }} to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and\n"},{"id":"c","statement":"Review and update the current system and information integrity:"},{"id":"c.1","statement":"Policy {{ si_01_odp_05 }} and following {{ si_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ si_01_odp_07 }} and following {{ si_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a system and information integrity policy is developed and documented;"},{"id":"a-2","statement":"the system and information integrity policy is disseminated to {{ si_01_odp_01 }};\n"},{"id":"a-3","statement":"system and information integrity procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls are developed and documented;\n"},{"id":"a-4","statement":"the system and information integrity procedures are disseminated to {{ si_01_odp_02 }};\n"},{"id":"a.1.a-1","statement":"the {{ si_01_odp_03 }} system and information integrity policy addresses purpose;\n"},{"id":"a.1.a-2","statement":"the {{ si_01_odp_03 }} system and information integrity policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2","slug":"si-2","display_id":"SI-2","name":"Flaw Remediation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify, report, and correct system flaws;"},{"id":"b","statement":"Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;\n"},{"id":"c","statement":"Install security-relevant software and firmware updates within {{ si_02_odp }} of the release of the updates; and\n"},{"id":"d","statement":"Incorporate flaw remediation into the organizational configuration management process.\n"}],"objectives_count":10,"objectives_preview":[{"id":"a-1","statement":"system flaws are identified;"},{"id":"a-2","statement":"system flaws are reported;"},{"id":"a-3","statement":"system flaws are corrected;"},{"id":"b-1","statement":"software updates related to flaw remediation are tested for effectiveness before installation;\n"},{"id":"b-2","statement":"software updates related to flaw remediation are tested for potential side effects before installation;\n"},{"id":"b-3","statement":"firmware updates related to flaw remediation are tested for effectiveness before installation;\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-vm-02-to-800-53-si-2-a","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#a","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Applying security updates corrects system flaws; identification and reporting are handled by vulnerability scanning.\n"},{"id":"mapping--ogrl-vm-02-to-800-53-si-2-b","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Updates are tested in non-production before production deployment per SI-2(b)."},{"id":"mapping--ogrl-vm-02-to-800-53-si-2-c","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_02_odp":"patch_sla"},"summary":"A defined installation timeframe for security updates satisfies SI-2(c)."},{"id":"mapping--ogrl-vm-02-to-800-53-si-2-d","source_ref":"control--ogrl-vm-02","target_ref":"requirement--nist-sp-800-53-r5-si-2#d","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Patches flow through the standard change process, incorporating flaw remediation into configuration management per SI-2(d).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-1","slug":"si-2-1","display_id":"SI-2(1)","name":"Central Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-2-1_to_nist-sp-800-53-r5-pl-9","source_ref":"requirement--nist-sp-800-53-r5-si-2-1","target_ref":"requirement--nist-sp-800-53-r5-pl-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-2","slug":"si-2-2","display_id":"SI-2(2)","name":"Automated Flaw Remediation Status","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Determine if system components have applicable security-relevant software and firmware updates installed using {{ si_02_02_odp_01 }} {{ si_02_02_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-02(02)","statement":"system components have applicable security-relevant software and firmware updates installed {{ si_02_02_odp_02 }} using {{ si_02_02_odp_01 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-3","slug":"si-2-3","display_id":"SI-2(3)","name":"Time to Remediate Flaws and Benchmarks for Corrective Actions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Measure the time between flaw identification and flaw remediation; and"},{"id":"b","statement":"Establish the following benchmarks for taking corrective actions: {{ si_02_03_odp }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the time between flaw identification and flaw remediation is measured;"},{"id":"b","statement":"{{ si_02_03_odp }} for taking corrective actions have been established."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-4","slug":"si-2-4","display_id":"SI-2(4)","name":"Automated Patch Management Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automated patch management tools to facilitate flaw remediation to the following system components: {{ si_02_04_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-02(04)","statement":"automated patch management tools are employed to facilitate flaw remediation to {{ si_02_04_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-5","slug":"si-2-5","display_id":"SI-2(5)","name":"Automatic Software and Firmware Updates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Install {{ si_02_05_odp_01 }} automatically to {{ si_02_05_odp_02 }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-02(05)","statement":"{{ si_02_05_odp_01 }} are installed automatically to {{ si_02_05_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-6","slug":"si-2-6","display_id":"SI-2(6)","name":"Removal of Previous Versions of Software and Firmware","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Remove previous versions of {{ si_02_06_odp }} after updated versions have been installed.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-02(06)","statement":"previous versions of {{ si_02_06_odp }} are removed after updated versions have been installed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-2-7","slug":"si-2-7","display_id":"SI-2(7)","name":"Root Cause Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Conduct root cause analysis to identify underlying causes of issues or failures."},{"id":"b","statement":"Develop actions to address the root cause of the issue or failure."},{"id":"c","statement":"Implement the actions and monitor the implementation for effectiveness."}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"Root cause analysis is conducted to identify underlying causes of issues or failures\n"},{"id":"b","statement":"Actions to address the root cause of the issue of failure are developed"},{"id":"c-1","statement":"The actions (defined in [SI-02(07)b.](#si-2.7_smt.b)) are implemented"},{"id":"c-2","statement":"The implementation of actions is monitored for effectiveness."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-2-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3","slug":"si-3","display_id":"SI-3","name":"Malicious Code Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Implement {{ si_03_odp_01 }} malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code;\n"},{"id":"b","statement":"Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures;\n"},{"id":"c","statement":"Configure malicious code protection mechanisms to:"},{"id":"c.1","statement":"Perform periodic scans of the system {{ si_03_odp_02 }} and real-time scans of files from external sources at {{ si_03_odp_03 }} as the files are downloaded, opened, or executed in accordance with organizational policy; and\n"},{"id":"c.2","statement":"{{ si_03_odp_04 }} ; and send alert to {{ si_03_odp_06 }} in response to malicious code detection; and\n"},{"id":"d","statement":"Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system.\n"}],"objectives_count":8,"objectives_preview":[{"id":"a-1","statement":"{{ si_03_odp_01 }} malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code;\n"},{"id":"a-2","statement":"{{ si_03_odp_01 }} malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code;\n"},{"id":"b","statement":"malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures;\n"},{"id":"c.1-1","statement":"malicious code protection mechanisms are configured to perform periodic scans of the system {{ si_03_odp_02 }};\n"},{"id":"c.1-2","statement":"malicious code protection mechanisms are configured to perform real-time scans of files from external sources at {{ si_03_odp_03 }} as the files are downloaded, opened, or executed in accordance with organizational policy;\n"},{"id":"c.2-1","statement":"malicious code protection mechanisms are configured to {{ si_03_odp_04 }} in response to malicious code detection;\n"}],"params_count":6,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-vm-03-to-800-53-si-3-a","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Endpoint and host anti-malware provides detection and eradication, though not necessarily at every system entry and exit point required by SI-3(a).\n"},{"id":"mapping--ogrl-vm-03-to-800-53-si-3-b","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Automatic engine and signature updates satisfy SI-3(b)."},{"id":"mapping--ogrl-vm-03-to-800-53-si-3-c-1","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#c.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_03_odp_02":"malware_scan_frequency"},"summary":"Real-time scanning plus scheduled full scans meet SI-3(c)(1)."},{"id":"mapping--ogrl-vm-03-to-800-53-si-3-c-2","source_ref":"control--ogrl-vm-03","target_ref":"requirement--nist-sp-800-53-r5-si-3#c.2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_03_odp_04":"malware_response_action","si_03_odp_06":"malware_alert_recipients"},"summary":"Automatic block or quarantine with alerts to defined recipients meets SI-3(c)(2).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-1","slug":"si-3-1","display_id":"SI-3(1)","name":"Central Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-3-1_to_nist-sp-800-53-r5-pl-9","source_ref":"requirement--nist-sp-800-53-r5-si-3-1","target_ref":"requirement--nist-sp-800-53-r5-pl-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-2","slug":"si-3-2","display_id":"SI-3(2)","name":"Automatic Updates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-3-2_to_nist-sp-800-53-r5-si-3","source_ref":"requirement--nist-sp-800-53-r5-si-3-2","target_ref":"requirement--nist-sp-800-53-r5-si-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-3","slug":"si-3-3","display_id":"SI-3(3)","name":"Non-privileged Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-3-3_to_nist-sp-800-53-r5-ac-6-10","source_ref":"requirement--nist-sp-800-53-r5-si-3-3","target_ref":"requirement--nist-sp-800-53-r5-ac-6-10","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-4","slug":"si-3-4","display_id":"SI-3(4)","name":"Updates Only by Privileged Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Update malicious code protection mechanisms only when directed by a privileged user.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-03(04)","statement":"malicious code protection mechanisms are updated only when directed by a privileged user.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-5","slug":"si-3-5","display_id":"SI-3(5)","name":"Portable Storage Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-3-5_to_nist-sp-800-53-r5-mp-7","source_ref":"requirement--nist-sp-800-53-r5-si-3-5","target_ref":"requirement--nist-sp-800-53-r5-mp-7","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-6","slug":"si-3-6","display_id":"SI-3(6)","name":"Testing and Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Test malicious code protection mechanisms {{ si_03_06_odp }} by introducing known benign code into the system; and\n"},{"id":"b","statement":"Verify that the detection of the code and the associated incident reporting occur.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"malicious code protection mechanisms are tested {{ si_03_06_odp }} by introducing known benign code into the system;\n"},{"id":"b-1","statement":"the detection of (benign test) code occurs;"},{"id":"b-2","statement":"the associated incident reporting occurs."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-7","slug":"si-3-7","display_id":"SI-3(7)","name":"Nonsignature-based Detection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-3-7_to_nist-sp-800-53-r5-si-3","source_ref":"requirement--nist-sp-800-53-r5-si-3-7","target_ref":"requirement--nist-sp-800-53-r5-si-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-8","slug":"si-3-8","display_id":"SI-3(8)","name":"Detect Unauthorized Commands","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Detect the following unauthorized operating system commands through the kernel application programming interface on {{ si_03_08_odp_02 }}: {{ si_03_08_odp_01 }} ; and\n"},{"id":"b","statement":"{{ si_03_08_odp_03 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ si_03_08_odp_01 }} are detected through the kernel application programming interface on {{ si_03_08_odp_02 }};\n"},{"id":"b","statement":"{{ si_03_08_odp_03 }} is/are performed."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-9","slug":"si-3-9","display_id":"SI-3(9)","name":"Authenticate Remote Commands","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-3-9_to_nist-sp-800-53-r5-ac-17-10","source_ref":"requirement--nist-sp-800-53-r5-si-3-9","target_ref":"requirement--nist-sp-800-53-r5-ac-17-10","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-3-10","slug":"si-3-10","display_id":"SI-3(10)","name":"Malicious Code Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ the following tools and techniques to analyze the characteristics and behavior of malicious code: {{ si_03_10_odp }} ; and\n"},{"id":"b","statement":"Incorporate the results from malicious code analysis into organizational incident response and flaw remediation processes.\n"}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"{{ si_03_10_odp }} are employed to analyze the characteristics and behavior of malicious code;\n"},{"id":"b-1","statement":"the results from malicious code analysis are incorporated into organizational incident response processes;\n"},{"id":"b-2","statement":"the results from malicious code analysis are incorporated into organizational flaw remediation processes.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-3-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4","slug":"si-4","display_id":"SI-4","name":"System Monitoring","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Monitor the system to detect:"},{"id":"a.1","statement":"Attacks and indicators of potential attacks in accordance with the following monitoring objectives: {{ si_04_odp_01 }} ; and\n"},{"id":"a.2","statement":"Unauthorized local, network, and remote connections;"},{"id":"b","statement":"Identify unauthorized use of the system through the following techniques and methods: {{ si_04_odp_02 }};\n"},{"id":"c","statement":"Invoke internal monitoring capabilities or deploy monitoring devices:"},{"id":"c.1","statement":"Strategically within the system to collect organization-determined essential information; and\n"},{"id":"c.2","statement":"At ad hoc locations within the system to track specific types of transactions of interest to the organization;\n"},{"id":"d","statement":"Analyze detected events and anomalies;"},{"id":"e","statement":"Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;\n"},{"id":"f","statement":"Obtain legal opinion regarding system monitoring activities; and"},{"id":"g","statement":"Provide {{ si_04_odp_03 }} to {{ si_04_odp_04 }} {{ si_04_odp_05 }}."}],"objectives_count":12,"objectives_preview":[{"id":"a.1","statement":"the system is monitored to detect attacks and indicators of potential attacks in accordance with {{ si_04_odp_01 }};\n"},{"id":"a.2-1","statement":"the system is monitored to detect unauthorized local connections;"},{"id":"a.2-2","statement":"the system is monitored to detect unauthorized network connections;"},{"id":"a.2-3","statement":"the system is monitored to detect unauthorized remote connections;"},{"id":"b","statement":"unauthorized use of the system is identified through {{ si_04_odp_02 }};"},{"id":"c.1","statement":"internal monitoring capabilities are invoked or monitoring devices are deployed strategically within the system to collect organization-determined essential information;\n"}],"params_count":6,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-02-to-800-53-si-4-a-1","source_ref":"control--ogrl-lm-02","target_ref":"requirement--nist-sp-800-53-r5-si-4#a.1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_04_odp_01":"monitoring_objectives"},"summary":"Continuous telemetry monitoring against defined threat objectives satisfies NIST SI-4(a.1).\n"},{"id":"mapping--ogrl-lm-02-to-800-53-si-4-b","source_ref":"control--ogrl-lm-02","target_ref":"requirement--nist-sp-800-53-r5-si-4#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_04_odp_02":"monitoring_methods"},"summary":"SIEM correlation and cloud threat detection identify unauthorized system use per SI-4(b).\n"},{"id":"mapping--ogrl-lm-02-to-800-53-si-4-g","source_ref":"control--ogrl-lm-02","target_ref":"requirement--nist-sp-800-53-r5-si-4#g","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_04_odp_04":"alert_recipients"},"summary":"Routing actionable security alerts to on-call responders satisfies NIST SI-4(g)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-1","slug":"si-4-1","display_id":"SI-4(1)","name":"System-wide Intrusion Detection System","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Connect and configure individual intrusion detection tools into a system-wide intrusion detection system.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-04(01).si-04(01)[01]","statement":"individual intrusion detection tools are connected to a system-wide intrusion detection system;\n"},{"id":"si-04(01).si-04(01)[02]","statement":"individual intrusion detection tools are configured into a system-wide intrusion detection system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-2","slug":"si-4-2","display_id":"SI-4(2)","name":"Automated Tools and Mechanisms for Real-time Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automated tools and mechanisms to support near real-time analysis of events.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(02)","statement":"automated tools and mechanisms are employed to support a near real-time analysis of events.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-3","slug":"si-4-3","display_id":"SI-4(3)","name":"Automated Tool and Mechanism Integration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automated tools and mechanisms to integrate intrusion detection tools and mechanisms into access control and flow control mechanisms.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-04(03).si-04(03)[01]","statement":"automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into access control mechanisms;\n"},{"id":"si-04(03).si-04(03)[02]","statement":"automated tools and mechanisms are employed to integrate intrusion detection tools and mechanisms into flow control mechanisms.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-4","slug":"si-4-4","display_id":"SI-4(4)","name":"Inbound and Outbound Communications Traffic","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine criteria for unusual or unauthorized activities or conditions for inbound and outbound communications traffic;\n"},{"id":"b","statement":"Monitor inbound and outbound communications traffic {{ si_4_4_prm_1 }} for {{ si_4_4_prm_2 }}.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"criteria for unusual or unauthorized activities or conditions for inbound communications traffic are defined;\n"},{"id":"a-2","statement":"criteria for unusual or unauthorized activities or conditions for outbound communications traffic are defined;\n"},{"id":"b-1","statement":"inbound communications traffic is monitored {{ si_04_04_odp_01 }} for {{ si_04_04_odp_02 }};\n"},{"id":"b-2","statement":"outbound communications traffic is monitored {{ si_04_04_odp_03 }} for {{ si_04_04_odp_04 }}.\n"}],"params_count":6,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-5","slug":"si-4-5","display_id":"SI-4(5)","name":"System-generated Alerts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Alert {{ si_04_05_odp_01 }} when the following system-generated indications of compromise or potential compromise occur: {{ si_04_05_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(05)","statement":"{{ si_04_05_odp_01 }} are alerted when system-generated {{ si_04_05_odp_02 }} occur.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-6","slug":"si-4-6","display_id":"SI-4(6)","name":"Restrict Non-privileged Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-4-6_to_nist-sp-800-53-r5-ac-6-10","source_ref":"requirement--nist-sp-800-53-r5-si-4-6","target_ref":"requirement--nist-sp-800-53-r5-ac-6-10","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-7","slug":"si-4-7","display_id":"SI-4(7)","name":"Automated Response to Suspicious Events","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Notify {{ si_04_07_odp_01 }} of detected suspicious events; and"},{"id":"b","statement":"Take the following actions upon detection: {{ si_04_07_odp_02 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ si_04_07_odp_01 }} are notified of detected suspicious events;"},{"id":"b","statement":"{{ si_04_07_odp_02 }} are taken upon the detection of suspicious events."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-8","slug":"si-4-8","display_id":"SI-4(8)","name":"Protection of Monitoring Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-4-8_to_nist-sp-800-53-r5-si-4","source_ref":"requirement--nist-sp-800-53-r5-si-4-8","target_ref":"requirement--nist-sp-800-53-r5-si-4","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-9","slug":"si-4-9","display_id":"SI-4(9)","name":"Testing of Monitoring Tools and Mechanisms","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Test intrusion-monitoring tools and mechanisms {{ si_04_09_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(09)","statement":"intrusion-monitoring tools and mechanisms are tested {{ si_04_09_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-10","slug":"si-4-10","display_id":"SI-4(10)","name":"Visibility of Encrypted Communications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Make provisions so that {{ si_04_10_odp_01 }} is visible to {{ si_04_10_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(10)","statement":"provisions are made so that {{ si_04_10_odp_01 }} is visible to {{ si_04_10_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-11","slug":"si-4-11","display_id":"SI-4(11)","name":"Analyze Communications Traffic Anomalies","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Analyze outbound communications traffic at the external interfaces to the system and selected {{ si_04_11_odp }} to discover anomalies.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-04(11).si-04(11)[01]","statement":"outbound communications traffic at the external interfaces to the system is analyzed to discover anomalies;\n"},{"id":"si-04(11).si-04(11)[02]","statement":"outbound communications traffic at {{ si_04_11_odp }} is analyzed to discover anomalies.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-12","slug":"si-4-12","display_id":"SI-4(12)","name":"Automated Organization-generated Alerts","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Alert {{ si_04_12_odp_01 }} using {{ si_04_12_odp_02 }} when the following indications of inappropriate or unusual activities with security or privacy implications occur: {{ si_04_12_odp_03 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(12)","statement":"{{ si_04_12_odp_01 }} is/are alerted using {{ si_04_12_odp_02 }} when {{ si_04_12_odp_03 }} indicate inappropriate or unusual activities with security or privacy implications.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-13","slug":"si-4-13","display_id":"SI-4(13)","name":"Analyze Traffic and Event Patterns","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Analyze communications traffic and event patterns for the system;"},{"id":"b","statement":"Develop profiles representing common traffic and event patterns; and"},{"id":"c","statement":"Use the traffic and event profiles in tuning system-monitoring devices."}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"communications traffic for the system is analyzed;"},{"id":"a-2","statement":"event patterns for the system are analyzed;"},{"id":"b-1","statement":"profiles representing common traffic are developed;"},{"id":"b-2","statement":"profiles representing event patterns are developed;"},{"id":"c-1","statement":"traffic profiles are used in tuning system-monitoring devices;"},{"id":"c-2","statement":"event profiles are used in tuning system-monitoring devices."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-14","slug":"si-4-14","display_id":"SI-4(14)","name":"Wireless Intrusion Detection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ a wireless intrusion detection system to identify rogue wireless devices and to detect attack attempts and potential compromises or breaches to the system.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-04(14).si-04(14)[01]","statement":"a wireless intrusion detection system is employed to identify rogue wireless devices;\n"},{"id":"si-04(14).si-04(14)[02]","statement":"a wireless intrusion detection system is employed to detect attack attempts on the system;\n"},{"id":"si-04(14).si-04(14)[03]","statement":"a wireless intrusion detection system is employed to detect potential compromises or breaches to the system.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-15","slug":"si-4-15","display_id":"SI-4(15)","name":"Wireless to Wireline Communications","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ an intrusion detection system to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(15)","statement":"an intrusion detection system is employed to monitor wireless communications traffic as the traffic passes from wireless to wireline networks.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-16","slug":"si-4-16","display_id":"SI-4(16)","name":"Correlate Monitoring Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correlate information from monitoring tools and mechanisms employed throughout the system.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(16)","statement":"information from monitoring tools and mechanisms employed throughout the system is correlated.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-17","slug":"si-4-17","display_id":"SI-4(17)","name":"Integrated Situational Awareness","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correlate information from monitoring physical, cyber, and supply chain activities to achieve integrated, organization-wide situational awareness.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(17)","statement":"information from monitoring physical, cyber, and supply chain activities are correlated to achieve integrated, organization-wide situational awareness.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-18","slug":"si-4-18","display_id":"SI-4(18)","name":"Analyze Traffic and Covert Exfiltration","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Analyze outbound communications traffic at external interfaces to the system and at the following interior points to detect covert exfiltration of information: {{ si_04_18_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-04(18).si-04(18)[01]","statement":"outbound communications traffic is analyzed at interfaces external to the system to detect covert exfiltration of information;\n"},{"id":"si-04(18).si-04(18)[02]","statement":"outbound communications traffic is analyzed at {{ si_04_18_odp }} to detect covert exfiltration of information.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-19","slug":"si-4-19","display_id":"SI-4(19)","name":"Risk for Individuals","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ si_04_19_odp_01 }} of individuals who have been identified by {{ si_04_19_odp_02 }} as posing an increased level of risk.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(19)","statement":"{{ si_04_19_odp_01 }} is implemented on individuals who have been identified by {{ si_04_19_odp_02 }} as posing an increased level of risk.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-20","slug":"si-4-20","display_id":"SI-4(20)","name":"Privileged Users","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following additional monitoring of privileged users: {{ si_04_20_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(20)","statement":"{{ si_04_20_odp }} of privileged users is implemented."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-21","slug":"si-4-21","display_id":"SI-4(21)","name":"Probationary Periods","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following additional monitoring of individuals during {{ si_04_21_odp_02 }}: {{ si_04_21_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(21)","statement":"{{ si_04_21_odp_01 }} of individuals is implemented during {{ si_04_21_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-22","slug":"si-4-22","display_id":"SI-4(22)","name":"Unauthorized Network Services","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Detect network services that have not been authorized or approved by {{ si_04_22_odp_01 }} ; and\n"},{"id":"b","statement":"{{ si_04_22_odp_02 }} when detected."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"network services that have not been authorized or approved by {{ si_04_22_odp_01 }} are detected;\n"},{"id":"b","statement":"{{ si_04_22_odp_02 }} is/are initiated when network services that have not been authorized or approved by authorization or approval processes are detected.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-23","slug":"si-4-23","display_id":"SI-4(23)","name":"Host-based Devices","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following host-based monitoring mechanisms at {{ si_04_23_odp_02 }}: {{ si_04_23_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-04(23)","statement":"{{ si_04_23_odp_01 }} are implemented on {{ si_04_23_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-24","slug":"si-4-24","display_id":"SI-4(24)","name":"Indicators of Compromise","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Discover, collect, and distribute to {{ si_04_24_odp_02 }} , indicators of compromise provided by {{ si_04_24_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-04(24).si-04(24)[01]","statement":"indicators of compromise provided by {{ si_04_24_odp_01 }} are discovered;"},{"id":"si-04(24).si-04(24)[02]","statement":"indicators of compromise provided by {{ si_04_24_odp_01 }} are collected;"},{"id":"si-04(24).si-04(24)[03]","statement":"indicators of compromise provided by {{ si_04_24_odp_01 }} are distributed to {{ si_04_24_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-24.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-4-25","slug":"si-4-25","display_id":"SI-4(25)","name":"Optimize Network Traffic Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide visibility into network traffic at external and key internal system interfaces to optimize the effectiveness of monitoring devices.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-04(25).si-04(25)[01]","statement":"visibility into network traffic at external system interfaces is provided to optimize the effectiveness of monitoring devices;\n"},{"id":"si-04(25).si-04(25)[02]","statement":"visibility into network traffic at key internal system interfaces is provided to optimize the effectiveness of monitoring devices.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-4-25.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-5","slug":"si-5","display_id":"SI-5","name":"Security Alerts, Advisories, and Directives","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Receive system security alerts, advisories, and directives from {{ si_05_odp_01 }} on an ongoing basis;\n"},{"id":"b","statement":"Generate internal security alerts, advisories, and directives as deemed necessary;\n"},{"id":"c","statement":"Disseminate security alerts, advisories, and directives to: {{ si_05_odp_02 }} ; and\n"},{"id":"d","statement":"Implement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a","statement":"system security alerts, advisories, and directives are received from {{ si_05_odp_01 }} on an ongoing basis;\n"},{"id":"b","statement":"internal security alerts, advisories, and directives are generated as deemed necessary;\n"},{"id":"c","statement":"security alerts, advisories, and directives are disseminated to {{ si_05_odp_02 }};\n"},{"id":"d","statement":"security directives are implemented in accordance with established time frames or if the issuing organization is notified of the degree of noncompliance.\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-vm-04-to-800-53-si-5-a","source_ref":"control--ogrl-vm-04","target_ref":"requirement--nist-sp-800-53-r5-si-5#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_05_odp_01":"advisory_sources"},"summary":"Ongoing subscriptions to named advisory sources satisfy SI-5(a)."},{"id":"mapping--ogrl-vm-04-to-800-53-si-5-c","source_ref":"control--ogrl-vm-04","target_ref":"requirement--nist-sp-800-53-r5-si-5#c","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Actionable advisories are disseminated to defined internal recipients per SI-5(c).\n"},{"id":"mapping--ogrl-vm-04-to-800-53-si-5-d","source_ref":"control--ogrl-vm-04","target_ref":"requirement--nist-sp-800-53-r5-si-5#d","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Tracking required actions to completion overlaps SI-5(d), which also covers formal directives and noncompliance notice.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-5-1","slug":"si-5-1","display_id":"SI-5(1)","name":"Automated Alerts and Advisories","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Broadcast security alert and advisory information throughout the organization using {{ si_05_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-05(01)","statement":"{{ si_05_01_odp }} are used to broadcast security alert and advisory information throughout the organization.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-6","slug":"si-6","display_id":"SI-6","name":"Security and Privacy Function Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Verify the correct operation of {{ si_6_prm_1 }};"},{"id":"b","statement":"Perform the verification of the functions specified in SI-6a {{ si_06_odp_03 }};"},{"id":"c","statement":"Alert {{ si_06_odp_06 }} to failed security and privacy verification tests; and"},{"id":"d","statement":"{{ si_06_odp_07 }} when anomalies are discovered."}],"objectives_count":7,"objectives_preview":[{"id":"a-1","statement":"{{ si_06_odp_01 }} are verified to be operating correctly;"},{"id":"a-2","statement":"{{ si_06_odp_02 }} are verified to be operating correctly;"},{"id":"b-1","statement":"{{ si_06_odp_01 }} are verified {{ si_06_odp_03 }};"},{"id":"b-2","statement":"{{ si_06_odp_02 }} are verified {{ si_06_odp_03 }};"},{"id":"c-1","statement":"{{ si_06_odp_06 }} is/are alerted to failed security verification tests;"},{"id":"c-2","statement":"{{ si_06_odp_06 }} is/are alerted to failed privacy verification tests;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-6-1","slug":"si-6-1","display_id":"SI-6(1)","name":"Notification of Failed Security Tests","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-6-1_to_nist-sp-800-53-r5-si-6","source_ref":"requirement--nist-sp-800-53-r5-si-6-1","target_ref":"requirement--nist-sp-800-53-r5-si-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-6-2","slug":"si-6-2","display_id":"SI-6(2)","name":"Automation Support for Distributed Testing","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement automated mechanisms to support the management of distributed security and privacy function testing.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-06(02).si-06(02)[01]","statement":"automated mechanisms are implemented to support the management of distributed security function testing;\n"},{"id":"si-06(02).si-06(02)[02]","statement":"automated mechanisms are implemented to support the management of distributed privacy function testing.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-6-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-6-3","slug":"si-6-3","display_id":"SI-6(3)","name":"Report Verification Results","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Report the results of security and privacy function verification to {{ si_06_03_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-06(03).si-06(03)[01]","statement":"the results of security function verification are reported to {{ si_06_03_odp }};\n"},{"id":"si-06(03).si-06(03)[02]","statement":"the results of privacy function verification are reported to {{ si_06_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-6-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7","slug":"si-7","display_id":"SI-7","name":"Software, Firmware, and Information Integrity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ integrity verification tools to detect unauthorized changes to the following software, firmware, and information: {{ si_7_prm_1 }} ; and\n"},{"id":"b","statement":"Take the following actions when unauthorized changes to the software, firmware, and information are detected: {{ si_7_prm_2 }}.\n"}],"objectives_count":6,"objectives_preview":[{"id":"a-1","statement":"integrity verification tools are employed to detect unauthorized changes to {{ si_07_odp_01 }};\n"},{"id":"a-2","statement":"integrity verification tools are employed to detect unauthorized changes to {{ si_07_odp_02 }};\n"},{"id":"a-3","statement":"integrity verification tools are employed to detect unauthorized changes to {{ si_07_odp_03 }};\n"},{"id":"b-1","statement":"{{ si_07_odp_04 }} are taken when unauthorized changes to the software, are detected;\n"},{"id":"b-2","statement":"{{ si_07_odp_05 }} are taken when unauthorized changes to the firmware are detected;\n"},{"id":"b-3","statement":"{{ si_07_odp_06 }} are taken when unauthorized changes to the information are detected.\n"}],"params_count":8,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-09-to-800-53-si-7-a","source_ref":"control--ogrl-cm-09","target_ref":"requirement--nist-sp-800-53-r5-si-7#a","relationship":"subset-of","review_status":"reviewed","parameter_map":{"si_7_prm_1":"integrity_protected_assets"},"summary":"Integrity verification covers software and critical configuration; firmware and general information are out of scope for SI-7(a).\n"},{"id":"mapping--ogrl-cm-09-to-800-53-si-7-b","source_ref":"control--ogrl-cm-09","target_ref":"requirement--nist-sp-800-53-r5-si-7#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_7_prm_2":"integrity_response_actions"},"summary":"Defined response actions on integrity failure satisfy SI-7(b)."},{"id":"mapping--ogrl-cr-05-to-800-53-si-7-a","source_ref":"control--ogrl-cr-05","target_ref":"requirement--nist-sp-800-53-r5-si-7#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Storage-level integrity verification covers the information portion of SI-7(a) but not software or firmware.\n"},{"id":"mapping--ogrl-cr-05-to-800-53-si-7-b","source_ref":"control--ogrl-cr-05","target_ref":"requirement--nist-sp-800-53-r5-si-7#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Alerting on detected data integrity errors is a response action for information integrity under SI-7(b).\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-1","slug":"si-7-1","display_id":"SI-7(1)","name":"Integrity Checks","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform an integrity check of {{ si_7_1_prm_1 }} {{ si_7_1_prm_2 }}.","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-07(01).si-07(01)[01]","statement":"an integrity check of {{ si_07_01_odp_01 }} is performed {{ si_07_01_odp_02 }};"},{"id":"si-07(01).si-07(01)[02]","statement":"an integrity check of {{ si_07_01_odp_05 }} is performed {{ si_07_01_odp_06 }};"},{"id":"si-07(01).si-07(01)[03]","statement":"an integrity check of {{ si_07_01_odp_09 }} is performed {{ si_07_01_odp_10 }}."}],"params_count":16,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-2","slug":"si-7-2","display_id":"SI-7(2)","name":"Automated Notifications of Integrity Violations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ automated tools that provide notification to {{ si_07_02_odp }} upon discovering discrepancies during integrity verification.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(02)","statement":"automated tools that provide notification to {{ si_07_02_odp }} upon discovering discrepancies during integrity verification are employed.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-3","slug":"si-7-3","display_id":"SI-7(3)","name":"Centrally Managed Integrity Tools","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ centrally managed integrity verification tools.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(03)","statement":"centrally managed integrity verification tools are employed."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-4","slug":"si-7-4","display_id":"SI-7(4)","name":"Tamper-evident Packaging","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-7-4_to_nist-sp-800-53-r5-sr-9","source_ref":"requirement--nist-sp-800-53-r5-si-7-4","target_ref":"requirement--nist-sp-800-53-r5-sr-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-5","slug":"si-7-5","display_id":"SI-7(5)","name":"Automated Response to Integrity Violations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Automatically {{ si_07_05_odp_01 }} when integrity violations are discovered.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(05)","statement":"{{ si_07_05_odp_01 }} are automatically performed when integrity violations are discovered.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-6","slug":"si-7-6","display_id":"SI-7(6)","name":"Cryptographic Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to detect unauthorized changes to software, firmware, and information.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-07(06).si-07(06)[01]","statement":"cryptographic mechanisms are implemented to detect unauthorized changes to software;\n"},{"id":"si-07(06).si-07(06)[02]","statement":"cryptographic mechanisms are implemented to detect unauthorized changes to firmware;\n"},{"id":"si-07(06).si-07(06)[03]","statement":"cryptographic mechanisms are implemented to detect unauthorized changes to information.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-7","slug":"si-7-7","display_id":"SI-7(7)","name":"Integration of Detection and Response","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Incorporate the detection of the following unauthorized changes into the organizational incident response capability: {{ si_07_07_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(07)","statement":"the detection of {{ si_07_07_odp }} are incorporated into the organizational incident response capability.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-8","slug":"si-7-8","display_id":"SI-7(8)","name":"Auditing Capability for Significant Events","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: {{ si_07_08_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-07(08).si-07(08)[01]","statement":"the capability to audit an event upon the detection of a potential integrity violation is provided;\n"},{"id":"si-07(08).si-07(08)[02]","statement":"{{ si_07_08_odp_01 }} is/are initiated upon the detection of a potential integrity violation.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-9","slug":"si-7-9","display_id":"SI-7(9)","name":"Verify Boot Process","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify the integrity of the boot process of the following system components: {{ si_07_09_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(09)","statement":"the integrity of the boot process of {{ si_07_09_odp }} is verified."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-10","slug":"si-7-10","display_id":"SI-7(10)","name":"Protection of Boot Firmware","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement the following mechanisms to protect the integrity of boot firmware in {{ si_07_10_odp_02 }}: {{ si_07_10_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(10)","statement":"{{ si_07_10_odp_01 }} are implemented to protect the integrity of boot firmware in {{ si_07_10_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-11","slug":"si-7-11","display_id":"SI-7(11)","name":"Confined Environments with Limited Privileges","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-7-11_to_nist-sp-800-53-r5-cm-7-6","source_ref":"requirement--nist-sp-800-53-r5-si-7-11","target_ref":"requirement--nist-sp-800-53-r5-cm-7-6","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-12","slug":"si-7-12","display_id":"SI-7(12)","name":"Integrity Verification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Require that the integrity of the following user-installed software be verified prior to execution: {{ si_07_12_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(12)","statement":"the integrity of {{ si_07_12_odp }} is verified prior to execution."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-13","slug":"si-7-13","display_id":"SI-7(13)","name":"Code Execution in Protected Environments","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-7-13_to_nist-sp-800-53-r5-cm-7-7","source_ref":"requirement--nist-sp-800-53-r5-si-7-13","target_ref":"requirement--nist-sp-800-53-r5-cm-7-7","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-14","slug":"si-7-14","display_id":"SI-7(14)","name":"Binary or Machine Executable Code","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-7-14_to_nist-sp-800-53-r5-cm-7-8","source_ref":"requirement--nist-sp-800-53-r5-si-7-14","target_ref":"requirement--nist-sp-800-53-r5-cm-7-8","relationship":"equivalent-to","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL moved-to link. NIST records the source requirement as moved to the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-15","slug":"si-7-15","display_id":"SI-7(15)","name":"Code Authentication","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement cryptographic mechanisms to authenticate the following software or firmware components prior to installation: {{ si_07_15_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(15)","statement":"cryptographic mechanisms are implemented to authenticate {{ si_07_15_odp }} prior to installation.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-16","slug":"si-7-16","display_id":"SI-7(16)","name":"Time Limit on Process Execution Without Supervision","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit processes from executing without supervision for more than {{ si_07_16_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(16)","statement":"processes are prohibited from executing without supervision for more than {{ si_07_16_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-7-17","slug":"si-7-17","display_id":"SI-7(17)","name":"Runtime Application Self-protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement {{ si_07_17_odp }} for application self-protection at runtime.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-07(17)","statement":"{{ si_07_17_odp }} are implemented for application self-protection at runtime."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-7-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-8","slug":"si-8","display_id":"SI-8","name":"Spam Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Employ spam protection mechanisms at system entry and exit points to detect and act on unsolicited messages; and\n"},{"id":"b","statement":"Update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.\n"}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"spam protection mechanisms are employed at system entry points to detect unsolicited messages;\n"},{"id":"a-2","statement":"spam protection mechanisms are employed at system exit points to detect unsolicited messages;\n"},{"id":"a-3","statement":"spam protection mechanisms are employed at system entry points to act on unsolicited messages;\n"},{"id":"a-4","statement":"spam protection mechanisms are employed at system exit points to act on unsolicited messages;\n"},{"id":"b","statement":"spam protection mechanisms are updated when new releases are available in accordance with organizational configuration management policies and procedures.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-8-1","slug":"si-8-1","display_id":"SI-8(1)","name":"Central Management","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-8-1_to_nist-sp-800-53-r5-pl-9","source_ref":"requirement--nist-sp-800-53-r5-si-8-1","target_ref":"requirement--nist-sp-800-53-r5-pl-9","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-8-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-8-2","slug":"si-8-2","display_id":"SI-8(2)","name":"Automatic Updates","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Automatically update spam protection mechanisms {{ si_08_02_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-08(02)","statement":"spam protection mechanisms are automatically updated {{ si_08_02_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-8-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-8-3","slug":"si-8-3","display_id":"SI-8(3)","name":"Continuous Learning Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Implement spam protection mechanisms with a learning capability to more effectively identify legitimate communications traffic.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-08(03)","statement":"spam protection mechanisms with a learning capability are implemented to more effectively identify legitimate communications traffic.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-8-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-9","slug":"si-9","display_id":"SI-9","name":"Information Input Restrictions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-9_to_nist-sp-800-53-r5-ac-2","source_ref":"requirement--nist-sp-800-53-r5-si-9","target_ref":"requirement--nist-sp-800-53-r5-ac-2","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-si-9_to_nist-sp-800-53-r5-ac-3","source_ref":"requirement--nist-sp-800-53-r5-si-9","target_ref":"requirement--nist-sp-800-53-r5-ac-3","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-si-9_to_nist-sp-800-53-r5-ac-5","source_ref":"requirement--nist-sp-800-53-r5-si-9","target_ref":"requirement--nist-sp-800-53-r5-ac-5","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"},{"id":"mapping--nist-sp-800-53-r5-si-9_to_nist-sp-800-53-r5-ac-6","source_ref":"requirement--nist-sp-800-53-r5-si-9","target_ref":"requirement--nist-sp-800-53-r5-ac-6","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10","slug":"si-10","display_id":"SI-10","name":"Information Input Validation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Check the validity of the following information inputs: {{ si_10_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the validity of the {{ si_10_odp }} is checked."}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-06-to-800-53-si-10","source_ref":"control--ogrl-sd-06","target_ref":"requirement--nist-sp-800-53-r5-si-10","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_10_odp":"validated_input_channels"},"summary":"Schema-based validity checks on named input channels satisfy SI-10."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10-1","slug":"si-10-1","display_id":"SI-10(1)","name":"Manual Override Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Provide a manual override capability for input validation of the following information inputs: {{ si_10_odp }};\n"},{"id":"b","statement":"Restrict the use of the manual override capability to only {{ si_10_01_odp }} ; and\n"},{"id":"c","statement":"Audit the use of the manual override capability."}],"objectives_count":3,"objectives_preview":[{"id":"a","statement":"a manual override capability for the validation of {{ si_10_odp }} is provided;"},{"id":"b","statement":"the use of the manual override capability is restricted to only {{ si_10_01_odp }};\n"},{"id":"c","statement":"the use of the manual override capability is audited."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10-2","slug":"si-10-2","display_id":"SI-10(2)","name":"Review and Resolve Errors","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Review and resolve input validation errors within {{ si_10_2_prm_1 }}.","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-10(02).si-10(02)[01]","statement":"input validation errors are reviewed within {{ si_10_02_odp_01 }};"},{"id":"si-10(02).si-10(02)[02]","statement":"input validation errors are resolved within {{ si_10_02_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10-3","slug":"si-10-3","display_id":"SI-10(3)","name":"Predictable Behavior","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Verify that the system behaves in a predictable and documented manner when invalid inputs are received.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-10(03).si-10(03)[01]","statement":"the system behaves in a predictable manner when invalid inputs are received;"},{"id":"si-10(03).si-10(03)[02]","statement":"the system behaves in a documented manner when invalid inputs are received."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10-4","slug":"si-10-4","display_id":"SI-10(4)","name":"Timing Interactions","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Account for timing interactions among system components in determining appropriate responses for invalid inputs.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-10(04)","statement":"timing interactions among system components are accounted for in determining appropriate responses for invalid inputs.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10-5","slug":"si-10-5","display_id":"SI-10(5)","name":"Restrict Inputs to Trusted Sources and Approved Formats","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Restrict the use of information inputs to {{ si_10_05_odp_01 }} and/or {{ si_10_05_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-10(05)","statement":"the use of information inputs is restricted to {{ si_10_05_odp_01 }} and/or {{ si_10_05_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-10-6","slug":"si-10-6","display_id":"SI-10(6)","name":"Injection Prevention","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent untrusted data injections.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-10(06)","statement":"untrusted data injections are prevented."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-10-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-11","slug":"si-11","display_id":"SI-11","name":"Error Handling","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and\n"},{"id":"b","statement":"Reveal error messages only to {{ si_11_odp }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"error messages that provide the information necessary for corrective actions are generated without revealing information that could be exploited;\n"},{"id":"b","statement":"error messages are revealed only to {{ si_11_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-07-to-800-53-si-11-a","source_ref":"control--ogrl-sd-07","target_ref":"requirement--nist-sp-800-53-r5-si-11#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"User-facing errors that aid correction without revealing exploitable details satisfy SI-11(a).\n"},{"id":"mapping--ogrl-sd-07-to-800-53-si-11-b","source_ref":"control--ogrl-sd-07","target_ref":"requirement--nist-sp-800-53-r5-si-11#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_11_odp":"error_detail_roles"},"summary":"Detailed error information is restricted to defined roles per SI-11(b)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-12","slug":"si-12","display_id":"SI-12","name":"Information Management and Retention","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines and operational requirements.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"_obj-1","statement":"information within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;\n"},{"id":"_obj-2","statement":"information within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;\n"},{"id":"_obj-3","statement":"information output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;\n"},{"id":"_obj-4","statement":"information output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-03-to-800-53-si-12","source_ref":"control--ogrl-cr-03","target_ref":"requirement--nist-sp-800-53-r5-si-12","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"A documented and enforced retention schedule manages and retains information in line with legal, contractual, and operational requirements per SI-12.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-12.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-12-1","slug":"si-12-1","display_id":"SI-12(1)","name":"Limit Personally Identifiable Information Elements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Limit personally identifiable information being processed in the information life cycle to the following elements of personally identifiable information: {{ si_12_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-12(01)","statement":"personally identifiable information being processed in the information life cycle is limited to {{ si_12_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-04-to-800-53-si-12-1","source_ref":"control--ogrl-pr-04","target_ref":"requirement--nist-sp-800-53-r5-si-12-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_12_01_odp":"permitted_pii_elements"},"summary":"Limiting processing to approved PII elements satisfies SI-12(1)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-12-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-12-2","slug":"si-12-2","display_id":"SI-12(2)","name":"Minimize Personally Identifiable Information in Testing, Training, and Research","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use the following techniques to minimize the use of personally identifiable information for research, testing, or training: {{ si_12_2_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-12(02).si-12(02)[01]","statement":"{{ si_12_02_odp_01 }} are used to minimize the use of personally identifiable information for research;\n"},{"id":"si-12(02).si-12(02)[02]","statement":"{{ si_12_02_odp_02 }} are used to minimize the use of personally identifiable information for testing;\n"},{"id":"si-12(02).si-12(02)[03]","statement":"{{ si_12_02_odp_03 }} are used to minimize the use of personally identifiable information for training.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-12-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-12-3","slug":"si-12-3","display_id":"SI-12(3)","name":"Information Disposal","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Use the following techniques to dispose of, destroy, or erase information following the retention period: {{ si_12_3_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-12(03).si-12(03)[01]","statement":"{{ si_12_03_odp_01 }} are used to dispose of information following the retention period;\n"},{"id":"si-12(03).si-12(03)[02]","statement":"{{ si_12_03_odp_02 }} are used to destroy information following the retention period;\n"},{"id":"si-12(03).si-12(03)[03]","statement":"{{ si_12_03_odp_03 }} are used to erase information following the retention period.\n"}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-12-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-13","slug":"si-13","display_id":"SI-13","name":"Predictable Failure Prevention","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Determine mean time to failure (MTTF) for the following system components in specific environments of operation: {{ si_13_odp_01 }} ; and\n"},{"id":"b","statement":"Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: {{ si_13_odp_02 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"mean time to failure (MTTF) is determined for {{ si_13_odp_01 }} in specific environments of operation;\n"},{"id":"b","statement":"substitute system components and a means to exchange active and standby components are provided in accordance with {{ si_13_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-13.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-13-1","slug":"si-13-1","display_id":"SI-13(1)","name":"Transferring Component Responsibilities","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Take system components out of service by transferring component responsibilities to substitute components no later than {{ si_13_01_odp }} of mean time to failure.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-13(01)","statement":"system components are taken out of service by transferring component responsibilities to substitute components no later than {{ si_13_01_odp }} of mean time to failure.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-13-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-13-2","slug":"si-13-2","display_id":"SI-13(2)","name":"Time Limit on Process Execution Without Supervision","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":true,"statement":null,"citation":null,"parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[{"id":"mapping--nist-sp-800-53-r5-si-13-2_to_nist-sp-800-53-r5-si-7-16","source_ref":"requirement--nist-sp-800-53-r5-si-13-2","target_ref":"requirement--nist-sp-800-53-r5-si-7-16","relationship":"subset-of","review_status":"draft","parameter_map":null,"summary":"Imported from an OSCAL incorporated-into link. NIST records the source requirement as incorporated into the target.\n"}],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-13-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-13-3","slug":"si-13-3","display_id":"SI-13(3)","name":"Manual Transfer Between Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manually initiate transfers between active and standby system components when the use of the active component reaches {{ si_13_03_odp }} of the mean time to failure.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-13(03)","statement":"transfers are initiated manually between active and standby system components when the use of the active component reaches {{ si_13_03_odp }} of the mean time to failure.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-13-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-13-4","slug":"si-13-4","display_id":"SI-13(4)","name":"Standby Component Installation and Notification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"If system component failures are detected:","citation":null,"parts":[{"id":"a","statement":"Ensure that the standby components are successfully and transparently installed within {{ si_13_04_odp_01 }} ; and\n"},{"id":"b","statement":"{{ si_13_04_odp_02 }}."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"the standby components are successfully and transparently installed within {{ si_13_04_odp_01 }} if system component failures are detected;\n"},{"id":"b","statement":"{{ si_13_04_odp_02 }} are performed if system component failures are detected."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-13-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-13-5","slug":"si-13-5","display_id":"SI-13(5)","name":"Failover Capability","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Provide {{ si_13_05_odp_01 }} {{ si_13_05_odp_02 }} for the system.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-13(05)","statement":"{{ si_13_05_odp_01 }} {{ si_13_05_odp_02 }} is provided for the system."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-13-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-14","slug":"si-14","display_id":"SI-14","name":"Non-persistence","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement non-persistent {{ si_14_odp_01 }} that are initiated in a known state and terminated {{ si_14_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"_obj-1","statement":"non-persistent {{ si_14_odp_01 }} that are initiated in a known state are implemented;\n"},{"id":"_obj-2","statement":"non-persistent {{ si_14_odp_01 }} are terminated {{ si_14_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-14.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-14-1","slug":"si-14-1","display_id":"SI-14(1)","name":"Refresh from Trusted Sources","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Obtain software and data employed during system component and service refreshes from the following trusted sources: {{ si_14_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-14(01)","statement":"the software and data employed during system component and service refreshes are obtained from {{ si_14_01_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-14-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-14-2","slug":"si-14-2","display_id":"SI-14(2)","name":"Non-persistent Information","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"{{ si_14_02_odp_01 }} ; and"},{"id":"b","statement":"Delete information when no longer needed."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ si_14_02_odp_01 }} is performed;"},{"id":"b","statement":"information is deleted when no longer needed."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-14-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-14-3","slug":"si-14-3","display_id":"SI-14(3)","name":"Non-persistent Connectivity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish connections to the system on demand and terminate connections after {{ si_14_03_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-14(03).si-14(03)[01]","statement":"connections to the system are established on demand;"},{"id":"si-14(03).si-14(03)[02]","statement":"connections to the system are terminated after {{ si_14_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-14-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-15","slug":"si-15","display_id":"SI-15","name":"Information Output Filtering","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Validate information output from the following software programs and/or applications to ensure that the information is consistent with the expected content: {{ si_15_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"information output from {{ si_15_odp }} is validated to ensure that the information is consistent with the expected content.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-08-to-800-53-si-15","source_ref":"control--ogrl-sd-08","target_ref":"requirement--nist-sp-800-53-r5-si-15","relationship":"superset-of","review_status":"reviewed","parameter_map":{"si_15_odp":"validated_output_sources"},"summary":"Validating outputs against expected content meets SI-15, with authorized distribution added.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-15.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-16","slug":"si-16","display_id":"SI-16","name":"Memory Protection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement the following controls to protect the system memory from unauthorized code execution: {{ si_16_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ si_16_odp }} are implemented to protect the system memory from unauthorized code execution.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-16.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-17","slug":"si-17","display_id":"SI-17","name":"Fail-safe Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement the indicated fail-safe procedures when the indicated failures occur: {{ si_17_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ si_17_odp_01 }} are implemented when {{ si_17_odp_02 }} occur."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-17.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-18","slug":"si-18","display_id":"SI-18","name":"Personally Identifiable Information Quality Operations","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Check the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle {{ si_18_prm_1 }} ; and\n"},{"id":"b","statement":"Correct or delete inaccurate or outdated personally identifiable information."}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"the accuracy of personally identifiable information across the information life cycle is checked {{ si_18_odp_01 }};\n"},{"id":"a-2","statement":"the relevance of personally identifiable information across the information life cycle is checked {{ si_18_odp_02 }};\n"},{"id":"a-3","statement":"the timeliness of personally identifiable information across the information life cycle is checked {{ si_18_odp_03 }};\n"},{"id":"a-4","statement":"the completeness of personally identifiable information across the information life cycle is checked {{ si_18_odp_04 }};\n"},{"id":"b","statement":"inaccurate or outdated personally identifiable information is corrected or deleted.\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-10-to-800-53-si-18-a","source_ref":"control--ogrl-pr-10","target_ref":"requirement--nist-sp-800-53-r5-si-18#a","relationship":"equivalent-to","review_status":"reviewed","parameter_map":{"si_18_prm_1":"pii_quality_check_cadence"},"summary":"Periodic accuracy, completeness, relevance, and timeliness checks satisfy SI-18(a).\n"},{"id":"mapping--ogrl-pr-10-to-800-53-si-18-b","source_ref":"control--ogrl-pr-10","target_ref":"requirement--nist-sp-800-53-r5-si-18#b","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Correcting or deleting inaccurate or outdated PII satisfies SI-18(b)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-18.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-18-1","slug":"si-18-1","display_id":"SI-18(1)","name":"Automation Support","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correct or delete personally identifiable information that is inaccurate or outdated, incorrectly determined regarding impact, or incorrectly de-identified using {{ si_18_01_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-18(01)","statement":"{{ si_18_01_odp }} are used to correct or delete personally identifiable information that is inaccurate, outdated, incorrectly determined regarding impact, or incorrectly de-identified.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-18-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-18-2","slug":"si-18-2","display_id":"SI-18(2)","name":"Data Tags","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ data tags to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-18(02)","statement":"data tags are employed to automate the correction or deletion of personally identifiable information across the information life cycle within organizational systems.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-18-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-18-3","slug":"si-18-3","display_id":"SI-18(3)","name":"Collection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Collect personally identifiable information directly from the individual.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-18(03)","statement":"personally identifiable information is collected directly from the individual."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-18-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-18-4","slug":"si-18-4","display_id":"SI-18(4)","name":"Individual Requests","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Correct or delete personally identifiable information upon request by individuals or their designated representatives.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-18(04)","statement":"personally identifiable information is corrected or deleted upon request by individuals or their designated representatives.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-07-to-800-53-si-18-4","source_ref":"control--ogrl-pr-07","target_ref":"requirement--nist-sp-800-53-r5-si-18-4","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Correcting or deleting PII on verified request satisfies SI-18(4)."}],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-18-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-18-5","slug":"si-18-5","display_id":"SI-18(5)","name":"Notice of Correction or Deletion","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Notify {{ si_18_05_odp }} and individuals that the personally identifiable information has been corrected or deleted.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-18(05)","statement":"{{ si_18_05_odp }} and individuals are notified when the personally identifiable information has been corrected or deleted.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-18-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19","slug":"si-19","display_id":"SI-19","name":"De-identification","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Remove the following elements of personally identifiable information from datasets: {{ si_19_odp_01 }} ; and\n"},{"id":"b","statement":"Evaluate {{ si_19_odp_02 }} for effectiveness of de-identification."}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ si_19_odp_01 }} are removed from datasets;"},{"id":"b","statement":"the effectiveness of de-identification is evaluated {{ si_19_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-1","slug":"si-19-1","display_id":"SI-19(1)","name":"Collection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"De-identify the dataset upon collection by not collecting personally identifiable information.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-19(01)","statement":"the dataset is de-identified upon collection by not collecting personally identifiable information.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-2","slug":"si-19-2","display_id":"SI-19(2)","name":"Archiving","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prohibit archiving of personally identifiable information elements if those elements in a dataset will not be needed after the dataset is archived.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-19(02)","statement":"the archiving of personally identifiable information elements is prohibited if those elements in a dataset will not be needed after the dataset is archived.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-3","slug":"si-19-3","display_id":"SI-19(3)","name":"Release","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Remove personally identifiable information elements from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-19(03)","statement":"personally identifiable information elements are removed from a dataset prior to its release if those elements in the dataset do not need to be part of the data release.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-4","slug":"si-19-4","display_id":"SI-19(4)","name":"Removal, Masking, Encryption, Hashing, or Replacement of Direct Identifiers","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Remove, mask, encrypt, hash, or replace direct identifiers in a dataset.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-19(04)","statement":"direct identifiers in a dataset are removed, masked, encrypted, hashed, or replaced.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-5","slug":"si-19-5","display_id":"SI-19(5)","name":"Statistical Disclosure Control","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Manipulate numerical data, contingency tables, and statistical findings so that no individual or organization is identifiable in the results of the analysis.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"si-19(05).si-19(05)[01]","statement":"numerical data is manipulated so that no individual or organization is identifiable in the results of the analysis;\n"},{"id":"si-19(05).si-19(05)[02]","statement":"contingency tables are manipulated so that no individual or organization is identifiable in the results of the analysis;\n"},{"id":"si-19(05).si-19(05)[03]","statement":"statistical findings are manipulated so that no individual or organization is identifiable in the results of the analysis.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-6","slug":"si-19-6","display_id":"SI-19(6)","name":"Differential Privacy","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Prevent disclosure of personally identifiable information by adding non-deterministic noise to the results of mathematical operations before the results are reported.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-19(06)","statement":"the disclosure of personally identifiable information is prevented by adding non-deterministic noise to the results of mathematical operations before the results are reported.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-7","slug":"si-19-7","display_id":"SI-19(7)","name":"Validated Algorithms and Software","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform de-identification using validated algorithms and software that is validated to implement the algorithms.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"si-19(07).si-19(07)[01]","statement":"de-identification is performed using validated algorithms;"},{"id":"si-19(07).si-19(07)[02]","statement":"de-identification is performed using software that is validated to implement the algorithms.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-19-8","slug":"si-19-8","display_id":"SI-19(8)","name":"Motivated Intruder","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Perform a motivated intruder test on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"si-19(08)","statement":"a motivated intruder test is performed on the de-identified dataset to determine if the identified data remains or if the de-identified data can be re-identified.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-19-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-20","slug":"si-20","display_id":"SI-20","name":"Tainting","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Embed data or capabilities in the following systems or system components to determine if organizational data has been exfiltrated or improperly removed from the organization: {{ si_20_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"data or capabilities are embedded in {{ si_20_odp }} to determine if organizational data has been exfiltrated or improperly removed from the organization.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-20.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-21","slug":"si-21","display_id":"SI-21","name":"Information Refresh","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Refresh {{ si_21_odp_01 }} at {{ si_21_odp_02 }} or generate the information on demand and delete the information when no longer needed.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"the {{ si_21_odp_01 }} is refreshed {{ si_21_odp_02 }} or is generated on demand and deleted when no longer needed.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-21.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-22","slug":"si-22","display_id":"SI-22","name":"Information Diversity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Identify the following alternative sources of information for {{ si_22_odp_02 }}: {{ si_22_odp_01 }} ; and\n"},{"id":"b","statement":"Use an alternative information source for the execution of essential functions or services on {{ si_22_odp_03 }} when the primary source of information is corrupted or unavailable.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"{{ si_22_odp_01 }} for {{ si_22_odp_02 }} are identified;"},{"id":"b","statement":"an alternative information source is used for the execution of essential functions or services on {{ si_22_odp_03 }} when the primary source of information is corrupted or unavailable.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-22.yaml"},{"id":"requirement--nist-sp-800-53-r5-si-23","slug":"si-23","display_id":"SI-23","name":"Information Fragmentation","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Based on {{ si_23_odp_01 }}:","citation":null,"parts":[{"id":"a","statement":"Fragment the following information: {{ si_23_odp_02 }} ; and"},{"id":"b","statement":"Distribute the fragmented information across the following systems or system components: {{ si_23_odp_03 }}.\n"}],"objectives_count":2,"objectives_preview":[{"id":"a","statement":"under {{ si_23_odp_01 }}, {{ si_23_odp_02 }} is fragmented;"},{"id":"b","statement":"under {{ si_23_odp_01 }} , the fragmented information is distributed across {{ si_23_odp_03 }}.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/si-23.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-1","slug":"sr-1","display_id":"SR-1","name":"Policy and Procedures","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop, document, and disseminate to {{ sr_1_prm_1 }}:"},{"id":"a.1","statement":"{{ sr_01_odp_03 }} supply chain risk management policy that:"},{"id":"a.1.a","statement":"Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and\n"},{"id":"a.1.b","statement":"Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and\n"},{"id":"a.2","statement":"Procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls;\n"},{"id":"b","statement":"Designate an {{ sr_01_odp_04 }} to manage the development, documentation, and dissemination of the supply chain risk management policy and procedures; and\n"},{"id":"c","statement":"Review and update the current supply chain risk management:"},{"id":"c.1","statement":"Policy {{ sr_01_odp_05 }} and following {{ sr_01_odp_06 }} ; and"},{"id":"c.2","statement":"Procedures {{ sr_01_odp_07 }} and following {{ sr_01_odp_08 }}."}],"objectives_count":17,"objectives_preview":[{"id":"a-1","statement":"a supply chain risk management policy is developed and documented;"},{"id":"a-2","statement":"the supply chain risk management policy is disseminated to {{ sr_01_odp_01 }};"},{"id":"a-3","statement":"supply chain risk management procedures to facilitate the implementation of the supply chain risk management policy and the associated supply chain risk management controls are developed and documented;\n"},{"id":"a-4","statement":"the supply chain risk management procedures are disseminated to {{ sr_01_odp_02 }}.\n"},{"id":"a.1.a-1","statement":"the {{ sr_01_odp_03 }} supply chain risk management policy addresses purpose;"},{"id":"a.1.a-2","statement":"the {{ sr_01_odp_03 }} supply chain risk management policy addresses scope;"}],"params_count":9,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-2","slug":"sr-2","display_id":"SR-2","name":"Supply Chain Risk Management Plan","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop a plan for managing supply chain risks associated with the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of the following systems, system components or system services: {{ sr_02_odp_01 }};\n"},{"id":"b","statement":"Review and update the supply chain risk management plan {{ sr_02_odp_02 }} or as required, to address threat, organizational or environmental changes; and\n"},{"id":"c","statement":"Protect the supply chain risk management plan from unauthorized disclosure and modification.\n"}],"objectives_count":12,"objectives_preview":[{"id":"a-1","statement":"a plan for managing supply chain risks is developed;"},{"id":"a-2","statement":"the supply chain risk management plan addresses risks associated with the research and development of {{ sr_02_odp_01 }};\n"},{"id":"a-3","statement":"the supply chain risk management plan addresses risks associated with the design of {{ sr_02_odp_01 }};\n"},{"id":"a-4","statement":"the supply chain risk management plan addresses risks associated with the manufacturing of {{ sr_02_odp_01 }};\n"},{"id":"a-5","statement":"the supply chain risk management plan addresses risks associated with the acquisition of {{ sr_02_odp_01 }};\n"},{"id":"a-6","statement":"the supply chain risk management plan addresses risks associated with the delivery of {{ sr_02_odp_01 }};\n"}],"params_count":2,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-01-to-800-53-sr-2-a","source_ref":"control--ogrl-tp-01","target_ref":"requirement--nist-sp-800-53-r5-sr-2#a","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A tiered vendor inventory is a core input to supply chain risk planning but is not itself a supply chain risk management plan.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-2-1","slug":"sr-2-1","display_id":"SR-2(1)","name":"Establish SCRM Team","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish a supply chain risk management team consisting of {{ sr_02_01_odp_01 }} to lead and support the following SCRM activities: {{ sr_02_01_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-02(01)","statement":"a supply chain risk management team consisting of {{ sr_02_01_odp_01 }} is established to lead and support {{ sr_02_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-2-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-3","slug":"sr-3","display_id":"SR-3","name":"Supply Chain Controls and Processes","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Establish a process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ sr_03_odp_01 }} in coordination with {{ sr_03_odp_02 }};\n"},{"id":"b","statement":"Employ the following controls to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events: {{ sr_03_odp_03 }} ; and\n"},{"id":"c","statement":"Document the selected and implemented supply chain processes and controls in {{ sr_03_odp_04 }}.\n"}],"objectives_count":4,"objectives_preview":[{"id":"a-1","statement":"a process or processes is/are established to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ sr_03_odp_01 }};\n"},{"id":"a-2","statement":"the process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of {{ sr_03_odp_01 }} is/are coordinated with {{ sr_03_odp_02 }};\n"},{"id":"b","statement":"{{ sr_03_odp_03 }} are employed to protect against supply chain risks to the system, system component, or system service and to limit the harm or consequences from supply chain-related events;\n"},{"id":"c","statement":"the selected and implemented supply chain processes and controls are documented in {{ sr_03_odp_04 }}.\n"}],"params_count":5,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-03-to-800-53-sr-3-b","source_ref":"control--ogrl-tp-03","target_ref":"requirement--nist-sp-800-53-r5-sr-3#b","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Contract terms are one control employed to limit harm from supply chain events.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-3-1","slug":"sr-3-1","display_id":"SR-3(1)","name":"Diverse Supply Base","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ a diverse set of sources for the following system components and services: {{ sr_3_1_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sr-03(01).sr-03(01)[01]","statement":"a diverse set of sources is employed for {{ sr_03_01_odp_01 }};"},{"id":"sr-03(01).sr-03(01)[02]","statement":"a diverse set of sources is employed for {{ sr_03_01_odp_02 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-3-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-3-2","slug":"sr-3-2","display_id":"SR-3(2)","name":"Limitation of Harm","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following controls to limit harm from potential adversaries identifying and targeting the organizational supply chain: {{ sr_03_02_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-03(02)","statement":"{{ sr_03_02_odp }} are employed to limit harm from potential adversaries identifying and targeting the organizational supply chain.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-3-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-3-3","slug":"sr-3-3","display_id":"SR-3(3)","name":"Sub-tier Flow Down","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Ensure that the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-03(03)","statement":"the controls included in the contracts of prime contractors are also included in the contracts of subcontractors.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-3-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-4","slug":"sr-4","display_id":"SR-4","name":"Provenance","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: {{ sr_04_odp }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"[01]","statement":"valid provenance is documented for {{ sr_04_odp }};"},{"id":"[02]","statement":"valid provenance is monitored for {{ sr_04_odp }};"},{"id":"[03]","statement":"valid provenance is maintained for {{ sr_04_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-4-1","slug":"sr-4-1","display_id":"SR-4(1)","name":"Identity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish and maintain unique identification of the following supply chain elements, processes, and personnel associated with the identified system and critical system components: {{ sr_04_01_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sr-04(01).sr-04(01)[01]","statement":"unique identification of {{ sr_04_01_odp }} is established;"},{"id":"sr-04(01).sr-04(01)[02]","statement":"unique identification of {{ sr_04_01_odp }} is maintained."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-4-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-4-2","slug":"sr-4-2","display_id":"SR-4(2)","name":"Track and Trace","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Establish and maintain unique identification of the following systems and critical system components for tracking through the supply chain: {{ sr_04_02_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sr-04(02).sr-04(02)[01]","statement":"the unique identification of {{ sr_04_02_odp }} is established for tracking through the supply chain;\n"},{"id":"sr-04(02).sr-04(02)[02]","statement":"the unique identification of {{ sr_04_02_odp }} is maintained for tracking through the supply chain.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-4-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-4-3","slug":"sr-4-3","display_id":"SR-4(3)","name":"Validate as Genuine and Not Altered","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following controls to validate that the system or system component received is genuine and has not been altered: {{ sr_4_3_prm_1 }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sr-04(03).sr-04(03)[01]","statement":"{{ sr_04_03_odp_01 }} are employed to validate that the system or system component received is genuine;\n"},{"id":"sr-04(03).sr-04(03)[02]","statement":"{{ sr_04_03_odp_02 }} are employed to validate that the system or system component received has not been altered.\n"}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-4-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-4-4","slug":"sr-4-4","display_id":"SR-4(4)","name":"Supply Chain Integrity — Pedigree","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ sr_04_04_odp_01 }} and conduct {{ sr_04_04_odp_02 }} to ensure the integrity of the system and system components by validating the internal composition and provenance of critical or mission-essential technologies, products, and services.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sr-04(04).sr-04(04)[01]","statement":"{{ sr_04_04_odp_01 }} are employed to ensure the integrity of the system and system components;\n"},{"id":"sr-04(04).sr-04(04)[02]","statement":"{{ sr_04_04_odp_02 }} is conducted to ensure the integrity of the system and system components.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-4-4.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-5","slug":"sr-5","display_id":"SR-5","name":"Acquisition Strategies, Tools, and Methods","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ the following acquisition strategies, contract tools, and procurement methods to protect against, identify, and mitigate supply chain risks: {{ sr_05_odp }}.\n","citation":null,"parts":[],"objectives_count":3,"objectives_preview":[{"id":"[01]","statement":"{{ sr_05_odp }} are employed to protect against supply chain risks;"},{"id":"[02]","statement":"{{ sr_05_odp }} are employed to identify supply chain risks;"},{"id":"[03]","statement":"{{ sr_05_odp }} are employed to mitigate supply chain risks."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-5.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-5-1","slug":"sr-5-1","display_id":"SR-5(1)","name":"Adequate Supply","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ the following controls to ensure an adequate supply of {{ sr_05_01_odp_02 }}: {{ sr_05_01_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-05(01)","statement":"{{ sr_05_01_odp_01 }} are employed to ensure an adequate supply of {{ sr_05_01_odp_02 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-5-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-5-2","slug":"sr-5-2","display_id":"SR-5(2)","name":"Assessments Prior to Selection, Acceptance, Modification, or Update","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Assess the system, system component, or system service prior to selection, acceptance, modification, or update.\n","citation":null,"parts":[],"objectives_count":4,"objectives_preview":[{"id":"sr-05(02).sr-05(02)[01]","statement":"the system, system component, or system service is assessed prior to selection;"},{"id":"sr-05(02).sr-05(02)[02]","statement":"the system, system component, or system service is assessed prior to acceptance;"},{"id":"sr-05(02).sr-05(02)[03]","statement":"the system, system component, or system service is assessed prior to modification;\n"},{"id":"sr-05(02).sr-05(02)[04]","statement":"the system, system component, or system service is assessed prior to update."}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-5-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-6","slug":"sr-6","display_id":"SR-6","name":"Supplier Assessments and Reviews","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Assess and review the supply chain-related risks associated with suppliers or contractors and the system, system component, or system service they provide {{ sr_06_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-06","statement":"the supply chain-related risks associated with suppliers or contractors and the systems, system components, or system services they provide are assessed and reviewed {{ sr_06_odp }}.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-02-to-800-53-sr-6","source_ref":"control--ogrl-tp-02","target_ref":"requirement--nist-sp-800-53-r5-sr-6","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Pre-onboarding and change-triggered supplier assessments address SR-6; periodic reassessment is handled by OGRL-TP-04.\n"}],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-6.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-6-1","slug":"sr-6-1","display_id":"SR-6(1)","name":"Testing and Analysis","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ {{ sr_06_01_odp_01 }} of the following supply chain elements, processes, and actors associated with the system, system component, or system service: {{ sr_06_01_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-06(01)","statement":"{{ sr_06_01_odp_01 }} is/are employed on {{ sr_06_01_odp_02 }} associated with the system, system component, or system service.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-6-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-7","slug":"sr-7","display_id":"SR-7","name":"Supply Chain Operations Security","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Employ the following Operations Security (OPSEC) controls to protect supply chain-related information for the system, system component, or system service: {{ sr_07_odp }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-07","statement":"{{ sr_07_odp }} are employed to protect supply chain-related information for the system, system component, or system service.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-7.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-8","slug":"sr-8","display_id":"SR-8","name":"Notification Agreements","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Establish agreements and procedures with entities involved in the supply chain for the system, system component, or system service for the {{ sr_08_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-08","statement":"agreements and procedures are established with entities involved in the supply chain for the system, system components, or system service for {{ sr_08_odp_01 }}.\n"}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-8.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-9","slug":"sr-9","display_id":"SR-9","name":"Tamper Resistance and Detection","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Implement a tamper protection program for the system, system component, or system service.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-09","statement":"a tamper protection program is implemented for the system, system component, or system service.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-9.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-9-1","slug":"sr-9-1","display_id":"SR-9(1)","name":"Multiple Stages of System Development Life Cycle","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Employ anti-tamper technologies, tools, and techniques throughout the system development life cycle.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-09(01)","statement":"anti-tamper technologies, tools, and techniques are employed throughout the system development life cycle.\n"}],"params_count":0,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-9-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-10","slug":"sr-10","display_id":"SR-10","name":"Inspection of Systems or Components","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Inspect the following systems or system components {{ sr_10_odp_02 }} to detect tampering: {{ sr_10_odp_01 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sr_10_odp_01 }} are inspected {{ sr_10_odp_02 }} to detect tampering."}],"params_count":4,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-10.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-11","slug":"sr-11","display_id":"SR-11","name":"Component Authenticity","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":null,"citation":null,"parts":[{"id":"a","statement":"Develop and implement anti-counterfeit policy and procedures that include the means to detect and prevent counterfeit components from entering the system; and\n"},{"id":"b","statement":"Report counterfeit system components to {{ sr_11_odp_01 }}."}],"objectives_count":5,"objectives_preview":[{"id":"a-1","statement":"an anti-counterfeit policy is developed and implemented;"},{"id":"a-2","statement":"anti-counterfeit procedures are developed and implemented;"},{"id":"a-3","statement":"the anti-counterfeit procedures include the means to detect counterfeit components entering the system;\n"},{"id":"a-4","statement":"the anti-counterfeit procedures include the means to prevent counterfeit components from entering the system;\n"},{"id":"b","statement":"counterfeit system components are reported to {{ sr_11_odp_01 }}."}],"params_count":3,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-11.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-11-1","slug":"sr-11-1","display_id":"SR-11(1)","name":"Anti-counterfeit Training","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Train {{ sr_11_01_odp }} to detect counterfeit system components (including hardware, software, and firmware).\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-11(01)","statement":"{{ sr_11_01_odp }} are trained to detect counterfeit system components (including hardware, software, and firmware).\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-11-1.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-11-2","slug":"sr-11-2","display_id":"SR-11(2)","name":"Configuration Control for Component Service and Repair","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Maintain configuration control over the following system components awaiting service or repair and serviced or repaired components awaiting return to service: {{ sr_11_02_odp }}.\n","citation":null,"parts":[],"objectives_count":2,"objectives_preview":[{"id":"sr-11(02).sr-11(02)[01]","statement":"configuration control over {{ sr_11_02_odp }} awaiting service or repair is maintained;\n"},{"id":"sr-11(02).sr-11(02)[02]","statement":"configuration control over serviced or repaired {{ sr_11_02_odp }} awaiting return to service is maintained.\n"}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-11-2.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-11-3","slug":"sr-11-3","display_id":"SR-11(3)","name":"Anti-counterfeit Scanning","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"enhancement","withdrawn":false,"statement":"Scan for counterfeit system components {{ sr_11_03_odp }}.","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"sr-11(03)","statement":"scanning for counterfeit system components is conducted {{ sr_11_03_odp }}."}],"params_count":1,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-11-3.yaml"},{"id":"requirement--nist-sp-800-53-r5-sr-12","slug":"sr-12","display_id":"SR-12","name":"Component Disposal","framework_id":"framework--nist-sp-800-53-r5","framework_slug":"nist-sp-800-53-r5","class":"control","withdrawn":false,"statement":"Dispose of {{ sr_12_odp_01 }} using the following techniques and methods: {{ sr_12_odp_02 }}.\n","citation":null,"parts":[],"objectives_count":1,"objectives_preview":[{"id":"_obj","statement":"{{ sr_12_odp_01 }} are disposed of using {{ sr_12_odp_02 }}."}],"params_count":2,"mappings":[],"incoming_mappings":[],"yaml_path":"library/requirement/nist-sp-800-53-r5/sr-12.yaml"},{"id":"requirement--soc2-tsc-2017-a1-1","slug":"a1-1","display_id":"A1.1","name":"Capacity Management","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC A1.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-08-to-soc2-a1-1","source_ref":"control--ogrl-bc-08","target_ref":"requirement--soc2-tsc-2017-a1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Utilization monitoring and capacity forecasting are central to managing processing capacity for availability.\n"},{"id":"mapping--ogrl-bc-09-to-soc2-a1-1","source_ref":"control--ogrl-bc-09","target_ref":"requirement--soc2-tsc-2017-a1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"DoS protection preserves usable capacity under attack traffic, complementing capacity management.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/a1-1.yaml"},{"id":"requirement--soc2-tsc-2017-a1-2","slug":"a1-2","display_id":"A1.2","name":"Environmental Protection, Backup, and Recovery Infrastructure","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC A1.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-01-to-soc2-a1-2","source_ref":"control--ogrl-bc-01","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The plan defines the recovery objectives and procedures that recovery infrastructure is designed to meet.\n"},{"id":"mapping--ogrl-bc-03-to-soc2-a1-2","source_ref":"control--ogrl-bc-03","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated, protected backups are a core element of the data backup processes this criterion addresses.\n"},{"id":"mapping--ogrl-bc-04-to-soc2-a1-2","source_ref":"control--ogrl-bc-04","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Restore testing confirms that backup processes actually support recovery."},{"id":"mapping--ogrl-bc-05-to-soc2-a1-2","source_ref":"control--ogrl-bc-05","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Redundant processing and storage locations are recovery infrastructure within this criterion.\n"},{"id":"mapping--ogrl-bc-06-to-soc2-a1-2","source_ref":"control--ogrl-bc-06","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Runbook-driven restoration within objectives relies on and exercises the recovery infrastructure.\n"},{"id":"mapping--ogrl-bc-07-to-soc2-a1-2","source_ref":"control--ogrl-bc-07","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Impact analysis sets the recovery objectives that backup and recovery infrastructure must support.\n"},{"id":"mapping--ogrl-ps-05-to-soc2-a1-2","source_ref":"control--ogrl-ps-05","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Environmental protections for organization-operated facilities are one part of A1.2.\n"},{"id":"mapping--ogrl-ps-07-to-soc2-a1-2","source_ref":"control--ogrl-ps-07","target_ref":"requirement--soc2-tsc-2017-a1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Maintaining supporting infrastructure contributes to the availability protections in A1.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/a1-2.yaml"},{"id":"requirement--soc2-tsc-2017-a1-3","slug":"a1-3","display_id":"A1.3","name":"Recovery Plan Testing","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC A1.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-02-to-soc2-a1-3","source_ref":"control--ogrl-bc-02","target_ref":"requirement--soc2-tsc-2017-a1-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Exercising the continuity and recovery plan is the plan-level portion of recovery testing; backup restoration testing is a separate control.\n"},{"id":"mapping--ogrl-bc-04-to-soc2-a1-3","source_ref":"control--ogrl-bc-04","target_ref":"requirement--soc2-tsc-2017-a1-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Backup restoration tests are one part of testing recovery procedures."}],"yaml_path":"library/requirement/soc2-tsc-2017/a1-3.yaml"},{"id":"requirement--soc2-tsc-2017-c1-1","slug":"c1-1","display_id":"C1.1","name":"Confidential Information Identification and Protection","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC C1.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-12-to-soc2-c1-1","source_ref":"control--ogrl-ac-12","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Preventing cross-tenant exposure helps protect customers' confidential information under C1.1.\n"},{"id":"mapping--ogrl-am-02-to-soc2-c1-1","source_ref":"control--ogrl-am-02","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Classification identifies confidential information so it can be protected."},{"id":"mapping--ogrl-hr-03-to-soc2-c1-1","source_ref":"control--ogrl-hr-03","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Binding personnel to confidentiality obligations contributes to protecting confidential information under C1.1.\n"},{"id":"mapping--ogrl-tp-03-to-soc2-c1-1","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-c1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Vendor confidentiality and deletion obligations help protect confidential information under C1.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/c1-1.yaml"},{"id":"requirement--soc2-tsc-2017-c1-2","slug":"c1-2","display_id":"C1.2","name":"Confidential Information Disposal","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC C1.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-03-to-soc2-c1-2","source_ref":"control--ogrl-cr-03","target_ref":"requirement--soc2-tsc-2017-c1-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Scheduled and request-driven deletion disposes of confidential information when it is no longer needed.\n"},{"id":"mapping--ogrl-cr-04-to-soc2-c1-2","source_ref":"control--ogrl-cr-04","target_ref":"requirement--soc2-tsc-2017-c1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Media sanitization is one mechanism for disposing of confidential information."}],"yaml_path":"library/requirement/soc2-tsc-2017/c1-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc1-1","slug":"cc1-1","display_id":"CC1.1","name":"Integrity and Ethical Values","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC1.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-04-to-soc2-cc1-1","source_ref":"control--ogrl-gv-04","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"An acknowledged code of conduct establishes standards of integrity and ethics; tone from leadership and evaluation of adherence go further.\n"},{"id":"mapping--ogrl-gv-05-to-soc2-cc1-1","source_ref":"control--ogrl-gv-05","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Triaging reports of misconduct supports identifying and addressing deviations from expected conduct.\n"},{"id":"mapping--ogrl-gv-09-to-soc2-cc1-1","source_ref":"control--ogrl-gv-09","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Acknowledged rules of behavior communicate expected conduct when using systems."},{"id":"mapping--ogrl-hr-01-to-soc2-cc1-1","source_ref":"control--ogrl-hr-01","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Vetting personnel supports the integrity expectations of CC1.1 but does not address the broader tone and conduct standards.\n"},{"id":"mapping--ogrl-hr-03-to-soc2-cc1-1","source_ref":"control--ogrl-hr-03","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Signed policy acknowledgements help communicate and enforce expected conduct, one aspect of CC1.1.\n"},{"id":"mapping--ogrl-hr-05-to-soc2-cc1-1","source_ref":"control--ogrl-hr-05","target_ref":"requirement--soc2-tsc-2017-cc1-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Consistently addressing deviations from expected conduct supports the integrity commitments of CC1.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc1-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc1-2","slug":"cc1-2","display_id":"CC1.2","name":"Board Independence and Oversight","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC1.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-03-to-soc2-cc1-2","source_ref":"control--ogrl-gv-03","target_ref":"requirement--soc2-tsc-2017-cc1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Documented board briefings demonstrate oversight of security; board independence and composition are outside this control.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc1-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc1-3","slug":"cc1-3","display_id":"CC1.3","name":"Organizational Structure and Authority","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC1.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-02-to-soc2-cc1-3","source_ref":"control--ogrl-gv-02","target_ref":"requirement--soc2-tsc-2017-cc1-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented reporting lines, security roles, and a designated leader address organizational structure and authority for security.\n"},{"id":"mapping--ogrl-hr-06-to-soc2-cc1-3","source_ref":"control--ogrl-hr-06","target_ref":"requirement--soc2-tsc-2017-cc1-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Defining security responsibilities per position supports the assignment of responsibilities addressed by CC1.3.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc1-3.yaml"},{"id":"requirement--soc2-tsc-2017-cc1-4","slug":"cc1-4","display_id":"CC1.4","name":"Workforce Competence","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC1.4","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-01-to-soc2-cc1-4","source_ref":"control--ogrl-hr-01","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Pre-access screening is one element of the workforce competence and trustworthiness expectations in CC1.4.\n"},{"id":"mapping--ogrl-hr-04-to-soc2-cc1-4","source_ref":"control--ogrl-hr-04","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Extending screening and training expectations to external personnel supports the workforce expectations of CC1.4.\n"},{"id":"mapping--ogrl-hr-06-to-soc2-cc1-4","source_ref":"control--ogrl-hr-06","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented role expectations provide a basis for hiring and developing competent personnel under CC1.4.\n"},{"id":"mapping--ogrl-hr-07-to-soc2-cc1-4","source_ref":"control--ogrl-hr-07","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recurring security training develops personnel competence, one element of CC1.4.\n"},{"id":"mapping--ogrl-hr-08-to-soc2-cc1-4","source_ref":"control--ogrl-hr-08","target_ref":"requirement--soc2-tsc-2017-cc1-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Role-specific training develops the competence of personnel in security-relevant roles, part of CC1.4.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc1-4.yaml"},{"id":"requirement--soc2-tsc-2017-cc1-5","slug":"cc1-5","display_id":"CC1.5","name":"Accountability for Control Responsibilities","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC1.5","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-02-to-soc2-cc1-5","source_ref":"control--ogrl-gv-02","target_ref":"requirement--soc2-tsc-2017-cc1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Assigning named accountability for the security program supports holding individuals accountable; performance enforcement is elsewhere.\n"},{"id":"mapping--ogrl-gv-04-to-soc2-cc1-5","source_ref":"control--ogrl-gv-04","target_ref":"requirement--soc2-tsc-2017-cc1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Stated disciplinary consequences and individual acknowledgment support accountability for conduct.\n"},{"id":"mapping--ogrl-hr-05-to-soc2-cc1-5","source_ref":"control--ogrl-hr-05","target_ref":"requirement--soc2-tsc-2017-cc1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Disciplinary action for security violations is a mechanism for holding individuals accountable under CC1.5.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc1-5.yaml"},{"id":"requirement--soc2-tsc-2017-cc2-1","slug":"cc2-1","display_id":"CC2.1","name":"Quality Information for Internal Control","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC2.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-08-to-soc2-cc2-1","source_ref":"control--ogrl-gv-08","target_ref":"requirement--soc2-tsc-2017-cc2-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A maintained system description is a key source of relevant, quality information about system scope and controls.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc2-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc2-2","slug":"cc2-2","display_id":"CC2.2","name":"Internal Communication","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC2.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-01-to-soc2-cc2-2","source_ref":"control--ogrl-gv-01","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Publishing policies to all workforce members is one form of internal communication of security responsibilities.\n"},{"id":"mapping--ogrl-gv-03-to-soc2-cc2-2","source_ref":"control--ogrl-gv-03","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Briefing the governing body is one channel of internal communication about security objectives and results.\n"},{"id":"mapping--ogrl-gv-05-to-soc2-cc2-2","source_ref":"control--ogrl-gv-05","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A confidential reporting channel provides a separate internal communication path for raising concerns.\n"},{"id":"mapping--ogrl-gv-09-to-soc2-cc2-2","source_ref":"control--ogrl-gv-09","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The policy and acknowledgment communicate security responsibilities to every user.\n"},{"id":"mapping--ogrl-hr-07-to-soc2-cc2-2","source_ref":"control--ogrl-hr-07","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Awareness training is a primary channel for communicating security responsibilities internally under CC2.2.\n"},{"id":"mapping--ogrl-hr-08-to-soc2-cc2-2","source_ref":"control--ogrl-hr-08","target_ref":"requirement--soc2-tsc-2017-cc2-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Role-based training communicates role-specific security responsibilities, one aspect of CC2.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc2-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc2-3","slug":"cc2-3","display_id":"CC2.3","name":"External Communication","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC2.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-07-to-soc2-cc2-3","source_ref":"control--ogrl-gv-07","target_ref":"requirement--soc2-tsc-2017-cc2-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Publishing commitments and a security contact covers communication with customers; communication with other external parties is outside this control.\n"},{"id":"mapping--ogrl-gv-08-to-soc2-cc2-3","source_ref":"control--ogrl-gv-08","target_ref":"requirement--soc2-tsc-2017-cc2-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Sharing the system description with auditors and customers communicates system boundaries and controls externally.\n"},{"id":"mapping--ogrl-ir-04-to-soc2-cc2-3","source_ref":"control--ogrl-ir-04","target_ref":"requirement--soc2-tsc-2017-cc2-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Notifying customers and authorities of incidents is one form of communicating with external parties about matters affecting internal control.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc2-3.yaml"},{"id":"requirement--soc2-tsc-2017-cc3-1","slug":"cc3-1","display_id":"CC3.1","name":"Objective Specification","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC3.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-06-to-soc2-cc3-1","source_ref":"control--ogrl-gv-06","target_ref":"requirement--soc2-tsc-2017-cc3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Measurable security objectives give a clear basis for identifying and assessing risks to achieving them.\n"},{"id":"mapping--ogrl-rm-01-to-soc2-cc3-1","source_ref":"control--ogrl-rm-01","target_ref":"requirement--soc2-tsc-2017-cc3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Defined tolerance and scoring criteria enable risks to objectives to be identified and assessed.\n"},{"id":"mapping--ogrl-rm-02-to-soc2-cc3-1","source_ref":"control--ogrl-rm-02","target_ref":"requirement--soc2-tsc-2017-cc3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The assessment is the mechanism through which risks to stated objectives are identified.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc3-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc3-2","slug":"cc3-2","display_id":"CC3.2","name":"Risk Identification and Analysis","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC3.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-am-01-to-soc2-cc3-2","source_ref":"control--ogrl-am-01","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The inventory identifies the assets whose risks are assessed."},{"id":"mapping--ogrl-rm-01-to-soc2-cc3-2","source_ref":"control--ogrl-rm-01","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The methodology sets how risks are analyzed and how responses are determined; the assessment itself is a separate control.\n"},{"id":"mapping--ogrl-rm-02-to-soc2-cc3-2","source_ref":"control--ogrl-rm-02","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Identifies and rates risks to the system, including vendor risks; deciding how to respond is handled by risk treatment.\n"},{"id":"mapping--ogrl-rm-04-to-soc2-cc3-2","source_ref":"control--ogrl-rm-04","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Determining and tracking how each identified risk will be managed."},{"id":"mapping--ogrl-vm-01-to-soc2-cc3-2","source_ref":"control--ogrl-vm-01","target_ref":"requirement--soc2-tsc-2017-cc3-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Continuous vulnerability scanning identifies technical risks informing SOC 2 CC3.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc3-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc3-3","slug":"cc3-3","display_id":"CC3.3","name":"Fraud Risk Assessment","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC3.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-rm-03-to-soc2-cc3-3","source_ref":"control--ogrl-rm-03","target_ref":"requirement--soc2-tsc-2017-cc3-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Directly addresses consideration of fraud potential in risk assessment; the criterion's broader scope is not claimed.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc3-3.yaml"},{"id":"requirement--soc2-tsc-2017-cc3-4","slug":"cc3-4","display_id":"CC3.4","name":"Significant Change Identification","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC3.4","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-04-to-soc2-cc3-4","source_ref":"control--ogrl-cm-04","target_ref":"requirement--soc2-tsc-2017-cc3-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Analyzing the security impact of significant system changes partly addresses identifying risks from change under CC3.4.\n"},{"id":"mapping--ogrl-rm-05-to-soc2-cc3-4","source_ref":"control--ogrl-rm-05","target_ref":"requirement--soc2-tsc-2017-cc3-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Evaluates internal and external changes for their effect on risk and controls."}],"yaml_path":"library/requirement/soc2-tsc-2017/cc3-4.yaml"},{"id":"requirement--soc2-tsc-2017-cc4-1","slug":"cc4-1","display_id":"CC4.1","name":"Ongoing and Separate Evaluations","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC4.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-06-to-soc2-cc4-1","source_ref":"control--ogrl-gv-06","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Periodic metric reporting is a form of ongoing evaluation of whether controls are performing.\n"},{"id":"mapping--ogrl-gv-10-to-soc2-cc4-1","source_ref":"control--ogrl-gv-10","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Periodic independent assessment is a separate evaluation; ongoing evaluations are addressed by continuous monitoring.\n"},{"id":"mapping--ogrl-gv-11-to-soc2-cc4-1","source_ref":"control--ogrl-gv-11","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated checks are ongoing evaluations of control operation; separate evaluations are covered by periodic assessment.\n"},{"id":"mapping--ogrl-lm-04-to-soc2-cc4-1","source_ref":"control--ogrl-lm-04","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented recurring log reviews provide some ongoing evaluation evidence relevant to CC4.1.\n"},{"id":"mapping--ogrl-tp-04-to-soc2-cc4-1","source_ref":"control--ogrl-tp-04","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Evaluating third-party assurance reports is a form of ongoing evaluation of controls relevant to CC4.1.\n"},{"id":"mapping--ogrl-vm-05-to-soc2-cc4-1","source_ref":"control--ogrl-vm-05","target_ref":"requirement--soc2-tsc-2017-cc4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Independent penetration tests are a separate evaluation of control effectiveness relevant to CC4.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc4-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc4-2","slug":"cc4-2","display_id":"CC4.2","name":"Deficiency Communication and Remediation","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC4.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-12-to-soc2-cc4-2","source_ref":"control--ogrl-gv-12","target_ref":"requirement--soc2-tsc-2017-cc4-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recording, reviewing, and escalating deficiencies communicates them to the parties responsible for corrective action.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc4-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc5-1","slug":"cc5-1","display_id":"CC5.1","name":"Control Activity Selection and Development","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC5.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-08-to-soc2-cc5-1","source_ref":"control--ogrl-ac-08","target_ref":"requirement--soc2-tsc-2017-cc5-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Segregating incompatible duties is a control activity that mitigates risk under CC5.1.\n"},{"id":"mapping--ogrl-gv-01-to-soc2-cc5-1","source_ref":"control--ogrl-gv-01","target_ref":"requirement--soc2-tsc-2017-cc5-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The policy framework establishes the control activities intended to reduce risk; selection against assessed risk is addressed by risk controls.\n"},{"id":"mapping--ogrl-gv-10-to-soc2-cc5-1","source_ref":"control--ogrl-gv-10","target_ref":"requirement--soc2-tsc-2017-cc5-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Assessment results inform whether selected control activities adequately mitigate risk.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc5-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc5-2","slug":"cc5-2","display_id":"CC5.2","name":"Technology General Controls","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC5.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-02-to-soc2-cc5-2","source_ref":"control--ogrl-cm-02","target_ref":"requirement--soc2-tsc-2017-cc5-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Hardened baselines are a technology general control contributing to CC5.2."},{"id":"mapping--ogrl-sd-01-to-soc2-cc5-2","source_ref":"control--ogrl-sd-01","target_ref":"requirement--soc2-tsc-2017-cc5-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The SDLC is a technology general control over development, contributing to CC5.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc5-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc5-3","slug":"cc5-3","display_id":"CC5.3","name":"Policy and Procedure Deployment","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC5.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-gv-01-to-soc2-cc5-3","source_ref":"control--ogrl-gv-01","target_ref":"requirement--soc2-tsc-2017-cc5-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Approved and published policies are the vehicle through which control activities are deployed; implementing procedures sit in other controls.\n"},{"id":"mapping--ogrl-gv-09-to-soc2-cc5-3","source_ref":"control--ogrl-gv-09","target_ref":"requirement--soc2-tsc-2017-cc5-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The acceptable use policy is one of the policies through which expected behavior is put into practice.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc5-3.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-1","slug":"cc6-1","display_id":"CC6.1","name":"Logical Access Security Controls","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-03-to-soc2-cc6-1","source_ref":"control--ogrl-ac-03","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Least-privilege RBAC and access enforcement satisfy SOC 2 CC6.1 logical access security.\n"},{"id":"mapping--ogrl-ac-04-to-soc2-cc6-1","source_ref":"control--ogrl-ac-04","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Default-deny network restrictions form part of the logical access security architecture in CC6.1.\n"},{"id":"mapping--ogrl-ac-05-to-soc2-cc6-1","source_ref":"control--ogrl-ac-05","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Universal MFA strengthens authentication required by SOC 2 CC6.1."},{"id":"mapping--ogrl-ac-06-to-soc2-cc6-1","source_ref":"control--ogrl-ac-06","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Protecting secrets and credentials is part of the logical access safeguards in CC6.1.\n"},{"id":"mapping--ogrl-ac-07-to-soc2-cc6-1","source_ref":"control--ogrl-ac-07","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Restricting and monitoring administrative access contributes to logical access protection under CC6.1.\n"},{"id":"mapping--ogrl-ac-10-to-soc2-cc6-1","source_ref":"control--ogrl-ac-10","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Session lock and termination is one logical access safeguard within CC6.1.\n"},{"id":"mapping--ogrl-ac-11-to-soc2-cc6-1","source_ref":"control--ogrl-ac-11","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Authenticated, logged remote access gateways contribute to logical access security under CC6.1.\n"},{"id":"mapping--ogrl-ac-12-to-soc2-cc6-1","source_ref":"control--ogrl-ac-12","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Segregating customer data at the application layer is a logical access protection within CC6.1.\n"},{"id":"mapping--ogrl-ac-13-to-soc2-cc6-1","source_ref":"control--ogrl-ac-13","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Unique identities and centralized authentication are foundational logical access measures under CC6.1.\n"},{"id":"mapping--ogrl-ac-14-to-soc2-cc6-1","source_ref":"control--ogrl-ac-14","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Password strength and lockout settings are authentication safeguards within CC6.1.\n"},{"id":"mapping--ogrl-ac-15-to-soc2-cc6-1","source_ref":"control--ogrl-ac-15","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Customer authentication safeguards protect the service's logical access boundary under CC6.1.\n"},{"id":"mapping--ogrl-am-01-to-soc2-cc6-1","source_ref":"control--ogrl-am-01","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Knowing which components exist is a precondition for applying logical access protections to them.\n"},{"id":"mapping--ogrl-am-02-to-soc2-cc6-1","source_ref":"control--ogrl-am-02","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Classification informs which protections apply to each data store."},{"id":"mapping--ogrl-cm-05-to-soc2-cc6-1","source_ref":"control--ogrl-cm-05","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Limiting production change permissions is a logical access restriction over protected assets under CC6.1.\n"},{"id":"mapping--ogrl-cr-01-to-soc2-cc6-1","source_ref":"control--ogrl-cr-01","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Encryption at rest protects information assets as part of the logical access safeguards in CC6.1.\n"},{"id":"mapping--ogrl-cr-02-to-soc2-cc6-1","source_ref":"control--ogrl-cr-02","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Protecting encryption keys is one element of the logical access security measures this criterion covers.\n"},{"id":"mapping--ogrl-lm-03-to-soc2-cc6-1","source_ref":"control--ogrl-lm-03","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting access to audit logs is a logical access protection over an information asset under CC6.1.\n"},{"id":"mapping--ogrl-vm-06-to-soc2-cc6-1","source_ref":"control--ogrl-vm-06","target_ref":"requirement--soc2-tsc-2017-cc6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting access to managed, compliant devices is a logical access safeguard under CC6.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-2","slug":"cc6-2","display_id":"CC6.2","name":"User Registration and Provisioning","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-01-to-soc2-cc6-2","source_ref":"control--ogrl-ac-01","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Documented provisioning approval and prompt deprovisioning satisfy SOC 2 CC6.2."},{"id":"mapping--ogrl-ac-02-to-soc2-cc6-2","source_ref":"control--ogrl-ac-02","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Periodic review confirms registered users remain authorized, supporting the credential lifecycle in CC6.2.\n"},{"id":"mapping--ogrl-ac-09-to-soc2-cc6-2","source_ref":"control--ogrl-ac-09","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Removing dormant and temporary accounts supports deregistration of users who no longer need access under CC6.2.\n"},{"id":"mapping--ogrl-ac-13-to-soc2-cc6-2","source_ref":"control--ogrl-ac-13","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Central identity registration supports the user registration aspect of CC6.2; authorization and removal are other controls.\n"},{"id":"mapping--ogrl-hr-02-to-soc2-cc6-2","source_ref":"control--ogrl-hr-02","target_ref":"requirement--soc2-tsc-2017-cc6-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Removing credentials and access at separation and transfer contributes to CC6.2; account registration and authorization are covered elsewhere.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-3","slug":"cc6-3","display_id":"CC6.3","name":"Role-Based Access Modification and Removal","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-01-to-soc2-cc6-3","source_ref":"control--ogrl-ac-01","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Revoking or modifying access on termination and role change addresses the removal and modification aspects of CC6.3.\n"},{"id":"mapping--ogrl-ac-02-to-soc2-cc6-3","source_ref":"control--ogrl-ac-02","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Quarterly access reviews and timely entitlement removal satisfy SOC 2 CC6.3."},{"id":"mapping--ogrl-ac-03-to-soc2-cc6-3","source_ref":"control--ogrl-ac-03","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Role-based least privilege governs how access is granted and modified under CC6.3.\n"},{"id":"mapping--ogrl-ac-07-to-soc2-cc6-3","source_ref":"control--ogrl-ac-07","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Limiting privileged roles to approved individuals applies least privilege to the most sensitive access under CC6.3.\n"},{"id":"mapping--ogrl-ac-08-to-soc2-cc6-3","source_ref":"control--ogrl-ac-08","target_ref":"requirement--soc2-tsc-2017-cc6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Separation of duties is a consideration when authorizing and modifying role-based access under CC6.3.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-3.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-4","slug":"cc6-4","display_id":"CC6.4","name":"Physical Access Restriction","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.4","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ps-01-to-soc2-cc6-4","source_ref":"control--ogrl-ps-01","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Authorizing and reviewing who may enter facilities is one part of restricting physical access under CC6.4.\n"},{"id":"mapping--ogrl-ps-02-to-soc2-cc6-4","source_ref":"control--ogrl-ps-02","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Enforced entry at facility access points is a core piece of physical access restriction under CC6.4.\n"},{"id":"mapping--ogrl-ps-03-to-soc2-cc6-4","source_ref":"control--ogrl-ps-03","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Visitor logging and escort contribute to restricting physical access under CC6.4.\n"},{"id":"mapping--ogrl-ps-04-to-soc2-cc6-4","source_ref":"control--ogrl-ps-04","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Monitoring physical entry supports enforcement of facility access restrictions under CC6.4.\n"},{"id":"mapping--ogrl-ps-06-to-soc2-cc6-4","source_ref":"control--ogrl-ps-06","target_ref":"requirement--soc2-tsc-2017-cc6-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Controlling equipment entering and leaving facilities contributes to physical protection under CC6.4.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-4.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-5","slug":"cc6-5","display_id":"CC6.5","name":"Asset Disposal and Data Removal","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.5","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-03-to-soc2-cc6-5","source_ref":"control--ogrl-cr-03","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Logical data disposal contributes to removing the ability to recover data before assets are retired, though physical media handling is addressed elsewhere.\n"},{"id":"mapping--ogrl-cr-04-to-soc2-cc6-5","source_ref":"control--ogrl-cr-04","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Sanitizing media before disposal ensures data cannot be recovered from retired assets.\n"},{"id":"mapping--ogrl-hr-02-to-soc2-cc6-5","source_ref":"control--ogrl-hr-02","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recovering and sanitizing devices from departing personnel contributes to CC6.5 but does not cover general asset disposal.\n"},{"id":"mapping--ogrl-ps-06-to-soc2-cc6-5","source_ref":"control--ogrl-ps-06","target_ref":"requirement--soc2-tsc-2017-cc6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Approved, recorded removal of components supports control over assets leaving the organization under CC6.5.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-5.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-6","slug":"cc6-6","display_id":"CC6.6","name":"Logical Boundary Protection","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.6","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ac-04-to-soc2-cc6-6","source_ref":"control--ogrl-ac-04","target_ref":"requirement--soc2-tsc-2017-cc6-6","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Default-deny network boundaries and restricted admin paths satisfy SOC 2 CC6.6."},{"id":"mapping--ogrl-ac-11-to-soc2-cc6-6","source_ref":"control--ogrl-ac-11","target_ref":"requirement--soc2-tsc-2017-cc6-6","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Controlling remote access paths into production protects against threats from outside system boundaries under CC6.6.\n"},{"id":"mapping--ogrl-bc-09-to-soc2-cc6-6","source_ref":"control--ogrl-bc-09","target_ref":"requirement--soc2-tsc-2017-cc6-6","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"DoS mitigation at public endpoints is a boundary protection against threats from outside the system.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-6.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-7","slug":"cc6-7","display_id":"CC6.7","name":"Transmission and Encryption Safeguards","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.7","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-01-to-soc2-cc6-7","source_ref":"control--ogrl-cr-01","target_ref":"requirement--soc2-tsc-2017-cc6-7","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"TLS in transit and encryption at rest satisfy SOC 2 CC6.7 transmission and data protection.\n"},{"id":"mapping--ogrl-vm-06-to-soc2-cc6-7","source_ref":"control--ogrl-vm-06","target_ref":"requirement--soc2-tsc-2017-cc6-7","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Encrypted, remotely wipeable devices protect information held on endpoints, overlapping CC6.7.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-7.yaml"},{"id":"requirement--soc2-tsc-2017-cc6-8","slug":"cc6-8","display_id":"CC6.8","name":"Unauthorized and Malicious Software Prevention","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC6.8","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-08-to-soc2-cc6-8","source_ref":"control--ogrl-cm-08","target_ref":"requirement--soc2-tsc-2017-cc6-8","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting software installation and unneeded functionality helps prevent unauthorized software under CC6.8.\n"},{"id":"mapping--ogrl-cm-09-to-soc2-cc6-8","source_ref":"control--ogrl-cm-09","target_ref":"requirement--soc2-tsc-2017-cc6-8","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Blocking unsigned or tampered software helps prevent unauthorized or malicious software under CC6.8.\n"},{"id":"mapping--ogrl-vm-03-to-soc2-cc6-8","source_ref":"control--ogrl-vm-03","target_ref":"requirement--soc2-tsc-2017-cc6-8","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Anti-malware detection and quarantine help prevent and detect malicious software under CC6.8.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc6-8.yaml"},{"id":"requirement--soc2-tsc-2017-cc7-1","slug":"cc7-1","display_id":"CC7.1","name":"Vulnerability and Configuration Detection","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC7.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-02-to-soc2-cc7-1","source_ref":"control--ogrl-cm-02","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Defined secure configuration standards are one input to the configuration and vulnerability monitoring expected under CC7.1.\n"},{"id":"mapping--ogrl-cm-03-to-soc2-cc7-1","source_ref":"control--ogrl-cm-03","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Detecting configuration changes that depart from approved baselines is a monitoring activity within CC7.1.\n"},{"id":"mapping--ogrl-gv-11-to-soc2-cc7-1","source_ref":"control--ogrl-gv-11","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Automated configuration checks detect drift that could introduce vulnerabilities.\n"},{"id":"mapping--ogrl-sd-03-to-soc2-cc7-1","source_ref":"control--ogrl-sd-03","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Pre-merge scanning identifies vulnerabilities introduced by new code, overlapping CC7.1 detection activities.\n"},{"id":"mapping--ogrl-vm-01-to-soc2-cc7-1","source_ref":"control--ogrl-vm-01","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Vulnerability scanning and SLA remediation satisfy SOC 2 CC7.1 detection obligations.\n"},{"id":"mapping--ogrl-vm-02-to-soc2-cc7-1","source_ref":"control--ogrl-vm-02","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Timely patching remediates the vulnerabilities that CC7.1 monitoring identifies."},{"id":"mapping--ogrl-vm-04-to-soc2-cc7-1","source_ref":"control--ogrl-vm-04","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Monitoring external advisories helps identify newly discovered vulnerabilities under CC7.1.\n"},{"id":"mapping--ogrl-vm-05-to-soc2-cc7-1","source_ref":"control--ogrl-vm-05","target_ref":"requirement--soc2-tsc-2017-cc7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Penetration testing identifies vulnerabilities as part of CC7.1 detection activities.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc7-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc7-2","slug":"cc7-2","display_id":"CC7.2","name":"System Anomaly and Event Monitoring","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC7.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-01-to-soc2-cc7-2","source_ref":"control--ogrl-lm-01","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Centralized security audit logging supplies telemetry required for SOC 2 CC7.2 monitoring.\n"},{"id":"mapping--ogrl-lm-02-to-soc2-cc7-2","source_ref":"control--ogrl-lm-02","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Continuous security monitoring and anomaly detection satisfy SOC 2 CC7.2."},{"id":"mapping--ogrl-lm-03-to-soc2-cc7-2","source_ref":"control--ogrl-lm-03","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Trustworthy, tamper-resistant logs underpin the anomaly monitoring expected under CC7.2.\n"},{"id":"mapping--ogrl-lm-04-to-soc2-cc7-2","source_ref":"control--ogrl-lm-04","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Periodic analysis of audit logs for anomalies is a monitoring activity under CC7.2.\n"},{"id":"mapping--ogrl-ps-04-to-soc2-cc7-2","source_ref":"control--ogrl-ps-04","target_ref":"requirement--soc2-tsc-2017-cc7-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Physical access monitoring is one source of anomaly detection relevant to CC7.2, which is broader.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc7-2.yaml"},{"id":"requirement--soc2-tsc-2017-cc7-3","slug":"cc7-3","display_id":"CC7.3","name":"Security Event Evaluation and Triage","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC7.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-01-to-soc2-cc7-3","source_ref":"control--ogrl-ir-01","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Incident response playbooks and exercises support event evaluation and response under SOC 2 CC7.3.\n"},{"id":"mapping--ogrl-ir-02-to-soc2-cc7-3","source_ref":"control--ogrl-ir-02","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Triage and severity classification determine whether security events are incidents requiring response.\n"},{"id":"mapping--ogrl-ir-03-to-soc2-cc7-3","source_ref":"control--ogrl-ir-03","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented incident records evidence how security events were evaluated and classified.\n"},{"id":"mapping--ogrl-lm-04-to-soc2-cc7-3","source_ref":"control--ogrl-lm-04","target_ref":"requirement--soc2-tsc-2017-cc7-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documenting and escalating log review findings feeds the evaluation of security events under CC7.3.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc7-3.yaml"},{"id":"requirement--soc2-tsc-2017-cc7-4","slug":"cc7-4","display_id":"CC7.4","name":"Incident Response Execution","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC7.4","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-01-to-soc2-cc7-4","source_ref":"control--ogrl-ir-01","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A documented, tested response plan defines how identified incidents are responded to under CC7.4.\n"},{"id":"mapping--ogrl-ir-02-to-soc2-cc7-4","source_ref":"control--ogrl-ir-02","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Containment, eradication, and recovery steps form the core of the organization's incident response activity.\n"},{"id":"mapping--ogrl-ir-03-to-soc2-cc7-4","source_ref":"control--ogrl-ir-03","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Incident records capture the response actions taken, supporting a defined and evidenced response process.\n"},{"id":"mapping--ogrl-ir-04-to-soc2-cc7-4","source_ref":"control--ogrl-ir-04","target_ref":"requirement--soc2-tsc-2017-cc7-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Internal escalation and external notification are part of responding to identified incidents.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc7-4.yaml"},{"id":"requirement--soc2-tsc-2017-cc7-5","slug":"cc7-5","display_id":"CC7.5","name":"Incident Recovery","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC7.5","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-01-to-soc2-cc7-5","source_ref":"control--ogrl-bc-01","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Documented recovery procedures and priorities guide restoration after incidents."},{"id":"mapping--ogrl-bc-03-to-soc2-cc7-5","source_ref":"control--ogrl-bc-03","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Backups provide the data needed to restore systems when recovering from incidents.\n"},{"id":"mapping--ogrl-bc-06-to-soc2-cc7-5","source_ref":"control--ogrl-bc-06","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Restoring systems to a secure state is the recovery activity following an incident.\n"},{"id":"mapping--ogrl-ir-05-to-soc2-cc7-5","source_ref":"control--ogrl-ir-05","target_ref":"requirement--soc2-tsc-2017-cc7-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Root-cause analysis and tracked improvements after incidents support recovery and prevention of recurrence.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc7-5.yaml"},{"id":"requirement--soc2-tsc-2017-cc8-1","slug":"cc8-1","display_id":"CC8.1","name":"Change Management Authorization and Testing","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC8.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cm-01-to-soc2-cc8-1","source_ref":"control--ogrl-cm-01","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"equivalent-to","review_status":"reviewed","parameter_map":null,"summary":"Peer-reviewed and CI-verified production change control directly satisfies SOC 2 CC8.1.\n"},{"id":"mapping--ogrl-cm-03-to-soc2-cc8-1","source_ref":"control--ogrl-cm-03","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Drift detection surfaces changes made outside the authorized change process, supporting CC8.1.\n"},{"id":"mapping--ogrl-cm-04-to-soc2-cc8-1","source_ref":"control--ogrl-cm-04","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Security impact analysis of significant changes is part of designing and authorizing changes under CC8.1.\n"},{"id":"mapping--ogrl-cm-05-to-soc2-cc8-1","source_ref":"control--ogrl-cm-05","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting who can implement production changes supports the authorized change process under CC8.1.\n"},{"id":"mapping--ogrl-cm-06-to-soc2-cc8-1","source_ref":"control--ogrl-cm-06","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"An authorized, documented, and retrospectively reviewed emergency path is part of change management under CC8.1.\n"},{"id":"mapping--ogrl-cm-07-to-soc2-cc8-1","source_ref":"control--ogrl-cm-07","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Pre-production testing in separated environments is part of the change process under CC8.1.\n"},{"id":"mapping--ogrl-sd-01-to-soc2-cc8-1","source_ref":"control--ogrl-sd-01","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A secure SDLC governs how changes are designed and developed, contributing to CC8.1.\n"},{"id":"mapping--ogrl-sd-02-to-soc2-cc8-1","source_ref":"control--ogrl-sd-02","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Security review of high-risk code before merge is part of authorizing and testing changes under CC8.1.\n"},{"id":"mapping--ogrl-sd-03-to-soc2-cc8-1","source_ref":"control--ogrl-sd-03","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Automated security testing gates contribute to testing changes before implementation under CC8.1.\n"},{"id":"mapping--ogrl-sd-04-to-soc2-cc8-1","source_ref":"control--ogrl-sd-04","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Protected, versioned source control enforces the authorized path for changes under CC8.1.\n"},{"id":"mapping--ogrl-vm-02-to-soc2-cc8-1","source_ref":"control--ogrl-vm-02","target_ref":"requirement--soc2-tsc-2017-cc8-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Patches are tested and deployed as controlled changes, contributing to CC8.1."}],"yaml_path":"library/requirement/soc2-tsc-2017/cc8-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc9-1","slug":"cc9-1","display_id":"CC9.1","name":"Business Disruption Risk Mitigation","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC9.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-bc-01-to-soc2-cc9-1","source_ref":"control--ogrl-bc-01","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"A continuity plan is a primary risk mitigation activity for potential business disruptions.\n"},{"id":"mapping--ogrl-bc-07-to-soc2-cc9-1","source_ref":"control--ogrl-bc-07","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Understanding the impact of disruption informs selection of business disruption risk mitigation activities.\n"},{"id":"mapping--ogrl-rm-01-to-soc2-cc9-1","source_ref":"control--ogrl-rm-01","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Defined treatment options, including transfer, frame how disruption risks are mitigated.\n"},{"id":"mapping--ogrl-rm-04-to-soc2-cc9-1","source_ref":"control--ogrl-rm-04","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Treatment decisions mitigate identified risks, including risks of business disruption.\n"},{"id":"mapping--ogrl-rm-06-to-soc2-cc9-1","source_ref":"control--ogrl-rm-06","target_ref":"requirement--soc2-tsc-2017-cc9-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Insurance is a risk transfer mechanism for losses from business disruption."}],"yaml_path":"library/requirement/soc2-tsc-2017/cc9-1.yaml"},{"id":"requirement--soc2-tsc-2017-cc9-2","slug":"cc9-2","display_id":"CC9.2","name":"Vendor and Business Partner Risk Management","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC CC9.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-hr-04-to-soc2-cc9-2","source_ref":"control--ogrl-hr-04","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Imposing personnel security obligations on providers addresses one dimension of vendor risk management under CC9.2.\n"},{"id":"mapping--ogrl-tp-01-to-soc2-cc9-2","source_ref":"control--ogrl-tp-01","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Identifying vendors and tiering their risk is the starting point for vendor risk management under CC9.2.\n"},{"id":"mapping--ogrl-tp-02-to-soc2-cc9-2","source_ref":"control--ogrl-tp-02","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Assessing vendor security before engagement is a key vendor risk management activity under CC9.2.\n"},{"id":"mapping--ogrl-tp-03-to-soc2-cc9-2","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Contractual security requirements are a primary means of managing vendor risk under CC9.2.\n"},{"id":"mapping--ogrl-tp-04-to-soc2-cc9-2","source_ref":"control--ogrl-tp-04","target_ref":"requirement--soc2-tsc-2017-cc9-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Ongoing review of vendor assurance reports is a vendor monitoring activity under CC9.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/cc9-2.yaml"},{"id":"requirement--soc2-tsc-2017-p1-1","slug":"p1-1","display_id":"P1.1","name":"Privacy Notice","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P1.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-01-to-soc2-p1-1","source_ref":"control--ogrl-pr-01","target_ref":"requirement--soc2-tsc-2017-p1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Publishing and maintaining a privacy notice addresses the notice obligations in P1.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p1-1.yaml"},{"id":"requirement--soc2-tsc-2017-p2-1","slug":"p2-1","display_id":"P2.1","name":"Choice and Consent","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P2.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-02-to-soc2-p2-1","source_ref":"control--ogrl-pr-02","target_ref":"requirement--soc2-tsc-2017-p2-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Obtaining and recording consent addresses the choice and consent obligations in P2.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p2-1.yaml"},{"id":"requirement--soc2-tsc-2017-p3-1","slug":"p3-1","display_id":"P3.1","name":"Collection Limited to Stated Purposes","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P3.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-03-to-soc2-p3-1","source_ref":"control--ogrl-pr-03","target_ref":"requirement--soc2-tsc-2017-p3-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Limiting collection to documented purposes overlaps the collection objectives in P3.1.\n"},{"id":"mapping--ogrl-pr-04-to-soc2-p3-1","source_ref":"control--ogrl-pr-04","target_ref":"requirement--soc2-tsc-2017-p3-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Collecting only necessary PII elements addresses P3.1."}],"yaml_path":"library/requirement/soc2-tsc-2017/p3-1.yaml"},{"id":"requirement--soc2-tsc-2017-p3-2","slug":"p3-2","display_id":"P3.2","name":"Explicit Consent for Collection","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P3.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-02-to-soc2-p3-2","source_ref":"control--ogrl-pr-02","target_ref":"requirement--soc2-tsc-2017-p3-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Separate explicit consent for sensitive categories addresses P3.2."}],"yaml_path":"library/requirement/soc2-tsc-2017/p3-2.yaml"},{"id":"requirement--soc2-tsc-2017-p4-1","slug":"p4-1","display_id":"P4.1","name":"Use Limited to Stated Purposes","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P4.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-03-to-soc2-p4-1","source_ref":"control--ogrl-pr-03","target_ref":"requirement--soc2-tsc-2017-p4-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Restricting use to documented purposes addresses the use limitation in P4.1."},{"id":"mapping--ogrl-pr-04-to-soc2-p4-1","source_ref":"control--ogrl-pr-04","target_ref":"requirement--soc2-tsc-2017-p4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Minimizing processed elements supports limiting use of personal information under P4.1.\n"},{"id":"mapping--ogrl-pr-05-to-soc2-p4-1","source_ref":"control--ogrl-pr-05","target_ref":"requirement--soc2-tsc-2017-p4-1","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Recording purposes and recipients per activity enables but does not enforce use limitation under P4.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p4-1.yaml"},{"id":"requirement--soc2-tsc-2017-p4-2","slug":"p4-2","display_id":"P4.2","name":"Retention of Personal Information","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P4.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-03-to-soc2-p4-2","source_ref":"control--ogrl-cr-03","target_ref":"requirement--soc2-tsc-2017-p4-2","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The retention schedule governs how long personal information is kept."}],"yaml_path":"library/requirement/soc2-tsc-2017/p4-2.yaml"},{"id":"requirement--soc2-tsc-2017-p4-3","slug":"p4-3","display_id":"P4.3","name":"Disposal of Personal Information","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P4.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-04-to-soc2-p4-3","source_ref":"control--ogrl-cr-04","target_ref":"requirement--soc2-tsc-2017-p4-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Media sanitization is one mechanism for securely disposing of personal information.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p4-3.yaml"},{"id":"requirement--soc2-tsc-2017-p5-1","slug":"p5-1","display_id":"P5.1","name":"Data Subject Access","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P5.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-06-to-soc2-p5-1","source_ref":"control--ogrl-pr-06","target_ref":"requirement--soc2-tsc-2017-p5-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Verified, timely access-request fulfillment addresses individual access under P5.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p5-1.yaml"},{"id":"requirement--soc2-tsc-2017-p5-2","slug":"p5-2","display_id":"P5.2","name":"Correction of Personal Information","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P5.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-07-to-soc2-p5-2","source_ref":"control--ogrl-pr-07","target_ref":"requirement--soc2-tsc-2017-p5-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Correction handling with recipient notification and denial reasons addresses P5.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p5-2.yaml"},{"id":"requirement--soc2-tsc-2017-p6-1","slug":"p6-1","display_id":"P6.1","name":"Disclosure to Third Parties","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-08-to-soc2-p6-1","source_ref":"control--ogrl-pr-08","target_ref":"requirement--soc2-tsc-2017-p6-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Authorizing third-party disclosures against notice, consent, and contract addresses P6.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-1.yaml"},{"id":"requirement--soc2-tsc-2017-p6-2","slug":"p6-2","display_id":"P6.2","name":"Authorized Disclosure Records","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-09-to-soc2-p6-2","source_ref":"control--ogrl-pr-09","target_ref":"requirement--soc2-tsc-2017-p6-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Logging disclosures with date, purpose, and recipient addresses P6.2."}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-2.yaml"},{"id":"requirement--soc2-tsc-2017-p6-3","slug":"p6-3","display_id":"P6.3","name":"Unauthorized Disclosure Records","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-06-to-soc2-p6-3","source_ref":"control--ogrl-ir-06","target_ref":"requirement--soc2-tsc-2017-p6-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The breach register keeps a record of detected or reported breaches of personal information.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-3.yaml"},{"id":"requirement--soc2-tsc-2017-p6-4","slug":"p6-4","display_id":"P6.4","name":"Third-Party Privacy Commitments","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.4","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-03-to-soc2-p6-4","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-p6-4","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Data protection terms bind vendors with access to personal information to privacy obligations relevant to P6.4.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-4.yaml"},{"id":"requirement--soc2-tsc-2017-p6-5","slug":"p6-5","display_id":"P6.5","name":"Third-Party Breach Notification","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.5","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-tp-03-to-soc2-p6-5","source_ref":"control--ogrl-tp-03","target_ref":"requirement--soc2-tsc-2017-p6-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Required vendor notification of unauthorized disclosures supports P6.5.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-5.yaml"},{"id":"requirement--soc2-tsc-2017-p6-6","slug":"p6-6","display_id":"P6.6","name":"Breach Notification to Data Subjects and Regulators","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.6","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-ir-06-to-soc2-p6-6","source_ref":"control--ogrl-ir-06","target_ref":"requirement--soc2-tsc-2017-p6-6","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Timely breach notification to affected individuals and regulators addresses the notification aspect of this criterion.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-6.yaml"},{"id":"requirement--soc2-tsc-2017-p6-7","slug":"p6-7","display_id":"P6.7","name":"Disclosure Accounting","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P6.7","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-05-to-soc2-p6-7","source_ref":"control--ogrl-pr-05","target_ref":"requirement--soc2-tsc-2017-p6-7","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"The inventory supplies the data needed to tell individuals what is held and shared, supporting P6.7.\n"},{"id":"mapping--ogrl-pr-09-to-soc2-p6-7","source_ref":"control--ogrl-pr-09","target_ref":"requirement--soc2-tsc-2017-p6-7","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Providing individuals their disclosure record covers the disclosure portion of P6.7.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p6-7.yaml"},{"id":"requirement--soc2-tsc-2017-p7-1","slug":"p7-1","display_id":"P7.1","name":"Personal Information Quality","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P7.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-10-to-soc2-p7-1","source_ref":"control--ogrl-pr-10","target_ref":"requirement--soc2-tsc-2017-p7-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Validating and correcting personal information addresses data quality under P7.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p7-1.yaml"},{"id":"requirement--soc2-tsc-2017-p8-1","slug":"p8-1","display_id":"P8.1","name":"Privacy Inquiries, Complaints, and Disputes","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC P8.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-pr-11-to-soc2-p8-1","source_ref":"control--ogrl-pr-11","target_ref":"requirement--soc2-tsc-2017-p8-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Tracked intake and timely response to privacy inquiries and complaints addresses P8.1.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/p8-1.yaml"},{"id":"requirement--soc2-tsc-2017-pi1-1","slug":"pi1-1","display_id":"PI1.1","name":"Processing Specifications Definition","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC PI1.1","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-05-to-soc2-pi1-1","source_ref":"control--ogrl-sd-05","target_ref":"requirement--soc2-tsc-2017-pi1-1","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Documented data definitions and processing specifications support PI1.1."}],"yaml_path":"library/requirement/soc2-tsc-2017/pi1-1.yaml"},{"id":"requirement--soc2-tsc-2017-pi1-2","slug":"pi1-2","display_id":"PI1.2","name":"Input Controls","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC PI1.2","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-06-to-soc2-pi1-2","source_ref":"control--ogrl-sd-06","target_ref":"requirement--soc2-tsc-2017-pi1-2","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Validating inputs for completeness and accuracy before processing contributes to PI1.2.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/pi1-2.yaml"},{"id":"requirement--soc2-tsc-2017-pi1-3","slug":"pi1-3","display_id":"PI1.3","name":"Processing Controls","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC PI1.3","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-lm-05-to-soc2-pi1-3","source_ref":"control--ogrl-lm-05","target_ref":"requirement--soc2-tsc-2017-pi1-3","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Monitoring processing completion and reconciling volumes supports complete and accurate processing under PI1.3.\n"},{"id":"mapping--ogrl-sd-07-to-soc2-pi1-3","source_ref":"control--ogrl-sd-07","target_ref":"requirement--soc2-tsc-2017-pi1-3","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Rolling back or queuing failed transactions for correction supports complete and accurate processing under PI1.3.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/pi1-3.yaml"},{"id":"requirement--soc2-tsc-2017-pi1-4","slug":"pi1-4","display_id":"PI1.4","name":"Output Controls","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC PI1.4","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-sd-08-to-soc2-pi1-4","source_ref":"control--ogrl-sd-08","target_ref":"requirement--soc2-tsc-2017-pi1-4","relationship":"subset-of","review_status":"reviewed","parameter_map":null,"summary":"Output validation and restricted delivery support complete, accurate, and properly distributed outputs under PI1.4.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/pi1-4.yaml"},{"id":"requirement--soc2-tsc-2017-pi1-5","slug":"pi1-5","display_id":"PI1.5","name":"Data Storage Integrity","framework_id":"framework--soc2-tsc-2017","framework_slug":"soc2-tsc-2017","class":"criterion","withdrawn":false,"statement":null,"citation":"AICPA TSC PI1.5","parts":[],"objectives_count":0,"objectives_preview":[],"params_count":0,"mappings":[],"incoming_mappings":[{"id":"mapping--ogrl-cr-05-to-soc2-pi1-5","source_ref":"control--ogrl-cr-05","target_ref":"requirement--soc2-tsc-2017-pi1-5","relationship":"intersects-with","review_status":"reviewed","parameter_map":null,"summary":"Integrity verification and replication help keep stored data complete and accurate over time.\n"}],"yaml_path":"library/requirement/soc2-tsc-2017/pi1-5.yaml"}]}