IoT devices; it should be determined whether these can be
generic or domain-specific to application domains. In fact,
since CC certification is known for being a relatively slow
and costly process, a non-CC certification approach may
prove more suitable for IoT devices.
Owing to a lack of legislation, the adoption of security
guidelines and best practices remains voluntary. An initial
step taken by the United States is to mandate that the
government shall only procure IoT devices that conform to
some measure of security. This approach can contribute
significantly towards a secure IoT when large countries
participate, but smaller economies such as Singapore and
the Netherlands should work together for greater impact.
Liability can prove to be an effective mechanism to drive the
industry towards security, although in most cases liability
legislation needs to be modernised to account for the
nature of IoT. The process of identifying the responsible
manufacturer or supplier and holding them liable for a
vulnerability is a supply chain management challenge.
IoT hardware and software manufacturers and suppliers
should adopt a supply chain risk management framework
(e.g. ISO28000, TL9000) to cascade cybersecurity
requirements, risk and liability up the supply chain.
At the device level, a root of trust (RoT) is an immutable
trust anchor; the chain of trust should preferably build on
a hardware RoT. RoT-based cybersecurity is provided by
several solutions including TPMs and PUFs. IoT security
guidelines emphasise hardware roots of trust; yet,
established practices are lacking regarding their use in
resource-constrained devices. Security reference
architectures are required across a range of constraint
classes.
84
There is a diversity of operating systems, cloud solutions
and application development frameworks in the IoT market.
An in-depth evaluation is required on the security claims
made for each solution. Cloud-based IoT platforms offer
comprehensive device management functionality including
onboarding and patching, but are largely unstandardised.
IoT-specific secure software development lifecycle (SDLC)
guidelines are necessary for IoT developers, platform
operators, industry and manufacturers.
A number of standards have emerged for IoT networking;
however, an in-depth review is required of the security of
these protocols and the security and privacy requirements
on each level of the communication stack in the IoT
ecosystem. Regardless of communication protocol, secure
gateways are recommended and can provide a level of
security even in deployments that use low-cost IoT devices.
History shows that device-level vulnerabilities are invariably
found after a product is deployed – and are often exploited
in “zero-day” attacks. It is important to be able to detect
unforeseen vulnerabilities, anomalies and threats in live
deployments, and to respond quickly, recover and
remediate. Monitoring is especially vital for IoT, but data
collection and analytics for massive numbers of IoT devices
remains a challenge. A strategy to deal with discovered
threats and vulnerabilities should include a CVD program
that balances security with the interests of manufacturers
and stakeholders, and includes the propagation of
vulnerability information up and across supply chains.
Keeping software and firmware up-to-date via patches and
updates is critical for a secure IoT ecosystem. Updates
should be delivered and deployed using a secure and
verifiable methodology. If a vendor identifies or is informed
about vulnerabilities, it must patch them in a timely manner
and publish patch information as part of an auditable
Vulnerability Management Program.
Most importantly, the industry should act as a global
community when learning from incidents. This requires an
open culture of sharing and mutual learning, and the
understanding that security is a joint responsibility.
It is recommended to set up a global initiative on secure IoT
in order to address the below gaps.
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents