Security Hub controls for Amazon Connect
These Security Hub controls evaluate the Amazon Connect service and resources.
These controls may not be available in all AWS Regions. For more information, see Availability of controls by Region.
[Connect.1] Amazon Connect Customer Profiles object types should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::CustomerProfiles::ObjectType
AWS Config rule:
customerprofiles-object-type-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 AWS requirements. | No default value |
This control checks whether an Amazon Connect Customer Profiles object type has tags
with the specific keys defined in the parameter requiredKeyTags.
The control fails if the object type 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 object type 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 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 AWS services, including AWS Billing. For more tagging best practices, see Best practices and strategies in the Tagging AWS Resources and Tag Editor User Guide.
Remediation
To add tags to a Customer Profiles object type, see Add tags to resources in Amazon Connect in the Amazon Connect Administrator Guide.
[Connect.2] Amazon Connect instances should have CloudWatch logging enabled
Category: Identify > Logging
Severity: Medium
Resource type:
AWS::Connect::Instance
AWS Config rule: connect-instance-logging-enabled
Schedule type: Change triggered
Parameters: None
This control checks whether an Amazon Connect instance is configured to generate and store flow logs in an Amazon CloudWatch log group. The control fails if the Amazon Connect instance isn't configured to generate and store flow logs in a CloudWatch log group.
Amazon Connect flow logs provide real-time details about events in Amazon Connect flows. A flow defines the customer experience with an Amazon Connect contact center from start to finish. By default, when you create a new Amazon Connect instance, an Amazon CloudWatch log group is created automatically to store flow logs for the instance. Flow logs can help you analyze flows, find errors, and monitor operational metrics. You can also set up alerts for specific events that can occur in a flow.
Remediation
For information about enabling flow logs for an Amazon Connect instance, see Enable Amazon Connect flow logs in an Amazon CloudWatch log group in the Amazon Connect Administrator Guide.
