Skip to content

ISO/IEC 27018

ISO 27018
cloud privacy.

ISO 27018 is the code of practice for protecting personal data in public clouds. It is aimed at cloud processors and gives enterprise customers assurance about how their users' data is handled. We implement it alongside ISO 27001 and 27017.

Issued by

ISO / IEC

Type

Code of practice

Jurisdiction

International

Structure

Extends ISO 27002 for PII in cloud

Understanding ISO 27018

PII in the cloud,
as a processor.

ISO 27018 establishes controls for public cloud service providers acting as PII processors. It adds requirements around consent and choice, purpose limitation, transparency about subprocessors and data location, disclosure to law enforcement, and return and deletion of PII.

Like 27017, it is implemented within an ISO 27001 ISMS and appears as a statement of conformity. SaaS companies serving enterprise customers in regulated industries use it to answer the privacy section of security questionnaires with a certified standard rather than a narrative.

What ISO 27018 asks for

Processor
obligations.

The additional controls formalize what enterprise customers already ask SaaS providers in contracts and questionnaires.

What it requires

Process PII only on customer instruction, do not use it for marketing or advertising without consent, and limit processing to the contracted purpose.

How ForgePath helps

We document processing boundaries and build the controls that keep customer data from drifting into other uses.

What it requires

Disclose the countries where PII may be stored, the subprocessors involved, and changes to them, with customer notification.

How ForgePath helps

We build the subprocessor register, data location disclosure, and change notification process.

What it requires

Notify customers of legally binding requests for PII disclosure unless prohibited, and reject non binding requests.

How ForgePath helps

We write the disclosure handling procedure and train the people who would receive such requests.

What it requires

Return or delete PII at contract end, and securely erase temporary files and PII on decommissioned media.

How ForgePath helps

We build and verify the deletion process customers ask about in every security review.

Good security starts with asking

The right
questions about
your business

Organizations bring us the question they are actually asking. We answer it with one of three offers, each led by the people who will do the work, and each scoped to your situation rather than a catalog.

Trusted by industry leaders.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

ISO 27018 explained

Frequently asked
questions.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

Cloud service providers and SaaS companies that process personal data on behalf of customers. If enterprise customers send you privacy questionnaires, this is the standard that answers them.

27018 is specific to public cloud processors and is a code of practice. 27701 is a broader certifiable privacy management system covering controllers and processors. Many cloud providers implement both.

It maps closely to Article 28 processor requirements and is strong evidence. It does not replace the data processing agreement or legal counsel.

No. Independence matters, so the certificate, report, or assessment comes from an accredited third party. We prepare you, help select the assessor, sit beside you during the audit, and close any findings.

Yes, and that is how we build. One control set mapped to every framework you answer to, with evidence collected once and reused. Separate programs per framework is the expensive way.

Yes. Under Lead, a senior practitioner can serve as your named security owner or fractional CISO, keeping the program current between assessments.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.