Continuous Validation

Keep proving defenses between annual tests.

Technique sprints and retests as your environment changes. You see the trend, not a yearly snapshot.

From one test to a trend.

Five steps that repeat as your environment changes.

  1. Re-run the paths

    Prior attack paths are exercised again as your environment changes.

  2. Test what is new

    New assets and releases enter the cycle before the next annual test.

  3. Track the latency

    Detection latency is measured on each run so the trend is visible.

  4. Report the trend

    A periodic brief and a trend view keep the board informed.

  5. Close the loop

    Each cycle ends with closure letters for the paths that are gone.

What this engagement covers

When you need it

  • After each major release
  • For board-level trend reporting

What we do

  • Re-run prior attack paths
  • Test new assets
  • Track detection latency

What you get

  • A trend view
  • A periodic brief
  • Closure letters

How it runs

  • Duration: Scoped and quoted in the scoping call.
  • What we need from you: The prior attack paths to re-run, the new assets to test and a contact for the periodic brief.

Standards

  • MITRE ATT&CK

Frequently Asked Questions

How does this differ from an annual test?
An annual test is a snapshot. Continuous Validation re-runs prior attack paths and tests new assets as your environment changes, so you see the trend.
What do we receive?
A trend view, a periodic brief and closure letters as findings are fixed.
Does it measure detection?
Yes. We track detection latency across sprints alongside the attack-path results.

How We Work

Eight steps from the first call to the closure letter. Every engagement follows them.

  1. Scoping call
  2. Rules of engagement
  3. Threat model
  4. Execution
  5. Analysis
  6. Readout
  7. Remediation support
  8. Retest
Read the full lifecycle

Ready to scope an engagement?

Tell us the asset and the decision the test should inform.

Scope a call