Shared Responsibility: Cloud providers handle infrastructure, user data management is typically the user's responsibility.

Responsibility Matrix: Outlines who is responsible for what in a cloud environment.

Cloud
Hybrid Considerations: Merging on-premises and cloud can complicate security.
Third-party Vendors: More vendors can increase risk but may also distribute responsibility.
Infrastructure as Code (IaC) Automation can speed deployment but can also propagate errors or vulnerabilities quickly.
Serverless Reduced infrastructure overhead but increased reliance on third-party services.
Microservices Isolation of services can limit breach scope, but increased inter-service communication can introduce new vulnerabilities.
Physical Isolation (Air-gapped): No external network connections, reducing external threats.
Network Infrastructure Design and segmentation can greatly impact security posture. Logical Segmentation: Isolate parts of the network to contain breaches.
Software-defined Networking (SDN): Greater flexibility but potential for misconfigurations.
On-premises Full control over infrastructure but also full responsibility for all aspects of security.
Architecture Models
Centralized: Offers a single control point but can be a single point of failure.
Centralized vs. Decentralized
Decentralized: Distributes risk but can be harder to manage.
Containerization Lightweight, isolated environments but potential for container vulnerabilities.
Virtualization Efficient resource use and isolation, but hypervisor vulnerabilities can impact multiple virtual machines.
IoT Expanded attack surface with many devices, often with limited security features.
ICS/SCADA Critical infrastructure with potential for physical harm if breached.
RTOS (Real-time Operating Systems) Time-sensitive operations can make patching or downtime difficult.
Mitigation Techniques and Architecture Models
Embedded Systems Often lack sophisticated security features and may be difficult to update.
High Availability Infrastructure resilience but requires synchronization and potential for replication of vulnerabilities.
Availability: Can it be accessed when needed?
Resilience: Can it recover from attacks or failures?
Cost: What are the financial implications?
Responsiveness: How quickly can it adapt or respond?
Scalability: Can it handle growth?
Ease of Deployment: How simple is it to roll out?
Considerations when Evaluating Models
Risk Transference: Can risks be shifted elsewhere (e.g., to cloud providers)?
Ease of Recovery: How simple is it to recover after an incident?
Patch Availability: Can security updates be applied regularly?
Inability to Patch: Are there constraints preventing regular updates?
Power: Does it meet processing needs?
Compute: Can it handle the computational load?

markmap