Prof. Dr. Larry AdamsAcademic, Author & Researcher
Cybersecurity & Digital Risk Management · Book 2

Cloud Infrastructure Security and Resilience

Cloud Architecture, Workload Protection and Recovery Engineering

Dr. Lance Adams and Prof. Dr. Larry Adams

Free to read online. For a copy of this book, or to quote, highlight or reproduce any part of it, please request permission through the contact page beforehand.

Publication and use note

This document is an educational manuscript draft prepared for development, teaching and professional discussion. It is not legal advice, a guarantee of security, or a substitute for a qualified assessment of a specific environment. Technical configurations, product features, standards editions and legal obligations change. Before publication or operational use, verify all claims against current authoritative documentation and the relevant jurisdiction. Practical activities must be conducted only in authorised, controlled environments.

Preface

This volume forms part of the Cybersecurity & Digital Risk Management collection. It is designed to connect clear conceptual explanations with practical decisions, professional judgement and reflective learning. The aim is to help readers understand not only which controls may be useful, but why they matter, where they can fail and how their effectiveness can be evaluated.

Help readers understand how to design, configure, monitor and recover cloud environments using risk-based defensive practices.

Intended readership

The material is intended for students, educators, IT and security practitioners, managers, auditors, entrepreneurs and interested readers. Readers should adapt examples to their own context and seek specialist advice where technical, contractual or legal consequences are significant.

Learning outcomes

  • Explain cloud service and deployment models and shared responsibility.
  • Design identity, network, storage and logging controls for cloud workloads.
  • Recognise common configuration and workload risks.
  • Develop backup, recovery and resilience objectives.
  • Assess cloud security using documented evidence and safe lab scenarios.

How to use this book

Read the chapters in sequence for a structured introduction, or use individual chapters as workshop material. Complete the practical tasks in a lab or with fictional data. For group learning, ask participants to state assumptions, compare alternative controls and explain the trade-offs between security, usability, cost, privacy and availability.

Contents

  • Chapter 1: Cloud Models and Shared Responsibility
  • Chapter 2: Cloud Identity and Least Privilege
  • Chapter 3: Secure Storage, Databases and Encryption
  • Chapter 4: Cloud Network Design and Segmentation
  • Chapter 5: Virtual Machines, Containers and Serverless Workloads
  • Chapter 6: Configuration Management and Secure Migration
  • Chapter 7: Logging, Monitoring and Threat Detection
  • Chapter 8: Resilience, Backup and Recovery Engineering
  • Applied case study
  • Practical activities and assessment
  • Glossary
  • Selected references and further reading

Chapter 1: Cloud Models and Shared Responsibility

Cloud computing provides configurable computing resources through a service model. Infrastructure as a Service gives customers substantial responsibility for operating systems and workloads; Platform as a Service shifts more operational responsibility to the provider; Software as a Service places more of the application stack under provider management while leaving customers responsible for identities, data, configuration and appropriate use. Public, private, hybrid and multicloud arrangements each introduce different dependencies.

Shared responsibility is not a reason to assume that a provider handles every security task. The exact division varies by service and contract. Organisations should document who configures access, patches guest systems, protects data, monitors events, tests recovery and reports incidents. A responsibility matrix is especially important when several teams and suppliers operate the same service.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on cloud models and shared responsibility?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 2: Cloud Identity and Least Privilege

Identity is a primary cloud security boundary. Human users, workloads, services and automated pipelines all need identities, and each identity should receive only the permissions required for its defined task. Prefer short-lived credentials and managed identities over long-lived secrets where supported. Protect administrator accounts with strong authentication, separate privileged work from everyday activity and monitor sensitive changes.

Access reviews should examine whether permissions remain necessary, not merely whether an account is still active. Emergency access must be documented, protected and tested. Service accounts should have clear owners and rotation or retirement procedures. In infrastructure-as-code and deployment pipelines, secrets should be stored in appropriate secret-management systems rather than embedded in source files or logs.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on cloud identity and least privilege?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 3: Secure Storage, Databases and Encryption

Cloud storage errors often arise from excessive permissions, public exposure, weak retention controls or unclear data ownership. Establish default-private configurations, classify information before storage, and make exceptions explicit and time-limited. Databases should use private connectivity where practical, least-privilege database roles, supported versions, secure backups and auditable administrative access.

Encryption at rest and in transit reduces exposure but does not replace access control. Key management includes creation, storage, rotation, access approval, backup, revocation and retirement. Separation of duties may be appropriate for high-impact keys. Teams should understand which service manages keys, who can use them and what happens if a key is disabled or lost.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on secure storage, databases and encryption?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 4: Cloud Network Design and Segmentation

Cloud networks should be designed around required communication paths rather than broad connectivity by default. Separate production, development, management and sensitive-data environments where justified. Use security groups, network access controls, private endpoints, firewalls and routing rules to restrict traffic. Administrative interfaces should not be exposed publicly without a documented need and strong compensating controls.

Network diagrams and data-flow maps help teams understand dependencies. Review ingress and egress rules, identify unnecessary public addresses, and test whether a compromised workload could reach unrelated systems. Segmentation is not only a technical setting; it requires ownership of rules and a process for approving, reviewing and removing exceptions.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on cloud network design and segmentation?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 5: Virtual Machines, Containers and Serverless Workloads

Virtual machines require hardened images, patch management, secure administration and monitoring. Containers add image provenance, dependency management, runtime permissions and orchestration configuration. Use trusted base images, scan dependencies, avoid privileged containers unless necessary and prevent secrets from being baked into images. Serverless services reduce some infrastructure-management tasks but still require secure permissions, input validation, dependency updates, logging and limits on resource consumption.

Workload security should be integrated into development and deployment. Automated checks can detect known vulnerable components and risky configuration before release. Findings need prioritisation: a vulnerability in an internet-facing service handling sensitive data may warrant faster action than the same issue in an isolated test environment.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on virtual machines, containers and serverless workloads?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 6: Configuration Management and Secure Migration

Misconfiguration can expose data even when underlying cloud technology is robust. Common examples include overly broad access policies, publicly reachable management ports, disabled logging, unencrypted storage and unprotected secrets. Use approved baseline configurations, version-controlled infrastructure-as-code, peer review and automated policy checks. Drift detection helps identify when live resources no longer match the approved design.

Migration planning should inventory applications and data, identify dependencies, classify information, define security requirements and test rollback. Do not copy legacy permissions into the cloud without review. Pilot migrations should validate identity integration, network controls, logging, backup restoration and incident escalation before critical workloads move.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on configuration management and secure migration?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 7: Logging, Monitoring and Threat Detection

Effective monitoring begins with a clear question: which events would indicate misuse, compromise or unsafe change? Collect identity events, administrative actions, network telemetry, workload logs and relevant application records. Ensure timestamps are consistent, access to logs is controlled and retention meets operational and legal needs. Logs should be protected from alteration by the same accounts that could be under investigation.

Alerting should be tied to response procedures. Excessive low-value alerts can hide significant events, so tune detections and assign owners. Monitor unusual privilege changes, unexpected data transfers, disabled security services and suspicious authentication patterns. Detection is not complete until an alert can be triaged, investigated, escalated and closed with documented reasoning.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on logging, monitoring and threat detection?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 8: Resilience, Backup and Recovery Engineering

Resilience means sustaining or restoring essential services despite disruption. Define recovery time objectives (RTOs) and recovery point objectives (RPOs) with business owners. RTO expresses the target time to restore a service; RPO expresses the acceptable amount of data loss measured in time. These targets should reflect business impact, not simply technical preference.

Backups should be isolated from routine administrative credentials, protected against deletion and tested through realistic restoration exercises. Consider regional failure, provider outages, compromised identities and destructive changes. Recovery runbooks should identify decision-makers, dependencies, communications and verification steps. A backup that has never been restored is an assumption, not proven resilience.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on resilience, backup and recovery engineering?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Integrated case study

A cloud storage bucket containing customer reports becomes publicly accessible after a deployment change. The response team should restrict access promptly, preserve configuration and access logs, establish what data was exposed, notify the privacy and legal functions as appropriate, rotate affected credentials if necessary, and introduce preventive configuration checks and change review.

Case study analysis

  • Identify the important assets, stakeholders and business objectives.
  • Describe the likely threat scenarios and the evidence needed to assess them.
  • Recommend immediate actions and longer-term preventive improvements.
  • Explain how the organisation should document decisions and measure effectiveness.
  • Identify privacy, legal, ethical or operational considerations that require specialist review.

Practical activities and assessment

  • Draw a reference cloud architecture showing identity, network, data, logging and recovery controls.
  • Review a fictional cloud configuration checklist and prioritise findings by likelihood and impact.
  • Write an RTO/RPO proposal for three services and justify the business assumptions.
  • Create a shared-responsibility matrix for a selected cloud service model.

Suggested assessment rubric

Glossary of key terms

Asset: Something of value to an individual or organisation, including data, services, identities and systems.

Authentication: A process used to establish that a user, device or service is the entity it claims to be.

Confidentiality: Protection against unauthorised disclosure of information.

Control: A safeguard or process intended to modify risk.

Incident: An event that compromises or threatens the security or operation of systems, services or information.

Least privilege: The principle of granting only the access and permissions needed for a defined task.

Residual risk: Risk remaining after controls and treatment decisions are considered.

Resilience: The ability to anticipate, withstand, recover from and adapt to disruption.

Threat: A potential cause of unwanted harm.

Vulnerability: A weakness that could be exploited or otherwise contribute to harm.

Selected standards and further reading

The following are starting points for verification and further study. Confirm the current edition, applicability and licensing conditions before quoting or relying on a standard.

  • National Institute of Standards and Technology (NIST). Cybersecurity Framework (CSF) 2.0. NIST, 2024.
  • International Organization for Standardization. ISO/IEC 27001, Information security management systems — Requirements. Consult the current edition.
  • International Organization for Standardization. ISO/IEC 27002, Information security controls. Consult the current edition.
  • International Organization for Standardization. ISO 31000, Risk management — Guidelines. Consult the current edition.
  • Center for Internet Security. CIS Critical Security Controls. Consult the current version.
  • National Institute of Standards and Technology. NIST Privacy Framework. Consult the current version.
  • OWASP Foundation. OWASP Top 10 and other relevant application-security guidance. Consult the current version.
  • National Institute of Standards and Technology. Relevant SP 800-series publications on security, privacy, incident response and contingency planning; verify the publication status and current revision.

Editorial development checklist

  • Verify every technical claim and update examples to reflect current practice.
  • Add properly sourced APA 7 in-text citations throughout the manuscript before publication.
  • Review jurisdiction-specific legal and regulatory sections with qualified advisers.
  • Add diagrams, figures and accessible alt text where they materially aid understanding.
  • Conduct technical peer review and copy-editing; validate all exercises in authorised lab settings.
  • Add index, acknowledgements, final copyright details and publisher information when known.