Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
AWS Certified Security – Specialty Exam Guide

You're reading from   AWS Certified Security – Specialty Exam Guide Build your cloud security knowledge and expertise as an AWS Certified Security Specialist (SCS-C01)

Arrow left icon
Product type Paperback
Published in Sep 2020
Publisher Packt
ISBN-13 9781789534474
Length 558 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Stuart Scott Stuart Scott
Author Profile Icon Stuart Scott
Stuart Scott
Wilberto Palomar Wilberto Palomar
Author Profile Icon Wilberto Palomar
Wilberto Palomar
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

Preface 1. Section 1: The Exam and Preparation
2. AWS Certified Security - Specialty Exam Coverage FREE CHAPTER 3. Section 2: Security Responsibility and Access Management
4. AWS Shared Responsibility Model 5. Access Management 6. Working with Access Policies 7. Federated and Mobile Access 8. Section 3: Security - a Layered Approach
9. Securing EC2 Instances 10. Configuring Infrastructure Security 11. Implementing Application Security 12. DDoS Protection 13. Incident Response 14. Securing Connections to Your AWS Environment 15. Section 4: Monitoring, Logging, and Auditing
16. Implementing Logging Mechanisms 17. Auditing and Governance 18. Section 5: Best Practices and Automation
19. Automating Security Detection and Remediation 20. Discovering Security Best Practices 21. Section 6: Encryption and Data Security
22. Managing Key Infrastructure 23. Managing Data Security 24. Mock Tests 25. Assessments 26. Other Books You May Enjoy

Summary

This chapter took you through the various types of access policies, their structure, and how to effectively and securely manage access to your AWS resources. You need to be fully aware of the different policies that exist within AWS and how they work together to either grant or deny access to resources based on different actions.  

Regardless of which policy you are using, one key point is to always implement security based on the Principle of Least Privilege (PoLP). This essentially means that you should only ever grant permissions for an identity that they actually need, and no more. For example, let's say a user needed access to be able to stop and terminate instances using ec2:stopinstances and ec2:terminateinstances. Then, you wouldn’t issue a policy that allowed access to all ec2 APIs—for example, ec2:*. If this happens, you are increasing the potential of security threats, especially from an internal perspective. For the certification exam...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $24.99/month. Cancel anytime