Skip to content

Agree the test. Review the results.

Start with a no-charge call. Before any testing, we agree what is included, the price and your permission. You get a report and a debrief.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing
  • Onshore

    US engineers, Central time

  • Senior engineers

    Scope it, then build it

  • Reproducible

    Steps and evidence each

  • Scope agreed

    Before any testing

What happens, in order.

Each phase is agreed separately.

  1. Phase 1

    First call

    45 minutes · no charge

    Discuss the security concern, requirement or training need.

    What happens, what you get and how to leave

    We identify the systems and people involved, the result you need and any deadline. We recommend an assessment, a penetration test or training where it fits.

    What happens

    • Discuss the concern and desired result
    • Identify systems, locations and stakeholders
    • Check deadlines and access requirements

    What you get

    • A recommended next step
    • A scoping proposal where needed

    ExitYou leave with a recommendation. There is nothing to cancel.

  2. Phase 2

    Scope and authorization

    Up to 2 weeks typical · scope dependent

    Agree the work, price, permissions and operating limits before delivery.

    What happens, what you get and how to leave

    We define the targets, exclusions, access, schedule and reporting. Active tests require written authorization and rules of engagement. Training plans identify the audience and exercises.

    What happens

    • Confirm the scope and exclusions
    • Agree written permissions for active testing
    • Set operating limits and escalation contacts
    • Confirm the fee and schedule

    What you get

    • Agreed scope and price
    • Rules of engagement for active testing
    • A delivery and reporting plan

    ExitDelivery starts only after the scope, price and required permissions are agreed.

  3. Phase 3

    Testing or training

    1–6 weeks typical · scope dependent

    Perform the agreed assessment, penetration test or training program.

    What happens, what you get and how to leave

    Testing stays within the authorized scope. We record findings, reproduction steps and recommended fixes. Training exercises track participation and the measures agreed in the plan.

    What happens

    • Perform the scoped tests or exercises
    • Document evidence and operating limits
    • Escalate urgent findings through the agreed contacts

    What you get

    • Documented findings or training results
    • Recommended remediation or follow-up work

    ExitThe engagement ends at the agreed scope. Additional work is priced separately.

  4. Phase 4

    Report and debrief

    1–5 days typical · scope dependent

    Review the findings, their impact and the recommended next steps.

    What happens, what you get and how to leave

    We walk your team through the report, explain the evidence and agree priorities. Retesting follows the scope and window set in the engagement.

    What happens

    • Review findings with your team
    • Explain reproduction steps and recommended fixes
    • Confirm any agreed retest or follow-up

    What you get

    • A report and debrief
    • An agreed list of next steps

    ExitYou can use the report with your own team or another provider.

  5. Phase 5

    Follow-up support

    Optional, by agreement

    Arrange retesting, further training or remediation support where needed.

    What happens, what you get and how to leave

    Ongoing work is a separate decision. We agree its scope, price, schedule and responsibilities before it starts.

    What happens

    • Define any further testing or training
    • Coordinate remediation with the responsible team

    What you get

    • A separately agreed follow-up plan, if needed

    ExitThere is no obligation to buy further work.

Agree the work before testing.

  • External security assessment

    Security Assessment & Penetration Testing

    • 3 business days
    • Price agreed with the scope, before the work starts
  • Scoped penetration test

    Security Assessment & Penetration Testing

    • 1–3 weeks
    • Price agreed with the scope, before the work starts
  • Adversary emulation

    Security Assessment & Penetration Testing

    • 3–6 weeks
    • Price agreed with the scope, before the work starts
  • Baseline campaign

    Automated Phishing Training

    • 1–2 weeks
    • Price agreed with the scope, before the work starts
  • Managed campaigns

    Automated Phishing Training

    • Ongoing
    • Price agreed with the scope, before the work starts

Written permission before any active test

Active testing starts only after the targets, exclusions, operating limits and escalation contacts are agreed in writing. The external security assessment attacks nothing: it reads only what your business already exposes publicly.

A retest, then a separate decision

Retesting of remediated findings is included within the engagement window. Further testing, training or remediation support is scoped and priced before it starts, and there is no obligation to buy it.

How we estimate the work.

See the steps and what the estimate contains
  1. Estimate slices, not features

    A feature list contains no delivery risk, so estimating one produces a number that cannot be wrong until it is very wrong. We break the work into slices that are each independently deliverable, and estimate those. It is slower, and it is the reason a range narrows as the project proceeds instead of quietly widening.

  2. Give a range, and say what sits at each end

    You get a low and a high, plus the specific conditions that put the work at either end, not a single number with a padding factor buried in it. If we cannot describe what would have to be true for the top of the range, we do not understand the work well enough to have estimated it.

  3. Write our assumptions as your obligations, with dates

    Every estimate rests on things we assume about your side: an environment exists, someone can approve, a system has a test instance, a vendor answers. Those are listed as dated obligations in the statement of work rather than left implicit, because an unstated assumption is how a contractor manufactures a change order and calls it your fault.

  4. Attach a confidence, and say what would raise it

    Ranges carry a confidence level and the reason it is not higher. Usually the answer is one unknown that can be resolved by building something small, which is why discovery includes a spike against the single riskiest assumption rather than a longer document.

  5. Agree who pays for a miss before the work starts

    Modest variance is ours to absorb; that is the normal play in any estimate. A large miss means the estimate was a guess dressed as an estimate, which is our failure and not a change in your scope. The threshold between those two is a number in the statement of work, agreed before anyone starts, not a conversation in week nine.

  6. Show the last estimate against what it actually cost

    At every phase boundary you get the previous estimate next to the actual, and an explanation of any gap. This is the part firms leave out, and it is the only one that makes the rest verifiable: a method you cannot audit is a claim about our character, and you have no reason to take our word for that yet.

What the estimate contains

  • A low and a high figure, with the conditions that produce each
  • The slices behind them, priced individually
  • Our assumptions restated as dated obligations on your side
  • A confidence level, and the one unknown that would most improve it
  • The overrun threshold and who carries each side of it
  • Enough detail that another firm could price the same scope from it

Terms to review before work starts.

Ownership and licensing, Acceptance and payment, Scope and change, People, Data and security, Leaving
  • Ownership and licensing

    “Work made for hire” is a copyright concept. It says nothing about patents or trade secrets, and it does not reach work done by a contractor, which is why the mechanism matters more than the label.

    • Ownership and licensing settled in writing in the engagement agreement, before any work starts
    • Whatever is agreed is agreed by express assignment rather than by relying on work-made-for-hire language
    • Every engineer and subcontractor under written assignment before they touch the codebase, so there is a clean chain of title to assign
    • Any third-party or open-source component identified, with its license and any fee attached
    • No feedback clause. What you tell us about your business stays yours
  • Acceptance and payment

    Acceptance testing is the protection most services contracts leave out, and the one that decides what happens when a deliverable is not what you asked for.

    • Objective acceptance criteria written into the statement of work, not decided afterward
    • Nothing is “deemed accepted” because time passed
    • Rework to meet the agreed criteria is at our cost, inside a defined window
    • On a fixed-scope phase, payment tied to milestones and acceptance rather than to the calendar
    • Invoices are net 30, paid by purchase card, ACH or purchase order
    • A holdback on each phase: a share of the fee we don’t invoice until you accept that phase
  • Scope and change

    Underbidding a project and recovering the difference through change orders is a known pattern. The defense is a specific scope and a change process you control.

    • A statement of work in active voice, naming who does what and by when
    • Our assumptions rewritten as your obligations, with dates, so neither side discovers them late
    • Every change priced and signed before the work starts
    • Estimates given as a range with the assumptions stated, and a shared overrun mechanism agreed in advance
    • No legal terms buried in a statement of work
  • People

    The named team on the proposal and the team that arrives are frequently different. Staff turnover is the most reliable predictor of cost and delay on a long engagement.

    • Key personnel named in the statement of work and not substituted without your consent
    • Interview anyone you want to before they start
    • You can require removal of anyone, for any lawful reason
    • No charge for the ramp-up time of a replacement we initiated
    • All delivery performed in the United States. Nothing subcontracted offshore
  • Data and security

    Most privacy law holds you responsible for a breach whether it was your fault or your vendor’s. The contract is where that gets allocated.

    • A security requirements exhibit specific to your data, not a pointer to our then-current policy
    • Written notice of any actual or suspected incident within 24 hours
    • You control the content, timing and method of any notification to your customers or regulators
    • Log files and forensic cooperation preserved and provided
    • A signed BAA where PHI is involved, and joint security testing where you want it
  • Leaving

    The cost of leaving is set on the day you sign, not on the day you go.

    • Termination for convenience on thirty days’ notice after the first release, no fee
    • A hand-off phase in the plan from the start, not negotiated under pressure at the end
    • Your data returned in a platform-neutral format as well as ours, then certified destroyed to NIST SP 800-88
    • Documentation, runbooks and architecture decision records written as the work happens
    • A named handover contact for a defined window after the last day, so the last question does not go unanswered

Cost, timing and project questions.

  • Yes, and it is usually the fastest way to get a useful answer: several of the pieces we publish end by asking for exactly that. Two things worth knowing first. This is an ordinary web form: it is encrypted in transit and the message lands in our mailbox and our own console, but it is not a secure document channel, so redact freely. A workbook with the numbers changed, a clause with the parties removed, a day of messages with the identifiers swapped: each of those answers the question as well as the original does, and we would rather read a redacted one. And if you would rather have an agreement in place before you send anything, say so in a line: we work under your paper rather than asking you to work under ours, and we redline rather than refuse.

  • Assessments, penetration tests and adversary emulation are each quoted against the agreed scope. The scope, price and permissions are agreed in writing before any testing starts. Cyber Watch, our monitoring package, has a fixed monthly price on its page.

  • On résumé, they are ahead, and you should discount anyone who tells you otherwise. There are onshore firms in this space that have been doing it for eighteen, thirty, even fifty years, with senior engineers and named clients in your industry. The difference we would ask you to weigh is structural rather than technical. Most firms our competitors’ size specialize in one layer and subcontract or decline the rest, so the seams between the control network, the application, the estate and the security review end up owned by whoever is left in the room. We run those as four divisions inside one company, under one contract, which is why the escalation path ends somewhere useful instead of at a vendor boundary. That is the trade on offer: longer history and more logos on one side, and on the other a smaller senior team that can follow the problem across every layer it touches.

Next step

Tell us what’s breaking.

Forty-five minutes, no charge. We’ll say what we’d do, what it would likely cost, and whether the thing you’re worried about is actually your biggest risk.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.