Security Event Reporting and Information Sharing Detailed descriptions of IoT incidents, such as those provided by ENISA 281, can be used as input for evaluations and validations of certain security measures. The analytics framework should operate in the cloud, given that most IoT devices are resource-constrained. This approach creates an opportunity to compare large volumes of dataflows and detect and react to malicious activities over millions of devices. For example, the Malware Information Sharing Platform282 (MISP) is an open source threat intelligence platform that provides open standards for Threat Information Sharing. This platform is built to collect and share large amounts of data including reporting and alerting solutions. Gateway-Based Monitoring The gateway is uniquely suited to monitor traffic to and from the cloud, and should support anomaly detection and integrate easily with existing anomaly and intrusion detection systems. A secure gateway might even support intrusion prevention capabilities to exclude suspicious actors from the ecosystem. A logging and reporting framework should allow the gateway to observe, baseline, and monitor communications traffic and component behaviour. 80 281 Baseline Security Recommendations for IoT, ENISA, Nov 2017 282 http://www.misp-project.org/ 5.11.2 Key Findings – Data collection and analytics for massive numbers of IoT devices is a major challenge. – New metrics and methodologies are required to support IoT infrastructure analytics given the data characteristics of resource-constrained IoT devices. – Monitoring and analytics capabilities should provide input for vulnerability management programs. – In case vulnerabilities are not solved by the supplier, monitoring tools should be able to detect and disconnect vulnerable devices from the internet. – The industry should act as a global community when learning from incidents. This requires an open culture of sharing incidents and mutual learning where security is a joint responsibility. 5.12 INTERDEPENDENCIES AMONG CHALLENGES The IoT security challenges discussed throughout this study do not exist in isolation; rather, they are closely dependent on each other. These interdependencies are illustrated in Figure 25. IoT security needs to be based upon fundamentally sound cybersecurity principles, and all IoT products and services must be designed with security and privacy in mind. Manufacturers need to employ secure supply chains and carefully-considered lifecycle management strategies for device deployments. Devices themselves need a root of trust to allow for secure identification, booting and updates. Communications between devices and back-end need to be secured using authentication and encryption. Monitoring and analytics can detect vulnerabilities after deployment, and the information thus gathered can used to patch devices using lifecycle and supply chain management practices. At the same time, vulnerability information should be fed back into the supply chain to narrow down root causes and identify other devices that may be affected.

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents