Book Image

AWS Certified Security – Specialty Exam Guide

By : Stuart Scott
Book Image

AWS Certified Security – Specialty Exam Guide

By: Stuart Scott

Overview of this book

AWS Certified Security – Specialty is a certification exam to validate your expertise in advanced cloud security. With an ever-increasing demand for AWS security skills in the cloud market, this certification can help you advance in your career. This book helps you prepare for the exam and gain certification by guiding you through building complex security solutions. From understanding the AWS shared responsibility model and identity and access management to implementing access management best practices, you'll gradually build on your skills. The book will also delve into securing instances and the principles of securing VPC infrastructure. Covering security threats, vulnerabilities, and attacks such as the DDoS attack, you'll discover how to mitigate these at different layers. You'll then cover compliance and learn how to use AWS to audit and govern infrastructure, as well as to focus on monitoring your environment by implementing logging mechanisms and tracking data. Later, you'll explore how to implement data encryption as you get hands-on with securing a live environment. Finally, you'll discover security best practices that will assist you in making critical decisions relating to cost, security,and deployment complexity. By the end of this AWS security book, you'll have the skills to pass the exam and design secure AWS solutions.
Table of Contents (27 chapters)
1
Section 1: The Exam and Preparation
3
Section 2: Security Responsibility and Access Management
8
Section 3: Security - a Layered Approach
15
Section 4: Monitoring, Logging, and Auditing
18
Section 5: Best Practices and Automation
21
Section 6: Encryption and Data Security

Summary

To review, the three different models discussed in this chapter were the shared responsibility model for infrastructure services, the shared responsibility model for container services, and the shared responsibility model for abstract services. It is clear to see that across these models, from infrastructure to abstract, the level of security responsibility shifted more toward AWS and away from the customer. This is down to the fact that AWS has more control over the level of management of services falling within the container and abstract models.

It is certainly worth understanding these models and being able to differentiate between them; this will serve you in good stead when you come to implement your security strategies across different solutions. You will have a clear understanding of where your responsibility ends and where AWS' starts. This will help to ensure that you do not leave any vulnerabilities across your AWS infrastructure within your accounts.

In the next...