1. Home
  2. Training Library
  3. Amazon Web Services
  4. Amazon Web Services Courses
  5. Automating and Centralizing Security Checks with AWS Security Hub

AWS Security Hub Operation

Contents

keyboard_tab
Course Introduction
1
Introduction
PREVIEW2m 30s
Course Summary
10
Start course
Overview
Difficulty
Beginner
Duration
20m
Students
149
Ratings
5/5
starstarstarstarstar
Description

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.

Transcript

In addition to best practices, the information generated by security services is significant in terms of volume and categories. Gathering security findings in a single place is difficult and the information requires close attention and analysis in order to guarantee a secure and compliant environment at all times. This is where AWS Security Hub becomes essential by providing a single point of access to your security implementation and automatically verifying you are applying best practices as defined by AWS security experts. Let's discuss some of these foundational best practices for new AWS accounts. 

Whether you're just getting started or have some experience already with AWS, there's no doubt you have to interact with the AWS Identity and Access Management service. This is the service to provision users, define access controls for those users including passwords and access keys. Identity and Access Management is one of the many security services provided by AWS in order to assist you in the provisioning of a secure and compliant implementation.

This diagram represents three best practices regarding AWS Identity and Access Management. As you can see, it seems a little complicated. Let's break it down step by step into some of the foundational best practices that Security Hub verifies.

Number one, the Root User is the owner of AWS account, and it has access to everything including the credit card used to pay for services. As a best practice, always assign a multifactor authentication to the root user. That way, the root account is protected at all times. After that, create a group and apply administrator permissions to it. Then create a user, also assign an MFA to that user and provision keys if needed. Finally, add the user to the group, sign off the root account, and try never to use it again unless strictly necessary.

Your implementation will begin by leveraging the administrator user that you just created. Groups are an efficiency mechanism to apply permissions. It is easier to define a group, apply permissions, and then add or remove users as needed. You should rarely have to apply permissions to a user directly. If required, you can also provision keys to a user. Finally, also if required, you can allow the user to assume roles. For item number three, roles represent a way to gain permissions on a temporary basis.

The primary use of roles is to allow services to interact with each other. Users can also assume a role if needed. The permissions attributed to a role should be what is needed and nothing in addition to that. This is called the principle of least privilege, sometimes also called the principle of maximum security. Roles are commonly associated with EC2 instances and services. As a general security best practice, never store access keys in your code on EC2 instances or Amazon S3 buckets.

Fortunately for us, AWS offers a variety of tools for automating provisioning, monitoring, and auditing, many of them using machine learning in order to help us get our Cloud Security compliant with best practices. We just implemented some of the foundational security best practices checked by AWS Security Hub. We're gonna see the results later on.

About the Author
Avatar
Jorge Negrón
AWS Content Architect
Students
2372
Courses
12

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).