1 | What the guide is for, what it references and how its controls are tagged | 0 |
5.1.0 | Own security accountability, plan cloud in the IT strategy and counter provider lock-in | 0 |
5.1.1 | Analyse the impact of jurisdiction on security procedures | 0 |
5.1.2 | Verify the provider's compliance with recognised security standards | 0 |
5.10.1 | Apply a secure development lifecycle to cloud applications | 0 |
5.10.2 | Manage and protect production credentials | 0 |
5.11.1 | Analyse security risks before deciding to use outsourced cloud services | 0 |
5.11.2 | Define measurable security requirements in the tender and a tailored SLA, and watch SLA changes | 0 |
5.11.3 | Make sure the provider's controls meet government requirements and address external threats | 0 |
5.11.4 | Formulate an exit strategy at the outset | 0 |
5.12.1 | Define incident monitoring and reporting responsibilities and secure access to incident data | 0 |
5.12.2 | Agree incident response steps, timing and evidence handling with the provider and review its track record | 0 |
5.12.3 | Document incident handling procedures for off-premises cloud services and rehearse them with the provider | 0 |
5.13.1 | Make sure backup and disaster recovery arrangements are effective and tied to the SLA | 0 |
5.13.2 | Cover loss of the provider in the business continuity plan and inspect the provider's plans | 0 |
5.14.1 | Assess security risks before production and major change and reassess regularly | 0 |
5.14.2 | Agree audit rights, scope and evidence sharing, and engage independent auditors | 0 |
5.14.3 | Specify compliance deliverables in the contract and perform onsite checks | 0 |
5.2 | Review the departmental security policy for cloud-specific adjustments | 0 |
5.3.1 | Define roles and responsibilities for resource control and information security | 0 |
5.3.2 | Bind provider staff to confidentiality and check their vetting and exit procedures | 0 |
5.3.3 | Issue user guidelines and reminders and train relevant personnel | 0 |
5.4.1 | Protect data by strong encryption at rest and in transit | 0 |
5.4.2 | Observe data protection and privacy law for outsourced data centres | 0 |
5.4.3 | De-identify personal data as an added layer of protection | 0 |
5.4.4 | Keep track of data location and prevent unapproved movement to the cloud | 0 |
5.4.5 | Maintain an up-to-date inventory of cloud assets | 0 |
5.4.6 | Make sure equipment disposal and re-use destroy data securely | 0 |
5.5.0 | Understand provider access controls, resume privileged access and keep keys out of the provider's hands | 0 |
5.5.1 | Define logical access control with default deny and least privilege | 0 |
5.5.2 | Build an identity and access management architecture on open standards | 0 |
5.5.3 | Require strong authentication and restrict privileged access | 0 |
5.5.4 | Restrict and control privileged utility programs | 0 |
5.6 | Manage and protect cryptographic keys through their lifecycle under B/D custody | 0 |
5.7.1 | Analyse risks of the site location and validate facility controls | 0 |
5.7.2 | Define and verify physical protection for equipment and media in shared data centres | 0 |
5.7.3 | Use an isolated, access-controlled area where data sensitivity requires it | 0 |
5.7.4 | Grade controlled areas by sensitivity and control access to shared racks at equipment level | 0 |
5.8.1 | Keep offline backups, test recovery and secure compliance copies | 0 |
5.8.2 | Keep complete, tamper-resistant logs and review them by criticality | 0 |
5.8.3 | Put in place processes to collect and keep configuration and audit evidence | 0 |
5.8.4 | Keep control over patch management | 0 |
5.9.1 | Protect data in transmission and the computing resources on the network | 0 |
5.9.2.1 | Keep the host operating system thin and harden every virtualisation component | 0 |
5.9.2.10 | Log privileged account activity on hypervisors and virtual machines | 0 |
5.9.2.11 | Protect administrative interfaces and monitor management sessions | 0 |
5.9.2.2 | Deploy high availability technologies against single points of failure | 0 |
5.9.2.3 | Control traffic between virtual machines with VM-specific and layered protection | 0 |
5.9.2.4 | Enforce least privilege and segregation of duties among cloud administrators | 0 |
5.9.2.5 | Create security zones by trust level and prefer bare-metal hypervisors for critical systems | 0 |
5.9.2.6 | Analyse virtualisation risks before adoption and plan VM resources | 0 |
5.9.2.7 | Keep an auditable inventory of the virtual environment and valid software licences | 0 |
5.9.2.8 | Patch dormant virtual machines and verify security after snapshot restores | 0 |
5.9.2.9 | Protect VM images, snapshots and configuration files and clear VM data securely | 0 |