Skip to content

Commit db126a3

Browse files
Merge pull request #220423 from tspivakms/patch-17
Update defender-for-containers-vulnerability-assessment-elastic.md
2 parents 3c605f9 + 3fd3f16 commit db126a3

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

articles/defender-for-cloud/defender-for-containers-vulnerability-assessment-elastic.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,21 @@ Defender for Containers lets you scan the container images stored in your Amazon
1414

1515
To enable scanning of vulnerabilities in containers, you have to [connect your AWS account to Defender for Cloud](quickstart-onboard-aws.md) and [enable Defender for Containers](defender-for-containers-enable.md). The agentless scanner, powered by the open-source scanner Trivy, scans your ECR repositories and reports vulnerabilities.
1616

17-
Defender for Containers creates resources in your AWS account to build an inventory of the software in your images. The scan then sends only the software inventory to Defender for Cloud. This architecture protects your information privacy and intellectual property, and also keeps the outbound network traffic to a minimum. Defender for Containers creates an ECS cluster in a dedicated VPC, an internet gateway, and an S3 bucket in the us-east-1 and eu-central-1 regions to build the software inventory.
17+
Defender for Containers creates resources in your AWS account to build an inventory of the software in your images. The scan then sends only the software inventory to Defender for Cloud. This architecture protects your information privacy and intellectual property, and also keeps the outbound network traffic to a minimum.
18+
19+
These resources are created under us-east-1 and eu-central-1 in each AWS account where container vulnerability assesment is enabled:
20+
21+
- **S3 bucket** with the prefix `defender-for-containers-va`
22+
- **ECS cluster** with the name `defender-for-containers-va`
23+
- **VPC**
24+
- Tag `name` with the value `defender-for-containers-va`
25+
- IP subnet CIDR 10.0.0.0/16
26+
- Associated with **default security group** with the tag `name` and the value `defender-for-containers-va` that has one rule of all incoming traffic.
27+
- **Subnet** with the tag `name` and the value `defender-for-containers-va` in the `defender-for-containers-va` VPC with the CIDR 10.0.1.0/24 IP subnet used by the ECS cluster `defender-for-containers-va`
28+
- **Internet Gateway** with the tag `name` and the value `defender-for-containers-va`
29+
- **Route table** - Route table with the tag `name` and value `defender-for-containers-va`, and with these routes:
30+
- Destination: `0.0.0.0/0`; Target: Internet Gateway with the tag `name` and the value `defender-for-containers-va`
31+
- Destination: `10.0.0.0/16`; Target: `local`
1832

1933
Defender for Cloud filters and classifies findings from the software inventory that the scanner creates. Images without vulnerabilities are marked as healthy and Defender for Cloud doesn't send notifications about healthy images to keep you from getting unwanted informational alerts.
2034

0 commit comments

Comments
 (0)