Skip to content

Integrated Assurance®

Integrated Assurance Maturity Model (IAMM®)

A structured way to understand how effectively an organization connects risk, technology, cybersecurity, operations, governance and resilience as an enterprise capability.

Understand where Integrated Assurance capabilities are established, where they remain fragmented and where improvement may have the greatest organizational impact.

The definition

What is the Integrated Assurance Maturity Model?

The Integrated Assurance Maturity Model (IAMM®) is the maturity model associated with Patrick M. Hayes’s Integrated Assurance® operating model. It provides a structured way to examine how effectively assurance operates across an organization, where capabilities remain fragmented or underdeveloped, and where closer coordination may be needed. IAMM examines governance, architecture and engineering, IT and engineering operations, risk, compliance and audit, metrics and reporting, and culture and collaboration. Each domain is considered separately against five maturity levels, recognizing that an organization’s capabilities rarely develop evenly. The purpose is not to produce one overall score or certify compliance. It is to understand the practices, evidence and operating relationships behind the current condition, then determine where improvement would be most useful in the organization’s business context.

Developed by Patrick M. Hayes as part of his Integrated Assurance® work.

Why Integrated Assurance Needs a Maturity Model

Organizations can have capable individual functions while still struggling to connect decisions across them. Cybersecurity, risk management and IT may each operate effectively. Finance, operations, architecture, compliance and governance may each have established processes.

Yet leadership can still lack a reliable view of how decisions and dependencies interact across those functions. IAMM examines the enterprise capability created by those connections, not simply whether individual departments perform their jobs well.

How IAMM Relates to Integrated Assurance

Integrated Assurance® is the operating model. IAMM® is the maturity model used to evaluate the development of that capability.

The operating model connects how the enterprise governs, designs, operates, manages risk, measures and collaborates. IAMM examines how consistently those connections work and how deeply assurance is part of normal organizational practice.

Maturity Is Not the Same as Compliance

IAMM is not another compliance checklist. A technically capable organization can still have weak Integrated Assurance when decisions, dependencies, risk information and recovery expectations remain fragmented. Maturity is not proof that an organization is secure or compliant; its purpose is to improve understanding and decision quality.

How Integrated Assurance complements GRC

Organizations rarely move from fragmented assurance to integrated assurance in one step, and no organization needs to reach the final level everywhere to benefit from the model.

The IAMM is intended to show where assurance is fragmented, where coordination is developing and where assurance has become part of how the organization actually operates.

More importantly, it helps leadership decide where greater maturity would create meaningful business value. The objective is not to achieve Level 5 everywhere. It is to understand the current condition honestly and make deliberate decisions about what needs to improve.

The question is not how mature the organization can become. It is how mature it needs to be.

The maturity levels

Understanding IAMM Maturity

  1. 01Fragmented

    Assurance activities largely operate independently, with limited shared governance, inconsistent integration and isolated measures.

  2. 02Defined

    Policies, frameworks and basic practices exist, but integration and cross-functional application remain inconsistent.

  3. 03Aligned

    Cross-functional practices begin to emerge. Ownership becomes clearer, shared information improves and assurance activities become more coordinated.

  4. 04Embedded

    Assurance becomes integrated into governance, engineering, operational processes, measurement and decision-making.

  5. 05Institutionalized

    Assurance functions as an enterprise capability and is embedded in strategic planning, governance, culture and continuous decision-making.

These levels describe progression in organizational capability, not simply the accumulation of controls. Reaching the highest level does not guarantee security, resilience, compliance, insurability or business survival.

The six domains

What IAMM Examines

The IAMM evaluates maturity across six organizational domains. This matters because organizations rarely mature evenly. Governance may be highly developed while operational integration remains fragmented. Architecture may be mature while metrics still provide little business context.

Looking at the domains independently exposes those differences and helps leadership see where fragmentation creates dependencies, gaps or unnecessary friction.

  1. Governance

    How assurance is governed, coordinated and connected to enterprise decisions.

    It examines shared decision authority, executive involvement and cross-functional ownership. These connections help assurance priorities become enterprise decisions rather than competing departmental agendas.

  2. Architecture & Engineering

    How assurance is incorporated into architecture, design and engineering practices.

    It examines whether requirements, reusable patterns and design evidence connect to policy and risk expectations. Assurance needs to shape what the organization builds, not only review it afterward.

  3. IT & Engineering Operations

    How assurance becomes part of operational processes, change, recovery and day-to-day execution.

    It examines shared operating information, control ownership and tested recovery within everyday workflows. These practices connect design intent to the services the business actually runs.

  4. Risk, Compliance & Audit

    How controls, risk information, compliance activities and audit are coordinated rather than managed as separate views of the organization.

    It examines coordinated frameworks, accountable ownership and correction of underlying control failures. Integrated Assurance needs these perspectives to inform action across domains, not remain isolated reports.

  5. Metrics & Reporting

    Whether measurement provides leadership with meaningful information about risk, performance, remediation and business consequence.

    It examines whether evidence and measures influence priorities, investment and risk decisions. Leadership needs information about business impact and effectiveness, not just activity counts.

  6. Culture & Collaboration

    Whether responsibility for assurance is shared across the organization and reinforced through leadership behavior and working practices.

    It examines shared responsibility, embedded roles and the ability to resolve issues across organizational boundaries. Assurance becomes an enterprise capability only when people sustain those connections in daily work.

The model

Six domains across five levels

Governance
  1. Level 1 · Fragmented

    Security and IT operate in silos with no shared governance mechanisms.

  2. Level 2 · Defined

    Policies exist but lack cross-functional enforcement or integration.

  3. Level 3 · Aligned

    Cross-functional risk forums and workflows are emerging.

  4. Level 4 · Embedded

    An Integrated Assurance Council oversees risk, investment, and policy decisions.

  5. Level 5 · Institutionalized

    Assurance is integral to strategic planning and enterprise governance.

Architecture & Engineering
  1. Level 1 · Fragmented

    Security is applied after-the-fact with little design integration.

  2. Level 2 · Defined

    Reference architectures exist but are inconsistently applied.

  3. Level 3 · Aligned

    Secure-by-design principles adopted in review cycles.

  4. Level 4 · Embedded

    Reusable secure patterns and policy-as-code are integrated into engineering pipelines.

  5. Level 5 · Institutionalized

    Assurance is a foundational design constraint; artifacts are governed and auto-validated.

IT & Engineering Operations
  1. Level 1 · Fragmented

    Availability is prioritized over security; controls are ad hoc or absent.

  2. Level 2 · Defined

    Basic security checks incorporated into change control processes.

  3. Level 3 · Aligned

    Shared telemetry and partial control ownership across teams.

  4. Level 4 · Embedded

    Policies and recovery standards are automatically enforced across systems.

  5. Level 5 · Institutionalized

    Operations are accountable for assurance KPIs; assurance is embedded in every lifecycle phase.

Risk, Compliance & Audit
  1. Level 1 · Fragmented

    Risk registers are static; audits are limited and event-driven.

  2. Level 2 · Defined

    Compliance frameworks are adopted inconsistently, contributing to audit fatigue.

  3. Level 3 · Aligned

    Control harmonization is in progress; ownership is being clarified.

  4. Level 4 · Embedded

    Control testing is automated; compliance is federated across domains.

  5. Level 5 · Institutionalized

    Assurance is adaptive, continuous, and audit-ready by default.

Metrics & Reporting
  1. Level 1 · Fragmented

    Isolated, technical metrics lacking context or strategic use.

  2. Level 2 · Defined

    Output-driven dashboards in place.

  3. Level 3 · Aligned

    Risk and remediation timelines are tracked collaboratively.

  4. Level 4 · Embedded

    Metrics drive prioritization, governance, and resource allocation.

  5. Level 5 · Institutionalized

    Metrics demonstrate convergence, impact, and cultural adoption of assurance.

Culture & Collaboration
  1. Level 1 · Fragmented

    Security is seen as obstructive; no shared responsibility.

  2. Level 2 · Defined

    Awareness is basic and engagement reactive.

  3. Level 3 · Aligned

    Assurance champions emerge; inter-team collaboration begins.

  4. Level 4 · Embedded

    Security roles are embedded; cross-functional collaboration formalized.

  5. Level 5 · Institutionalized

    Security and assurance are core cultural values reinforced by leadership behavior.

From assessment to action

Knowing where you are is different from knowing what to do next

The IAMM establishes the current condition. The Integrated Assurance implementation methodology provides a practical way to move from that condition toward greater coordination where greater maturity is warranted.

The two should not be treated as identical five-step scales. Maturity is assessed across organizational domains. Implementation is shaped around the organization’s actual gaps, priorities and operating environment.

IAMM tells you where assurance stands. The implementation methodology helps determine what happens next.

The practical path

Five stages for building Integrated Assurance

  1. Stage 1

    Define Strategic Intent and Organizational Alignment

    Establish leadership consensus, define shared outcomes and prepare the enterprise for a unified assurance model.

  2. Stage 2

    Baseline Capabilities and Identify Friction Points

    Assess current assurance maturity, surface capability fragmentation and identify control breakdowns and operational friction.

  3. Stage 3

    Execute Targeted Pilots and Codify Patterns

    Demonstrate value through focused pilots while developing reusable patterns, traceability and practical operating approaches.

  4. Stage 4

    Operationalize Assurance at Scale

    Expand assurance across the enterprise through repeatable practices, automation, federation and governance loops.

  5. Stage 5

    Institutionalize Assurance as an Enterprise Capability

    Embed assurance into leadership, strategic decision-making, funding, governance and continuous improvement.

Explore the implementation methodology

Stage 1

Define Strategic Intent and Organizational Alignment

Key actions

  • Appoint an executive sponsor and Integrated Assurance Lead
  • Form a cross-functional Assurance Council
  • Ratify a shared mission, principles, and outcomes
  • Identify regulatory or transformation drivers
  • Socialize the vision across domains

Success indicators

  • Executive sponsorship formalized
  • Shared vocabulary established
  • Strategic alignment across the enterprise

Stage 2

Baseline Capabilities and Identify Friction Points

Key actions

  • Inventory existing frameworks, controls, and governance
  • Map controls to business processes
  • Document known issues and audit failures
  • Capture pain points from operations, delivery, and risk

Success indicators

  • Gaps and friction points clearly documented
  • Ownership ambiguity and control duplication identified
  • Quick wins and systemic blockers prioritized

Stage 3

Execute Targeted Pilots and Codify Patterns

Key actions

  • Launch high-impact pilots (DevSecOps, vendor risk, identity)
  • Establish traceability between controls and execution
  • Develop reusable playbooks and design patterns
  • Build dashboards to visualize assurance

Success indicators

  • Operational teams validate pilot outcomes
  • Patterns and templates reused across teams
  • Assurance becomes traceable and measurable

Stage 4

Operationalize Assurance at Scale

Key actions

  • Deploy federated assurance operating model
  • Offer self-service templates and secure defaults
  • Integrate assurance into change and planning cycles
  • Embed security and compliance roles in delivery teams

Success indicators

  • Risk ownership is internalized at team level
  • Assurance behaviors embedded in workflows
  • Metrics support continuous investment decisions

Stage 5

Institutionalize Assurance as an Enterprise Capability

Key actions

  • Evolve the Assurance Council into a governance body with funding authority
  • Integrate assurance metrics into enterprise dashboards
  • Adopt continuous improvement loops
  • Leverage posture for external assurance and board reporting

Success indicators

  • Assurance posture influences enterprise decisions
  • Leadership owns and understands risk
  • Organization demonstrates resilience and defensibility

Using the model

How Organizations Can Use IAMM

Use IAMM to understand current capability, identify fragmentation, find areas requiring validation, support leadership conversations and set improvement priorities. Revisit practices and evidence as changes are implemented to examine progress over time. The value is understanding why the organization is at its current point and what should change, not simply receiving a designation.

An IAMM assessment should not begin with a questionnaire designed to produce a maturity score.

It begins by examining how assurance actually works across the six domains. Existing frameworks, reporting, governance, operating practices and evidence help establish the current condition. Interviews help explain why those conditions exist and where fragmentation affects the business.

The result is not simply six maturity ratings. It is a view of where assurance is working, where coordination breaks down and which improvements would create the most useful change.

The useful output is the gap between current maturity and required maturity

An organization may determine that Level 3 is entirely appropriate in one area while Level 4 or Level 5 is necessary somewhere else. That is not a weakness in the model. It is the point of using it.

The assessment should identify where current maturity is sufficient, where additional coordination would reduce risk or friction and where the organization may be investing in maturity that does not materially improve the business.

IAMM Self-Assessment

Explore Your Integrated Assurance Maturity

The IAMM Self-Assessment gives you a quick view across the six domains of Integrated Assurance and helps identify where assurance is coordinated, where it remains fragmented and where a closer look may be useful.

18 questions · 6 domains · About 5 minutes

Three questions per domain produce an indicative profile based on your responses, not one overall score. “Not Sure” responses are shown as uncertainty, not treated as low maturity. No account or contact information is required to see results. Answers stay in your browser unless you choose to send them. This is not a certification, independent audit, formal assurance opinion or formal IAMM assessment.

Maturity without business context becomes another compliance exercise.

Origins

Development of IAMM

Patrick M. Hayes developed IAMM as part of his broader work on Integrated Assurance®. Integrated Assurance: Unified Risk Strategy is part of the underlying body of work. This attributes the particular model described here, not the invention of maturity models or the broader integrated assurance discipline.

The IAMM grew from Patrick M. Hayes’ work in enterprise security architecture, assurance, governance and operations. Patrick became a Zachman Enterprise Architect in 2000, which shaped his approach to viewing organizations as interconnected systems rather than collections of independent functions.

Over more than two decades of architecture, assessment, security operations, governance and executive work, the same problem repeatedly appeared: capable functions could each hold valid views of risk while leadership was still left to reconcile those views at the moment a decision had to be made.

Integrated Assurance developed from that problem. The IAMM provides a way to assess how far an organization has progressed from fragmented functional assurance toward a more coordinated enterprise capability.

IAMM and Business Survivability

Organizations need to understand how technology, cyber risk, operational dependency, governance, recovery and financial consequence affect their ability to continue creating value during disruption.

IAMM helps examine whether the organizational capability needed to make those decisions is developing coherently. Stronger coordination can support a more informed view of dependencies and recovery expectations; a maturity designation does not guarantee survival.

Is IAMM a Cybersecurity Maturity Model?

No.

Cybersecurity is an important component of Integrated Assurance, but IAMM looks beyond security controls to relationships among technology, governance, operations, risk, resilience and business decision-making.

Control-focused cybersecurity frameworks can provide useful requirements and evidence. They serve a different purpose and can complement this examination of enterprise capability; IAMM does not replace them or suggest they are inferior.

Questions and answers

Frequently Asked Questions

What does IAMM stand for?

IAMM stands for Integrated Assurance Maturity Model, the maturity model associated with Patrick M. Hayes’s Integrated Assurance® operating model.

What is the Integrated Assurance Maturity Model?

IAMM is a structured way to examine the development of Integrated Assurance as an enterprise capability across six organizational domains and five maturity levels. Domains are examined separately, not combined into one overall maturity score.

Who developed IAMM?

Patrick M. Hayes developed IAMM as part of his work on Integrated Assurance and the relationships among enterprise risk, technology, cybersecurity, operations, governance and resilience.

How does IAMM relate to Integrated Assurance?

Integrated Assurance® is the operating model. IAMM® is the maturity model used to examine how far that capability has developed across the organization.

Is IAMM a cybersecurity maturity model?

No. Cybersecurity is an important component, but IAMM examines enterprise relationships across governance, architecture, operations, risk, measurement and culture—not security controls alone.

Is IAMM a compliance framework?

No. IAMM examines organizational capability and coordination. Compliance obligations and control frameworks can supply relevant evidence, but compliance is not the same as Integrated Assurance maturity.

Does IAMM provide a certification?

No. Neither the model nor the public self-assessment provides a certification or accreditation. A maturity designation is not a guarantee of security, resilience, compliance or business survival.

What does an IAMM assessment measure?

An IAMM assessment examines how assurance operates across each of the six domains using practices, evidence, governance and operating relationships. The public 18-question self-assessment offers an indicative profile based on the respondent’s answers, not an independent audit or formal assurance opinion.

How can an organization improve its Integrated Assurance maturity?

Examine the evidence behind each domain, identify fragmentation and unclear ownership, and agree which capabilities need to improve in the business context. Use targeted changes, pilots and operating evidence to test progress; Level 5 everywhere is not the objective.

Related Resources

Continue with the operating model, its underlying books, practical learning or the indicative self-assessment.

Explore the thinking

Further reading and conversations on Integrated Assurance Maturity Model

Books

Speaking sessions

  • RRC Polytech Inspire 2025

    October 2025

Speaking & Media Archive

An assessment conversation is usually the faster route to a useful answer.

The objective is not to sell an organization a path to Level 5. It is to understand where greater coordination would actually matter.