International (ISO/IEC JTC 1/SC 27)

ISO/IEC 27400:2022

98 controls. 287 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.

98 controls 287 frameworks share controls with it International (ISO/IEC JTC 1/SC 27) 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
27400-10.1Vulnerability Management for IoT0
27400-10.2Incident Response for IoT0
27400-10.3Logging and Monitoring3
27400-11.1Decommissioning and Disposal0
27400-11.2Supplier and Third-Party Management0
27400-4IoT overview and concepts0
27400-5.1IoT Security and Privacy Governance18
27400-5.2IoT Risk Assessment27
27400-5.3Network and communication risks0
27400-5.4Data and privacy risks116
27400-6.1Secure Device Design111
27400-6.2Device Identity and Authentication136
27400-6.3Secure Update Mechanism81
27400-6.4Default Configuration Security57
27400-6.5Security monitoring and incident response154
27400-7.1Network Security for IoT110
27400-7.2Gateway Security0
27400-7.3Data minimization and purpose limitation116
27400-7.4Data retention and deletion110
27400-8.1Platform and Backend Security0
27400-8.2Data Protection in IoT0
27400-8.3Maintenance and update security0
27400-8.4Decommissioning security0
27400-9.1Privacy by Design for IoT0
27400-9.2Consent and Transparency0
27400-9.3Data Subject Rights for IoT0
55 IoT concepts0
5.25.2 Characteristics of IoT systems0
5.35.3 Stakeholders of IoT systems0
5.3.25.3.2 IoT service provider0
5.3.35.3.3 IoT service developer0
5.3.45.3.4 IoT user0
5.45.4 IoT ecosystem0
5.55.5 IoT service life cycles0
5.65.6 Domain based reference model0
66 Risk sources for IoT systems0
6.16.1 Risk sources: general0
6.26.2 Risk sources0
6.2.16.2.1 Risk sources: general categories0
6.2.26.2.2 Sample risk sources related to IoT domains0
6.2.36.2.3 Risk sources from outside the IoT domains0
6.2.46.2.4 Privacy related risk sources0
77 Security and privacy controls0
7.17.1 Security controls0
7.1.27.1.2 Security controls for IoT service developer and IoT service provider0
7.1.2-017.1.2-01 IoT security policy0
7.1.2-027.1.2-02 Organization of IoT security0
7.1.2-037.1.2-03 Asset management0
7.1.2-047.1.2-04 Equipment and assets outside physically protected areas0
7.1.2-057.1.2-05 Secure disposal or reuse of equipment0
7.1.2-067.1.2-06 Learning from security incidents0
7.1.2-077.1.2-07 Secure IoT systems engineering principles0
7.1.2-087.1.2-08 Secure development environment and procedures0
7.1.2-097.1.2-09 IoT system security that supports safety0
7.1.2-107.1.2-10 Security when connecting diverse IoT devices0
7.1.2-117.1.2-11 Verification of IoT device and system design0
7.1.2-127.1.2-12 Monitoring and logging0
7.1.2-137.1.2-13 Protection of logs0
7.1.2-147.1.2-14 Use of appropriate networks for IoT systems0
7.1.2-157.1.2-15 Secure settings and configuration when supplying IoT devices and services0
7.1.2-167.1.2-16 Authentication of users and devices0
7.1.2-177.1.2-17 Provision of software and firmware updates0
7.1.2-187.1.2-18 Sharing vulnerability information0
7.1.2-197.1.2-19 Security measures adapted to the life cycle of IoT systems and services0
7.1.2-207.1.2-20 Guidance to IoT users on appropriate use of devices and services0
7.1.2-217.1.2-21 Determination of stakeholders' security roles0
7.1.2-227.1.2-22 Management of vulnerable devices0
7.1.2-237.1.2-23 Supplier relationship management for IoT security0
7.1.2-247.1.2-24 Secure disclosure of IoT device security information0
7.1.37.1.3 Security controls for IoT user0
7.1.3-017.1.3-01 Support contacts and service0
7.1.3-027.1.3-02 Initial settings of IoT devices and services0
7.1.3-037.1.3-03 Deactivation of unused devices0
7.1.3-047.1.3-04 Secure disposal or reuse of IoT devices0
7.27.2 Privacy controls0
7.2.27.2.2 Privacy controls for IoT service developer and IoT service provider0
7.2.2-017.2.2-01 Prevention of privacy-invasive events0
7.2.2-027.2.2-02 IoT privacy by default0
7.2.2-037.2.2-03 Provision of privacy notice0
7.2.2-047.2.2-04 Verification of IoT functionality0
7.2.2-057.2.2-05 Consideration of IoT users0
7.2.2-067.2.2-06 Management of IoT privacy controls0
7.2.2-077.2.2-07 Unique device identity0
7.2.2-087.2.2-08 Fail-safe authentication0
7.2.2-097.2.2-09 Minimisation of indirect data collection0
7.2.2-107.2.2-10 Communication of privacy preferences0
7.2.2-117.2.2-11 Verification of automated decisions0
7.2.2-127.2.2-12 Accountability of stakeholders0
7.2.2-137.2.2-13 Unlinkability of PII0
7.2.2-147.2.2-14 Sharing information on PII protection measures of IoT devices0
7.2.37.2.3 Privacy controls for IoT user0
7.2.3-017.2.3-01 User consent0
7.2.3-027.2.3-02 Purposeful connection to other devices and services0
7.2.3-037.2.3-03 Certification and validation of personal information protection0
ANNEXAAnnex A (informative): IoT monitoring camera sample risk scenario0
FRONTClauses 2 to 4: references, terms and abbreviations0
STANDARDISO/IEC 27400:2022: the standard and its scope0
STATUSEdition status: first edition 2022, current; ISO/IEC 27402 builds on its controls0

Tell me when ISO/IEC 27400:2022 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 27400:2022, 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