What evidence do auditors commonly ask for on I&S-06 Segmentation and Segregation?

Tenant isolation architecture description; Penetration test results on cross-tenant access; Configuration evidence of segmentation (VPCs, namespaces, tenant ID enforcement); Monitoring rules for cross-tenant access attempts.

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

Isolation relies on application logic never tested for cross-tenant leakage

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

`I&S-06` Segmentation and Segregation

Design, build, deploy and configure applications and infrastructure so service customer (tenant) access is properly segmented, segregated, monitored and restricted.

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

easy

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

Configuration evidence of segmentation (VPCs, namespaces, tenant ID enforcement) · Cloud console / configuration management
Monitoring rules for cross-tenant access attempts · SIEM / log platform

periodic reviewEvidence produced at each review

Penetration test results on cross-tenant access · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

Tenant isolation architecture description · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

Isolation relies on application logic never tested for cross-tenant leakage
Shared infrastructure components without tenant segregation
No alerting on cross-tenant access attempts

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-05 Production and Non-Production Environments · I&S-07 Migration to Cloud Environments