Security Hub controls for AWS Glue

These AWS Security Hub controls evaluate the AWS Glue service and resources.

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

[Glue.1] AWS Glue jobs should be tagged

Category: Identify > Inventory > Tagging

Severity: Low

Resource type: AWS::Glue::Job

AWS Config rule:tagged-glue-job (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 Glue job has tags with the specific keys defined in the parameter requiredTagKeys. The control fails if the job 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 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 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 a AWS Glue job, see AWS tags in AWS Glue in the AWS Glue User Guide.

[Glue.2] AWS Glue jobs should have logging enabled

Category: Identify > Logging

Severity: Medium

Resource type: AWS::Glue::Job

AWS Config rule: glue-job-logging-enabled

Schedule type: Change triggered

Parameters: No

This control checks whether an AWS Glue job has logging enabled. The control fails if the job doesn't have logging enabled.

Audit logs track and monitor system activities. They provide a record of events that can help you detect security breaches, investigate incidents, and comply with regulations. Audit logs also enhance the overall accountability and transparency of your organization.

[Glue.3] AWS Glue machine learning transforms should be encrypted at rest

Category: Protect > Data Protection > Encryption of data-at-rest

Severity: Medium

Resource type: AWS::Glue::MLTransform

AWS Config rule: glue-ml-transform-encrypted-at-rest

Schedule type: Change triggered

Parameters: No

This control checks whether an AWS Glue machine learning transform is encrypted at rest. The control fails if the machine learning transform isn't encrypted at rest.

Data at rest refers to data that's stored in persistent, non-volatile storage for any duration. Encrypting data at rest helps you protect its confidentiality, which reduces the risk that an unauthorized user can access it.