Before the Breach/How we work

Every engagement runs the same disciplined way.

From the first conversation to the final re-test, you know what happens next, who is doing the work, and what you receive.

The process

From first call to closed findings.

Seven steps, the same on every engagement, so you always know what happens next and what you will receive.

  1. Within 24 hours

    Conversation

    Tell us where you stand and what you are preparing for. A senior practitioner responds within 24 hours with a candid read and a short plan.

  2. Rules of engagement

    Written scope

    Targets, exclusions, testing windows, and emergency contacts are agreed in writing before any testing begins. You see exactly what is in scope and what is out.

  3. Typically 48 hours

    Kickoff

    Engagements typically start within 48 hours of an agreed scope, with named contacts on both sides and a clear schedule.

  4. Every step recorded

    Testing and assessment

    Manual, methodical work mapped to recognized standards. Exploitation is controlled, logged, and reversible, and agreed exclusions stay untouched.

  5. Three formats

    Reporting

    A technical narrative, a prioritized fix list with severity and business impact, a one-page executive summary, and attack playback your defenders can study.

  6. Your team, our bench

    Readout and working sessions

    Live debriefs with your engineers, plus hands-on remediation support when your team wants help closing findings.

  7. Day 30 · Day 90

    Re-test and close

    Re-tests at 30 and 90 days verify each fix, and closure is documented with evidence delivered to your portal.

What stays constant

Four commitments, every time.

01

Senior practitioners on every engagement

The people you meet at scoping are the people who do the work, each a specialist in the surface they test.

02

Written rules of engagement

Scope, exclusions, windows, and contacts are documented and signed before work starts.

03

Evidence your team can act on

Findings arrive with severity, business impact, and an owner-ready remediation.

04

Closed means closed

Every finding gets a second look, and closure is proven with re-test evidence.

What you receive

Deliverables, by service.

Every engagement ends with artifacts, cleanly named and delivered to your portal.

Offensive Security

  • Technical narrative
  • Prioritized fix list
  • One-page executive summary
  • Attack playback
  • Re-tests at 30 and 90 days
  • Working sessions with your engineers
Explore Offensive Security →

Information Assurance

  • Maturity scorecard
  • Findings register
  • Remediation roadmap
  • SSP and PoAM
  • Evidence repository
  • One-page executive summary
Explore Information Assurance →

Cyber Boot Camp

  • Current-state control inventory
  • Maturity baseline
  • Policy and procedure writing
  • Hands-on engineering support
  • Mock audit dry-run
  • SSP and PoAM finalized
Explore Cyber Boot Camp →
Engagement models

Test once, on a schedule,
or continuously.

Choose the cadence that fits your business: a single engagement, a recurring subscription, or continuous coverage that keeps pace as your attack surface changes.

Point in time

One-Time Assessment

A scoped engagement with a defined start and end. We test, prove impact, and deliver the full report package. A strong fit for a compliance deadline, a board or customer requirement, a merger or acquisition, or a first baseline.

Best forAnnual requirements, due diligence, a first baseline.
Applies to
Every discipline
Scheduled cadence

Subscription

Recurring engagements on a set schedule at a predictable annual rate. You get priority scheduling, retests inside every window, and a team that already knows your environment. Coverage stays current as your systems change.

Best forQuarterly or semi-annual coverage, regulated programs, flat budgeting.
Applies to
NetworkWeb & APICloudWirelessSocial
Always on

Continuous (PTaaS)

Ongoing offensive testing delivered through your portal. We track your external attack surface as it changes, test new releases on request, and report findings as we confirm them. Re-tests run on demand, so a fix is validated the day it ships.

Best forFrequent releases, fast-moving cloud and web estates.
Applies to
External NetworkWeb & APICloud

Not sure which fits? We will recommend a model based on your attack surface, release cadence, and compliance calendar. Talk through the options →

Next step

Start with a candid read of where you stand.

Tell us where you stand and what you are preparing for. A senior practitioner responds within 24 hours with a candid read and a short plan.