Security Hub controls for AWS Backup
These Security Hub controls evaluate the AWS Backup service and resources.
These controls may not be available in all AWS Regions. For more information, see Availability of controls by Region.
[Backup.1] AWS Backup recovery points should be encrypted at rest
Related requirements: NIST.800-53.r5 CP-9(8), NIST.800-53.r5 SI-12
Category: Protect > Data Protection > Encryption of data-at-rest
Severity: Medium
Resource type:
AWS::Backup::RecoveryPoint
AWS Config rule:
backup-recovery-point-encrypted
Schedule type: Change triggered
Parameters: None
This control checks if an AWS Backup recovery point is encrypted at rest. The control fails if the recovery point isn't encrypted at rest.
An AWS Backup recovery point refers to a specific copy or snapshot of data that is created as part of a backup process. It represents a particular moment in time when the data was backed up and serves as a restore point in case the original data becomes lost, corrupted, or inaccessible. Encrypting the backup recovery points adds an extra layer of protection against unauthorized access. Encryption is a best practice to protect the confidentiality, integrity, and security of backup data.
Remediation
To encrypt an AWS Backup recovery point, see Encryption for backups in AWS Backup in the AWS Backup Developer Guide.
[Backup.2] AWS Backup recovery points should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::Backup::RecoveryPoint
AWS Configrule: tagged-backup-recoverypoint (custom Security Hub rule)
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredTagKeys
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList | List of tags that meet AWS requirements | No default value |
This control checks whether an AWS Backup recovery point has tags with the specific keys defined in the parameter
requiredTagKeys. The control fails if the recovery point doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredTagKeys. If the parameter requiredTagKeys isn't provided, the control only checks for the existence
of a tag key and fails if the recovery point isn't tagged with any key. System tags, which are automatically applied and begin with aws:,
are ignored.
A tag is a label that you assign to an AWS resource, and it consists of a key and an optional value. You can create tags to categorize resources by purpose, owner, environment, or other criteria. Tags can help you identify, organize, search for, and filter resources. Tagging also helps you track accountable resource owners for actions and notifications. When you use tagging, you can implement attribute-based access control (ABAC) as an authorization strategy, which defines permissions based on tags. You can attach tags to IAM entities (users or roles) and to AWS resources. You can create a single ABAC policy or a separate set of policies for your IAM principals. You can design these ABAC policies to allow operations when the principal's tag matches the resource tag. For more information, see What is ABAC for AWS? in the IAM User Guide.
Note
Don’t add personally identifiable information (PII) or other confidential or sensitive information in tags. Tags are accessible to many AWS services, including AWS Billing. For more tagging best practices, see Tagging your AWS resources in the AWS General Reference.
Remediation
To add tags to an AWS Backup recovery point
Open the AWS Backup console at https://console.aws.amazon.com/backup
. In the navigation pane, choose Backup plans.
Select a backup plan from the list.
In the Backup plan tags section, choose Manage tags.
Enter the key and value for the tag. Choose Add new tag for additional key-value pairs.
When you are finished adding tags, choose Save.
[Backup.3] AWS Backup vaults should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::Backup::BackupVault
AWS Configrule: tagged-backup-backupvault (custom Security Hub rule)
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredTagKeys
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList | List of tags that meet AWS requirements | No default value |
This control checks whether an AWS Backup vault has tags with the specific keys defined in the parameter
requiredTagKeys. The control fails if the recovery point doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredTagKeys. If the parameter requiredTagKeys isn't provided, the control only checks for the existence
of a tag key and fails if the recovery point isn't tagged with any key. System tags, which are automatically applied and begin with aws:,
are ignored.
A tag is a label that you assign to an AWS resource, and it consists of a key and an optional value. You can create tags to categorize resources by purpose, owner, environment, or other criteria. Tags can help you identify, organize, search for, and filter resources. Tagging also helps you track accountable resource owners for actions and notifications. When you use tagging, you can implement attribute-based access control (ABAC) as an authorization strategy, which defines permissions based on tags. You can attach tags to IAM entities (users or roles) and to AWS resources. You can create a single ABAC policy or a separate set of policies for your IAM principals. You can design these ABAC policies to allow operations when the principal's tag matches the resource tag. For more information, see What is ABAC for AWS? in the IAM User Guide.
Note
Don’t add personally identifiable information (PII) or other confidential or sensitive information in tags. Tags are accessible to many AWS services, including AWS Billing. For more tagging best practices, see Tagging your AWS resources in the AWS General Reference.
Remediation
To add tags to an AWS Backup vault
Open the AWS Backup console at https://console.aws.amazon.com/backup
. In the navigation pane, choose Backup vaults.
Select a backup vault from the list.
In the Backup vault tags section, choose Manage tags.
Enter the key and value for the tag. Choose Add new tag for additional key-value pairs.
When you are finished adding tags, choose Save.
[Backup.4] AWS Backup report plans should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::Backup::ReportPlan
AWS Configrule: tagged-backup-reportplan (custom Security Hub rule)
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredTagKeys
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList | List of tags that meet AWS requirements | No default value |
This control checks whether an AWS Backup report plan has tags with the specific keys defined in the parameter
requiredTagKeys. The control fails if the report plan doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredTagKeys. If the parameter requiredTagKeys isn't provided, the control only checks for the existence
of a tag key and fails if the report plan isn't tagged with any key. System tags, which are automatically applied and begin with aws:,
are ignored.
A tag is a label that you assign to an AWS resource, and it consists of a key and an optional value. You can create tags to categorize resources by purpose, owner, environment, or other criteria. Tags can help you identify, organize, search for, and filter resources. Tagging also helps you track accountable resource owners for actions and notifications. When you use tagging, you can implement attribute-based access control (ABAC) as an authorization strategy, which defines permissions based on tags. You can attach tags to IAM entities (users or roles) and to AWS resources. You can create a single ABAC policy or a separate set of policies for your IAM principals. You can design these ABAC policies to allow operations when the principal's tag matches the resource tag. For more information, see What is ABAC for AWS? in the IAM User Guide.
Note
Don’t add personally identifiable information (PII) or other confidential or sensitive information in tags. Tags are accessible to many AWS services, including AWS Billing. For more tagging best practices, see Tagging your AWS resources in the AWS General Reference.
Remediation
To add tags to an AWS Backup report plan
Open the AWS Backup console at https://console.aws.amazon.com/backup
. In the navigation pane, choose Backup vaults.
Select a backup vault from the list.
In the Backup vault tags section, choose Manage tags.
Choose Add new tag. Enter the key and value for the tag. Repeat for additional key-value pairs.
When you are finished adding tags, choose Save.
[Backup.5] AWS Backup backup plans should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::Backup::BackupPlan
AWS Configrule: tagged-backup-backupplan (custom Security Hub rule)
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredTagKeys
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList | List of tags that meet AWS requirements | No default value |
This control checks whether an AWS Backup backup plan has tags with the specific keys defined in the parameter
requiredTagKeys. The control fails if the backup plan doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredTagKeys. If the parameter requiredTagKeys isn't provided, the control only checks for the existence
of a tag key and fails if the backup plan isn't tagged with any key. System tags, which are automatically applied and begin with aws:,
are ignored.
A tag is a label that you assign to an AWS resource, and it consists of a key and an optional value. You can create tags to categorize resources by purpose, owner, environment, or other criteria. Tags can help you identify, organize, search for, and filter resources. Tagging also helps you track accountable resource owners for actions and notifications. When you use tagging, you can implement attribute-based access control (ABAC) as an authorization strategy, which defines permissions based on tags. You can attach tags to IAM entities (users or roles) and to AWS resources. You can create a single ABAC policy or a separate set of policies for your IAM principals. You can design these ABAC policies to allow operations when the principal's tag matches the resource tag. For more information, see What is ABAC for AWS? in the IAM User Guide.
Note
Don’t add personally identifiable information (PII) or other confidential or sensitive information in tags. Tags are accessible to many AWS services, including AWS Billing. For more tagging best practices, see Tagging your AWS resources in the AWS General Reference.
Remediation
To add tags to an AWS Backup backup plan
Open the AWS Backup console at https://console.aws.amazon.com/backup
. In the navigation pane, choose Backup vaults.
Select a backup vault from the list.
In the Backup vault tags section, choose Manage tags.
Choose Add new tag. Enter the key and value for the tag. Repeat for additional key-value pairs.
When you are finished adding tags, choose Save.
