EvidenceSheet
CIS Controls v8.1 · CIS Control 13: Network Monitoring and Defense

13.10 Perform Application Layer Filtering

Inspect and filter traffic at layer 7, for instance with a web proxy that filters, an application firewall or a filtering gateway. Implementation Group: IG3 only (for enterprises facing sophisticated attackers or holding highly sensitive data). Asset type: Network. Security function: Protect.

Source: CIS Controls v8.1, 13.10. 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: Network.

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
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
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

  • Proxy, WAF or next-generation firewall application policy · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Policy review records · Cloud console / configuration management

governing documentDocuments that govern the control

  • Coverage of key traffic flows · Policy repository / GRC workspace

First move

Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.

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

13.9 Deploy Port-Level Access Control · 13.11 Tune Security Event Alerting Thresholds