+SYS.4.4 General IoT Devices
---+SYS.4.4.G1. Espionage using IoT Devices
---+SYS.4.4.G2. Use of UPnP
---+SYS.4.4.G3. Distributed Denial of Service (DDoS)
---+SYS.4.4.G4. Espionage Attacks Through Backdoors in IoT Devices
---+SYS.4.4.A1 Criteria for Using IoT Devices (B)
---+SYS.4.4.A2 Authentication (B)
---+SYS.4.4.A5 Restriction of Network Access (B)
---+SYS.4.4.A6 Integration of IoT Devices into Organisation Security Policies (S)
---+SYS.4.4.A7 Planning the Use of IoT Devices (S)
---+SYS.4.4.A8 Procurement Criteria for IoT Devices [Procurement Department] (S)
---+SYS.4.4.A9 Controlling the Use of IoT Devices (S)
---+SYS.4.4.A10 Secure Installation and Configuration of IoT Devices (S)
---+SYS.4.4.A11 Using Encrypted Data Transmission (S)
---+SYS.4.4.A13 Deactivation and Uninstallation of Unnecessary Components (S)
---+SYS.4.4.A15 Restrictive Granting of Access Rights (S)
---+SYS.4.4.A16 Elimination of Malware on IoT Devices (S)
---+SYS.4.4.A17 Monitoring Network Traffic on IoT Devices (S)
---+SYS.4.4.A18 Logging Security-Relevant Events on IoT Devices (S)
---+SYS.4.4.A19 Protection of Administration Interfaces (S)
---+SYS.4.4.A20 Controlled Decommissioning of IoT Devices (S)
---+SYS.4.4.A21 Operational Environment and Power Supply [Building Services] (H)
---+SYS.4.4.A22 System Monitoring (H)
---+SYS.4.4.A23 Auditing of IoT Devices (H)
---+SYS.4.4.A24 Secure Configuration and Usage of an Embedded Web Server (H)
|
SYS.4.4 General IoT Devices
IntroductionIn contrast to classic end devices, those with Internet of Things (IoT) functions are networked devices or objects that have additional “smart” functions. IoT devices are usually connected wirelessly to data networks. Most of these devices can access information on the Internet and be reached via the same means. As a consequence, they may have effects on the information security of the entire corresponding information domain. IoT devices such as smartwatches or other wearables can enter organisations when they are worn by employees or visitors. However, many organisations also procure and operate IoT devices themselves—including detectors for fire, gas, and other hazards; coffee machines; or building management elements such as cameras and HVAC (heating, ventilation and air conditioning) systems. In general, a differentiation can be made between IoT devices that may be addressed directly and IoT devices that require a central controller. Devices that can be addressed directly are usually connected to a LAN with their own IP address and can act autonomously, or are managed by a central control unit. There are also IoT devices that communicate only directly with controllers (e.g. via radio networks such as Bluetooth or ZigBee) and thus do not connect directly to existing data networks. ObjectiveThe objective of this module is to secure IoT devices such that they impair neither the information security of one’s own organisation nor the security of external parties. As a consequence, both unauthorised data leaks and any manipulation of these devices should be avoided, especially with regard to attacks through third parties. Scoping and ModellingModule SYS.4.4 General IoT Devices must be applied to every device with functions related to the Internet of Things (IoT). This module addresses IoT devices in general and should thus be applicable to a wide range of such devices. Dedicated security properties, such as those of operating and display systems or specific hardware and software architectures, are not described in more detail here. Depending on the characteristics of the IoT devices, their interfaces to industrial control systems (ICS systems) or embedded systems may be fluid. Requirements for devices used in production and manufacturing can be found in the modules of the IND Industrial IT layer. Embedded systems, on the other hand, are information-processing systems which are integrated into a larger system or product; assume control, regulation, and data processing tasks there; and are often not recognised directly by the user. Module SYS.4.3 Embedded Systems must be implemented for these systems. Requirements for the radio links often used in connection with IoT devices can be found in the modules of the layer NET.2 Radio Networks. The IoT devices used in the information domain under consideration must also be taken into account in identity and access management. To that end, module ORP.4 Identity and Access Management should be implemented. Useful resourcesIn the document “Security of IP-Based Surveillance Cameras”, the BSI provides an overview of the basic best practices for the secure operation of IP-based surveillance cameras. The United States Department of Homeland Security (DHS) has published strategic principles for the security of IoT devices. The Open Web Application Security Project (OWASP) Foundation offers best practices for the security of IoT devices.
1. Áttekintés
| Megnevezés |
Szabvány |
|
SYS.4.4.A1 Criteria for Using IoT Devices (B)
|
IoT devices MUST have update functions. The respective manufacturers MUST provide an update process. The devices MUST allow for appropriate authentication. Hard-coded access data MUST NOT be present in the devices.
|
|
SYS.4.4.A2 Authentication (B)
|
Appropriate authentication MUST be activated. IoT devices MUST be integrated into the corresponding organisation's identity and access management system.
|
|
SYS.4.4.A5 Restriction of Network Access (B)
|
The network access of IoT devices MUST be restricted to the required minimum. This SHOULD be monitored regularly. The following aspects should be taken into consideration in this regard: - For traffic control at network gateways (e.g. by means of rules on firewalls and access control lists (ACLs) on routers), the incoming and outgoing connections permitted MUST be defined in advance.
- Routings on IoT devices and sensors SHOULD be configured restrictively, especially with regard to the suppression of default routes.
- IoT devices and sensors SHOULD be operated in a separate network segment that is only allowed to communicate with the network segment for management.
- Virtual private networks (VPNs) between networks with IoT devices, sensor networks, and management networks SHOULD be configured restrictively.
- The UPnP feature MUST be disabled on all routers.
|
|
SYS.4.4.A6 Integration of IoT Devices into Organisation Security Policies (S)
|
Requirements for IoT devices SHOULD be specified in organisations' general security policies. This policy SHOULD be known to all persons who procure and operate IoT devices and be integral to their work. The implementation of the rules required by the policy SHOULD be reviewed regularly and the results documented in a sensible way.
|
|
SYS.4.4.A7 Planning the Use of IoT Devices (S)
|
To ensure secure operation of IoT devices, where and how these devices should be used SHOULD be planned in advance. Besides addressing aspects usually associated with information security in the traditional sense, this planning SHOULD also consider normal operational aspects that entail requirements in the area of security. All decisions taken in the planning phase SHOULD be documented appropriately.
|
|
SYS.4.4.A8 Procurement Criteria for IoT Devices [Procurement Department] (S)
|
The CISO SHOULD also be involved in procuring IoT devices that do not have any obvious IT functionality. Prior to procuring IoT devices, the security requirements they must meet SHOULD be specified. When procuring IoT devices, aspects of material security and requirements regarding the security characteristics of the devices' software SHOULD be sufficiently considered. A requirements list SHOULD be drawn up that can be used to evaluate the products available on the market.
|
|
SYS.4.4.A9 Controlling the Use of IoT Devices (S)
|
A person SHOULD be put in charge of the operation of every IoT device. The persons in charge SHOULD be appropriately informed about handling their IoT devices.
|
|
SYS.4.4.A10 Secure Installation and Configuration of IoT Devices (S)
|
The framework conditions applicable to the installation and configuration of IoT devices SHOULD be defined. IoT devices SHOULD only be installed and configured by authorised persons (persons in charge of IoT devices, administrators, or service providers bound by contracts) in accordance with a defined process. All installation and configuration steps SHOULD be documented such that they can be understood and repeated by a qualified third party based on the documentation. The basic settings of IoT devices SHOULD be checked and, where necessary, adapted to the specifications of the security policy in question. If possible, IoT devices SHOULD only be connected to data networks after installation and configuration are complete.
|
|
SYS.4.4.A11 Using Encrypted Data Transmission (S)
|
IoT devices SHOULD only transfer encrypted data.
|
|
SYS.4.4.A13 Deactivation and Uninstallation of Unnecessary Components (S)
|
Once IoT devices have been installed, the protocols, applications, and other tools that have been installed and enabled on them SHOULD be checked. Protocols, services, user IDs, and interfaces that are not required SHOULD be disabled or uninstalled entirely. The use of wireless interfaces that are not needed SHOULD be prevented. If this is not possible using the device itself, services that are not required SHOULD be restricted using the corresponding firewall. The decisions taken SHOULD be documented such that the configurations selected for IoT devices can be determined.
|
|
SYS.4.4.A15 Restrictive Granting of Access Rights (S)
|
Access authorisations for IoT devices SHOULD be granted as restrictively as possible. If this is not possible using IoT devices themselves, it SHOULD be considered via the network.
|
|
SYS.4.4.A16 Elimination of Malware on IoT Devices (S)
|
The IT Operation Department SHOULD regularly obtain information as to whether the IoT devices used could become infected with malware and how it can be removed. Malware SHOULD be eliminated immediately. If the cause of an infection cannot be eliminated or a new infection cannot be effectively prevented, the affected IoT devices SHOULD no longer be used.
|
|
SYS.4.4.A17 Monitoring Network Traffic on IoT Devices (S)
|
Whether IoT devices or sensor systems communicate only with IT systems that are necessary for their operation SHOULD be monitored.
|
|
SYS.4.4.A18 Logging Security-Relevant Events on IoT Devices (S)
|
Security-relevant events SHOULD be logged automatically. If this is not possible using IoT devices themselves, routers and logging mechanisms of other IT systems SHOULD be used. The log data SHOULD be evaluated appropriately.
|
|
SYS.4.4.A19 Protection of Administration Interfaces (S)
|
Depending on whether IoT devices are administered locally; directly using the respective network; or using central, network-based tools, appropriate security precautions SHOULD be taken. Access to the administration interfaces of IoT devices SHOULD be restricted as follows: - Network-based administration interfaces SHOULD be limited to authorised IT systems or network segments.
- Preference SHOULD be given to local administration interfaces on IoT devices or administration interfaces via local networks.
The methods used for administration SHOULD be defined in the corresponding security policy. IoT devices SHOULD be administered according to this security policy.
|
|
SYS.4.4.A20 Controlled Decommissioning of IoT Devices (S)
|
There SHOULD be an overview of the data stored in each location on IoT devices. A checklist which can be completed when decommissioning IoT devices SHOULD be created. This checklist SHOULD, at minimum, include aspects of backing up data that is still needed and the subsequent secure deletion of all data.
|
|
SYS.4.4.A21 Operational Environment and Power Supply [Building Services] (H)
|
It SHOULD be clarified whether IoT devices may be operated in the intended operational environment (i.e. taking the protection needs of other IT systems and data protection into account). IoT devices SHOULD be protected against theft, destruction, and manipulation in their operational environment. It SHOULD be clarified whether an IoT device has certain requirements regarding its physical operational environment (e.g. humidity, temperature, energy supply). If required, additional safeguards SHOULD be implemented regarding the infrastructure at hand. If IoT devices are operated using batteries, a procedure SHOULD be specified for regular functional testing and replacement of the batteries. IoT devices SHOULD be protected against dust and pollution in accordance with their intended type and place of use.
|
|
SYS.4.4.A22 System Monitoring (H)
|
IoT devices SHOULD be integrated into an appropriate system monitoring concept. This concept SHOULD continuously monitor the system status and functionality of the IoT devices in use and report error states and threshold violations to the respective operating personnel. Whether the devices used meet the availability requirements at hand SHOULD be checked. Alternatively, it SHOULD be checked whether further safeguards are required, such as setting up a cluster or procuring standby devices.
|
|
SYS.4.4.A23 Auditing of IoT Devices (H)
|
All IoT devices in use SHOULD be checked at regular intervals.
|
|
SYS.4.4.A24 Secure Configuration and Usage of an Embedded Web Server (H)
|
Web servers integrated into IoT devices SHOULD be configured as restrictively as possible. Whenever possible, a web server of this kind SHOULD NOT be operated using a privileged account.
|
1.1 Hivatkozások
1.2 Azonosított követelmények
1.3 Kapcsolódó szabályozások
2. Azonosított követelmények
Követelmények
| Forrás |
Követelmény |
3. Kapcsolódó szabályozások
Szabályozások
| Forrás |
Szabályozás |
Kapcsolt feladatok
|