You're reading from Cloud Security Handbook Find out how to effectively secure cloud environments using AWS, Azure, and GCP

Product type Paperback

Published in Apr 2022

Publisher Packt

ISBN-13 9781800569195

Length 456 pages

Edition 1st Edition

Tools

AWS

Concepts

Cloud Computing

Author (1):

Eyal Estrin

Preface

1. Section 1: Securing Infrastructure Cloud Services

2. Chapter 1: Introduction to Cloud Security FREE CHAPTER

3. Chapter 2: Securing Compute Services

4. Chapter 3: Securing Storage Services

5. Chapter 4: Securing Networking Services

6. Section 2: Deep Dive into IAM, Auditing, and Encryption

7. Chapter 5: Effective Strategies to Implement IAM Solutions

8. Chapter 6: Monitoring and Auditing Your Cloud Environments

9. Chapter 7: Applying Encryption in Cloud Services

10. Section 3: Threats and Compliance Management

11. Chapter 8: Understanding Common Security Threats to Cloud Services

12. Chapter 9: Handling Compliance and Regulation

13. Chapter 10: Engaging with Cloud Providers

14. Section 4: Advanced Use of Cloud Services

15. Chapter 11: Managing Hybrid Clouds

16. Chapter 12: Managing Multi-Cloud Environments

17. Chapter 13:Security in Large-Scale Environments

18. Other Books You May Enjoy

Conducting incident response and digital forensics

Incident response and forensics are challenging in cloud environments for several reasons:

Our entire environment is stored at a physical location, managed by an external service provider.
Our entire environment is split between our on-premises and a cloud provider (also known as a hybrid cloud environment).
Our entire environment is split between multiple cloud providers (also known as a multi-cloud environment).
Our cloud environment is in multiple regions or multiple cloud accounts (such as across an AWS account, Azure subscriptions, and GCP projects), and we might lack visibility to all resources deployed in our cloud environment or information about who owns or manages those accounts.
According to the shared responsibility model, we may not have visibility for actions done by our cloud provider (such as a cloud engineer making changes to a managed database or performing a backup or restore from an SaaS...

The rest of the chapter is locked