Aevora

Azure Penetration Test

Scoping - First Phase

The first phase of scoping focuses on gathering enough detail to propose a timeline and quote. It also captures general information about your environment and engagement to support further communication. The second phase covers more specific technical details, such as target lists, test credentials, and other environment-specific requirements. Once both phases are complete, we review all information, provide a summary of work, and proceed to kick-off the engagement.

This form is submitted securely over an encrypted HTTPS connection. Your privacy is important to us. We understand that you may not be ready to answer certain questions without further discussion, or you may not yet have all the necessary details. That’s completely understandable—please complete the required fields and answer the remaining questions as best you can or as you feel comfortable.

When would you like this test to be completed?
Does this engagement have a report deadline?
Are there other services that you would be interested in bundling into this engagement?
Are there any compliance requirements?
Are multiple AWS accounts/environments in scope (e.g., dev, staging, prod)? If so list how many.
What major Azure services are in use and in scope for testing?
Please include other AWS services not listed above that are used and in scope for testing.
How many Azure tenants are in scope for testing?
How many Azure subscriptions are in scope for testing?
Is Azure Active Directory (Azure AD/Entra ID) integrated with on-premises AD?
Is the environment part of a hybrid cloud or multi-cloud setup?
What level of access will be provided for the Azure penetration test?
How is identity managed within the environment?
Are custom RBAC roles or Azure AD roles in use?
Are there any web apps or APIs hosted in Azure that are part of the assessment? Aevora will perform limited application security testing if in scope.
Please feel free to include any other details that you would like to share.