What evidence do auditors commonly ask for on I&S-01 Infrastructure and Virtualization Security Policy and Procedures?

Infrastructure and virtualisation security policy and procedures with approval records; Supporting standards for network segregation, hypervisor and host hardening, and environment separation; Communication record to infrastructure and operations teams; Evidence of the yearly review and of a review after a significant change.

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

Policy predates container and serverless platforms now in use

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

`I&S-01` Infrastructure and Virtualization Security Policy and Procedures

Keep approved, communicated and applied policies and procedures for securing infrastructure and virtualisation, and keep them reviewed every year and again whenever a significant change occurs.

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

Communication record to infrastructure and operations teams · Cloud console / configuration management
Evidence of the yearly review and of a review after a significant change · Cloud console / configuration management

governing documentDocuments that govern the control

Infrastructure and virtualisation security policy and procedures with approval records · Policy repository / GRC workspace
Supporting standards for network segregation, hypervisor and host hardening, and environment separation · 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

Policy predates container and serverless platforms now in use
Procedures not maintained by the teams running the infrastructure
No review record

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

HRS-13 Compliance User Responsibility · I&S-02 Capacity and Resource Planning