SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
IVS-01: Infrastructure and Virtualization Security Policy and Procedures
Infrastructure and Virtualization Security Policy and Procedures
IVS-01: Are infrastructure and virtualization security policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained?
Infrastructure Virtualization Security Policy and Procedures should include, but are not limited to:
a. Governance and control VM lifecycle management.
b. Storage restriction of VM images and snapshots.
c. Backup and failover systems.
d. Tagging for the VM based on sensitivity / risk level.
e. A formal change management process for creation, storage, and use of VM images. Approve changes only when necessary.
f. Consistent security policy and configuration across the physical/virtual network.
g. Implementation of security technologies that span physical and virtual environments with a consistent policy management and enforcement framework.
To implement security technologies that span physical and virtual environments with a consistent policy management and enforcement framework.
h. Firewalls, whether physical or virtual, to isolate groups of VMs from other hosted groups.
i. Design and implementation access from each trust level to physical and virtual management and security systems.
Control implemented
Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
Control ownership
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for infrastructure and virtualization security. Review and update the policies and procedures at least annually.

Infrastructure and Virtualization Security Policy and Procedures
IVS-01: Are infrastructure and virtualization security policies and procedures reviewed and updated at least annually?
Infrastructure Virtualization Security Policy and Procedures should include, but are not limited to:
a. Governance and control VM lifecycle management.
b. Storage restriction of VM images and snapshots.
c. Backup and failover systems.
d. Tagging for the VM based on sensitivity / risk level.
e. A formal change management process for creation, storage, and use of VM images. Approve changes only when necessary.
f. Consistent security policy and configuration across the physical/virtual network.
g. Implementation of security technologies that span physical and virtual environments with a consistent policy management and enforcement framework.
To implement security technologies that span physical and virtual environments with a consistent policy management and enforcement framework.
h. Firewalls, whether physical or virtual, to isolate groups of VMs from other hosted groups.
i. Design and implementation access from each trust level to physical and virtual management and security systems.
Control implemented
Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
Control ownership
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for infrastructure and virtualization security. Review and update the policies and procedures at least annually.