Best Penetration Testing Companies

Practical guide · November 16, 2026

What permissions and exclusions belong in an AWS pentest brief?

Document the customer-owned resources, AWS services, proposed activities and authorization boundaries separately. AWS allows testing without prior approval for listed permitted services under its policy, but that does not authorize every technique, every service or testing of AWS itself.

The current policy also requires prior approval for testing involving command-and-control activity and lists prohibited activities and separate procedures for certain simulations. Check the live policy against the actual engagement before work begins. AWS penetration-testing policy

Review resources and activities as separate decisions

Hypothetical example: A company proposes testing its application on EC2 and an API served through API Gateway. The brief includes:

Brief field Illustrative content
Resource ownership Customer account and resource owner documented privately
Targets Exact customer endpoints and environment identifiers
Services EC2 and API Gateway, checked against current AWS policy
Activities Agreed application and authorization testing
Exclusions The AWS service infrastructure itself, as distinct from the customer’s application/resources on a permitted service; unapproved third-party targets
Operational limits Approved window, agreed traffic limits and stop contacts
Special approvals Separate review of any proposed simulation or C2 activity

This table is a preparation aid, not an authorization document. Listing a permitted service does not make an otherwise prohibited activity acceptable.

Do not confuse target services with tooling services

AWS's policy distinguishes permitted target services from restrictions on services used for outbound penetration testing. Read the relevant sections for both the target and any AWS-hosted tooling. A brief that says only “all resources in our account” leaves that distinction unresolved. AWS service and activity restrictions

Policy distinction checked November 16, 2026: AWS lists Amazon API Gateway among permitted target services, but lists it among services prohibited for outbound penetration-testing tooling. Testing an authorized customer API hosted there is a different policy question from using API Gateway to originate testing traffic. EC2 is a permitted target service and can host testing tools subject to the policy’s activity restrictions. This does not authorize probing AWS’s underlying service infrastructure. AWS target and tooling policy

Record the policy review date and any required approval reference in the private brief. Recheck after scope changes, especially when a new service or activity is introduced. Do not interpret a missing service as approved merely because it resembles a listed one.

Separate customer authorization from platform policy

Have the appropriate owner authorize the testing team to assess the specified resources. Identify dependencies such as external identity providers, payment processors or partner systems and exclude them unless the necessary permission exists.

For the fictional API, a request that reaches a third-party integration may cross the customer's control boundary. Agree how that path will be handled before testing rather than discovering the issue during the engagement.

Prepare the interruption and cleanup plan

Give the team a reachable operational contact and identify who can stop testing. Agree how test accounts, temporary access, generated records and test infrastructure will be handled afterward. Record what evidence the provider will retain and where sensitive results will be delivered.

The final report should identify tested resources and exclusions precisely enough to reconcile with the signed scope. If an activity was withheld because approval was missing, keep that limitation visible; do not relabel it as completed coverage.

Before the kickoff, review the target list, technique list and authorization record together. That comparison is more useful than a general statement that “AWS permits pentesting.”

Evidence reviewed November 16, 2026. Based on AWS's published policy, which can change. The example is fictional and does not authorize or execute testing.