用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-euc-5-1命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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 职业分类
正在显示 SKILL.md
| name | cis-aws-euc-5.1 |
| description | Ensure AppStream is utilizing its own virtual private cloud (VPC) |
| category | cis-end-user-compute |
| version | 1.2.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","end-user-compute","appstream","vpc","network-isolation"] |
| cis_id | 5.1 |
| cis_benchmark | CIS AWS End User Compute Services Benchmark v1.2.0 |
| tech_stack | ["aws"] |
| cwe_ids | ["CWE-668"] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
AppStream 2.0 should be configured using a VPC with Private subnets and a NAT Gateway.
For AppStream 2.0 the public subnet will have direct access to the internet through the NAT gateway. This setup allows the streaming instances in your private subnets to connect to the internet or other AWS services.
None - this is a security best practice.
Perform the following to determine if a VPC is setup for AppStream 2.0 correctly.
Login to the VPC console at https://console.aws.amazon.com/vpc/
In the left pane, click Your VPCs
Select the VPC for AppStream 2.0 and take note of the name and the VPC ID
In the left pane, click Subnets
Confirm you have 3 subnets labeled and associated with the VPC:
Confirm the AppStream Public Subnet is configured correctly:
AppStream ID and nameExample - Destination - 10.0.0.0/20, Target - localExample - Destination - 0.0.0.0/0, Target - internet_gateway_IDConfirm the 2 AppStream Private Subnets are configured correctly:
AppStream ID and name and note Availability zoneExample - Destination - 10.0.0.0/20, Target - localExample - Destination - 0.0.0.0/0, Target - nat_gateway_IDExample- optional - Destination - S3bucket_enpoint_ID, Target - storage_vpce_IDAppStream ID and name and Availability zone is set to something different than Private subnet 1Example - Destination - 10.0.0.0/20, Target - localExample - Destination - 0.0.0.0/0, Target - nat_gateway_IDExample- optional - Destination - S3bucket_enpoint_ID, Target - storage_vpce_IDIf The AppStream VPC, subnets and route tables are not configured correctly refer to the remediation procedure below.
Not applicable - must be audited via Console.
AppStream has a dedicated VPC with 1 public subnet and 2 private subnets with proper route tables configured.
Perform the steps below to create a VPC, subnets and routing table for AppStream 2.0.
Allocate an Elastic IP address:
https://console.aws.amazon.com/vpc/Create a New VPC with one public subnet and two private subnets:
Login to the VPC console at https://console.aws.amazon.com/vpc/
Click Launch VPC Wizard
Choose VPC with Public and Private Subnet's and then click Select
Configure the VPC as follows:
IPv4 CIDR block - enter a CIDR block from the private (non-publicly routable) IP address range i.e. 10.0.0.0/16IPv6 CIDR block - Accept the default value - No IPv6 CIDR BlockVPC name enter a name for the VPC (example, AppStream VPC)Public subnet's IPv4 CIDR - enter a CIDR block from the private (non-publicly routable) IP address range i.e. 10.0.0.0/24Availability Zone - Accept the default value - No PreferencePublic subnet name - enter a name for the subnet (example, AppStream Public Subnet)Private subnet's IPv4 CIDR - enter the CIDR block for the subnetAvailability Zone - Accept the default value - No PreferencePrivate subnet name - enter a name for the subnet (example, AppStream Private Subnet 1)Elastic IP Allocation ID - enter the Elastic IP address that you createdService Endpoints - Accept the default value - BlankEnable DNS hostnames - Accept the default value - YesHardware tenancy - Accept the default value - DefaultClick on Create VPC
Note: It takes several minutes to set up your VPC. After the VPC is created, choose OK.
Create the Second Private subnet to the VPC:
In the left pane, choose Subnets
Click Create subnet
Name tag - enter a name for the private subnet (example, AppStream Private subnet 2)
VPC - select the VPC that you created for AppStream 2.0Availability Zone - select a different one than you are using for AppStream2 Private subnet 1IPv4 CIDR block - enter the CIDR block for the subnetClick Create
Verify and Name the Route Tables:
Not applicable - must be configured via Console.
By default, there is no VPC tied to the Appstream 2.0 service.
v8:
v7:
Level 1