Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon IoT controls

These controls are related to Amazon IoT resources.

These controls may not be available in all Amazon Web Services Regions. For more information, see Availability of controls by Region.

[IoT.1] Amazon IoT Core security profiles should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::IoT::SecurityProfile

Amazon Config rule: tagged-iot-securityprofile (custom Security Hub rule)

Schedule type: Change triggered

Parameters:

This control checks whether an Amazon IoT Core security profile has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the security profile 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 security 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 What is ABAC for Amazon? in the IAM User Guide.

Remediation

To add tags to an Amazon IoT Core security profile, see Tagging your Amazon IoT resources in the Amazon IoT Developer Guide.

[IoT.2] Amazon IoT Core mitigation actions should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::IoT::MitigationAction

Amazon Config rule: tagged-iot-mitigationaction (custom Security Hub rule)

Schedule type: Change triggered

Parameters:

This control checks whether an Amazon IoT Core mitigation action has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the mitigation action 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 mitigation action 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 What is ABAC for Amazon? in the IAM User Guide.

Remediation

To add tags to an Amazon IoT Core mitigation action, see Tagging your Amazon IoT resources in the Amazon IoT Developer Guide.

[IoT.3] Amazon IoT Core dimensions should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::IoT::Dimension

Amazon Config rule: tagged-iot-dimension (custom Security Hub rule)

Schedule type: Change triggered

Parameters:

This control checks whether an Amazon IoT Core dimension has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the dimension 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 dimension 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 What is ABAC for Amazon? in the IAM User Guide.

Remediation

To add tags to an Amazon IoT Core dimension, see Tagging your Amazon IoT resources in the Amazon IoT Developer Guide.

[IoT.4] Amazon IoT Core authorizers should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::IoT::Authorizer

Amazon Config rule: tagged-iot-authorizer (custom Security Hub rule)

Schedule type: Change triggered

Parameters:

This control checks whether an Amazon IoT Core authorizer has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the authorizer 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 authorizer 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 What is ABAC for Amazon? in the IAM User Guide.

Remediation

To add tags to an Amazon IoT Core authorizer, see Tagging your Amazon IoT resources in the Amazon IoT Developer Guide.

[IoT.5] Amazon IoT Core role aliases should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::IoT::RoleAlias

Amazon Config rule: tagged-iot-rolealias (custom Security Hub rule)

Schedule type: Change triggered

Parameters:

This control checks whether an Amazon IoT Core role alias has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the role alias 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 role alias 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 What is ABAC for Amazon? in the IAM User Guide.

Remediation

To add tags to an Amazon IoT Core role alias, see Tagging your Amazon IoT resources in the Amazon IoT Developer Guide.

[IoT.6] Amazon IoT Core policies should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::IoT::Policy

Amazon Config rule: tagged-iot-policy (custom Security Hub rule)

Schedule type: Change triggered

Parameters:

This control checks whether an Amazon IoT Core policy has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the policy 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 policy 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 What is ABAC for Amazon? in the IAM User Guide.

Remediation

To add tags to an Amazon IoT Core policy, see Tagging your Amazon IoT resources in the Amazon IoT Developer Guide.