I&S-09 Network Defense
Define, put in place and assess processes, procedures and layered defensive techniques to protect against, detect and respond promptly to network-based attacks.
Source: CSA CCM v4.1, I&S-09. 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 CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
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
- IDS or IPS alert records and response tickets · SIEM / log platform
periodic reviewEvidence produced at each review
- DDoS response runbook and test results · Source control / CI pipeline
- Periodic evaluation report of network defence effectiveness · Cloud console / configuration management
governing documentDocuments that govern the control
- Network defence architecture showing layered controls (WAF, DDoS protection, IDS/IPS, segmentation) · Policy repository / GRC workspace
First move
Common gaps auditors find
- Single perimeter control with no internal detection
- Alerts generated but not triaged in time
- DDoS plan never exercised
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 sheetI&S-08 Network Architecture Documentation · IAM-01 Identity and Access Management Policy and Procedures