CIS Controls v8 CIS-16.12: Implement Code-Level Security Checks

What else in your programme already covers this

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

NIST SP 800-218 · 7 controls

SP800-218-PO.1.2 Implement Security Requirements in the Toolchain
SP800-218-PW.4.4 Verify Acquired Components Meet Security Requirements
SP800-218-PW.7.1 Code Review
SP800-218-PW.7.2 Perform Code Review and Analysis
SP800-218-PW.8.1 Executable Testing for Security
SP800-218-PW.8.2 Execute Security Testing
SP800-218-RV.1.2 Review and Analyze Code for Vulnerabilities

NIST SP 800-53 Rev 5 · 6 controls

NIST800-SA-11 SA-11 Developer Testing and Evaluation
NIST800-SA-15 SA-15 Development Process, Standards, and Tools
NIST800-SA-20 SA-20 Customized Development of Critical Components
NIST800-SC-38 SC-38 Operations Security
NIST800-SI-10 SI-10 Information Input Validation
NIST800-SI-6 SI-6 Security and Privacy Function Verification

PCI DSS 4.0 · 5 controls

6.2.1 6.2.1 Secure development of bespoke and custom software
6.2.3 6.2.3 Code review before release
6.2.3.1 6.2.3.1 Manual code review independence and approval
6.2.4 6.2.4 Engineering techniques against common software attacks
6.3.1 6.3.1 Vulnerability identification and risk ranking

Azure Security Benchmark · 4 controls

ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
ASBv3-IM-8 Restrict the exposure of credential and secrets
DS-6 Enforce security of workload throughout DevOps lifecycle

FedRAMP High · 4 controls

CM-3(2) Testing, Validation, and Documentation of Changes
SA-11 Developer Testing and Evaluation
SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
SI-10 Information Input Validation

FedRAMP Moderate · 4 controls

CM-3(2) Testing, Validation, and Documentation of Changes
SA-11 Developer Testing and Evaluation
SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
SI-10 Information Input Validation

ISO 27001:2022 · 4 controls

8.25 Secure development life cycle
8.28 Secure coding
8.29 Security testing in development and acceptance
8.4 Access to source code

Australian Information Security Manual · 3 controls

ISM-0402 SAST, DAST and SCA testing
ISM-2028 Testing software artefacts for known weaknesses
ISM-2102 Periodic weakness testing of software artefacts

ISO 27002:2022 · 3 controls

8.25 Secure development life cycle
8.28 Secure coding
8.29 Security testing in development and acceptance

AWS Well-Architected Security Pillar · 2 controls

SEC11-BP02 Automate testing throughout the development and release lifecycle
SEC11-BP04 Conduct code reviews

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

CCM-AIS-05 Automated Application Security Testing
CCM-CCC-02 Quality Testing

ISO 27701:2019 · 2 controls

6.11 Systems acquisition, development and maintenance
6.11.2 Security in development and support processes

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-4 Formal vulnerability management program

C5 (Germany) · 1 control

C5-DEV-06 Testing changes

CIS Controls v8.1 · 1 control

16.12 Implement Code-Level Security Checks

NIST Cybersecurity Framework 2.0 · 1 control

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-172 · 1 control

3.14.7e Verify Correctness of Security Functions

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 CIS Controls v8 have you already done?

CIS Controls v8 CIS-16.12 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gaps If you hold FedRAMP Moderate62.7% covered · 57 gaps If you hold NIST SP 800-53 Rev 557.5% covered · 65 gaps If you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gaps If you hold ISO 27002:202249.7% covered · 77 gaps If you hold Azure Security Benchmark49% covered · 78 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. 240 were rejected on the ISO 27001:2022 pair alone.

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