Join our Newsletter — 33% off our NHI Course
Home› Guides› Third-Party Attestation Comparison Map: SOC 2, ISO 27001,…
Regulatory Map Audit, Assurance & Compliance

Third-Party Attestation Comparison Map: SOC 2, ISO 27001, CSA STAR, HITRUST, C5 and Cyber Essentials Compared

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 12 min read
On this page

Buyers ask for "a SOC 2 or ISO certificate" as if they were interchangeable, and suppliers buy the wrong attestation, or several overlapping ones, as a result. SOC 2, ISO/IEC 27001, CSA STAR, HITRUST, BSI C5 and Cyber Essentials differ in who issues them, what they examine, how long they last and what a relying party can actually conclude from them. This map compares the six side by side, with status as checked on 27 October 2026, and explains what each says (and does not say) about service accounts, API keys and AI agents. It is written for procurement and third-party risk teams deciding what to accept, and for supplier compliance leads deciding what to pursue. For the wider assurance landscape, see the Audit, Assurance and Compliance Guide.

Key takeaways

  • Attestation and certification are different products. SOC 2 and C5 produce an auditor's report describing controls and test results; ISO/IEC 27001, HITRUST and Cyber Essentials produce a certificate stating that requirements were met.
  • Scope is the first thing to read. Every one of these can be scoped narrowly; a certificate covering one data centre or one product says nothing about the service you are buying unless the scope statement names it.
  • Validity differs widely. Cyber Essentials lasts 12 months, HITRUST e1 and i1 one year and r2 two years, while SOC 2 and C5 reports describe a past period and age from the day they are issued.
  • Many map onto each other. CSA STAR Level 2 is built on an ISO/IEC 27001 certificate or a SOC 2 report plus the CAIQ, so one audit can serve several buyer requirements.
  • None is an NHI assessment. Machine identities fall under general access control criteria, so buyers who care about API keys, OAuth apps and AI agents must read the detail or ask targeted questions.

Attestations at a glance

SchemeOwnerOutputWho performs itValidity or currencyTypical demand
SOC 2AICPAAttestation report against the 2017 Trust Services Criteria (revised points of focus 2022)Licensed CPA firmReport covers a defined period; buyers usually expect a new one every 12 monthsNorth American SaaS and service buyers
ISO/IEC 27001:2022ISO and IECCertificate of conformity for an information security management systemCertification body, ideally accreditedCertificate cycle with surveillance auditsGlobal, especially Europe and Asia
CSA STARCloud Security AllianceRegistry listing: Level 1 self-assessment, Level 2 third-party auditSelf (Level 1); auditor for ISO, SOC 2 or C-STAR (Level 2)Follows the underlying auditCloud buyers who use the CAIQ
HITRUSTHITRUST AllianceCertification: e1, i1 or r2HITRUST-approved External Assessore1 and i1: 1 year; r2: 2 yearsUS healthcare and payers
BSI C5German Federal Office for Information Security (BSI)Auditor's examination report against the C5 criteria catalogueIndependent auditor (BSI does not select auditors or check reports)Report period; current catalogue C5:2026German public sector and regulated buyers of cloud services
Cyber Essentials and PlusUK NCSC, delivered by IASMECertificate: self-assessment (CE) or with independent technical testing (CE Plus)IASME certification bodies12 monthsUK public sector supply chains and small businesses

Scope: who and what is covered

  • SOC 2: a service organisation's system, described by management, assessed against one or more of the five categories: Security, Availability, Processing Integrity, Confidentiality and Privacy. In audit practice, reports are described as Type 1 (design at a point in time) or Type 2 (operating effectiveness tested over a period); confirm the report type and categories with the issuing CPA firm. Buyers should normally require Type 2.
  • ISO/IEC 27001:2022: an organisation's ISMS, with its own declared scope and a Statement of Applicability against Annex A. The current edition was published on 25 October 2022 and the 2013 edition is withdrawn; Amendment 1:2024 adds climate action changes. See the ISO 27001 Certification Guide.
  • CSA STAR: a specific cloud service, described through the Consensus Assessments Initiative Questionnaire (CAIQ) mapped to the Cloud Controls Matrix. STAR for AI applies the same approach to AI services with the AI-CAIQ and the AI Controls Matrix. See the Cloud Security Alliance CCM and STAR Guide.
  • HITRUST: an organisation's in-scope systems and facilities assessed against the HITRUST CSF, at a depth chosen by assessment type: e1 (43 core controls), i1 (182 control requirements) or r2 (a risk-tailored, highest-level assessment). See the HITRUST CSF Guide.
  • BSI C5: a cloud service, with minimum requirements for secure cloud computing. C5:2026 splits criteria into subcriteria aligned with the EU cloud certification scheme structure and adds additional criteria that either sharpen or complement the basic ones. See the Germany BSI C5 Guide.
  • Cyber Essentials: an organisation's internet-connected IT, against five technical controls. CE Plus testing covers a representative set of user devices, all internet gateways and all servers with internet-accessible services. See the Cyber Essentials Guide.

Key obligations

What each scheme requires of the organisation being assessed, and what the relying party gets:

SchemeWhat the organisation must doWhat the buyer receivesCan the buyer see test results?
SOC 2 Type 2Write a system description, operate controls for the period, support auditor testingReport with auditor's opinion, controls, tests and exceptions, complementary user entity controlsYes, including exceptions
ISO/IEC 27001Run an ISMS (risk assessment, treatment, SoA, internal audit, management review, corrective action) and pass certification and surveillance auditsCertificate with scope statement; SoA on requestNo, only the certificate unless shared
CSA STAR Level 1Complete and publish the CAIQSupplier's own answers in the STAR registryNo independent testing
CSA STAR Level 2Publish the CAIQ and hold an ISO/IEC 27001 certificate, SOC 2 report or C-STARRegistry entry plus the underlying auditDepends on the underlying audit
HITRUST e1, i1, r2Implement CSF requirements for the chosen type; external assessor testing; HITRUST reviewCertification letter and reportReport shows scoring by requirement
BSI C5Meet basic (and chosen additional) criteria; publish a C5 report through the auditorAuditor's examination report stating applicable criteriaYes, the report details criteria
Cyber EssentialsImplement firewalls, secure configuration, security update management, user access control and malware protection; answer the question setCertificate (searchable through IASME)No, pass or fail only; CE Plus adds testing

Timeline and current status

SchemeCurrent version or status, checked 27 October 2026What to watch
SOC 22017 Trust Services Criteria with revised points of focus (2022)Any AICPA revision of criteria or points of focus
ISO/IEC 27001ISO/IEC 27001:2022 with Amd 1:2024; 2013 edition withdrawnCertificates must reference the 2022 edition
CSA STARLevel 1 and Level 2 for cloud; STAR for AI with AI-CAIQSTAR for AI Level 2 routes include ISO/IEC 27001, ISO/IEC 42001, both together, or SOC 2
HITRUSTe1, i1, r2 and an AI Security assessment; NIST CSF 2.0 add-on for r2Control count changes between CSF versions
BSI C5C5:2026 current; C5:2020 still listed as a previous versionBSI has not stated a transition period on its C5 page; ask auditors which version a report uses
Cyber EssentialsFive controls; certificates valid 12 monthsQuestion set updates published by IASME; check the version a certificate was issued under

Versions and requirements change. Re-check the owner's page before writing a contract clause that names a specific version.

Enforcement and penalties

None of these schemes is a law, so there are no statutory fines for not holding one. The consequences come from contracts, scheme rules and misrepresentation:

  • Contractual: buyers commonly make an attestation a condition of award or renewal. A lapsed certificate or a qualified SOC 2 opinion can trigger termination or remediation clauses.
  • Scheme rules: ISO certification bodies can suspend or withdraw a certificate after a failed surveillance audit; Cyber Essentials and HITRUST certifications simply expire if not renewed.
  • Auditor discipline: the AICPA states it may act against members whose SOC work does not follow professional standards, who are not enrolled in peer review or who are unlicensed. Buyers should check the CPA firm, not just the logo.
  • Misrepresentation: claiming a certification that has lapsed, or implying a narrow scope covers the whole service, exposes the supplier to contract and, in some jurisdictions, consumer or procurement fraud claims.

What it means for AI agents and non-human identities

All six schemes include access control, authentication and logging requirements that apply to service accounts, API keys, OAuth integrations and AI agents, but none treats non-human identities as a separate domain. A clean report can therefore coexist with unrotated keys and over-privileged integrations.

SchemeWhere NHIs are coveredWhat to ask the supplier
SOC 2Common criteria on logical accessWere service accounts and API keys in the population tested for access reviews and removal?
ISO/IEC 27001Annex A controls on access control, identity, privileged access and secure authenticationDoes the SoA and risk assessment treat machine identities and AI agents explicitly?
CSA STARCCM Identity and Access Management domain; AICM for AI servicesHow are customer-issued keys and tokens stored, scoped and revoked?
HITRUSTAccess control and authentication requirements in the CSFWere non-interactive accounts sampled at r2 depth?
BSI C5Identity and access management criteriaWhich criteria cover technical accounts and keys, and were any exceptions reported?
Cyber EssentialsUser access control, including administrative accountsIs MFA enforced for cloud service admin and service accounts where supported?

Third-party credentials are a recurring breach path, as the SpotBugs token leak showed, when one maintainer's personal access token led to the reviewdog and tj-actions supply chain compromise. An attestation is evidence about the past period, so pair it with targeted questions. See the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide and the Security Questionnaires Guide.

Compliance steps

For buyers

  1. Define what you need to conclude. Tested operating effectiveness points to SOC 2 Type 2, C5 or HITRUST r2; a management system baseline points to ISO/IEC 27001; a basic hygiene floor for small suppliers points to Cyber Essentials.
  2. Accept equivalents explicitly. Write contracts that accept a named set of attestations rather than one brand, and state the minimum depth (for example SOC 2 Type 2 including Security and Confidentiality).
  3. Read scope and dates first. Check the system description or scope statement names the service you buy, and that the period ended recently enough for your risk appetite.
  4. Read the exceptions and user controls. In SOC 2 and C5 reports, exceptions and complementary user entity controls tell you what you must do yourself. See the How to Read a SOC 2 Report Guide.
  5. Verify the issuer. Check the CPA firm's licence, the certification body's accreditation, the IASME certificate search or the STAR registry entry.

For suppliers

  1. List what your buyers actually require by region and sector before choosing; one ISO/IEC 27001 certificate or SOC 2 report can also support CSA STAR Level 2.
  2. Build one control set and map it to each scheme so evidence is collected once.
  3. Scope honestly to cover the service customers buy, including identity providers, CI/CD and secrets stores.
  4. Include non-human identities in access review populations and key rotation evidence, so that auditors test them.

Small versus large organisations

SituationUsually sufficientUsually expected
Small UK supplier with no sensitive dataCyber EssentialsCyber Essentials Plus where a buyer requires tested controls
SaaS start-up selling to US enterprisesSOC 2 Type 1 as a first stepSOC 2 Type 2 within a year, renewed annually
Global SaaS or managed service providerISO/IEC 27001 and SOC 2 Type 2Plus CSA STAR Level 2 for cloud buyers and C5 for German public sector buyers
Supplier handling US health dataHITRUST e1 or i1HITRUST r2 for large payers and providers
AI service providerSTAR for AI Level 1 (AI-CAIQ)STAR for AI Level 2, for example via ISO/IEC 27001 plus ISO/IEC 42001

Large buyers gain most from accepting several equivalent schemes and reading the reports properly; small buyers gain most from a short list of accepted schemes plus a handful of targeted identity questions, because they rarely have time to read a 100-page SOC 2 report for every supplier.

Practitioner checklist

  • Record, for each supplier, which attestation it holds, the scope, the period or certificate dates and the issuer.
  • Require SOC 2 Type 2 rather than Type 1 where tested effectiveness matters.
  • Check ISO/IEC 27001 certificates reference the 2022 edition and an accredited certification body.
  • Confirm which C5 catalogue version a report uses and which additional criteria were in scope.
  • Diarise expiry: 12 months for Cyber Essentials, one year for HITRUST e1 and i1, two for r2.
  • Review exceptions and complementary user entity controls and assign owners for your side.
  • Ask targeted questions about API keys, OAuth apps, service accounts and AI agents that the attestation does not answer.
  • Reassess when a supplier changes scope, ownership or hosting provider.

Standards and references

Related NHI Mgmt Group resources: Audit, Assurance and Compliance Guide · SOC 2 Guide · Third-Party Risk Management Guide · CSA STAR for AI and AI-CAIQ Guide. This guide summarises the SOC 2, ISO/IEC 27001, CSA STAR, HITRUST, BSI C5 and Cyber Essentials schemes as published by their owners on 27 October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.