What evidence do auditors commonly ask for on I&S-08 Network Architecture Documentation?

Network architecture diagrams marking high-risk environments; Criteria for classing an environment as high risk (data sensitivity, exposure, business impact); Inventory of high-risk environments with review dates; Risk assessment records supporting the classification.

What is the most common gap auditors find on I&S-08?

Diagrams outdated after cloud expansion

CSA CCM v4.1 · I&S - Infrastructure Security

`I&S-08` Network Architecture Documentation

Identify and record high-risk environments, judged by the sensitivity of their data, how exposed they are to threats and the business impact.

Source: CSA CCM v4.1, I&S-08. 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.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Network architecture diagrams marking high-risk environments · Policy repository / GRC workspace
Criteria for classing an environment as high risk (data sensitivity, exposure, business impact) · Policy repository / GRC workspace
Inventory of high-risk environments with review dates · Policy repository / GRC workspace
Risk assessment records supporting the classification · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Diagrams outdated after cloud expansion
No written criteria, so classification is ad hoc
Internet-facing environments not marked high risk

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

I&S-07 Migration to Cloud Environments · I&S-09 Network Defense