Security Hub overview in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable AWS Security Hub in a specific region.

AWS

aws securityhub [1] --region us-east-1

Drag options to blanks, or click blank then click option'

Aenable-security-hub

Bactivate

Cstart

Denable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' or 'activate' which are not valid AWS CLI commands for Security Hub.

Using 'enable' which is not the correct command syntax.

The correct command to enable Security Hub is enable-security-hub. This activates Security Hub in the specified region.

2fill in blank

medium

Complete the code to list all findings in AWS Security Hub.

AWS

aws securityhub [1] --region us-west-2

Drag options to blanks, or click blank then click option'

Adescribe-findings

Blist-findings

Cshow-findings

Dget-findings

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'list-findings' which is not a valid Security Hub command.

Using 'describe-findings' which is used in other AWS services but not Security Hub.

The correct command to retrieve findings is get-findings. It returns the security findings detected by Security Hub.

3fill in blank

hard

Fix the error in the command to disable Security Hub.

AWS

aws securityhub [1] --region eu-central-1

Drag options to blanks, or click blank then click option'

Adelete

Bdisable-security-hub

Cdisable

Dstop

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stop' or 'disable' which are not valid commands for Security Hub.

Using 'delete' which removes resources but is not the correct command here.

The correct command to disable Security Hub is disable-security-hub. Other options are invalid commands.

4fill in blank

hard

Fill both blanks to filter Security Hub findings by severity and resource type.

AWS

aws securityhub get-findings --filters SeverityLabel={Eq=[1],ResourceType={Eq=[2] --region us-east-2

Drag options to blanks, or click blank then click option'

AHIGH

BCRITICAL

CAwsEc2Instance

DAwsS3Bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or unquoted values causing command errors.

Mixing resource types or severity labels incorrectly.

SeverityLabel should be set to CRITICAL to filter high severity findings. ResourceType should be AwsEc2Instance to filter findings related to EC2 instances.

5fill in blank

hard

Fill all three blanks to create a custom action in Security Hub.

AWS

aws securityhub create-action-target --name [1] --description [2] --identifier [3] --region ap-southeast-1

Drag options to blanks, or click blank then click option'

A"NotifyTeam"

B"Notify the security team of critical findings"

C"NotifyTeamAction"

D"AlertOps"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same value for name and id causing confusion.

Leaving description empty or too short.

The --name is a short identifier like "NotifyTeam". The --description explains the action purpose. The --identifier is a unique string identifier like "NotifyTeamAction".