Security Hub controls for Amazon AppConfig
These Security Hub controls evaluate the Amazon AppConfig service and resources.
These controls may not be available in all Amazon Web Services Regions. For more information, see Availability of controls by Region.
[AppConfig.1] Amazon AppConfig applications should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::AppConfig::Application
Amazon Config rule: appconfig-application-tagged
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredKeyTags
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList (maximum of 6 items) | 1–6 tag keys that meet Amazon requirements. | No default value |
This control checks whether an Amazon AppConfig application has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the application doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredKeyTags. If the parameter requiredKeyTags isn't provided, the control only checks for the existence
of a tag key and fails if the application 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 Amazon 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 Amazon 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 Define permissions based on attributes with ABAC authorization 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 Amazon Web Services services, including Amazon Billing. For more tagging best practices, see Best practices and strategies in the Tagging Amazon Resources and Tag Editor User Guide.
Remediation
To add tags to an Amazon AppConfig application, see TagResource in the Amazon AppConfig API Reference.
[AppConfig.2] Amazon AppConfig configuration profiles should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::AppConfig::ConfigurationProfile
Amazon Config rule: appconfig-configuration-profile-tagged
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredKeyTags
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList (maximum of 6 items) | 1–6 tag keys that meet Amazon requirements. | No default value |
This control checks whether an Amazon AppConfig configuration profile has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the configuration profile doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredKeyTags. If the parameter requiredKeyTags isn't provided, the control only checks for the existence
of a tag key and fails if the configuration profile 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 Amazon 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 Amazon 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 Define permissions based on attributes with ABAC authorization 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 Amazon Web Services services, including Amazon Billing. For more tagging best practices, see Best practices and strategies in the Tagging Amazon Resources and Tag Editor User Guide.
Remediation
To add tags to an Amazon AppConfig configuration profile, see TagResource in the Amazon AppConfig API Reference.
[AppConfig.3] Amazon AppConfig environments should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::AppConfig::Environment
Amazon Config rule: appconfig-environment-tagged
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredKeyTags
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList (maximum of 6 items) | 1–6 tag keys that meet Amazon requirements. | No default value |
This control checks whether an Amazon AppConfig environment has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the environment doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredKeyTags. If the parameter requiredKeyTags isn't provided, the control only checks for the existence
of a tag key and fails if the environment 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 Amazon 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 Amazon 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 Define permissions based on attributes with ABAC authorization 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 Amazon Web Services services, including Amazon Billing. For more tagging best practices, see Best practices and strategies in the Tagging Amazon Resources and Tag Editor User Guide.
Remediation
To add tags to an Amazon AppConfig environment, see TagResource in the Amazon AppConfig API Reference.
[AppConfig.4] Amazon AppConfig extension associations should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::AppConfig::ExtensionAssociation
Amazon Config rule: appconfig-extension-association-tagged
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredKeyTags
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList (maximum of 6 items) | 1–6 tag keys that meet Amazon requirements. | No default value |
This control checks whether an Amazon AppConfig extension association has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the extension association doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredKeyTags. If the parameter requiredKeyTags isn't provided, the control only checks for the existence
of a tag key and fails if the extension association 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 Amazon 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 Amazon 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 Define permissions based on attributes with ABAC authorization 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 Amazon Web Services services, including Amazon Billing. For more tagging best practices, see Best practices and strategies in the Tagging Amazon Resources and Tag Editor User Guide.
Remediation
To add tags to an Amazon AppConfig extension association, see TagResource in the Amazon AppConfig API Reference.