Securing the IoT Value Chain with AWS

SECURING THE IOT
VALUE CHAIN WITH AWS
Business Unit Manager – IoT | Storm Reply
GABRIEL PAREDES LOZA
June 2022

2 Reply © 2022 All rights reserved. Do not distribute without written authorization
INTRODUCTION
Gabriel Paredes Loza
BU Manager – IoT @ Storm Reply
AWS Cloud Expert with a passion
for IoT and Bigdata solutions

3
• IoT Value Chain
• Overview
• Security Considerations
• IoT Software Development Life Cycle (SDLC)
• Phases
• Security Measures with AWS
• Conclusions
• Q&A
Reply © 2022 All rights reserved. Do not distribute without written authorization
TODAY’S AGENDA
24.06.2022 / Securing the IoT Value Chain with AWS

WHAT DOES VALUE CHAIN MEAN IN IOT TERMS?
Different components, in Combination with one another or
Separately, Add Value to the overall Solution, and to the End
User. Main difference stands in the Complexity and interaction
of the Physical and the Virtual worlds of an IoT Solution.
IOT VALUE CHAIN
Overview
WHY SHOULD I CARE ABOUT SECURITY?
• 76%* of IoT Projects Fail due to Lack of Interdisciplinary
Collaboration and Cybersecurity Vulnerabilities.
• Underestimating Undesired Threats:
• Firm’s Reputation due to Data Theft, Ransomware
• Man-In-The-Middle with disastrous consequences at large
scale (AVs, Healthcare, Oil & Gas, etc.)
* Source: IoT For All, https://www.iotforall.com/why-76-percent-iot-projects-fail-how-to-achieve-success

IOT VALUE CHAIN
End-2-End Security
End-2-End Governance
Hardware
Development
Life
Cycle
(HDLC)
Actors
Physical Value Chain
(Device, etc.)
Logical Value Chain
(IoT Platform, Firmware, etc.)
Overview
Processes Technologies
Software
Development
Life
Cycle
(SDLC)
Design
Provisioning
Operating
Repurposing
• IoT Leaders / Managers
• Chief Information
Security Officers (CISOs)
• IT Managers
• Device
Manufacturers
• System
Integrators (SI)
• HW Engineers
• Platform
Owners
• System
Integrators (SI)
• SW Engineers
• IoT SW Developers
• Device Manufacturers
• Information Security Experts
• IT / Security Solution Architects
Its Physical and
Logical nature makes
IoT Initiatives complex
to design, develop,
utilize, and maintain
Actors
Processes
Technologies
Holistic Approach
Design
Provisioning
Operating
Disposing
Service
Operating
Provisioning
End Users

IOT VALUE CHAIN
Security Considerations
Define Accountability
Define Trust Models
Increase Visibility
Comprehensive
Approach to
Security
Security
By Design
Leverage
Standards
& Good
Practices
Cultivate
Cyber
Security
Expertise
Forging
Better
Relations
Among
Actors
Actors Processes Technologies

IOT VALUE CHAIN
Comprehensive
Approach to
Security
Security
By Design
Leverage
Standards
& Good
Practices
Cultivate
Cyber
Security
Expertise
Forging
Better
Relations
Among
Actors
Factor-In Security
Leverage Emerging
Technologies
Start from the Basics

IOT VALUE CHAIN
Comprehensive
Approach to
Security
Security
By Design
Leverage
Standards
& Good
Practices
Cultivate
Cyber
Security
Expertise
Forging
Better
Relations
Among
Actors
Document Efforts
Seek for Expertise
Verify Previous Cases

IOT VALUE CHAIN
Comprehensive
Approach to
Security
Security
By Design
Leverage
Standards
& Good
Practices
Cultivate
Cyber
Security
Expertise
Forging
Better
Relations
Among
Actors
Risk-Based Approach
Educate Users
Security Culture

IOT SOFTWARE
DEVELOPMENT LIFE CYCLE

Ø Detailed Version of Logical
IoT Value Chain
Ø Different SDLC Models:
§ Waterfall (Sequential)
§ Spiral (Iterative)
§ Agile (DevSecOps)
Ø Heterogeneous SW:
§ Devices FW
§ IoT Services / SW
§ Network Protocols
§ APIs Source Code
§ GWs, Backend Code
Ø IoT Software Development
cannot neglect underlying
Hardware
IOT SDLC
Phases of the Software Development Life Cycle
Design
Provisioning
Operating /
Disposing
1
Defining Concepts/
Requirements
Software
Design
2
Development /
Implementation
Testing and
Acceptance
Deployment and
Integration
3
Maintenance
and Disposal
Confidentiality Integrity Availability

Ø 2 Expected Outputs:
Ø Context
Ø Functionalities
Ø Ensures Consistency
through Quality
Gateways
13
IOT SDLC
Security Measures – Requirements Collection
Externally-Driven
Requirements
Internally-Driven
Requirements
Physical-Hardware
Requirements
Security Hardware Software
• User
• Business
• Functional
• Legal & Regulatory
• 3rd-Party Dependencies
• Security Standards
• Certification Objectives
• IoT Threats / Attack Vectors
• Hardware Security Modules (HSM)
• Secure Boot, Root-of-Trust (RoT) Mechanisms
Device Manufactures
Software Engineers
Security Engineers
Business Analysts
Defining Concepts/
Requirements
Software
Design
Design
1

14
IOT SDLC
Security Measures – Requirements Collection
Ø Considers the Cyber-
Physical nature of IoT
for Interoperability of
Legacy-Coded /
Outdated Devices
* Depending on the application of IoT and Industry, other frameworks might be more appropriate (e. g. STRIDE, OWASP Top 10, etc.)
Security Risk Assessment with
Frameworks (e. g. MITRE ATT&CK*)
• Critical Assets
• External Dependencies
• Data Flows
AWS Well
Architected Framework
(Security Pillar + IoT Lens)
AWS
Organizations
AWS IoT
Device Management
AWS
Systems Manager
Security Hardware Software
Device Manufactures
Software Engineers
Security Engineers
Business Analysts
Maintain Asset Inventory
for all IoT (and Non-)
Assets & Categorize them
Monitor & Review
Requirements Periodically
throughout the SDLC
Defining Concepts/
Requirements
Software
Design
Design
1

15
IOT SDLC
Security Measures – Software Design
Ø Spans the whole SDLC,
from High-Level
Architecture (modules) to
Detailed Architecture
(functions & methods)
Ø Considers Safety aspects
for Cyber-Physical
interaction (Actuators,
Sensors in Environment,
Human Safety, etc.)
Ø Designs Security
Foundations to avoid future
Costlier Remediations
Defining Concepts/
Requirements
Software
Design
Design
1
Requirements System Specifications Software Specifications
IoT / Software
Security
Requirements
• FOTA
• Remote Credentials Management
• Access Control
• Policies Configuration
• Security Lifecycle
1. Decompose App. Architecture in functional components
2. Categorize and Prioritize Threats
3. Plan & Prioritize Controls
4. Define Countermeasures for Attacks & Vulnerabilities:
Chain of Trust
Recovery Plan
Security Mechanisms
Functional &
Business
Requirements
Software Engineers
Security Engineers
Product Owners

Ø Design IoT Devices &
Systems with Unique IDs;
Apply Auth & Access
Control at each Interface
16
IOT SDLC
Security Measures – Software Design (Authentication & Authorization)
AWS
Certificate Manager
Amazon
Cognito
AWS Identity
Access Management (IAM)
AWS
Secrets Manager
AWS Key Management
Service (AWS KMS)
AWS Well
Architected Framework
(Security Pillar + IoT Lens)
Defining Concepts/
Requirements
Software
Design
Design
1

17
IOT SDLC
Software Design – Example of what NOT TO DO!!
Defining Concepts/
Requirements
Software
Design
Design
1
Requirements System Specifications Software Specifications
Incident’s Root Cause
• Undefined Security Mechanisms
(Remote Credentials Management)
• No update-certificate mechanism
• Root Certificate became Blacklisted
Outcome / Security Incident
• 30% of devices not able to connect
• 4+ weeks of service unavailability
• Huge involvement of AWS and the CA
• Only 2 future options:
• Ignore the issue (Reputation – Unmeasurable)
• Replace deprecated devices (> 1M€ !!!)
Suggestions
Ø Invest, early, enough
resources and time
during the Design and
Requirements Phase
Ø Define a Certificate
Trust Store to manage/
store Root Certificate(s)
Ø DO NOT store required
root certificate(s)
without the possibility to
update them (e. g. as
part of the firmware or
hardcoded in the
software) !!!

18
IOT SDLC
Security Measures – Software Development, Testing, and Acceptance
2
Ø Mind Hardware & Software
Constraints in IoT Devices
Ø Includes in the loop IaaC
Ø Assesses 3rd-party / Open-
Source APIs, libraries
BEFORE Integration
Ø Manual Checklist-Based
Code Peer Reviews to
Detect Vulnerabilities not
Identified by Automation
Ø E2E Reply’s IoT Security
Test Unit
Development /
Implementation
Testing and
Acceptance
Provisioning
Design Specifications Code Development Automation & Testing
Secure Coding Guidelines & Standards
• ETSI TS 303 645 V2.1
• IoT Security Compliance Framework
• OWASP ISVS
• ENISA Baseline Security Recommendations for IoT
Automation & Scalability
• Code Reviews (manual)
• Configuration
Management
• CI / CD Strategy
(DevSecOps)
Software Engineers
Security Engineers
Product Owners
Testing Strategy
• Static Code Testing (SAST)
• Dynamic Analysis / Testing
• Design Testing Environment
• Penetration Testing of ALL SW
• Holistic approach: End Devices,
Firmware, Communications, etc.)

19
IOT SDLC
IoT DevSecOps CI/CD Pipeline with SCA, SAST, DAST Practices, and Security Events Management
2
Development /
Implementation
Testing and
Acceptance
Provisioning
Reply © 2022 All rights reserved. Do not distribute without written
authorization

20
IOT SDLC
Software Development – Example of what NOT TO DO!!
2
Development /
Implementation
Testing and
Acceptance
Provisioning
Design Specifications Code Development Automation & Testing
Incident’s Root Cause
• Human Error
• IaC GitHub Public Repository
• AWS Admin Credentials hardcoded in IaC
• No centralized logging was in place
Outcome / Security Incident
• Hackers got access to credentials
• AWS account was hacked
• >200k€ of AWS costs over a weekend
• RCA & Resolution took 2 Working Days
Suggestions
Ø Include Static
Application Security
Testing (SAST) ALSO
to the Infrastructure as
Code (IaC)
Ø Periodically Educate
the workforce over
security best practices
when developing code
Ø Use the Least-Privilege
Principle when
assigning permissions

21
IOT SDLC
Security Measures – Deployment, Integration, and Maintenance
Deployment Strategy
• Consider Rollout/ Rollback, Timings, Downtime
Requirements
• Include Final Security Reviews (FSRs) by subject
matter security experts
Ø Considers Heterogeneity of
Deployment Environments
Ø Create and Test Business
Continuity and Disaster
Recovery Plans
Ø Consider lifetime of IoT
Devices and plan ahead
Ø Defines special Asset &
User Authorization
methods for self-enrolling
devices (e. g. over the air)
Maintenance
and Disposal
3
Deployment and
Integration
Operating /
Disposing
End Users
Production Teams
Development Teams
System Integrators
Maintenance Strategy
• Define Security Auditing & Monitoring Procedures
in IoT and IT Environments
• Define Incident Management with Proactive
Detection & Response Procedures
• Conduct Penetration Testing of IoT Software and
its Infrastructure (IaC)
Disposal Strategy
• Define Data Erasure Mechanisms to preserve
Privacy Management for Sensitive Data Types

22
IOT SDLC
Security Measures – Deployment, Integration, and Maintenance
AWS IoT
Device Defender
AWS
Security Hub
Amazon
CloudWatch
AWS
CloudTrail
Amazon
GuardDuty
AWS
Config
Maintenance
and Disposal
3
Deployment and
Integration
Operating /
Disposing
CloudEndure
Disaster Recovery
AWS
Backup
Ø Other AWS Services for
Security Auditing &
Monitoring in IoT and IT
Environments:

24
CONCLUSIONS
How can Enterprises and
Developers make sure
Cybersecurity does not
represent a blocker for
successful IoT Initiatives?
ü Consider ALL the Actors,
Processes, and Technologies
involved in the IoT Value Chain
ü Factor-in Security Investments
to Avoid Costly Remediations
ü Forge a Security-First Culture
in the Organization
ü Engage the Right Partners
ü Test Software in Every Stage
of the Chain, and Test it Often
Key Takeaways

THANK YOU
Gabriel Paredes Loza
BU Manager @ Storm Reply

Securing the IoT Value Chain with AWS

Recomendados

Recomendados

Más contenido relacionado

Similar a Securing the IoT Value Chain with AWS

Similar a Securing the IoT Value Chain with AWS (20)

Último

Último (20)

Securing the IoT Value Chain with AWS