NIST SP 800-53 Rev 5 NIST800-SC-38: SC-38 Operations Security

What else in your programme already covers this

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

ISO 27701:2019 · 6 controls

5.6 Operation
6.11.2 Security in development and support processes
6.9 Operations security
6.9.1 Operational procedures and responsibilities
6.9.4 Logging and monitoring
6.9.6 Technical vulnerability management

CIS Controls v8 · 5 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.12 Implement Code-Level Security Checks
CIS-16.14 Conduct Threat Modeling
CIS-16.8 Separate Production and Non-Production Systems
CIS-3.7 Establish and Maintain a Data Classification Scheme

HIPAA Security Rule · 4 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(1)(ii)(B) Risk Management (Required)
164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable)
164.312(b) Audit Controls (Standard)

ISO 27001:2022 · 4 controls

8.15 Logging
8.25 Secure development life cycle
8.31 Separation of development, test and production environments
8.32 Change management

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
NIST-CSF-PR.DS-11 Backups of data are created, protected, maintained, and tested
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-66 Rev 2 · 4 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(1)(ii)(B) Risk Management (Required)
164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable)
164.312(b) Audit Controls (Standard)

SOC 2 · 4 controls

SOC2-C1.1 C1.1 Identifying and maintaining confidential information
SOC2-C1.2 C1.2 Disposing of confidential information
SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

PCI DSS 4.0 · 3 controls

6.2.1 6.2.1 Secure development of bespoke and custom software
6.5.1 6.5.1 Change control procedure for production
6.5.2 6.5.2 Confirm PCI DSS controls after significant change

NIST SP 800-161 Rev 1 · 2 controls

161R1-SC-38 Operations Security
161R1-SR-7 Supply Chain Operations Security

ISO 27002:2022 · 1 control

8.29 Security testing in development and acceptance

ISO/IEC 42001:2023 · 1 control

A.6.2.6 AI system operation and monitoring

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 NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-SC-38 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202216.1% covered · 851 gaps If you hold ISO 27002:202210.8% covered · 904 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.110.2% covered · 911 gaps If you hold CIS Controls v810.1% covered · 912 gaps If you hold NIST SP 800-171 Rev 310.1% covered · 912 gaps If you hold C5 (Germany)9.6% covered · 917 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. 342 were rejected on the ISO 27001:2022 pair alone.

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