Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

ISO/IEC 29100: The Privacy Framework Standard Explained

ISO/IEC 29100 is an international privacy framework that defines terminology, actors and 11 privacy principles. Here is what it is, who uses it, and how to apply it.

ISO/IEC 29100: The Privacy Framework Standard Explained

ISO/IEC 29100 is an international standard that gives organizations a common vocabulary and a set of principles for protecting personally identifiable information (PII) in information and communication technology systems. It is a framework, not a certification scheme and not a law. Its value is in giving privacy, security and engineering teams a shared model to build on.

What it is

ISO/IEC 29100, titled "Information technology — Security techniques — Privacy framework" in its original edition, is published jointly by ISO and IEC through their joint technical committee for information technology (JTC 1). The first edition appeared in 2011, and a later revision has since been issued. Check the current edition with ISO before citing it in policy documents, as the title and details may differ between editions.

The standard is voluntary and is not certifiable. It contains guidance rather than auditable "shall" requirements for a management system. Its purpose is to:

  • Define common privacy terminology.
  • Describe the actors involved in processing PII and their roles.
  • Describe safeguarding considerations for privacy.
  • Provide a set of privacy principles that can guide the design, implementation and operation of systems.

It sits at the base of a family of privacy standards. Other ISO/IEC documents, such as ISO/IEC 27701 (a privacy information management system standard) and ISO/IEC 29151 (a code of practice for PII protection), build on similar concepts with more operational detail.

Who it applies to

ISO/IEC 29100 has no jurisdiction, sector or size threshold. Any organization that handles PII can use it: controllers, processors, product teams building systems that handle personal data, and vendors that need a neutral model to describe their privacy practices. Because it is not law, no one is legally required to follow it, though some contracts, procurement requirements or internal policies may reference it.

It is particularly useful for multinational organizations that face several privacy laws at once. The standard does not replace those laws, but it offers a stable internal model that can be mapped to each of them.

Key requirements and control areas

Actors and roles

The standard identifies the main actors: the PII principal (the individual the data relates to), the PII controller, the PII processor, and third parties. Clarifying these roles for each processing activity is the first practical step, because obligations differ by role.

Interactions and PII identification

It describes how to recognize PII, including identifiers and data that becomes identifying when combined, and how PII flows between actors. Understanding data flows is the foundation for everything else.

Privacy safeguarding requirements

Organizations are expected to consider legal and regulatory factors, contractual factors, business factors and other factors when deciding what safeguards are needed. They also consider the risks to individuals, and then select privacy controls accordingly.

The 11 privacy principles

The core of the standard is this set of principles:

  1. Consent and choice: give individuals meaningful choices and obtain consent where appropriate.
  2. Purpose legitimacy and specification: ensure purposes comply with law and are communicated.
  3. Collection limitation: collect only what is within the specified purpose.
  4. Data minimization: minimize the PII processed and the number of parties with access.
  5. Use, retention and disclosure limitation: limit use and disclosure to the specified purposes and retain only as long as necessary.
  6. Accuracy and quality: keep PII accurate, complete and up to date.
  7. Openness, transparency and notice: provide clear information about policies and practices.
  8. Individual participation and access: let individuals access and review their PII and challenge its accuracy.
  9. Accountability: assign responsibility, and document and communicate privacy practices.
  10. Information security: protect PII with controls proportionate to the risk.
  11. Privacy compliance: verify and demonstrate that processing meets safeguarding requirements, through audits and privacy risk assessments.

These ideas will look familiar to anyone who knows the OECD guidelines or GDPR principles. The standard is a general framework and does not prescribe specific technical controls.

Assessment, audit and enforcement

No body certifies organizations against ISO/IEC 29100, and no regulator enforces it. There are no penalties attached to the standard itself. Assessment is therefore internal or contractual: an organization may run a self-assessment against the principles, or a customer may ask a vendor to describe how it implements them.

If you need independent assurance, the usual routes are:

  • Certification to ISO/IEC 27701 (a privacy information management system standard, often combined with ISO/IEC 27001), which uses concepts consistent with the privacy framework.
  • Attestation reports, such as SOC 2 with the privacy criteria.
  • Regulatory supervision under whichever privacy laws apply to you, such as GDPR, where data protection authorities enforce and set penalties.

A practical path to applying it

  1. Set scope. Decide which systems, products and processing activities will be assessed against the framework.
  2. Inventory PII and data flows. Record what PII you handle, where it is stored, who receives it and why.
  3. Assign roles. For each activity, identify whether you act as controller, processor or both, and who the third parties are.
  4. Identify safeguarding requirements. List applicable laws, contracts and business needs, and assess privacy risk to individuals.
  5. Map principles to controls. For each of the 11 principles, document the policy, process or technical control that implements it, and name an owner.
  6. Build privacy into design. Add privacy risk review to your development lifecycle so new features are examined before release.
  7. Manage vendors. Check that processors and other third parties support the same principles, and reflect this in contracts.
  8. Collect evidence and review. Retain proof that controls operate, run periodic assessments, and update the mapping when laws or systems change.
  9. Consider certifiable follow-on schemes. If customers want independent assurance, pursue ISO/IEC 27701 or an attestation that covers privacy.

How it maps to other frameworks

These are overlaps, not equivalences.

  • ISO/IEC 27701: the most direct relationship. It specifies a privacy information management system with privacy-specific controls for controllers and processors (the 2019 edition extended ISO/IEC 27001; the 2025 edition is standalone), and uses the same underlying privacy concepts.
  • ISO/IEC 27001: addresses the information security principle in depth, but is not a privacy framework on its own.
  • GDPR and similar privacy laws: many principles, such as purpose limitation, minimization, transparency, accuracy and accountability, have clear counterparts. The laws add binding legal obligations, such as lawful bases and breach notification, that the standard does not provide.
  • NIST Privacy Framework: a voluntary U.S. framework with comparable goals; its functions are organized differently from the ISO principles.
  • SOC 2 privacy criteria: cover notice, choice, access, disclosure and quality themes that echo several principles, but are assessed through an auditor's attestation.

FAQs

Can we get certified to ISO/IEC 29100?

No. It is a guidance framework without auditable management system requirements. Organizations seeking certification typically use ISO/IEC 27701, often alongside ISO/IEC 27001.

Does following ISO/IEC 29100 make us compliant with GDPR?

No. It can support a GDPR program by organizing your privacy practices, but legal compliance depends on meeting the law's specific requirements, which go beyond the standard's principles.

Is it mandatory?

Not by itself. It becomes relevant only if a contract, customer, policy or national adoption of the standard makes it so.

How does it differ from ISO/IEC 27701?

ISO/IEC 29100 defines concepts and principles. ISO/IEC 27701 is a certifiable privacy information management system standard with concrete controls for protecting PII.

Who should own it internally?

Usually privacy or data protection leadership, working with security, legal and engineering. The accountability principle expects clear assignment of responsibility.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform. Teams using ISO/IEC 29100 as an internal privacy model can use it to connect that model to the frameworks and laws they are actually assessed against. See the list of compliance frameworks for more.

  • Map controls across 340+ frameworks, so one evidence base supports privacy principles and related requirements at the same time.
  • Collect evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, instead of using manual screenshots or spreadsheets.
  • Monitor control effectiveness and receive alerts when controls drift, so gaps are fixed before auditors find them.
  • Generate threat models from code, IaC and architecture diagrams, including LINDDUN for privacy threats.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.