Applications
As identified by Subramanian and Swaminathan236,
applications in a typical IoT environment fall into the
following categories:
1. Device applications that reside on the nodes and/or
gateways.
2. Controlling applications that typically reside in the data
centre or on a user or operator’s mobile device.
3. Consuming applications that typically reside in the data
centre and receive data from the devices for further
processing and analytics.
4. Relay services that format and transfer data between
different components, e.g., APIs and web services.
To realise safe and secure software, it is important to adopt
a secure design and development methodology. Useful
guidelines for secure software development are provided by
OWASP237, which also offers a comprehensive developer
checklist that covers input validation, access control,
session management, error handling, logging, database
security and memory management.
suites. The aim is to reduce the risk from waterfall-style
“penetration testing at the end”, which can lead to
expensive refactoring when delivering milestone builds into
production.
ASVS defines detailed
verification requirements
for levels 1 and above;
whereas level 0 is meant
to be flexible and is
customised by each
organisation
3 Advanced
2 Standard
1 Opportunistic
0 Cursory
Figure 23: OWASP Security Verification Levels (Source: OWASP)
OWASP’s Application Security Verification Standard
(ASVS)238 is a list of application security requirements or
tests that can be used by architects, developers, testers,
security professionals, and even consumers to determine
the security level of a given application in a consistent
manner. ASVS defines 3 security verification levels of
successively increasing depth, with a set of security
requirements for each level. OWASP specifically discusses
the use of ASVS as the basis of a secure SDLC: developers
are encouraged to use the ASVS as a peer review checklist
to ensures that unsafe code does not get checked in;
further, developers can use the ASVS as part of their
automated verification secure unit and integration test
IoT devices (or, more specifically, the applications running
on them) should “prove their health”, before accessing
other IoT devices or services. Associated capabilities
include a process for securely determining software and
firmware versions and a secure software and firmware
update mechanism. For example, the Trusted Computing
Group’s Trusted Network Connect (TNC) standards, which
specify a standard mechanism to check which software or
firmware is running on a device, are among the protocols
and mechanisms for safeguarding the patch and upgrade
process. Malware can be detected at boot time using the
device’s Trusted Boot and Remote Attestation capabilities,
even to the point of finding changes in the device’s BIOS or
other firmware.
236 https://www.isaca.org/Journal/archives/2017/Volume-3/Pages/securityassurance-in-the-sdlc-for-the-internet-of-things.aspx
237 https://www.owasp.org/index.php/
OWASP_Secure_Coding_Practices_-_Quick_Reference_Guide
238 https:// www.owasp.org/images/3/33/
OWASP_Application_Security_Verification_Standard_3.0.1.pdf
71
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents