EvidenceSheet
CIS Controls v8.1 · CIS Control 16: Application Software Security

16.12 Implement Code-Level Security Checks

Use static and dynamic analysis tools across the application life cycle to confirm secure coding practices are being followed. Implementation Group: IG3 only (for enterprises facing sophisticated attackers or holding highly sensitive data). Asset type: Software. Security function: Protect.

Source: CIS Controls v8.1, 16.12. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CIS Controls v8.1 in the compliance library.

Scope: Implementation Groups: IG3. Security function: Protect; asset type: Software.

Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.

3
artefacts
2
held by a system
0
at each review
easy
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • SAST and DAST tool configuration in CI/CD pipelines · Source control / CI pipeline
  • Scan results and triage records · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Build gates on high-severity findings · Policy repository / GRC workspace

First move

Automate the pull from your Source control / CI pipeline. Pull-request approvals, pipeline test results and deployment records from source control, per release.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

16.11 Leverage Vetted Modules or Services for Application Security Components · 16.13 Conduct Application Penetration Testing