Ensure WorkSpaces are deployed in their own virtual private cloud (VPC) (Manual)
Profile Applicability
Description
Amazon WorkSpaces VPC should be created with two private subnets for your WorkSpaces and a NAT gateway in a public subnet.
Rationale
The NAT gateway will provide WorkSpaces access to the internet for updates to the operating system and so that applications can be deployed using Amazon WorkSpaces Application Manager if that is applicable for your environment.
Impact
Your VPC's subnets must be in different Availability Zones in the Region where you're launching WorkSpaces.
Audit Procedure
Using AWS Console
Perform the following steps to confirm that a VPC exists for WorkSpaces and is configured correctly:
- Login to the VPC console at https://console.aws.amazon.com/vpc/
- In the left pane, click Your VPC's
- Select the VPC for WorkSpaces
- Confirm the IPv4 settings are using a CIDR block from the private (non-publicly routable) IP address ranges. For example, 10.0.0.0/16. For more information, see the references below
- Confirm the IPv6 CIDR Block, set to No
- Confirm the IPv4 CIDR block for the public subnet (example - WorkSpaces Public Subnet)
- Availability Zone, set to No Preference
- Confirm the IPv4 CIDR block for the first private subnet (example - WorkSpaces Private Subnet 1)
- Availability Zone, set for Amazon WorkSpaces
- Elastic IP Allocation ID
- Service endpoints -
Blank
- Enable DNS hostnames, set to
Yes
- Hardware tenancy, Default
- Confirm the IPv4 CIDR block for the first private subnet (example - WorkSpaces Private Subnet 2)
- Availability Zone set for Amazon WorkSpaces
- NOTE: Make sure you select a different Availability zone from the one you selected for the Workspaces Private Subnet 1
- Elastic IP Allocation ID
- Service endpoints - Blank
- Enable DNS hostnames, set to
Yes
- Hardware tenancy, Default
If this is not set as referenced above refer to the remediation procedure below.
Remediation
Using AWS Console
Allocate an Elastic IP Address
- Login in to the VPC console at https://console.aws.amazon.com/vpc/
- In the left pane, click Elastic IPs
- Click Allocate new address
- On the Allocate new address page, for IPv4 address pool, click Amazon pool or Owned by me
- Click Allocate
- Make a note of the Elastic IP address, click Close
Create a VPC with one public subnet and two private subnets as follows:
Login in to the VPC console at https://console.aws.amazon.com/vpc/
In the left pane, click VPC Dashboard in the upper-left corner
Click Launch VPC Wizard
Click VPC with Public and Private Subnets
Click Select
Configure the VPC as follows:
- For IPv4 CIDR block, enter the CIDR block from the private (non-publicly routable) IP address ranges. For example 10.0.0.0/16
- For IPv6 CIDR block, keep
No IPv6 CIDR Block
- For VPC name, enter a
name for the VPC (example: WorkspacesVPC)
- For Public subnet's IPv4 CIDR - enter a CIDR block from the private (non-publicly routable) IP address ranges. For example - 10.0.0.0/24
- For Availability Zone, keep
No Preference
- For Public subnet name, enter a
name for the subnet (example: WorkSpaces Public Subnet)
- For Private subnet's IPv4 CIDR, enter the CIDR block for the subnet
Availability Zone - Accept the default value = No Preference- For Private subnet name, enter a
name for the subnet (example: WorkSpaces Private Subnet 1)
- For Elastic IP Allocation ID, enter the Elastic IP address that you created
- For Service endpoints,
do nothing
- For Enable DNS hostnames, keep
Yes
- For Hardware tenancy, keep
Default
Click Create VPC. Note that it takes several minutes to set up your VPC. After the VPC is created
Click OK
Create a Second Private Subnet
- In the left pane, click Subnets
- Click Create Subnet
- For Name tag, enter a
name for the private subnet (example: WorkSpaces Private Subnet 2)
- For VPC,
select the VPC that you created
- For Availability Zone. Make sure you select a different Availability Zone from the one you used in WorkSpaces Private Subnet 1
- For IPv4 CIDR block, enter the CIDR block for the subnet
- Click Create
Verify and Name the Route Tables for Public
- In the left pane, click Subnets
- Click the public subnet that you created. (example: WorkSpaces Public Subnet)
- On the Route Table tab, choose the ID of the route table (example: rtb-12345678)
- Click the route table
- Under Name, choose the edit icon, enter a name (example: workspaces-public-routetable)
- Click the check mark to save the name
Verify and Name the Route Tables for Private
- In the left pane, click Subnets
- Click the private subnet 1 that you created. (example: WorkSpaces Private Subnet 1)
- On the Route Table tab, choose the ID of the route table (example: rtb-12345678)
- Click the route table
- Under Name, choose the edit icon, enter a name (example: workspaces-private-routetable)
- Click the check mark to save the name
- On the Routes tab, verify that there is one route for local traffic and another route that sends all other traffic to the internet gateway for the VPC
- Repeat steps 1-7 under Verify and Name the Route Tables for Private
for WorkSpaces Private Subnet 2'
Default Value
By default, AWS Workspaces does not create its own VPC. A VPC must be created to run an AWS Workspace environment.
References
- https://docs.aws.amazon.com/workspaces/latest/adminguide/amazon-workspaces-vpc.html
- https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html#vpc-sizing-ipv4
- https://docs.aws.amazon.com/workspaces/latest/adminguide/azs-workspaces.html
CIS Controls
v8:
- 3.12 Segment Data Processing and Storage Based on Sensitivity
- Segment data processing and storage based on the sensitivity of the data. Do not process sensitive data on enterprise assets intended for lower sensitivity data.
v7:
- 14.1 Segment the Network Based on Sensitivity
- Segment the network based on the label or classification level of the information stored on the servers, locate all sensitive information on separated Virtual Local Area Networks (VLANs).
1---2name: cis-aws-euc-2-43description: Ensure WorkSpaces are deployed in their own virtual private cloud (VPC)4---56# Ensure WorkSpaces are deployed in their own virtual private cloud (VPC) (Manual)78## Profile Applicability910- Level 11112## Description1314Amazon WorkSpaces VPC should be created with two private subnets for your WorkSpaces and a NAT gateway in a public subnet.1516## Rationale1718The NAT gateway will provide WorkSpaces access to the internet for updates to the operating system and so that applications can be deployed using Amazon WorkSpaces Application Manager if that is applicable for your environment.1920## Impact2122Your VPC's subnets must be in different Availability Zones in the Region where you're launching WorkSpaces.2324## Audit Procedure2526### Using AWS Console2728Perform the following steps to confirm that a VPC exists for WorkSpaces and is configured correctly:29301. Login to the VPC console at https://console.aws.amazon.com/vpc/312. In the left pane, click **Your VPC's**323. Select the VPC for WorkSpaces334. Confirm the IPv4 settings are using a CIDR block from the private (non-publicly routable) IP address ranges. For example, 10.0.0.0/16. For more information, see the references below345. Confirm the IPv6 CIDR Block, set to **No**356. Confirm the IPv4 CIDR block for the public subnet (example - WorkSpaces Public Subnet)36 - Availability Zone, set to **No Preference**377. Confirm the IPv4 CIDR block for the first private subnet (example - WorkSpaces Private Subnet 1)38 - Availability Zone, set for Amazon WorkSpaces39 - Elastic IP Allocation ID40 - Service endpoints - `Blank`41 - Enable DNS hostnames, set to `Yes`42 - Hardware tenancy, Default438. Confirm the IPv4 CIDR block for the first private subnet (example - WorkSpaces Private Subnet 2)44 - Availability Zone set for Amazon WorkSpaces45 - NOTE: Make sure you select a different Availability zone from the one you selected for the Workspaces Private Subnet 146 - Elastic IP Allocation ID47 - Service endpoints - Blank48 - Enable DNS hostnames, set to `Yes`49 - Hardware tenancy, Default5051If this is not set as referenced above refer to the remediation procedure below.5253## Remediation5455### Using AWS Console5657**Allocate an Elastic IP Address**58591. Login in to the VPC console at https://console.aws.amazon.com/vpc/602. In the left pane, click **Elastic IPs**613. Click **Allocate new address**624. On the Allocate new address page, for IPv4 address pool, click **Amazon pool or Owned by me**635. Click **Allocate**646. Make a note of the Elastic IP address, click **Close**6566**Create a VPC with one public subnet and two private subnets as follows:**67681. Login in to the VPC console at https://console.aws.amazon.com/vpc/692. In the left pane, click **VPC Dashboard** in the upper-left corner703. Click **Launch VPC Wizard**714. Click **VPC with Public and Private Subnets**725. Click **Select**736. Configure the VPC as follows:74 - For IPv4 CIDR block, enter the CIDR block from the private (non-publicly routable) IP address ranges. For example 10.0.0.0/1675 - For IPv6 CIDR block, keep `No IPv6 CIDR Block`76 - For VPC name, enter a `name for the VPC` (example: WorkspacesVPC)77 - For Public subnet's IPv4 CIDR - enter a CIDR block from the private (non-publicly routable) IP address ranges. For example - 10.0.0.0/2478 - For Availability Zone, keep `No Preference`79 - For Public subnet name, enter a `name for the subnet` (example: WorkSpaces Public Subnet)80 - For Private subnet's IPv4 CIDR, enter the CIDR block for the subnet81 - `Availability Zone` - Accept the default value = `No Preference`82 - For Private subnet name, enter a `name for the subnet` (example: WorkSpaces Private Subnet 1)83 - For Elastic IP Allocation ID, enter the Elastic IP address that you created84 - For Service endpoints, `do nothing`85 - For Enable DNS hostnames, keep `Yes`86 - For Hardware tenancy, keep `Default`87887. Click Create VPC. Note that it takes several minutes to set up your VPC. After the VPC is created898. Click **OK**9091**Create a Second Private Subnet**92931. In the left pane, click **Subnets**942. Click **Create Subnet**95 - For Name tag, enter a `name for the private subnet` (example: WorkSpaces Private Subnet 2)96 - For VPC, `select the VPC` that you created97 - For Availability Zone. Make sure you select a different Availability Zone from the one you used in WorkSpaces Private Subnet 198 - For IPv4 CIDR block, enter the CIDR block for the subnet993. Click **Create**100101**Verify and Name the Route Tables for Public**1021031. In the left pane, click **Subnets**1042. Click the **public** subnet that you created. (example: WorkSpaces Public Subnet)1053. On the Route Table tab, choose the ID of the route table (example: rtb-12345678)1064. Click the route table1075. Under Name, choose the edit icon, **enter a name** (example: workspaces-public-routetable)1086. Click the check mark to save the name109110**Verify and Name the Route Tables for Private**1111121. In the left pane, click **Subnets**1132. Click the **private subnet 1** that you created. (example: WorkSpaces Private Subnet 1)1143. On the Route Table tab, choose the ID of the route table (example: rtb-12345678)1154. Click the route table1165. Under Name, choose the edit icon, **enter a name** (example: workspaces-private-routetable)1176. Click the check mark to save the name1187. On the Routes tab, verify that there is one route for local traffic and another route that sends all other traffic to the internet gateway for the VPC1198. Repeat steps 1-7 under **Verify and Name the Route Tables for Private** `for` WorkSpaces Private Subnet 2'120121## Default Value122123By default, AWS Workspaces does not create its own VPC. A VPC must be created to run an AWS Workspace environment.124125## References1261271. https://docs.aws.amazon.com/workspaces/latest/adminguide/amazon-workspaces-vpc.html1282. https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html#vpc-sizing-ipv41293. https://docs.aws.amazon.com/workspaces/latest/adminguide/azs-workspaces.html130131## CIS Controls132133**v8:**134135- 3.12 Segment Data Processing and Storage Based on Sensitivity136 - Segment data processing and storage based on the sensitivity of the data. Do not process sensitive data on enterprise assets intended for lower sensitivity data.137138**v7:**139140- 14.1 Segment the Network Based on Sensitivity141 - Segment the network based on the label or classification level of the information stored on the servers, locate all sensitive information on separated Virtual Local Area Networks (VLANs).
cyberstrikeus