ISO/IEC 27400:2022
Clause 5: IoT concepts – ISO/IEC 27400:2022

ISO/IEC 27400:2022 5.5: 5.5 IoT service life cycles

An IoT service is developed by a service developer and one or more device developers, provided by a service provider and used by users; their processes form four interlocking life cycles: device development, service development, service provision and service use. The device developer designs, develops, manufactures, sells and supports the device and stops supporting it at retirement, building security and privacy requirements into device features such as user authentication and access control, physical protection such as a secure case, and a software and firmware update mechanism, and should make sure current device information, including security information, reaches every stakeholder who needs it. The service developer produces and supports the system and stops at retirement, with features such as authentication and access control of the service, malware protection, redundant components and network, software updating and operations functions, aligned with the devices' features. The provider develops the operation, runs the service and ends it at retirement through the ISO/IEC 15288 processes (acquisition, supply, organizational project-enabling, technical management including risk management and quality assurance, and the technical operation, maintenance and disposal processes); risk management applies the device and system features and secure operations, quality assurance keeps vulnerabilities and malicious components out and ensures the safety functions, and the supply process gives users security information and updates. The user picks a service against its security and privacy requirements using the information supplied, then applies updates and follows that information until the device is decommissioned. Life cycles that fall out of step cause problems: a device's support can end while the service is still running, or a developer can leave the market while users carry on using the device, knowingly or not.

Maintained by Gerard BlokdykControl text last updated

Other controls in Clause 5: IoT concepts – ISO/IEC 27400:2022

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.