FedRAMP High SA-1: Policy and Procedures

What else in your programme already covers this

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

SOC 2 · 5 controls

SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

CIS Controls v8 · 4 controls

CIS-8.1 Establish and Maintain an Audit Log Management Process
CIS-8.10 Retain Audit Logs
CIS-8.11 Conduct Audit Log Reviews
CIS-8.2 Collect Audit Logs

ISO 27001:2022 · 4 controls

5.24 Information security incident management planning and preparation
5.25 Assessment and decision on information security events
8.15 Logging
8.16 Monitoring activities

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AU-11 AU-11 Audit Record Retention
NIST800-AU-2 AU-2 Event Logging
NIST800-AU-6 AU-6 Audit Record Review, Analysis, and Reporting
NIST800-IR-5 IR-5 Incident Monitoring

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

CCM-LOG-01 Logging and Monitoring Policy and Procedures
CCM-LOG-02 Audit Logs Protection
CCM-LOG-05 Audit Logs Monitoring and Response

Azure Security Benchmark · 1 control

ASBv3-GS-10 Define and implement DevOps security strategy

C5 (Germany) · 1 control

C5-DEV-01 Policies for the development/procurement of information systems

HIPAA Security Rule · 1 control

164.308(a)(1)(ii)(D) Information System Activity Review (Required)

NIST SP 800-161 Rev 1 · 1 control

161R1-SA-1 Policy and Procedures

NIST SP 800-171 Rev 3 · 1 control

03.15.01 Policy and Procedures

NIST SP 800-218 · 1 control

SP800-218-PO.2.3 Obtain Management Commitment to Secure Development

NIST SP 800-53 Rev 5 HIGH · 1 control

SA-1 SA-1 Policy and Procedures

NIST SP 800-53 Rev 5 LOW · 1 control

SA-1 SA-1 Policy and Procedures

NIST SP 800-53 Rev 5 MODERATE · 1 control

SA-1 SA-1 Policy and Procedures

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(1)(ii)(D) Information System Activity Review (Required)

PCI DSS 4.0 · 1 control

10.2.1 10.2.1 Audit logging enabled on all system components

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

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

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

If you hold C5 (Germany)29% covered · 291 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.

See the released pairs, $299 each Browse the graph free