RESILIAM INSIGHTS

Resiliam’s Insights translate key developments in information security, privacy, and AI governance into clear, practical guidance.

latest Insights

Need personalized guidance on these topics?

Executive Summary

AI governance is already showing up in security reviews, procurement processes, and client due diligence. Organizations are being asked not just whether controls exist, but how AI is governed, by whom, and through what processes. ISO/IEC 42001:2023 provides a structured, certifiable management system framework for AI governance that integrates with existing programs such as ISO 27001, allowing organizations to extend established governance practices to AI rather than starting from scratch.

AI Governance Is Already Being Evaluated

The conversation around AI governance has changed in enterprise environments.

Organizations are no longer being asked whether they use AI. They are being asked how it is governed, how risk is managed, and how accountability is enforced, and those questions are showing up in security reviews, procurement processes, and client conversations with increasing regularity.

For many organizations, internal programs have not fully caught up. Governance exists in some form, but it is often inconsistent across teams or difficult to explain clearly when questions become specific. That gap creates real friction, slowing evaluations, introducing uncertainty for clients, prospects, and auditors, and making trust harder to establish.

Existing Governance Structures Don’t Go Far Enough

Most organizations already operate structured information security and risk management programs. Frameworks such as ISO 27001, SOC 2, and ISO 27701 provide well-established governance foundations.

But where these programs fall short is in addressing and managing the new and dynamic risks posed by AI technologies.

AI introduces model behavior considerations, training data dependencies, and dynamic outputs that do not map cleanly onto traditional control structures. As a result, governance becomes inconsistent across use cases and difficult to validate when reviewed externally. Policies may be documented and oversight may be defined, but when it comes time to demonstrate how governance actually works, the answers are not always consistent or easy to assess.

Where ISO 42001 Fits

ISO/IEC 42001:2023 is the first certifiable management system standard dedicated to artificial intelligence. It applies the same management system model used in standards like ISO 27001 and ISO 9001 to AI governance, establishing requirements for scoping, accountability, risk management, and continual improvement.

For organizations already operating under established frameworks, ISO 42001 is designed to integrate rather than duplicate. In practice, that means:

  • Defining clear ownership and accountability for AI systems;
  • Establishing repeatable processes for identifying and evaluating AI-related risks;
  • Assessing impacts arising from the use of AI systems;
  • Managing AI system lifecycles from development or procurement through deployment and ongoing monitoring;
  • Extending third-party management processes to address AI-specific considerations;
  • Integrating AI governance into existing control environments; and
  • Creating mechanisms for continual improvement.

The value is not in any single control. It is in applying governance consistently across the organization – in a way that is structured enough to withstand external scrutiny and flexible enough to adapt as AI use evolves.

A Familiar Pattern

There is a useful parallel in how ISO 27001 evolved. Early on, certification was not a requirement. Organizations relied on internal controls and partial alignment with established frameworks. That approach worked until clients, prospects, and auditors began asking for evidence of how security was actually managed.

Organizations that moved early were able to reduce friction in evaluations, build trust more quickly, and establish a foundation that scaled as expectations rose. Over time, certification became a baseline expectation in many industries.

AI governance is following the same trajectory. The timeline is shorter – driven by regulatory development, client expectations, and the pace of AI adoption – but the underlying pattern is familiar.

A Practical Path Forward

ISO 42001 offers a practical roadmap to building a robust AI governance program that adapts and scales as AI usage grows and emerging technologies introduce novel risks.

In practice, that typically means mapping current controls to AI use cases, identifying gaps in how those controls are applied, establishing repeatable governance processes, and aligning AI governance with existing frameworks and standards. Organizations with mature information security or privacy programs will find much of this foundation already in place.

Why It Matters Now

Organizations are already being evaluated on how AI is governed, whether or not they have formalized their approach. Without a structured management system, responses to governance inquiries tend to vary, evaluations take longer, and confidence is harder to establish.

ISO 42001 provides a structured, internationally recognized basis for AI governance that builds on existing security and risk management practices. For organizations that have already invested in frameworks like ISO 27001, it is a practical extension, and an increasingly important one as expectations around AI governance continue to develop.

 

Executive Summary

As AI shifts from value-add to business necessity, organizations face a critical challenge: how to govern AI responsibly, defensibly, and at scale. ISO/IEC 42001 offers the first international management system standard dedicated specifically to artificial intelligence, providing a structured framework that integrates with existing governance practices to strengthen trust and manage AI-related risks.

For many organizations today, artificial intelligence has shifted from a value-add to a business necessity. Whether organizations are deploying generative AI tools, using AI to assist in decision-making, or embedding machine learning into core products and services, AI is increasingly business-critical. With that shift comes a familiar challenge: how do organizations govern AI in a way that is responsible, defensible, and scalable over time?

ISO/IEC 42001:2023 (“ISO 42001”), the international standard for Artificial Intelligence Management Systems (“AIMS”), offers a practical answer. Rather than focusing on any single technology or regulation, ISO 42001 provides a structured, certifiable framework for governing AI across its lifecycle. This article provides a practical overview of ISO 42001, explains why it matters, and highlights how organizations can use it to strengthen trust, manage risk, and future-proof their approach to AI.

What Is ISO 42001?

ISO 42001 is the first international management system standard dedicated specifically to artificial intelligence. Published in late 2023, it defines requirements and guidance for establishing, implementing, maintaining, and continually improving an Artificial Intelligence Management System.

Like other ISO management system standards (such as ISO 27001 for information security or ISO 9001 for quality), ISO 42001 follows a familiar structure. The standard includes requirements for governance, leadership, performance evaluation, and continual improvement, all within the context of the organization’s in-scope AI technologies and supporting resources. This design allows ISO 42001 to function either as a standalone management system or to integrate cleanly with existing management systems, extending established governance practices into the AI domain rather than starting from scratch. For organizations already operating mature security, privacy, or risk management programs, this alignment significantly lowers the barrier to adoption.

Why AI Governance Requires a Management System

AI introduces risks and impacts that differ meaningfully from traditional IT systems. These include, for example:

  • Inaccurate, misleading, or biased outputs; 
  • Enhanced privacy, security, and regulatory concerns; and
  • Over-reliance on AI outputs without sufficient human oversight.

Many organizations attempt to address AI risk through siloed efforts across IT, legal, security, and privacy teams. While well-intentioned, these fragmented efforts often fail to scale and become increasingly difficult to coordinate as AI use expands. ISO 42001 offers a collaborative approach: rather than treating AI governance as a collection of disconnected controls, the standard establishes an interconnected management system built around consistency, accountability, and continual improvement.

Scope and Applicability Across Industries

Among ISO 42001’s greatest merits is its flexibility; the standard is designed to be applicable to organizations of all sizes and across all sectors. Organizations define the scope of their AIMS based on how they interact with AI systems.

ISO 42001 recognizes several common roles, including:

  • AI developers, who design and build AI systems;
  • AI providers, who offer AI-enabled products or services; and
  • AI users, who deploy or rely on AI systems developed by others.

Most organizations will fall into one or more of these categories. A company using third-party generative AI tools, for example, may primarily be an AI user, while also developing internal models for specific business functions. ISO 42001 accommodates this reality by allowing organizations to tailor requirements and controls to their actual use cases.

Core Components of an AI Management System

At its core, ISO 42001 requires organizations to establish governance processes that span the full AI lifecycle. Key components include the following.

AI Policies and Acceptable Use

Organizations must document policies governing the development or use of AI systems. These policies typically address topics such as:

  • Approved AI systems and use cases;
  • Expectations for human oversight and professional judgment; and
  • Processes for reporting incidents or concerns.

Well-designed AI policies ensure discipline without stifling innovation, helping users understand both the capabilities and limitations of AI tools.

Governance Structure and Accountability

ISO 42001 places strong emphasis on organizational accountability. This includes defining roles and responsibilities for AI governance, establishing escalation paths for AI-related concerns, and ensuring leadership oversight of AI risks and objectives.

Clear accountability helps avoid common missteps such as “shadow AI” deployments, inconsistent decision-making, or unclear ownership when issues arise.

AI System Impact Assessments and AI Risk Assessments

ISO 42001 introduces a structured approach to understanding and managing AI-related risks through the use of both AI system impact assessments and AI risk assessments. While related, these assessments serve distinct but complementary purposes within an organization’s AIMS.

AI system impact assessments evaluate the potential positive and negative impacts of an AI system’s deployment, intended use, and foreseeable misuse on individuals, groups, and society. These assessments help organizations understand how AI systems may affect their ability to achieve their AIMS objectives (e.g., accountability, security, privacy, and transparency), as well as provide important context for evaluating downstream organizational risks.

AI risk assessments build on this foundation by examining potential events and outcomes related to the development or use of AI systems and the consequences those outcomes may have for the organization. In contrast to traditional IT risk assessments, ISO 42001 requires organizations to consider both negative risks that must be mitigated and positive risks that may present opportunities for improvement and increased effectiveness. Organizations may also look to supporting guidance, such as ISO/IEC 23894, when designing and executing AI risk assessment processes.

Together, AI system impact assessments and AI risk assessments support informed decision-making and continual improvement across the AI system lifecycle, helping organizations manage risk while demonstrating responsible and trustworthy use of AI.

Lifecycle Management and Monitoring

ISO 42001 requires organizations to define criteria and controls across the AI system lifecycle, including requirements and specification, verification and validation, deployment, and ongoing operation and monitoring. Some controls apply at the time of AI system development or procurement, while others (such as performance monitoring and change management) become critical once systems are deployed and in use.

This lifecycle-based approach closely aligns with robust project management practices, helping organizations apply appropriate governance at each stage rather than relying on one-time reviews. The specific controls implemented will vary depending on whether an organization is developing AI systems or using those provided by third parties, but in all cases, continuous oversight is essential to maintaining trust, effectiveness, and alignment with organizational objectives.

Third-Party Management

Few organizations build or operate AI systems entirely on their own. As a result, ISO 42001 includes requirements for managing third parties involved in the AI lifecycle, including AI vendors, service providers, and, in some cases, clients or business partners that rely on or are affected by the organization’s use of AI.

Effective third-party management extends beyond traditional vendor oversight. Organizations may need to demonstrate responsible AI practices through contractual controls, due diligence questionnaires, documentation reviews, and ongoing monitoring, as well as through client-facing disclosures and responses to inquiries.

These expectations often surface through contractual obligations, customer due diligence requests, and RFP processes – even in the absence of formal regulatory requirements. By integrating AI considerations into existing third-party and client engagement processes, organizations can provide greater transparency, manage risk more effectively, and build trust.

Looking Ahead

As AI technologies continue to evolve, expectations around their governance will continue to rise. While ISO/IEC 42001 is a voluntary standard rather than a regulation, it provides organizations with a structured and defensible approach to AI governance that aligns naturally with emerging legal, regulatory, and customer expectations.

Rather than prescribing specific controls or playbooks, ISO 42001 embeds AI governance into the same management system principles that have served as the bedrock of information security, privacy, and risk management programs for years. By applying these familiar principles to AI, organizations can establish governance practices that are consistent, scalable, and capable of adapting as AI use cases and risks change over time.

Visit our services page to learn how Resiliam can help with ISO 42001.

Executive Summary

AI system impact assessments represent the latest evolution in organizational impact analysis, addressing unique challenges that traditional security and privacy assessments don't fully capture. Learn how these structured evaluations help organizations make more deliberate, well-governed decisions about AI deployment while demonstrating responsible consideration of AI's broader impacts.

AI system impact assessments represent the latest step in a longer evolution of organizational impact analysis – one that began with business impact analyses (BIAs), expanded through privacy impact assessments (PIAs), and is now being extended to address the unique challenges posed by artificial intelligence. AI system impact assessments are evolving to become a baseline expectation for AI-enabled organizations, particularly those deploying potentially high-risk AI systems. These assessments identify potential consequences that are not fully captured by traditional security, privacy, or continuity assessments alone.

Several forces are driving this shift. Regulators increasingly expect organizations to demonstrate that they have considered how AI systems may affect various parties, particularly where AI plays a role in consequential decisions. Many organizations are also finding that AI-related concerns, such as bias, fairness, and over-dependency, do not align cleanly with existing risk or compliance models. Standards bodies have responded by codifying these expectations in AI governance frameworks, including ISO/IEC 42001 (“ISO 42001”) and the companion guidance in ISO/IEC 42005 (“ISO 42005”).

AI system impact assessments sit at the intersection of these pressures. When approached thoughtfully, they help organizations move toward more deliberate, well-governed decisions about whether, where, and how AI should be used. Furthermore, they communicate to internal and external stakeholders that the broader impacts of AI use at the organization have been responsibly considered.

What Is an AI System Impact Assessment?

An AI system impact assessment is a structured process used to identify and evaluate the potential impacts – both positive and negative – of developing, deploying, and using an AI system. These impacts may affect the organization itself, individuals, groups, or society more broadly.

AI system impact assessments examine how an AI system behaves in context, how its outputs are used, and what consequences may follow, including from foreseeable misuse.

Crucially, impact assessments are not limited to identifying harms. They also document expected benefits, such as improved efficiency, better decision-making, or expanded access to services. This balanced view helps organizations assess whether an AI system’s benefits justify its potential downsides.

Impact Assessments vs. Risk Assessments

Traditional information security risk assessments have long been used to evaluate risks affecting the confidentiality, integrity, and availability of systems and data. They are typically inward-facing and defensive, focusing on how threats could exploit vulnerabilities to harm the organization and how those risks can be mitigated through controls. 

AI system impact assessments take a more outward-looking and balanced view. Instead of asking only what could go wrong, they examine how an AI system may affect individuals, groups, or society when used in intended ways or foreseeably misused. This includes negative impacts, such as unfair or harmful outcomes, as well as positive impacts, such as increased productivity, efficiency, or consistency in decision-making.

AI risk assessments build on this foundation by considering events and outcomes – both positive and negative – arising from the development, deployment, and use of AI systems. Organizations can then look to mitigate potential negative risks through enhanced controls while seeking opportunities to amplify potential positive outcomes.

In practice, these assessments are complementary rather than redundant. AI system impact assessments are most effective when performed upstream and used as an input to AI risk assessments. By first identifying the full range of potential impacts, organizations are better positioned to assess which risks matter most, to whom, and why.

Core Elements of an Effective System Impact Assessment

While there is no universally required format, effective AI system impact assessments typically address a few core elements:

  • System context and purpose: What the system does, how it is used, and what falls outside its intended scope.
  • Affected stakeholders: Individuals or groups who may be directly or indirectly impacted by the organization’s use or development of the AI system.
  • Potential benefits: The value the organization expects the AI system to deliver.
  • Potential harms: Foreseeable negative consequences, including those arising from foreseen misuse.
  • Governance thresholds: Criteria that trigger additional review, approval, modification, or a decision not to deploy.

In practice, these elements are often informed by the risk profile of the AI system itself. Higher-risk systems, particularly those used in consequential decision-making, may warrant deeper analysis, broader stakeholder consideration, and more formal governance oversight. This risk-based approach also aligns with emerging regulatory requirements, such as the EU AI Act and Colorado’s SB24-205, which tie impact assessment obligations to the classification of certain AI systems as “high-risk”.

The complementary ISO 42005 standard reinforces the aforementioned elements while allowing organizations to scale the depth and formality of their assessments based on the system’s potential impact, regulatory exposure, and organizational context.

Making Impact Assessments Sustainable

A common pitfall is treating AI system impact assessments as one-time exercises performed solely to satisfy a requirement. This approach rarely delivers lasting value.

Instead, organizations should embed impact assessments into the AI lifecycle by:

  • Conducting assessments early (before full deployment)
  • Revisiting them periodically and when material changes occur
  • Aligning them with existing risk, compliance, and governance processes
  • Scaling effort to the system’s risk and impact profile

This approach keeps assessments practical, repeatable, and decision-oriented.

Laying the Foundation for an AI Management System

AI system impact assessments represent a shift in how organizations are expected to think about technology – not just in terms of performance and security, but in terms of consequences. Organizations that adopt this mindset early will be better positioned to deploy AI responsibly, adapt to evolving requirements, and maintain trust with stakeholders. More importantly, they will be equipped to make deliberate, well-governed choices about how AI fits into their operations, both today and in the future.

For those seeking to formalize this approach, AI system impact assessments also play a foundational role in building a broader AI management system. Standards such as ISO 42001 provide a structured framework for embedding impact assessments, risk management, and governance into a coherent, auditable program. Pursuing alignment with, or certification to, ISO 42001 can help organizations demonstrate that their approach to AI is systematic, repeatable, and credibly aligned with emerging global expectations.

Executive Summary

The Cybersecurity Maturity Model Certification is no longer a future consideration – it's an imminent reality for DoD supply chain businesses. Discover a practical roadmap to CMMC Level 2 readiness, learn about common pitfalls to avoid and get strategic guidance to improve your likelihood of certification success.

As cybersecurity requirements continue to expand across the U.S. Department of Defense (“DoD”) supply chain, organizations are facing increased pressure to demonstrate mature, auditable security programs. The Cybersecurity Maturity Model Certification (“CMMC”) is no longer a future consideration – it’s an imminent reality for many businesses.

The certification has three levels: Level 1 (Foundational), Level 2 (Advanced), and Level 3 (Expert). For many firms in the DoD supply chain, CMMC Level 2 represents the most common certification threshold.

This paper outlines a practical roadmap to CMMC Level 2 readiness, highlights common pitfalls, and offers strategic guidance to help organizations reduce risk and improve their likelihood of certification success.

Understanding CMMC Level 2 and Why It Matters

CMMC is a DoD program designed to ensure that contractors handling federal information meet robust cybersecurity standards. The program is overseen by The Cyber AB, an independent accreditation body responsible for administering CMMC assessment processes.

There are three levels in the CMMC scheme, each with different applications:

  • Level 1 applies to organizations handling Federal Contract Information (“FCI”) only – information provided by or generated for the government under a contract that is not intended for public release but is less sensitive than Controlled Unclassified Information (“CUI”).
  • Level 2 applies to organizations that store, receive, process, store, or transmit CUI – sensitive information that is not classified but requires safeguarding under federal law or regulation (e.g., defense technical data, legal documents).
  • Level 3 applies to organizations supporting high-priority DoD programs and high-risk environments.

For many firms, CMMC Level 2 applicability arises through activities such as:

  • Providing legal, advisory, or consultative services to DoD contractors, or
  • Receiving documents, contracts, or evidence containing CUI in the course of performing work for DoD-related clients.

At the end of the day, one of the most common drivers for CMMC Level 2 certification is a client contractual obligation – without it, organizations may be disqualified from current or future work.

CMMC Level 2 at a Glance

CMMC Level 2 is based on the 110 security requirements in NIST SP 800-171 and contains 320 auditable assessment objectives.

For most programs, a third-party assessment conducted by a Certified 3rd-Party Assessment Organization (“C3PAO”) is required. Certification is valid for three years but requires annual affirmation of compliance by a senior official of the organization.

Unlike some other compliance frameworks, CMMC Level 2 requires 100% implementation of all applicable requirements prior to certification. A single unmet requirement can prevent certification, making preparation and validation critical.

The Certification Roadmap

1. Scoping and Boundary Definition

The most important early decision in a CMMC program is scope. Organizations must identify all systems, people, applications, suppliers, and locations that store, process, or transmit CUI.
Defining a clear CMMC assessment boundary allows firms to reduce unnecessary compliance burden and avoid accidental inclusion of enterprise-wide systems.

Many organizations benefit from segregating and isolating CUI in a secure enclave. A well-designed enclave can significantly reduce audit complexity, remediation costs, and certification risk.

2. Gap Assessment

A gap assessment compares current practices against CMMC Level 2 requirements and identifies where controls are fully implemented, partially implemented, or missing.

  • At this stage, organizations should:
  • Assess technical, administrative, and physical controls,
  • Identify remediation needs and priorities, and
  • Quantify the effort required to achieve full compliance.

Because CMMC Level 2 does not allow assessments to begin with known open gaps, remediation planning must be realistic and thorough.

3. Remediation and Control Implementation

Remediation typically involves a combination of policy development, process alignment, and technical improvements. Common activities include:

  • Drafting and formalizing required security policies
  • Ensuring procedures reflect actual practices
  • Implementing key technical controls such as:
  • Role-based access control (“RBAC”)
  • Multi-factor authentication (“MFA”)
  • Encryption at rest and in transit
  • Vulnerability management
  • System hardening

Organizations with existing ISO 27001 or SOC 2 programs often have a strong foundation, but modifications are still required to meet CMMC-specific expectations.

4. Documentation and Evidence Preparation

CMMC assessments are evidence-driven. Assessors rely heavily on documentation to validate both technical controls and organizational maturity.

Required documentation and evidence commonly includes:

  • System Security Plan (“SSP”)
  • Policies and procedures
  • System configurations and screenshots
  • Incident response documentation
  • Access reviews and audit logs
  • Security awareness training records

Incomplete or inconsistent evidence is one of the leading causes of assessment failure.

5. The System Security Plan (“SSP”)

The SSP is the cornerstone of a successful CMMC assessment. It serves as the assessor’s primary reference for understanding how controls are implemented and managed.

An effective SSP clearly defines the system boundary, documents systems and data flows, identifies roles and responsibilities, maps each requirement to implemented practices, and documents security policies, procedures, and technical safeguards.The SSP must reflect reality. If it is inaccurate or outdated, assessors will question all supporting documentation.

6. Self-Assessment and SPRS Submission

Before pursuing an official Level 2 assessment, organizations must:

  • Rate their own maturity in implementing each of the 110 requirements,
  • Generate a NIST SP 800-171 Supplier Performance Risk System (“SPRS”) score, and
  • Submit the score to the SPRS.

A current SPRS score is mandatory before scheduling a C3PAO assessment.

7. Third-Party Assessment and Certification

While it will depend on organizational context and contractual obligations, most Level 2 assessments must be completed by an accredited third party. To start the certification process, organizations will:

  • Choose an authorized C3PAO from the CMMC marketplace,
  • Schedule an assessment engagement, and
  • Provide documentation required in advance (e.g., policies, diagrams, inventories).

C3PAO assessments are then conducted through a combination of:

  • Documentation review (e.g., policies, procedures, network diagrams, asset inventories, evidence),
  • Interviews with key staff (e.g., IT, security, HR, leadership), and
  • Validation of technical controls (e.g., MFA, logging, access control enforcement, patch management, system configurations).

During the C3PAO assessment, organizations must demonstrate full implementation of all requirements.

If issues arise during the assessment, the assessor may provide provisional certification and allow a 180-day remediation window to correct deficiencies via a limited number of Plans of Action and Milestones (“POA&Ms”).

That said, many requirements are not eligible for remediation during the assessment via POA&Ms. If one of these requirements fails during the assessment, the organization will fail the audit and must undergo another audit at a future date.

Once all deficiencies are resolved and the assessment is successfully completed, certification is submitted to The Cyber AB and recognized by the DoD.

Common Challenges and How to Avoid Them

There are a number of common pitfalls that organizations should proactively work to avoid:

  • Poor Scoping Decisions: Without a secure enclave, the entire organization – including all data storage locations, email accounts, mobile devices, and guest networks – may fall in scope. This dramatically increases implementation complexity, cost, and risk of failure.
  • Inaccurate or Weak SSPs: As the SSP is viewed as the source of truth during assessments, errors can call into question all of an organization’s practices. Common SSP missteps include vague system boundaries, missing or outdated system descriptions, and no clear mapping between controls and evidence.
  • Incomplete MFA Deployment: Assessors will look for evidence of MFA everywhere, including for remote access, privileged accounts, and cloud access to CUI. Partial implementation can lead to failed assessments.

Time and Effort Expectations

CMMC Level 2 readiness is a significant undertaking that varies based on organizational maturity, scoping decisions, and prior security investments.

The following offers a reasonable expectation for timelines, assuming that the organization is approaching the undertaking with a relatively solid security foundation:

  • Scoping and Gap Assessment: 2-6 weeks.
  • Remediation: 3-6+ months. This is the highest-effort phase with the most variance in timing.
  • Evidence Collection: 3-8 weeks.
  • C3PAO Assessment: 3-8 weeks.

Conclusion

CMMC Level 2 certification can be both a compliance requirement and a strategic opportunity. Organizations that approach CMMC as a structured transformation – rather than a last-minute audit exercise – are far more likely to succeed.

With clear scoping, disciplined documentation, and a realistic roadmap, organizations can meet DoD expectations, protect sensitive information, and position themselves as trusted partners in the Defense Industrial Base.

Executive Summary

The 2025 version of ISO/IEC 27701 brings significant changes to privacy governance frameworks. Most notably, organizations can now establish and certify a standalone Privacy Information Management System without requiring ISO/IEC 27001 certification. Explore how this updated standard provides greater flexibility while maintaining robust privacy accountability.

In October 2025, the International Standards Organization (“ISO”) released a second version of its flagship standard for privacy governance, ISO/IEC 27701.

The 2025 version, entitled “Information security, cybersecurity and privacy protection — Privacy information management systems — Requirements and guidance”, updates and replaces the first edition of the standard from 2019.

Similar to the original version, the 2025 standard provides a structured, certifiable framework for organizations to demonstrate accountability, manage risks, and continually improve their privacy practices around the processing of personally identifiable information (“PII”).

That said, the 2025 version differs from its predecessor in a number of material ways.

Independence from ISO/IEC 27001

The most substantive change in the 2025 version of ISO/IEC 27001 is that it is no longer an extension to ISO/IEC 27001, the leading international standard for information security. Under the 2025 version, organizations can establish and certify a standalone Privacy Information Management System (“PIMS”) without building upon an underlying Information Security Management System (“ISMS”). In other words, ISO/IEC 27701 certification no longer requires certification to ISO/IEC 27001:2022.

That said, given the significant overlap and alignment between the required information security controls and processes in ISO/IEC 27701 and those in ISO/IEC 27001, layering a PIMS on an ISMS is likely still the most effective approach for most organizations.

But by creating independence from ISO/IEC 27001, the International Standards Organization was able to restructure ISO/IEC 27701 with the same architecture as other ISO management system standards (i.e., identical clause numbers, similar clause descriptions, etc.), enabling seamless integration with a variety of other ISO standards, including those for business continuity and quality management, not just information security.

Modified Control Sets

Another key difference in the 2025 version is a reworking of the control sets included in the Annexes of the standard.

ISO/IEC 27701:2025 contains three sets of controls within its Annex A:

  • 31 controls for PII Controllers (entities who determine the purposes and means of PII processing);
  • 18 controls for PII Processors (entities who carry out PII processing on the instructions of a Controller); and
  • 29 security controls for both PII Controllers and PII Processors.

Although the 2025 version has a new numbering scheme as compared to its predecessor, the content of the PII Controller and PII Processor controls in Annexes A.1 and A.2 were not materially changed.

The significant change comes in the form of Annex A.3, which now has mandatory information security control statements that are required for consideration of applicability, as opposed to implementation guidance only, which the 2019 version had contained.

These information security controls must be addressed by both PII Controls and PII Processors and are mapped to the 2022 version of ISO/IEC 27001.

Additional Changes

The 2025 version contains a number of other changes in relation to the prior release:

  • The organization’s privacy policy must provide a framework for setting privacy objectives;
  • The process for privacy risk treatment must identify and document elements of the organization’s information security program; and
  • Implementation guidance for all three sets of controls in ISO/IEC 27701 is now consolidated into Annex B, which should be considered when determining the organization’s relevant PII Controller, PII Processor, and security controls.

Certification and Transition

Organizations seeking initial certification to ISO/IEC 27701 should absolutely implement the 2025 version of the standard rather than its predecessor. Furthermore, ISO has already released ISO/IEC 27706:2025, a standard for certification bodies that enables them to audit and certify to the 2025 version.

That said, the Global Accreditation Cooperation Incorporated (“Global ACI”) has not yet released guidance for organizations that were already certified to the 2019 version to transition to the 2025 version. Past experience indicates that a transition window of 18-36 months will likely be allowed. Resiliam will continue to monitor Global ACI releases for developments and will provide timely updates.

Latest Insights

Need personalized guidance on these topics?