ASIS SPC.1-2009 - Organizational Resilience StandardvsIRM Enterprise Risk Management Framework (Institute of Risk Management)
See exactly how ASIS SPC.1-2009 - Organizational Resilience Standard controls map to IRM Enterprise Risk Management Framework (Institute of Risk Management). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
ASIS SPC.1-2009 - Organizational Resilience Standard maps to IRM Enterprise Risk Management Framework (Institute of Risk Management) with 10% coverage across 4 directly mapped controls. Analysis of 42 ASIS SPC.1-2009 - Organizational Resilience Standard controls identifies 38 compliance gaps — primarily concentrated in Check.
Source: TheArtOfService Knowledge Graph | 42 controls analysed | 718 frameworks | 332K+ cross-framework mappings
Control Mappings
Showing 5 of 5 mapped controls across 2 domains. Sign up to explore all 332K+ mappings across 718 frameworks.
Policy and Planning(3 mappings)
Implementation and Operation(2 mappings)
Related Comparisons
Other ASIS SPC.1-2009 - Organizational Resilience Standard comparisons
Other IRM Enterprise Risk Management Framework (Institute of Risk Management) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.
Free
- ✓ 718 framework browser
- ✓ Cross-framework mappings (332K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between ASIS SPC.1-2009 - Organizational Resilience Standard and IRM Enterprise Risk Management Framework (Institute of Risk Management)?
ASIS SPC.1-2009 - Organizational Resilience Standard has 42 controls across its framework, while IRM Enterprise Risk Management Framework (Institute of Risk Management) covers 7 controls. Direct mapping analysis identifies 4 overlapping controls (10% coverage). The frameworks diverge most significantly in Check, where 6 ASIS SPC.1-2009 - Organizational Resilience Standard controls have no direct IRM Enterprise Risk Management Framework (Institute of Risk Management) equivalent.
How many controls map between ASIS SPC.1-2009 - Organizational Resilience Standard and IRM Enterprise Risk Management Framework (Institute of Risk Management)?
Of 42 total ASIS SPC.1-2009 - Organizational Resilience Standard controls, 4 map directly to IRM Enterprise Risk Management Framework (Institute of Risk Management) controls — representing 10% coverage. The remaining 38 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping ASIS SPC.1-2009 - Organizational Resilience Standard to IRM Enterprise Risk Management Framework (Institute of Risk Management)?
38 ASIS SPC.1-2009 - Organizational Resilience Standard controls have no direct equivalent in IRM Enterprise Risk Management Framework (Institute of Risk Management). The highest concentration of gaps is in Check with 6 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between ASIS SPC.1-2009 - Organizational Resilience Standard and IRM Enterprise Risk Management Framework (Institute of Risk Management)?
The domain with the highest gap count is Check (6 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.