用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-compute-8-2命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
基于 SOC 职业分类
| name | cis-aws-compute-8.2 |
| description | Ensure Batch roles are configured for cross-service confused deputy prevention |
| category | cis-compute |
| version | 1.1.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","compute","batch","iam","confused-deputy","cross-service","access-control"] |
| cis_id | 8.2 |
| cis_benchmark | CIS AWS Compute Services Benchmark v1.1.0 |
| tech_stack | ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-compute-8.1"] |
| prerequisites | [] |
| severity_boost | {} |
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.
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.
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.
RolesBatchaws:SourceArn key that contains the full ARN of the Batch resourceExample of a compliant policy with aws:SourceArn condition:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "batch.amazonaws.com"
},
"Action":
* 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"
}
]
}
N/A - This control is manual and console-based.
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 *).
Rolesaws:SourceArn to contain the full ARN of the resource"aws:SourceArn": [
"arn:aws:batch:us-east-1:123456789012:compute-environment/testCE",
N/A - This control is manual and console-based.
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"
}
}
}
]
}
By default, IAM roles for Batch do not include the aws:SourceArn condition key.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 6.8 Define and Maintain Role-Based Access Control | X |
Level 1 | Manual