Typing "is aws iso 27017 certified" into a search bar usually returns a vendor compliance page that lists the standard among a dozen others, with no link to the document itself. That is a claim, not evidence. ISO/IEC 27017:2015 is a code of practice for cloud security controls, and like most ISO standards it only becomes meaningful once it is attached to an actual certificate issued by an accredited body, with a defined scope and a statement of applicability behind it. This piece walks through where AWS actually publishes that evidence, what the certificate covers, and how to tell whether the claim on a marketing page matches the document underneath it.
ISO 27017 is an extension, not a standalone badge
ISO/IEC 27017:2015 adds cloud-specific implementation guidance to the controls already set out in ISO/IEC 27002. It is not a management system standard in its own right, so a vendor cannot hold "an ISO 27017 certificate" the way it holds an ISO 27001 one. In practice, a certification body audits the organisation's ISO/IEC 27001 information security management system and then confirms, as an addition to that same audit, that the cloud-specific controls from 27017 have also been assessed. The result is normally one certificate, or one certificate plus a companion annex, not two separate schemes.
This is exactly the pattern covered in ISO 27017 vs 27018: what vendors actually publish: the two standards are frequently bundled together on the same base certificate, cover different things, cloud security controls versus the protection of personal data processed in the cloud, and buyers who treat them as interchangeable end up asking the wrong follow-up question. The ISO/IEC 27017 framework page lists which vendors in the index have published evidence for this specific standard, rather than simply mentioning it in prose.
Quick check
If a vendor's page says ISO 27017 is in place with no certificate number, no issuing body named and no scope statement attached, treat it as marketing copy rather than evidence until you find the underlying document.
Where AWS actually publishes the certificate
AWS distributes its ISO certificates, including the 27017 scope, through AWS Artifact, the self-service portal where customers under the relevant agreement can download the certificate PDF directly from the certification body that issued it. The public-facing compliance pages summarise this in prose, which is useful for a first pass but is not the document a buyer should cite in a vendor file. The certificate itself names the certification body, the certificate number, the issue and expiry dates, and, critically, the scope: the specific services, regions and operational boundaries that were actually audited.
ISO/IEC 27017:2015 provides guidance on cloud-specific information security controls. Customers can view the certificate and its scope through AWS Artifact to confirm which services are included.
The statement of applicability is the part marketing pages skip
Every ISO/IEC 27001 certification is accompanied by a statement of applicability, the document that lists which Annex A controls, and for a cloud provider which 27017 cloud-specific controls, are actually implemented, and which have been excluded with a stated justification. A trust page that simply ticks a box next to "ISO 27017" tells a buyer nothing about which controls were assessed or which were out of scope. The SoA is the only document that answers that question, and it sits behind the certificate rather than on the marketing page.
- 1
Find the primary ISO 27001 certificate
Locate the base ISO/IEC 27001 certificate first. The 27017 extension is normally issued alongside it rather than as a separate audit, so if the base certificate cannot be found, the 27017 claim has nothing to stand on.
- 2
Open the scope statement
Check which services, regions and facilities are named. A scope that simply says the vendor's own name, without naming services, is not the full picture; the certificate lists what was actually audited.
- 3
Check the edition date
Confirm whether the certificate cites ISO/IEC 27001:2022 or the lapsed 2013 edition. Under IAF MD 26, certificates still citing the 2013 edition stopped being valid on 31 October 2025. - 4
Read the statement of applicability
The SoA lists which Annex A and ISO 27017 cloud-specific controls are implemented, and which are excluded, together with a reason for each exclusion.
- 5
Confirm the certification body
An accredited certification body issues the certificate. The accreditation of that body, not just the vendor's claim, can be checked against national accreditation registers, which is the kind of detail covered when reviewing ISO 27001 Annex A controls; the auditors directory is a starting point for working out who actually issued a given certificate.
Why scope depth changes the answer
A single yes or no answer to "is AWS ISO 27017 certified" hides the part that actually matters to a buyer: which service, in which region, was in scope at the time of the audit. Large cloud providers add services continuously, and a service launched after an audit window closed is not automatically covered by the existing certificate until the next surveillance audit brings it in. This is the gap between a general compliance statement and a specific scope statement.
| What a trust page often says | What the certificate and SoA actually show | Why it matters to a buyer |
|---|---|---|
| "ISO 27017 certified" as a blanket statement | A certificate scope naming specific services, regions and a certification body | Services launched after the audit window, or outside the named regions, may not be covered |
| One page listing ten standards together | Separate certificates, each with its own number, scope and expiry date | 27017 and 27018 usually ride on the same base ISO 27001 audit, not a standalone one |
| No visible issue or expiry date | A certificate number, issue date, expiry date, and a 2022 or 2013 edition reference | A certificate still citing the 2013 edition lapsed on 31 October 2025 under IAF MD 26 |
What a vendor page implies versus what the underlying certificate and SoA actually state.
The 2013 to 2022 edition problem applies here too
ISO/IEC 27001 moved from its 2013 edition to the 2022 edition, and IAF MD 26 set a transition deadline of 31 October 2025, after which certificates still citing the 2013 edition are no longer valid. Because ISO 27017 is normally audited as an extension of the base ISO 27001 management system, a 27017 claim resting on a certificate that has not migrated to the 2022 edition is resting on a lapsed foundation, even if the vendor's page has not updated its wording. This is the same pattern documented across the wider market in ISO 27001:2013 lapsed on 31 October 2025, and it is worth checking the edition line on any certificate before treating the 27017 claim as current.
A comparable example: Docebo's published evidence
Docebo's trust centre states ISO 27001, 27701, 27017 and 27018 together, which is the bundling pattern described above. Rather than reading specific dates here, use the card below to see how the ISO 27017 row is actually presented: whether it links through to a certificate, whether a scope or exclusion note sits beside it, and whether a named certification body appears rather than just the standard number on its own.

Docebo · Trust report
Education · Public evidence as of 16 Nov 2026
Framework overview
CertReports state for each framework with public evidence: 2 verified, 9 vendor-stated.
ISO 27017Vendor-statedTrust centre · 30 Sep 2026FedRAMPVerifiedModerate impact
DPFVerifiedValid to 30 Dec 2026
SOC 2Vendor-statedTrust centre · 30 Sep 2026GDPRVendor-statedTrust centre · 30 Sep 2026
PCI DSSVendor-statedTrust centre · 30 Sep 2026
ISO 27001Vendor-statedTrust centre · 30 Sep 2026
ISO 27701Vendor-statedTrust centre · 30 Sep 2026
ISO 27018Vendor-statedTrust centre · 30 Sep 2026
5Documents and agreements
Legal and review documents Docebo publishes or offers, as of 30 Sep 2026.
- Standard contractual clauses · On request
- Subprocessor list · Public
- Privacy policy · Public
- AI and data use policy · Public
- Public trust centre documents · Docebo SOC2 Report Renewal Statement (Bridge letter); Docebo ISO 27001, 27701, 27017, and 27018 latest certificate; Docebo ISO 9001 Certificate
2Security practices
Public statements from Docebo, shown as statements, not attestations, as of 30 Sep 2026.
- Penetration testing · annual
- Data residency · Australia, Canada, EU, India, US
1Subprocessors
Named on Docebo's public subprocessor list, last seen 30 Sep 2026.
A buyer's checklist
- Pull the certificate PDF itself, not the marketing paragraph, before recording ISO 27017 in a vendor file.
- Match the specific service you use against the named scope, not the vendor's full product catalogue.
- Note the issue and expiry dates alongside the audit cycle, since ISO certificates are time-bound, not permanent.
- Check whether ISO 27018 appears on the same certificate, since the two are frequently confused in security questionnaires.
- Record the certification body's name, so the certificate itself can be checked rather than taken on trust.
What the pattern looks like across the wider index
- 27017
- Standard number for cloud-specific security controls
- An extension to ISO/IEC 27002, not a standalone management system standard
- 31 Oct 2025
- Lapse date for ISO/IEC 27001:2013 certificates
- Set by IAF MD 26; a 27017 scope riding on a 2013-edition base certificate lapsed the same day
- 2026-11-16
- Date this evidence trail was last checked
- in the CertReports index
None of this means a buyer should assume the worst about AWS's certificate. It means the correct verification step is to open the certificate and the statement of applicability directly, rather than stopping at the summary paragraph on a compliance page. The same approach applies to any cloud vendor claiming ISO 27017, and it takes only a few minutes once the certificate is in hand.
People also ask
Is aws ISO 27017 certified?
AWS states that it has had its cloud services assessed against ISO/IEC 27017:2015, with the scope defined on the certificate it distributes through AWS Artifact alongside its base ISO/IEC 27001 certificate. The reliable way to confirm this for a specific service is to check that certificate's scope statement and issue date directly, rather than relying on a summary sentence on a marketing page.
Is ISO 27017 certifiable?
Yes, but not as a standalone scheme. ISO/IEC 27017 is a code of practice for cloud security controls that is normally assessed as an extension to an organisation's ISO/IEC 27001 certification, so the resulting evidence is usually one certificate, or a certificate plus a companion scope annex, rather than two independent certificates.
Is ISO 27017 a certification?
It can lead to one, but the standard itself is a set of implementation guidelines, not a management system specification an auditor certifies in isolation. A certification body confirms conformance to the cloud-specific controls as part of an ISO/IEC 27001 audit, which is why the resulting document usually names both standards together.
Is ISO 27017?
ISO/IEC 27017:2015 is an international standard titled "Code of practice for information security controls based on ISO/IEC 27002 for cloud services". It sets out additional, cloud-specific guidance for both cloud service providers and cloud customers, covering areas such as shared responsibilities, virtual machine configuration and administrator access, on top of the general controls in ISO/IEC 27002.
Solomon Amos · Founder, CertReports
Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.
Read next on CertReports
You might also like
The state of public compliance evidence in 2026: what 3,000 vendors actually publish
CertReports Research · 18 Sep 2026 · 12 min read
ISO 27001:2013 lapsed on 31 October 2025. Vendor pages have not caught up.
CertReports Research · 16 Sep 2026 · 9 min read