AWS securityagent documentation change
Summary
Added a note about ensuring GitHub accessibility via private VPC for penetration tests with GitHub repositories, recommending VPC NAT Gateway configuration or specific outbound rules for GitHub IPs
Security assessment
This change adds configuration guidance for network connectivity in penetration testing scenarios. It documents network requirements for security testing tools but doesn't address a specific security vulnerability or incident. The guidance helps ensure proper network configuration for security testing workflows.
Diff
diff --git a/securityagent/latest/userguide/perform-penetration-test.md b/securityagent/latest/userguide/perform-penetration-test.md index 7f6fd4170..aa2aceee6 100644 --- a//securityagent/latest/userguide/perform-penetration-test.md +++ b//securityagent/latest/userguide/perform-penetration-test.md @@ -368,0 +369,4 @@ Resources selected from available sources remain synchronized with their origina +###### Note + +If you have a private VPC associated with your pentest and a GitHub repository configured, ensure that GitHub is accessible via your private VPC for pulling GitHub resources. In most cases, you will need to either ensure that outbound traffic via [VPC NAT Gateway](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html) is allowed by default or configure specific rules to allow outbound traffic for GitHub IPs (see [GitHub Meta API Endpoint](https://api.github.com/meta)) +