Rules of engagement and authorization
Capture the customer’s approval and unlock only the assets and window they signed for.
Before asking for a signature
- Review every domain, public IP, subnet, SSID, and tenant with the authorized customer contact.
- Confirm that the contact owns the assets or has authority to approve their testing.
- Agree on a realistic testing start and end time. External checks run only while this window is active.
Capture authorization
- Hand the device to the customer contact.
- They enter their name and title, optionally their email, then sign on the screen.
- They must tick the authorization confirmation before choosing Sign & authorize.
- The signed scope is saved as a read-only snapshot and the action is added to the audit log.
Changing scope or dates
An admin can choose Void and re-sign. This locks external checks until a replacement signature is captured. Use this whenever the scope or testing window must change; do not treat an old signature as approval for new assets.
What the signature permits
Only the listed non-intrusive assessment activities. It does not permit exploitation, password cracking, denial-of-service, malware, or testing of unlisted assets.
Related help
Authorized testing only. External checks require a signed, active authorization and an in-scope public target. Never test assets you do not own or have explicit permission to assess.
