Test access to the data you need to protect.
Name the data source and the access you want to test. AutoAttack pursues that objective from its deployment position and records what the campaign retrieves.
← All objectivesWhat allowed a read of the finance document?
In this hypothetical assessment, an employee account is the starting point. The objective is to read a designated test document on the finance share. The scope permits reading a shared configuration file and retrieving that document.
Inspect the document retrieved
Captured content from the designated document supports the data-access claim. Subscribers can inspect target names and captured evidence beside each gain.
Review the exposure and the share permission
Identify the configuration file and the service account with access to the finance share. The owner can review who needs those permissions and which services depend on the account before changing them. Remediation advice sits beside the relevant gain in a paid report.
- A shared file exposes a service credential.The employee account can read a configuration file containing a service account’s password.
- That credential enables the permitted read.The campaign uses the recovered account to retrieve the designated test document from the finance share.
What the evidence establishes
- Data retrieved
- Captured output shows the data a successful step obtained. The published lab example covers directory credentials.
- A route to review
- Read how the starting access led to the source, including the credentials or permissions that made the route possible.
- The boundary tested
- Reading data demonstrates access to it. Testing whether it can cross a particular outbound network boundary needs that boundary included in the objective and scope.
- Published example
- Read the credential-extraction results →
How a data-access route develops
- 1Start from the agreed footholdThe campaign uses its network position and any credentials you provide. An application weakness or another recovered credential may extend that access.
- 2Reach the sourceThe route follows available access toward the named source, such as a domain controller, database server or file share.
- 3Test the permitted readThe campaign attempts to retrieve data using the access and supported techniques available. What it may read must stay within the agreed scope.
- 4Review the evidenceThe report records the access achieved and the captured output. Use the route and stopping point to choose the next objective and scope.
Related
Set an objective for your network.
Run a campaign free and review its masked report before subscribing.
Contact