OpenParable
Skip to content
← Back to skills

Cis AWS Compute 8.2

DevOps & Security
cis-aws-compute-8.2

Cis AWS Compute 8.2 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure Batch roles are configured for cross-service confused deputy prevention

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_AWS_Compute_Services_Benchmark_v1.1.0/cis-aws-compute-8.2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aws-compute-8-2, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

8.2 Ensure Batch roles are configured for cross-service confused deputy prevention (Manual)

Description

The Cross-service confused deputy problem is a security issue where an entity that doesn't have permission to perform an action can coerce a more-privileged entity to perform the action.

Rationale

Cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the calling service) calls another service (the called service). The calling service can be manipulated to use its permissions to act on another customer's resources in a way it should not otherwise have permission to access.

Impact

An IAM role is an identity you can create that has specific permissions with credentials that are valid for short durations. Roles can be assumed by entities that you trust. IAM Roles are often organization named and organization based. Searching for and reviewing the roles for this recommendation is a manual process.

Audit Procedure

Using AWS Console

  1. Login to the AWS Console using https://console.aws.amazon.com/iam/
  2. On the left hand side under Access management, Click on Roles
  3. Search for any roles related to Batch
  4. Click on the role and the Assume Role Policy Document and confirm that the AssumeRole Action has a aws:SourceArn key that contains the full ARN of the Batch resource

Example of a compliant policy with aws:SourceArn condition:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "batch.amazonaws.com"
      },
      "Action": "sts:AssumeRole",
      "Condition": {
        "ArnLike": {
          "aws:SourceArn": ["arn:aws:batch:us-east-1:123456789012:compute-environment/testCE"]
        }
      }
    }
  ]
}
  1. If it is showing an * within the ARN or does not have this condition key specified, then the Batch process has access to all of the resources defined in that environment.

Example of a non-compliant policy (missing aws:SourceArn condition):

"arn:aws:batch:us-east-1:123456789012:compute-environment/*",
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "batch.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}
  1. Repeat for any roles assigned to Batch that have AssumeRole
  2. Refer to the remediation below

Using AWS CLI

N/A - This control is manual and console-based.

Expected Result

All IAM roles associated with AWS Batch have an aws:SourceArn condition key in the AssumeRole policy document that contains the full ARN of the specific Batch resource (not a wildcard *).

Remediation

Using AWS Console

  1. Login to the AWS Console using https://console.aws.amazon.com/iam/
  2. On the left hand side under Access management, Click on Roles
  3. Search for any roles identified above in the audit.
  4. Click on the role and update the Action AssumeRole, aws:SourceArn to contain the full ARN of the resource
"aws:SourceArn": [
            "arn:aws:batch:us-east-1:123456789012:compute-environment/testCE",
  1. Repeat for any roles defined in the Audit.

Using AWS CLI

N/A - This control is manual and console-based.

Additional Information

Note: Usage of the aws:SourceAccount condition key can be used to prevent cross service confused deputy impersonation from external accounts. This condition key is not as specific as using aws:SourceArn which can be used to limit access of the IAM Role for specific resources or a group of specific resources.

Example using aws:SourceAccount:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "batch.amazonaws.com"
      },
      "Action": "sts:AssumeRole",
      "Condition": {
        "StringEquals": {
          "aws:SourceAccount": "123456789012"
        }
      }
    }
  ]
}

Default Value

By default, IAM roles for Batch do not include the aws:SourceArn condition key.

References

  1. https://docs.aws.amazon.com/batch/latest/userguide/cross-service-confused-deputy-prevention.html

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v86.8 Define and Maintain Role-Based Access ControlX

Profile

Level 1 | Manual