International

ISO/IEC 27013:2021

25 controls. 0 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.

25 controls 0 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.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1-4Scope, terms and overview of ISO/IEC 27001 and ISO/IEC 20000-10
5.1Consider the integration factors before planning the combined system0
5.2Define and align the scopes of the ISMS and the SMS0
5.3.2Starting from neither standard: choose the order and run an integration working group0
5.3.3Starting from one conforming system: integrate the other without loss of service or security0
5.3.4Starting from two separate systems: review scopes, compatibility and the business case0
6.1Use consistent terminology and keep documented traceability to both standards0
6.2.1Distinguish requirements from Annex A controls and the statement of applicability0
6.2.10Set classification and escalation criteria for sensitive incidents and restrict access to their records0
6.2.11Run one change management process that reviews information security risk0
6.2.2Decide how assets and configuration items are classified and keep configuration information secure0
6.2.3Consider information security in the design, transition and removal of every service0
6.2.4Adopt a risk management approach that serves both disciplines0
6.2.5Agree risk levels and security expectations with customers and third parties early0
6.2.6Decide how incidents in both scopes are handled and publish classification criteria0
6.2.7Define the scope of problem management and link it to security analysis0
6.2.8Balance evidence gathering against rapid service restoration0
6.2.9Manage major incidents that are also security incidents with informed top management and skilled investigators0
6.3.1Use service reporting to carry information security measures0
6.3.2Secure top management commitment and a single continual improvement discipline0
6.3.3Use capacity and demand management to support information security and availability0
6.3.4Manage third parties and their risk through contracts and risk assessment0
6.3.5Extend continuity and availability management to integrity and confidentiality0
6.3.6Build information security into release and deployment, including emergency releases0
A-CAnnexes: clause correspondence, control comparison and terms comparison0

Tell me when ISO/IEC 27013:2021 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 this page is

A control-level reference for ISO/IEC 27013:2021, 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