Security Hub overview in AWS - Commands & Configuration

Introduction

Security Hub helps you see and manage security alerts from many AWS services in one place. It collects findings and shows you where your cloud setup might have security problems.

When you want to check your AWS account for security issues regularly without logging into many different services.

When you need a single dashboard to see all security alerts from AWS services like GuardDuty, Inspector, and Macie.

When you want to automate security checks and get recommendations to fix problems.

When you manage multiple AWS accounts and want to see their security status in one place.

When you want to follow AWS best practices for cloud security and compliance.

Commands

This command turns on Security Hub in your AWS account so it can start collecting security findings.

Terminal

aws securityhub enable-security-hub

Expected Output

{"HubArn": "arn:aws:securityhub:us-east-1:123456789012:hub/default", "SubscribedAt": "2024-06-01T12:00:00Z"}

This command retrieves the current security findings that Security Hub has collected for your account.

Terminal

aws securityhub get-findings

Expected Output

{"Findings": []}

This command enables a security standard, like the CIS AWS Foundations Benchmark, which provides automated checks and recommendations.

Terminal

aws securityhub batch-enable-standards --standards-subscription-requests StandardsArn=arn:aws:securityhub:::ruleset/cis-aws-foundations-benchmark/v/1.2.0

Expected Output

{"StandardsSubscriptions": [{"StandardsSubscriptionArn": "arn:aws:securityhub:us-east-1:123456789012:subscription/cis-aws-foundations-benchmark", "StandardsArn": "arn:aws:securityhub:::ruleset/cis-aws-foundations-benchmark/v/1.2.0", "Status": "ENABLED"}]}

→

--standards-subscription-requests - Specifies which security standards to enable

This command turns off Security Hub in your AWS account when you no longer want to use it.

Terminal

aws securityhub disable-security-hub

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: Security Hub collects and shows all your AWS security alerts in one easy place.

Common Mistakes

Trying to get findings before enabling Security Hub

Security Hub must be enabled first to collect any security data, otherwise the get-findings command returns empty.

Always run 'aws securityhub enable-security-hub' before retrieving findings.

Not enabling security standards after turning on Security Hub

Without enabling standards, Security Hub won't run automated checks or provide recommendations.

Use 'aws securityhub batch-enable-standards' to activate useful security checks.

Summary

Enable Security Hub to start collecting security alerts in your AWS account.

Retrieve security findings to see current issues and alerts.

Enable security standards to get automated security checks and recommendations.

Disable Security Hub when you no longer need centralized security monitoring.

Practice

1. What is the main purpose of AWS Security Hub?

easy

A. To manage user permissions

B. To create virtual machines

C. To show all your security alerts in one place

D. To store large amounts of data

Solution

1. Step 1: Understand Security Hub's role

   AWS Security Hub collects and shows security alerts from different services.

2. Step 2: Compare options with Security Hub's function

   Only To show all your security alerts in one place describes showing security alerts in one place, which matches Security Hub's purpose.

3. Final Answer:

   To show all your security alerts in one place -> Option C

4. Quick Check:

   Security Hub = central alert view [OK]

Hint: Security Hub centralizes security alerts [OK]

Common Mistakes:

• Confusing Security Hub with storage services
• Thinking Security Hub manages users
• Assuming it creates virtual machines

2. Which command is used to enable AWS Security Hub in your account?

easy

A. aws securityhub enable-security-hub

B. aws ec2 start-instances

C. aws s3 create-bucket

D. aws iam create-user

Solution

1. Step 1: Identify the command for enabling Security Hub

   The command to enable Security Hub is specific and includes 'securityhub' and 'enable-security-hub'.

2. Step 2: Eliminate unrelated commands

   Other options relate to EC2, S3, and IAM, which are unrelated to enabling Security Hub.

3. Final Answer:

   aws securityhub enable-security-hub -> Option A

4. Quick Check:

   Enable Security Hub = aws securityhub enable-security-hub [OK]

Hint: Enable Security Hub with aws securityhub enable-security-hub [OK]

Common Mistakes:

• Using EC2 or S3 commands by mistake
• Confusing IAM user creation with enabling Security Hub
• Missing the 'securityhub' part in the command

3. After enabling Security Hub, what will you see when you open the Security Hub console?

medium

A. A list of all your security findings from multiple AWS services

B. A dashboard showing your EC2 instance statuses

C. A list of your S3 buckets and their contents

D. A user management panel

Solution

1. Step 1: Understand what Security Hub displays

   Security Hub shows security findings collected from various AWS services in one place.

2. Step 2: Match options with Security Hub's display

   Only A list of all your security findings from multiple AWS services describes a list of security findings, which is what Security Hub shows.

3. Final Answer:

   A list of all your security findings from multiple AWS services -> Option A

4. Quick Check:

   Security Hub console = security findings list [OK]

Hint: Security Hub console shows security findings [OK]

Common Mistakes:

• Confusing Security Hub with EC2 or S3 consoles
• Expecting user management features in Security Hub
• Thinking it shows bucket contents

4. You enabled Security Hub but do not see any findings. What could be the reason?

medium

A. Security Hub is disabled automatically after enabling

B. No integrated AWS services are sending security data to Security Hub

C. You need to create an S3 bucket first

D. Security Hub only works in specific AWS regions

Solution

1. Step 1: Check data sources for Security Hub

   Security Hub shows findings only if integrated services send data to it.

2. Step 2: Evaluate other options

   Security Hub does not disable itself automatically; no S3 bucket is needed; it works in many regions but not limited to one.

3. Final Answer:

   No integrated AWS services are sending security data to Security Hub -> Option B

4. Quick Check:

   No findings = no data sent [OK]

Hint: Check if services send data to Security Hub [OK]

Common Mistakes:

• Assuming Security Hub disables itself
• Thinking S3 bucket is required
• Believing Security Hub is region-limited

5. You want to improve your cloud security by automatically aggregating findings from multiple AWS accounts into one Security Hub dashboard. What should you do?

hard

A. Manually copy findings from each account to a central S3 bucket

B. Create IAM users in each account and share credentials

C. Use EC2 instances to collect and forward security data

D. Enable Security Hub in the master account and invite member accounts to send findings

Solution

1. Step 1: Understand Security Hub multi-account setup

   Security Hub supports a master-member model where a master account aggregates findings from member accounts.

2. Step 2: Evaluate other options for aggregation

   Creating IAM users or manual copying is inefficient and insecure; EC2 instances are not used for this aggregation.

3. Final Answer:

   Enable Security Hub in the master account and invite member accounts to send findings -> Option D

4. Quick Check:

   Multi-account aggregation = master invites members [OK]

Hint: Use master account to aggregate member findings [OK]

Common Mistakes:

• Trying manual copying of findings
• Using IAM users instead of Security Hub invitations
• Relying on EC2 instances for aggregation