cis-aws-compute-3.12
This skill audits Amazon ECS task definitions to verify they contain at least one user-defined tag for asset management and compliance tracking. Use it to identify ECS task definitions lacking proper tagging and to apply remediation through either AWS Console or CLI methods, ensuring organizational tagging standards are met across compute infrastructure.
git clone --depth 1 https://github.com/CyberStrikeus/CyberStrike /tmp/cis-aws-compute-3.12 && cp -r /tmp/cis-aws-compute-3.12/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_AWS_Compute_Services_Benchmark_v1.1.0/cis-aws-compute-3.12 ~/.claude/skills/cis-aws-compute-3.12SKILL.md
# Ensure Amazon ECS task definitions are tagged ## Description Ensure all Amazon ECS task definitions have resource tags to facilitate asset management, tracking, and compliance. Note: This recommendation assumes that only the latest active revision of a task definition is in use. If older revisions are in use, apply the audit and remediation procedures to those revisions as needed. ## Rationale Consistent tagging supports compliance and helps identify unauthorized or misconfigured resources. ## Impact There is minimal administrative overhead associated with implementing and maintaining resource tags. ## Audit Procedure ### Using AWS Console 1. Login to the ECS console using https://console.aws.amazon.com/ecs/. 2. In the left panel, click `Task definitions`. 3. Click the name of a task definition. 4. Click on the latest active revision of the task definition. 5. Click `Tags`. 6. Ensure at least one tag is listed that does not begin with `aws:`. Tags prefixed with `aws:` are AWS-managed. 7. Repeat steps 1-6 for each ECS task definition. ### Using AWS CLI Run the following command to list task definitions: ``` aws ecs list-task-definitions ``` For the latest revision, run the following command to view the tags: ``` aws ecs list-tags-for-resource --resource-arn <task-definition-arn> ``` Ensure that tags are returned that do not begin with `aws:`. Tags prefixed with `aws:` are AWS-managed. Repeat for each task definition. ## Expected Result All ECS task definitions should have at least one user-defined tag (not prefixed with `aws:`). ## Remediation ### Using AWS Console 1. Login to the ECS console using https://console.aws.amazon.com/ecs/. 2. In the left panel, click `Task definitions`. 3. Click the name of a task definition. 4. Click on the latest active revision of the task definition. 5. Click `Create new revision`. 6. Click `Create new revision` again. 7. Expand the `Tags` section. 8. Click `Add tag`. 9. Provide a `Key` and `Value` for the tag. 10. Click `Create`. 11. Repeat steps 1-10 for each task definition requiring remediation. Note: When a task definition is updated, running tasks launched from the previous task definition remain unchanged. Updating a running task requires redeploying it with the new task definition. ### Using AWS CLI Use the `aws ecs tag-resource` command to add tags to a task definition: ``` aws ecs tag-resource --resource-arn <task-definition-arn> --tags key=<TagKey>,value=<TagValue> ``` ## Default Value By default, Amazon ECS task definitions are not tagged. ## References 1. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html 2. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-task-definitions.html 3. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-tags-for-resource.html ## CIS Controls | Controls Version | Control | IG 1 | IG 2 | IG 3 | | ---------------- | -------------------------------------------------------------- | ---- | ---- | ---- | | v8 | 1.1 Establish and Maintain Detailed Enterprise Asset Inventory | x | x | x | | v7 | 1.4 Maintain Detailed Asset Inventory | x | x | x | ## Profile Level 1 | Automated
Ensure Managed Platform updates is configured
Ensure Persistent logs is setup and configured to S3
Ensure access logs are enabled
Ensure that HTTPS is enabled on load balancer
Ensure customer-managed keys are used to encrypt AWS Fargate ephemeral storage data for Amazon ECS
Ensure AWS Config is Enabled for Lambda and Serverless
Ensure Lambda functions do not allow unknown cross account access via permission policies
Ensure that the runtime environment versions used for your Lambda functions do not have end of support dates