Hong Kong SAR

Hong Kong Government Practice Guide for Cloud Computing Security (ISPG-SM04 v2.1)

54 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

54 controls 0 frameworks share controls with it Hong Kong SAR verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1What the guide is for, what it references and how its controls are tagged0
5.1.0Own security accountability, plan cloud in the IT strategy and counter provider lock-in0
5.1.1Analyse the impact of jurisdiction on security procedures0
5.1.2Verify the provider's compliance with recognised security standards0
5.10.1Apply a secure development lifecycle to cloud applications0
5.10.2Manage and protect production credentials0
5.11.1Analyse security risks before deciding to use outsourced cloud services0
5.11.2Define measurable security requirements in the tender and a tailored SLA, and watch SLA changes0
5.11.3Make sure the provider's controls meet government requirements and address external threats0
5.11.4Formulate an exit strategy at the outset0
5.12.1Define incident monitoring and reporting responsibilities and secure access to incident data0
5.12.2Agree incident response steps, timing and evidence handling with the provider and review its track record0
5.12.3Document incident handling procedures for off-premises cloud services and rehearse them with the provider0
5.13.1Make sure backup and disaster recovery arrangements are effective and tied to the SLA0
5.13.2Cover loss of the provider in the business continuity plan and inspect the provider's plans0
5.14.1Assess security risks before production and major change and reassess regularly0
5.14.2Agree audit rights, scope and evidence sharing, and engage independent auditors0
5.14.3Specify compliance deliverables in the contract and perform onsite checks0
5.2Review the departmental security policy for cloud-specific adjustments0
5.3.1Define roles and responsibilities for resource control and information security0
5.3.2Bind provider staff to confidentiality and check their vetting and exit procedures0
5.3.3Issue user guidelines and reminders and train relevant personnel0
5.4.1Protect data by strong encryption at rest and in transit0
5.4.2Observe data protection and privacy law for outsourced data centres0
5.4.3De-identify personal data as an added layer of protection0
5.4.4Keep track of data location and prevent unapproved movement to the cloud0
5.4.5Maintain an up-to-date inventory of cloud assets0
5.4.6Make sure equipment disposal and re-use destroy data securely0
5.5.0Understand provider access controls, resume privileged access and keep keys out of the provider's hands0
5.5.1Define logical access control with default deny and least privilege0
5.5.2Build an identity and access management architecture on open standards0
5.5.3Require strong authentication and restrict privileged access0
5.5.4Restrict and control privileged utility programs0
5.6Manage and protect cryptographic keys through their lifecycle under B/D custody0
5.7.1Analyse risks of the site location and validate facility controls0
5.7.2Define and verify physical protection for equipment and media in shared data centres0
5.7.3Use an isolated, access-controlled area where data sensitivity requires it0
5.7.4Grade controlled areas by sensitivity and control access to shared racks at equipment level0
5.8.1Keep offline backups, test recovery and secure compliance copies0
5.8.2Keep complete, tamper-resistant logs and review them by criticality0
5.8.3Put in place processes to collect and keep configuration and audit evidence0
5.8.4Keep control over patch management0
5.9.1Protect data in transmission and the computing resources on the network0
5.9.2.1Keep the host operating system thin and harden every virtualisation component0
5.9.2.10Log privileged account activity on hypervisors and virtual machines0
5.9.2.11Protect administrative interfaces and monitor management sessions0
5.9.2.2Deploy high availability technologies against single points of failure0
5.9.2.3Control traffic between virtual machines with VM-specific and layered protection0
5.9.2.4Enforce least privilege and segregation of duties among cloud administrators0
5.9.2.5Create security zones by trust level and prefer bare-metal hypervisors for critical systems0
5.9.2.6Analyse virtualisation risks before adoption and plan VM resources0
5.9.2.7Keep an auditable inventory of the virtual environment and valid software licences0
5.9.2.8Patch dormant virtual machines and verify security after snapshot restores0
5.9.2.9Protect VM images, snapshots and configuration files and clear VM data securely0

Tell me when Hong Kong Government Practice Guide for Cloud Computing Security (ISPG-SM04 v2.1) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Hong Kong Government Practice Guide for Cloud Computing Security (ISPG-SM04 v2.1), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition