ISO Standards

ISO 27701:2025 Changes: Now a Standalone Standard

ISO 27701:2025 Changes: Now a Standalone Standard
In short

ISO/IEC 27701:2025 was published in October 2025 and replaces the 2019 edition. The main change is that it is now a standalone standard: you can certify a privacy information management system without ISO 27001. It also expands guidance for controllers and processors and adds implementation guidance. Ask your certification body about transition rules.

In this article
  1. ISO 27701:2025 changes: what is new?
  2. What does standalone mean in practice?
  3. What should existing certificate holders do?
  4. Which parts of your PIMS need the closest look?
  5. How can AdWiser help?
  6. Frequently asked questions

ISO 27701:2025 changes the way organisations can approach privacy certification. The standard was published on 14 October 2025 and replaces ISO/IEC 27701:2019. Its biggest change is simple to state: it is now a standalone standard, so you no longer need ISO 27001 as a starting point.

ISO 27701 sets requirements for a privacy information management system (PIMS). A PIMS helps an organisation manage personal data, protect the rights of the people it concerns and show that it does so. It is often used alongside laws such as the GDPR and India's data protection rules, though the standard itself is not a law.

ISO 27701:2025 changes: what is new?#

Summaries from certification bodies and consultancies point to these changes. Read the standard before you change your system, since details matter.

AreaISO 27701:2019ISO 27701:2025
StatusAn extension to ISO 27001 and ISO 27002A standalone management system standard
PrerequisiteISO 27001 certification context neededNo ISO 27001 prerequisite
RolesController and processor guidanceExpanded guidance for both roles
TechnologyLimited view of new technologyClearer handling of AI and digital ecosystems
GuidanceAnnexes with controlsNew implementation guidance annex

What does standalone mean in practice?#

Before, ISO 27701 worked as an add-on. You built an information security system under ISO 27001, then extended it with privacy controls. Now an organisation can build a PIMS on its own. This helps companies that handle personal data but have no need for a full security certification, for example a small data processor or a marketing business.

It does not mean security is less important. Protecting personal data still needs good security controls. Many organisations will still run both standards together, because the two fit well. The difference is that you now choose, and the choice depends on your customers and contracts.

Think of a typical case. A software company in India processes customer data for clients abroad. Its clients ask for evidence of privacy controls, but they do not ask for ISO 27001. Under the 2019 edition, the company would have needed a full security certification first. Under the 2025 edition, it can focus on the privacy system, then add security certification later if the market asks for it.

What should existing certificate holders do?#

If you hold a 2019 certificate, it remains valid for now. Transition rules were still being settled by the accreditation community when this was written, and some sources point to a deadline in 2028. Do not rely on a date from a blog post. Ask your certification body for its written transition plan and dates.

  1. Obtain ISO/IEC 27701:2025 and read it against your current PIMS.
  2. Run a gap analysis and record the differences.
  3. Review your scope, roles and records of processing.
  4. Check how you treat AI tools and other new technology that handle personal data.
  5. Update policies, procedures and internal audit checklists.
  6. Brief top management and train the people involved.
  7. Agree your transition audit with your certification body.

If you do not hold a certificate yet, build on the 2025 edition from the start. Organisations that also use ISO 27001 can keep a combined system and add what is missing.

Which parts of your PIMS need the closest look?#

Experience with other revisions suggests a few areas that deserve attention first. Your scope statement should say clearly whether you act as a controller, a processor or both, and for which activities. Your records of processing should match what really happens, including data shared with suppliers. Your risk assessment should cover privacy risks to people, not only risks to the business. Finally, your controls for supplier contracts, data subject requests and breach handling should be tested, not just written.

New technology needs its own look. If staff use AI tools that handle personal data, decide who approves them, what data may be entered and how you keep records. These are good questions for management review in any case, whatever the final transition dates turn out to be.

Finally, keep your documents readable. A privacy system that only a consultant understands will fail at audit, because the auditor will talk to the people who do the work. Short, clear procedures and a few well-chosen records serve you better than a thick manual.

How can AdWiser help?#

Our ISO 27701 toolkit offers editable documents and a gap checklist, with one year of e-mail support and a free upgrade within 6 months. It supports your own work, but you still need to adapt it to your data, your role as controller or processor, and your legal duties. If you prefer hands-on help, see our ISO 27701 consulting. We cannot promise an audit result, because the certification body decides.

Whichever route you take, start with a short, honest self-assessment. List the personal data you hold, where it flows, who can access it and which suppliers handle it. This single exercise usually exposes most of the gaps, and it gives you a base for the gap analysis, the scope decision and the plan you agree with your certification body. Share the result with top management early, because support from the top decides whether the project gets time and people.

Finally, remember that a new edition is a chance to simplify. If a record or procedure exists only because an old template required it, ask whether it still helps. Removing clutter makes the system easier to run and easier to audit.

Frequently asked questions#

Do I still need ISO 27001 to get ISO 27701?#

No. ISO 27701:2025 is a standalone standard. Many organisations still use both together, but ISO 27001 is no longer a prerequisite.

Is my ISO 27701:2019 certificate still valid?#

Yes, for now. Ask your certification body about its transition rules and final dates, since these were still being confirmed when this was written.

Does ISO 27701 make us compliant with privacy laws?#

No. It helps you build a system that supports compliance, but a law has its own legal tests. Take legal advice for your specific duties.

For a full overview, read our complete guide to ISO 27701 or contact AdWiser to plan your move.

Found this useful?

Share it with your network, and follow AdWiser Enterprise Consulting on LinkedIn for more certification guides and compliance tips.

Share:

Leave a Comment

Comments are reviewed before they appear. Please keep them relevant and leave out web links.

Ready to put this into practice?

Start with the ISO 27701:2025 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp