APTStrikeRequest a scope call

Method

Four steps. No surprises.

Every engagement follows the same four steps, so you know what happens, what we need from you and what you receive — before testing starts.

Request a scope call
Steps
Scope · Recon ·
Exploitation · Report
Typical duration
[TYPICAL DURATION]
Testing
Manual first,
tools second
Retest
Free, once you
have fixed
  1. 01 / 04

    Scope & authorization

    We start by understanding what you run and what worries you, then agree exactly what will be tested — in writing.

    What happens

    • A scope call about your systems and goals
    • Targets, testing windows and rules of engagement agreed
    • A fixed-price proposal
    • A signed authorization letter before anything is touched

    You provide

    • A list of targets and environments
    • One technical contact
    • Test accounts, where testing needs them

    You receive

    • Written scope and rules of engagement
    • Fixed-price proposal
    • Authorization letter to sign
  2. 02 / 04

    Reconnaissance

    We map your attack surface the way an outsider would, and plan the testing around the paths a real adversary is most likely to take.

    What happens

    • Domains, subdomains and exposed services mapped
    • Public data and leaked information reviewed
    • Entry points ranked by likely impact
    • A test plan built around real attack paths

    You provide

    • Nothing beyond the agreed access

    You receive

    • Start-of-testing notice
    • A direct channel to the tester
  3. 03 / 04

    Exploitation

    Hands-on, manual testing to confirm what is actually exploitable. Every finding is proven with evidence; scanner output alone never reaches your report.

    What happens

    • Manual testing within the agreed scope
    • Each finding confirmed and documented with evidence
    • No destructive actions without your approval
    • Critical issues reported to you immediately

    You provide

    • A reachable contact during the testing window

    You receive

    • Immediate notice of critical findings
  4. 04 / 04

    Report & retest

    A report written for both the engineers who fix and the leaders who decide, a call to walk through it, and a retest once you have fixed.

    What happens

    • Risk-rated report with reproduction steps
    • Specific remediation guidance per finding
    • Walkthrough call with your team
    • Free retest after you patch

    You provide

    • Time for the walkthrough call
    • A note when fixes are ready to retest

    You receive

    • Executive summary and technical report
    • Walkthrough call
    • Retest and updated report

Start with
a scope call.

Request a scope call SeeAll services