
Integrated Assurance
Unified Risk Strategy
Foundational work defining the operating model and the structural problem of fragmented assurance.
Integrated Assurance®
Integrated Assurance® connects governance, technology, cybersecurity, operations, risk and financial decision-making so organizations can understand how risk moves through the business and make better decisions about what to control, what to recover and what to finance.
Explore the operating modelThe definition
Patrick M. Hayes’s Integrated Assurance® is an enterprise operating model for connecting decisions across governance, technology, cybersecurity, operations, risk and financial resilience. It brings those perspectives together around a shared understanding of what the business depends on, how it creates value and what could interrupt that value.
The objective is not simply to coordinate assurance functions or combine their reports. It is to understand how decisions and dependencies in one part of the organization affect exposure, obligations and recovery elsewhere. Controls, architecture, operating evidence and financial consequences are considered together, so leadership can judge both prevention and the ability to continue creating value during disruption. This particular model extends the broader practice of integrated assurance across the operating enterprise without removing the expertise or accountability of individual functions.
Primary source: Patrick M. Hayes, author of Integrated Assurance: Unified Risk Strategy.
Cybersecurity, IT, enterprise risk, compliance, operations, finance, architecture, insurance and resilience often work with different information and different definitions of risk. A decision made in one area can create consequences elsewhere that leadership cannot easily see.
Individual functions may have mature processes, experienced people and useful information while the organization still struggles to understand how risk crosses the boundaries between them.
Integrated Assurance® addresses that fragmentation by connecting governance, architecture, engineering, operations, risk, compliance, audit, measurement and culture around a more coherent understanding of the enterprise.
Origins
Patrick M. Hayes became a Zachman Enterprise Architect in 2000. His work in enterprise and security architecture reinforced the importance of understanding an organization as an interconnected system rather than through the perspective of a single function.
More than two decades of work across cybersecurity, operations, governance, risk, assurance and executive leadership expanded that thinking into Integrated Assurance®. The model addresses a recurring problem: organizations can become increasingly capable within individual disciplines while the relationships between those disciplines remain difficult to see and govern.
The operating model
Integrated Assurance® extends across six organizational domains. It is not simply a cybersecurity model or a collection of risk functions. It reaches into how the enterprise governs, designs, operates, measures and collaborates.
The relationships matter as much as the domains. Governance sets expectations; architecture translates them into design; operations tests whether that design holds. Risk and audit challenge the evidence, metrics make consequences visible, and culture determines whether people act on what they learn. Finance, legal and insurance perspectives enter these relationships wherever exposure, obligations and recovery require them; they are not additional maturity domains.
From the event to its consequences
Security Liability Recovery
A cyber or technology event does not remain a technical event. A compromised service can interrupt operations, activate contractual or legal obligations, produce financial loss and test the organization’s ability to recover. A decision about access, a vendor agreement or a recovery priority can change the consequences across that chain.
Integrated Assurance® examines the whole relationship. Security evidence informs exposure; obligations shape response; recovery performance affects loss, customer confidence and continued operation. These are interdependent, not a rigid one-way sequence: untested recovery or contractual ambiguity can undo the value of otherwise strong controls.
The business survivability question follows naturally: can the organization preserve enough operational and financial capacity to continue creating value while those consequences unfold?
Integrated Assurance Maturity Model
Developed by Patrick M. Hayes, the Integrated Assurance Maturity Model (IAMM®) provides a structured way to evaluate Integrated Assurance as an enterprise capability. It examines how assurance currently operates across the six domains and how deeply it has become part of the organization’s operating model. Each domain is evaluated separately; this is not one overall score. The dedicated IAMM reference page explains the model in greater depth.
Level 1
Assurance activities largely operate independently, with limited shared governance, inconsistent integration and isolated measures.
Level 2
Policies, frameworks and basic practices exist, but integration and cross-functional application remain inconsistent.
Level 3
Cross-functional practices begin to emerge. Ownership becomes clearer, shared information improves and assurance activities become more coordinated.
Level 4
Assurance becomes integrated into governance, engineering, operational processes, measurement and decision-making.
Level 5
Assurance functions as an enterprise capability and is embedded in strategic planning, governance, culture and continuous decision-making.
Maturity is assessed domain by domain. An organization may be Aligned in one domain and Fragmented in another.
Measure where you are
The IAMM Self-Assessment provides an indicative view across the six domains of Integrated Assurance maturity.
18 questions · Six domains · Immediate results
Start with a service or outcome the business needs to sustain. Understand the people, systems, suppliers, information and decisions it depends on, and identify where ownership or assumptions are unclear.
Trace meaningful risk through those dependencies. Connect a technical failure to the business commitments it could interrupt, the obligations it could create and the financial exposure the organization would retain. Compare those consequences with leadership’s tolerance for disruption.
Validate controls and assumptions with operating evidence. Test whether recovery can restore a usable business service, not just a system, and whether financial capacity and insurance align with the time and loss involved. Use the findings to change priorities, ownership, design or investment.
Repeat as the business changes. New suppliers, technology, growth and delegated decisions can make yesterday’s evidence less relevant. The implementation stages below provide the existing path from shared intent to an embedded enterprise capability.
From assessment to implementation
IAMM establishes the current maturity of Integrated Assurance. The implementation methodology provides a practical path for moving the organization forward.
Stage 1
Stage 2
Stage 3
Stage 4
Stage 5
At the highest level of maturity, assurance is no longer an activity performed around the business. It becomes part of how the business governs, designs, operates, measures and makes decisions.
Leadership owns and understands risk. Assurance information influences enterprise decisions. Architecture and engineering incorporate assurance into design. Operational teams internalize risk ownership. Metrics demonstrate business impact. Culture reinforces shared responsibility.
Prevention matters, but it is imperfect. The leadership question is not only whether disruption can be prevented; it is whether the organization can continue creating value when disruption occurs. Business Survivability examines that capability when assumptions, systems, people and dependencies stop behaving as expected.
Technical restoration is not necessarily meaningful business recovery. A system can be online while orders remain unfulfilled, suppliers unavailable or cash insufficient to sustain the interruption. Integrated Assurance® connects security, operations, third-party dependencies, financial capacity, insurance and recovery to the service the business actually needs to deliver. Insurance may finance some loss; it does not itself restore that service.
Integrated assurance is a broader concept with established uses in audit, risk, governance and assurance disciplines. Traditional integrated and combined assurance approaches often coordinate internal audit, risk, compliance and other assurance providers to improve coverage and reduce gaps or duplication. These are useful purposes; they are not obsolete or wrong.
Patrick M. Hayes’s Integrated Assurance® addresses the same underlying fragmentation but extends the operating purpose across the enterprise: technology, cybersecurity, architecture, operations, governance, risk, financial consequence and recovery. It asks not only who provides assurance, but how decisions and evidence connect to the business’s ability to function.
The distinction is between coordinating assurance providers and embedding assurance into the way the enterprise designs, operates and makes decisions. The approaches can complement one another.
Integrated Assurance vs. Combined Assurance: what gets integratedGovernance, risk and compliance supplies essential oversight and obligations. Integrated Assurance® connects that work to the six operating domains, recovery evidence and business consequences. It does not replace GRC disciplines or require a particular software platform.
Integrated Assurance vs. GRC: how they work togetherPatrick M. Hayes is the author of Integrated Assurance: Unified Risk Strategy. He developed the particular operating model and Integrated Assurance Maturity Model described on this site through his work connecting cybersecurity, enterprise risk, resilience and business decision-making.
This page is a primary-source explanation of that body of work, not a claim of authorship of the general integrated assurance concept. His enterprise architecture background, described above, helps explain the model’s emphasis on the relationships between functions.
Framework, practice and learning

Unified Risk Strategy
Foundational work defining the operating model and the structural problem of fragmented assurance.

A Field Guide to Integrated Assurance
Practical application to leadership and organizational decision-making, including prioritization, ownership, evidence and reporting.
Structured assessment of Integrated Assurance capability across the six organizational domains. It connects the operating model to observable maturity and targeted improvement.
Education and practitioner development connecting the body of work to the practical task of seeing risk across the enterprise.
The related essays and research develop the operating model’s implications for implementation, existing frameworks and enterprise resilience.
Questions and answers
In Patrick M. Hayes’s work, Integrated Assurance® is an enterprise operating model connecting governance, technology, cybersecurity, operations and risk with business consequences and recovery. The broader term also has established uses in audit and assurance; Patrick’s model is a specific application across the operating enterprise.
Patrick M. Hayes developed the particular Integrated Assurance® operating model described here and in Integrated Assurance: Unified Risk Strategy. He did not originate the general phrase integrated assurance or the wider practice of coordinating assurance providers.
The Integrated Assurance Maturity Model (IAMM®), developed by Patrick M. Hayes, evaluates how assurance operates across six organizational domains and five maturity levels. It describes development of Integrated Assurance as an enterprise capability, with maturity considered separately for each domain.
Combined assurance commonly coordinates assurance providers to improve risk coverage and reduce duplication. Patrick’s operating model shares the concern about fragmentation but extends its focus to how the enterprise designs, operates, makes decisions and recovers. The distinction is scope and purpose, not a claim that combined assurance is wrong.
Governance, risk and compliance (GRC) connects oversight, risk management and obligations. Integrated Assurance draws on those disciplines while also connecting architecture, engineering, operations, evidence, culture and recovery. It is an operating model, not a replacement GRC platform or a substitute for compliance requirements.
It relates security controls and incident response to the services, commitments and financial capacity the business depends on. A control is considered alongside its evidence, operating consequences and recovery assumptions, rather than judged only by its existence or technical coverage.
Business survivability asks whether an organization can continue creating value during disruption. Integrated Assurance helps leadership connect prevention, dependencies, obligations, financial exposure and recovery capability so that restoring technology is not mistaken for restoring the business.
Begin with strategic intent and a business service that matters. Map its dependencies and owners, compare the evidence held by different functions, and test control and recovery assumptions against business tolerance. Use IAMM to identify domain-specific gaps, run targeted improvements and repeat as the business changes.
An Integrated Assurance Assessment uses the IAMM to examine maturity across the six domains, identify fragmentation and friction, and establish the next meaningful steps toward a more integrated operating model.
The term integrated assurance is also used within the internal audit, governance, risk and compliance professions to describe the coordination of assurance activities across functions. That work is important and shares some common ground with the ideas discussed here.
Integrated Assurance® as developed by Patrick M. Hayes refers to a specific operating model that extends beyond the coordination of assurance providers. It looks at how governance, cybersecurity, technology and engineering operations, risk and compliance, measurement, and organizational culture work together to influence risk, resilience and business survivability.
The Integrated Assurance Maturity Model (IAMM®), the Integrated Assurance Loop, the Risk Value Chain, and the related methods, models and educational materials are components of this body of work.
References to Integrated Assurance® on this website, in Patrick M. Hayes’s published works, and within the Integrated Assurance Academy refer to this specific framework and body of intellectual property.
Intellectual Property
Integrated Assurance® is the intellectual framework developed by Patrick M. Hayes through his work in enterprise architecture, cybersecurity, operations, governance, and risk management. The Integrated Assurance trademark is owned by Patrick M. Hayes. The associated original methodologies, models, diagrams, educational materials, written works, and other proprietary content are protected intellectual property.
Integrated Assurance® is used throughout this site, Patrick M. Hayes's published works, and the Integrated Assurance Academy to identify this body of work. Unauthorized reproduction or commercial use of proprietary Integrated Assurance materials is prohibited except with written permission.
Explore the thinking
September 18, 2025
November 26, 2025
September 24, 2025
November 4, 2025
Unified Risk Strategy
A Field Guide to Integrated Assurance
White Paper
White Paper
White Paper
Risk Society · October 2026
The EDP Audit, Control, and Security Newsletter · June 2025
Security Magazine · November 2023
Good Governance Academy Podcast · November 2026
Leadership & Success Podcast with Coach BZ · June 2026
October 2025