Security Hub controls for Amazon IoT TwinMaker
These Amazon Security Hub controls evaluate the Amazon IoT TwinMaker service and resources.
These controls may not be available in all Amazon Web Services Regions. For more information, see Availability of controls by Region.
[IoTTwinMaker.1] Amazon IoT TwinMaker sync jobs should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::IoTTwinMaker::SyncJob
Amazon Config rule: iottwinmaker-sync-job-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 IoT TwinMaker sync job has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the sync job 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 sync job 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 IoT TwinMaker sync job, see TagResource in the Amazon IoT TwinMaker User Guide.
[IoTTwinMaker.2] Amazon IoT TwinMaker workspaces should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::IoTTwinMaker::Workspace
Amazon Config rule: iottwinmaker-workspace-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 IoT TwinMaker workspace has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the workspace 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 workspace 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 IoT TwinMaker workspace, see TagResource in the Amazon IoT TwinMaker User Guide.
[IoTTwinMaker.3] Amazon IoT TwinMaker scenes should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::IoTTwinMaker::Scene
Amazon Config rule: iottwinmaker-scene-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 IoT TwinMaker scene has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the scene 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 scene 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 IoT TwinMaker scene, see TagResource in the Amazon IoT TwinMaker User Guide.
[IoTTwinMaker.4] Amazon IoT TwinMaker entities should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::IoTTwinMaker::Entity
Amazon Config rule: iottwinmaker-entity-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 IoT TwinMaker entity has tags with the specific keys defined in the parameter
requiredKeyTags. The control fails if the entity 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 entity 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 IoT TwinMaker entity, see TagResource in the Amazon IoT TwinMaker User Guide.