Flintlatch

Authorization required

Security testing without permission can be illegal. Every engagement starts with written authorization and a signed scope.

Before any work begins

  1. Proof of ownership or control. You confirm in writing that you own, or are authorized to approve testing of, every website, domain, email list, IP address and system in scope.
  2. Signed Rules of Engagement. We both sign a document listing exactly what is in scope, what is out of scope, the testing methods allowed, dates and times, and who to contact if something urgent comes up.
  3. Third-party permission when needed. If a system is run by a hosting company, cloud provider or IT vendor, their testing rules apply and their approval may be needed first.
  4. A named contact. You name a person who can approve, pause or stop testing at any time.

What I will never do

  • Test anything not listed in your signed scope.
  • Test a system for someone who doesn't own or control it.
  • Use real malware, damage data or deliberately disrupt your operations.
  • Keep or share passwords, personal data or findings beyond what the engagement requires.

Each service and its authorization

ServiceWhat you authorize
Website security checkThe website addresses to check (passive checks only)
Breach monitoringThe email domain or addresses to monitor. Domain monitoring services may also ask you to verify the domain.
Phishing simulationsThe list of people to include and the email domain to send to, with your email admin's approval
Vulnerability assessmentThe internet-facing systems and IP addresses to scan, with scan windows
Penetration testA full Rules of Engagement: targets, methods, exclusions, dates and stop conditions
No guarantees. Testing shows weak spots at a point in time. It can't prove a system is secure, and no one can make a business "unhackable."