ISO 27017: every control, and what you already have

37 controls 282 frameworks share controls with it International held in the corpus

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.

ISO/IEC 27017:2015 Evidence & Implementation Kit

37 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

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.

If you run	Shared controls
ISO 27018	21	measure it →
MTCS (Singapore)	21	measure it →
NIST SP 800-144	21	measure it →
NIST SP 800-145	21	measure it →
NIST SP 800-146	21	measure it →
NIST SP 800-190	21	measure it →
Singapore Government Instruction Manual on ICT&SS Management (IM8)	15	measure it →
NIST Privacy Framework	15	measure it →
South Korea ISMS-P	13	measure it →
NIST SP 800-53 Rev 5	13	measure it →
Oman National Cybersecurity Framework	13	measure it →
AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)	12	measure it →

Every control

Code	Control	Also in
`11.2.7`	Secure disposal or reuse of equipment (cloud)	0
`14.1.1`	Information security requirements analysis (cloud apps)	1
`15.1.1`	Information security policy for supplier relationships (cloud)	0
`16.1.1`	Responsibilities and procedures (cloud incidents)	1
`18.1.1`	Identification of applicable legislation (cloud)	0
`CLD.12.1.5`	Administrator's operational security	1
`CLD.12.4.5`	Monitoring of cloud services	1
`CLD.13.1.4`	Alignment of security management for virtual and physical networks	1
`CLD.6.3.1`	Shared roles and responsibilities within a cloud computing environment	1
`CLD.8.1.5`	Removal of cloud service customer assets	1
`CLD.9.5.1`	Segregation in virtual computing environments	1
`CLD.9.5.2`	Virtual machine hardening	1
`ISO27017-01`	Shared responsibility model definition	135
`ISO27017-02`	Cloud security policy and strategy	14
`ISO27017-03`	Cloud risk assessment	123
`ISO27017-04`	Regulatory compliance for cloud services	58
`ISO27017-05`	Cloud security roles and responsibilities	14
`ISO27017-06`	Cloud identity management	34
`ISO27017-07`	Multi-factor authentication for cloud	69
`ISO27017-08`	Privileged access in cloud environments	64
`ISO27017-09`	Federation and single sign-on	0
`ISO27017-10`	API security and access tokens	0
`ISO27017-11`	Data classification for cloud	42
`ISO27017-12`	Encryption of cloud-stored data	142
`ISO27017-13`	Data residency and sovereignty	89
`ISO27017-14`	Data backup and recovery in cloud	69
`ISO27017-15`	Secure data deletion in cloud	89
`ISO27017-16`	Virtual network segmentation	55
`ISO27017-17`	Container and serverless security	14
`ISO27017-18`	Cloud workload protection	0
`ISO27017-19`	Image and template hardening	43
`ISO27017-20`	Cloud configuration management	43
`ISO27017-21`	Cloud security monitoring and logging	74
`ISO27017-22`	Incident response in cloud	109
`ISO27017-23`	Cloud vulnerability management	53
`ISO27017-24`	Cloud change management	34
`ISO27017-25`	Service level agreement management	0

Tell me when ISO 27017 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 an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

System security plans
Standard operating procedures
Current-as-at dates and approval records
Revenue analysis
Exemption documentation
Annual applicability review
IAM policy
MFA enforcement report
Federation configuration
API token inventory

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

no annual review named by 13 frameworks
Long-lived tokens named by 5 frameworks
No drift detection named by 3 frameworks
No attestation named by 3 frameworks

What this page is

A control-level reference for ISO 27017, 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