This course explores AWS Security Hub, starting with a high-level overview of AWS security. We are then going to highlight some of the services that sit in the AWS security space concluding with AWS Security Hub and some sample security result findings obtained using the AWS Console.
Learning Objectives
- Learn how AWS Security Hub helps you automate security checks, manage security issues, and identify the highest priority security findings in your AWS implementation
- Understand AWS security services including Amazon Inspector, Macie, and Guard Duty
- Learn how to check your environments and systems against security industry standards and best practices
Intended Audience
This course is intended for architects, developers, and system operators looking for a unified, scalable way to secure AWS accounts and resources.
Prerequisites
To get the most out of this course, you should meet the requirements for the AWS Cloud Practitioner certification and preferably one of the AWS associate-level certifications.
We started with AWS Security Hub and we're about to close with a discussion of AWS Security Hub. Security Hub helps you automate security checks, manage security issues and identify the highest priority security findings in your AWS implementation. It automatically checks that you're taking the right steps towards the security implementation and aggregates findings from a dozen AWS services, including Inspector, GuardDuty, and Macie among others as discussed previously. It also automates checks for CIS AWS Foundational Security Best Practices version 1.0 and provides a security and compliance score based on it.
For this demonstration, we open a brand new account with AWS and implemented the steps discussed earlier including enabling AWS Security Hub and the AWS Foundational Security Best Practices version one to obtain a score. Logging into the console and navigating to the AWS Security Hub dashboard, we get to see these findings. As you get to see, we obtained a good score. It's not 100. and that is because the account was misconfigured at the beginning on purpose in order to test some of the services discussed in this presentation.
Following those tests for AWS Config, GuardDuty, and Macie, we took all the needed corrections. This is our final score after implementing all of the best practices mentioned earlier for AWS Identity and Access Management. As well as sealing public access to all Amazon S3 buckets. I hope you now have a basic understanding of AWS Security Hub, Security Best Practices, and some of the other security services AWS makes available to you. Again, AWS security is to be taken seriously. Fortunately, we have tools like AWS Security Hub available to get your security implementation compliant with best practices.
Experienced in architecture and delivery of cloud-based solutions, the development, and delivery of technical training, defining requirements, use cases, and validating architectures for results. Excellent leadership, communication, and presentation skills with attention to details. Hands-on administration/development experience with the ability to mentor and train current & emerging technologies, (Cloud, ML, IoT, Microservices, Big Data & Analytics).