You're reading from Mastering AWS Security - Second Edition

Product type Book

Published in Apr 2024

Publisher Packt

ISBN-13 9781805125440

Pages 370 pages

Edition 2nd Edition

Languages

Concepts

Author (1):

Laurent Mathieu

Preface

1. Part 1: Foundations of AWS Security

2. Chapter 1: Introduction to AWS Security Concepts and the Shared Responsibility Model

3. Chapter 2: Infrastructure Security – Keeping Your VPC secure

4. Chapter 3: Identity and Access Management – Securing Users, Roles, and Policies

5. Chapter 4: Data Protection – Encryption, Key Management, and Data Storage Best Practices

6. Chapter 5: Introduction to AWS Security Services

7. Part 2: Architecting and Deploying Secure AWS Environments

8. Chapter 6: Designing Secure Microservices Architectures in AWS

9. Chapter 7: Implementing Security for Serverless Deployments

10. Chapter 8: Secure Design Patterns for Multi-Tenancy in Shared Environments

11. Chapter 9: Automate Everything to Build Immutable and Ephemeral Resources

12. Part 3: Monitoring, Automation and Continuous Improvement

13. Chapter 10: Advanced Logging, Auditing, and Monitoring in AWS

14. Chapter 11: Security Compliance with AWS Config, AWS Security Hub, and Automated Remediation

15. Chapter 12: DevSecOps – Integrating Security into CI/CD Pipelines

16. Chapter 13: Keeping Up with Evolving AWS Security Best Practices and Threat Landscape

17. Chapter 14: Closing Note

18. Index

19. Other Books You May Enjoy

Answers

Here are the answers to this chapter’s questions:

While responsibilities can be shared between AWS and the customer, accountability cannot. Regardless of the shared model, the customer always retains ultimate accountability for their data and for ensuring their part of the responsibilities is adequately addressed.
The shared responsibility model’s significance in terms of IaaS, PaaS, and SaaS lies in the delineation of security responsibilities. For IaaS, AWS is responsible for the security of the underlying infrastructure while the customer is responsible for the security of the OS, application, and data. For PaaS, AWS extends its responsibility to include the runtime and middleware, while the customer is responsible for the applications and data. For SaaS, AWS is responsible for the entire stack, and the customer is only responsible for user-related settings and data.
The shared responsibility model applies differently to various AWS compute...