International

ISO/IEC 27031:2011

82 controls. 311 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

82 controls 311 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
27031-10.1Continual Improvement16
27031-10.2Supplier Continuity Arrangements0
27031-10.3Communication During Incidents13
27031-4.1Overview of IRBC0
27031-4.2IRBC framework elements0
27031-5.1IRBC Policy165
27031-5.2ICT services and infrastructure scope0
27031-6.1Understanding the Organisation0
27031-6.2Business Impact Analysis for ICT1
27031-6.3Risk Assessment for ICT Continuity4
27031-7.1IRBC Strategy30
27031-7.2Resource Requirements177
27031-7.3Incident Response Structure0
27031-7.4IRBC Plans0
27031-7.5Awareness and Training1
27031-8.1Exercising and Testing112
27031-8.2Maintaining IRBC82
27031-8.3IRBC plan documents0
27031-8.4Awareness, competency and training0
27031-9.1Performance Measurement0
27031-9.2Internal Audit14
27031-9.3Management Review97
27031-9.4IRBC review and improvement0
27031-AIRBC milestones during disruption0
27031-BHigh availability embedded systems56
27031-CAssessing failure scenarios0
27031-DDeveloping performance criteria30
1-4Introduction, scope, normative references, terms and abbreviations0
5.1The role of IRBC in Business Continuity Management0
5.2The Principles of IRBC0
5.3The Elements of IRBC0
5.4Outcomes and benefits of IRBC0
5.5Establishing IRBC0
5.6Using Plan Do Check Act to establish IRBC0
5.7Management Responsibility0
5.7.1Management leadership and commitment0
5.7.2IRBC policy0
6.2Resources0
6.2.2Competency of IRBC staff0
6.3Defining requirements0
6.3.2Understanding critical ICT services0
6.3.3Identifying gaps between ICT Readiness capabilities and business continuity requirements0
6.4Determining IRBC Strategy Options0
6.4.2IRBC Strategy Options0
6.5Sign Off0
6.6Enhancing IRBC Capability0
6.6.1Enhancing Resilience0
6.7ICT Readiness Performance Criteria0
6.7.1Identification of performance criteria0
7.2Implementing the Elements of the IRBC Strategies0
7.2.1Awareness, Skills and Knowledge0
7.2.2Facilities0
7.2.3Technology0
7.2.4Data0
7.2.5Processes0
7.2.6Suppliers0
7.3Incident Response0
7.4IRBC Plan Documents0
7.4.2Content of Plan Documents0
7.4.3The ICT Response and Recovery Plan Documentation0
7.5Awareness, competency and training program0
7.6Document Control0
7.6.1Control of IRBC records0
7.6.2Control of IRBC documentation0
8.1Maintaining IRBC0
8.1.2Monitoring, detection and analysis of threats0
8.1.3Test and exercise0
8.2IRBC Internal Audit0
8.3Management Review0
8.3.2Review Input0
8.3.3Review Output0
8.4Measurement of ICT Readiness Performance Criteria0
8.4.1Monitoring and measurement of ICT Readiness0
8.4.2Quantitative and Qualitative Performance Criteria0
9.1Continual improvement0
9.2Corrective action0
9.3Preventive action0
AAnnex A (informative) IRBC and milestones during a disruption0
BAnnex B (informative) High availability embedded system0
CAnnex C (informative) Assessing failure scenarios0
DAnnex D (informative) Developing performance criteria0
STATUSEdition status: withdrawn, replaced by ISO/IEC 27031:20250

Tell me when ISO/IEC 27031:2011 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • complaint handling procedure
  • complaint register
  • PDPC complaint responses
  • 30-day SLA tracking
  • corrective action register
  • root cause analyses for IRBC failures
  • Approved information security policy
  • Policy review and approval history
  • Roles and responsibilities matrix
  • Management commitment statement

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for ISO/IEC 27031:2011, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition