Saluki
04Platform / Resolve

Fixed, and proven fixed.

Findings arrive owned, prioritised and routed to the tools your team already uses. When the fix lands, Saluki retests and says so.

See Resolve on your surface
01From finding to closure

Every finding has a timeline, and an end.

A verified finding becomes a ticket with its owner, its heat and its evidence attached. The channel that owns it is told. When the ticket closes, Pursuit retests from a clean session and only then marks the finding fixed. The board page updates itself. The number that matters at the end is how long all of that took.

Mean time to fix

3.2 d0.4 d

90 days

One finding, end to end: Pursuit verifies it, Resolve routes it, the team fixes it, Pursuit retests it, and the board page records the result. Nothing in the chain waits for a person to remember.

Saluki
Verify, route, retest, report
Your team
Acknowledge, fix, close
SalukiYour team
  1. 01Verified24 Oct · 22:27

    Pursuit reproduced PR-0917 three times from a clean session.

    Saluki

  2. 02Routed24 Oct · 22:28

    Ticket PLT-412 raised to the Platform team with heat, owner and evidence.

    Jira

  3. 03Notified24 Oct · 22:28

    #sec-platform told, evidence a click away.

    Slack

  4. 04Acknowledged25 Oct · 09:12

    Platform picked it up and scheduled the fix for the maintenance window.

    Jira

  5. 05Fix deployed25 Oct · 23:40

    Change shipped and the ticket closed.

    GitHub Actions

  6. Ticket closed → retest

    06Retested26 Oct · 22:09

    Ticket closure triggered a retest. The path no longer works.

    Saluki

  7. 07Verified fixed26 Oct · 22:09

    Finding closed with the retest evidence attached.

    Saluki

  8. 08Board page26 Oct · 22:10

    October's page updated: hot exposures 7 to 2.

    Saluki

Routed
Ticket raised in Jira or ServiceNow, owner assigned, evidence attached
Notified
The owning channel in Slack or Microsoft Teams is told, with the evidence a click away
Retested
Closing the ticket triggers a retest from a clean session
Reported
The board page shows hot to fixed, every month, on one page

02Features

  1. 01

    Routed to owners

    Every finding knows its asset, its owner and its ticket. Nothing waits in an inbox.

  2. 02

    Automatic retest

    When a ticket closes, Pursuit retests. A finding is only closed when it is fixed.

  3. 03

    A page for the board

    What is hot, what changed, what is fixed. One page, every month, in plain language.

In the loop

Resolve runs the Strengthen step and feeds what was learned back into Sight.

Explore Sight

In the loop

  1. 01 · WatchSight
  2. 02 · IdentifySignal
  3. 03 · EmulatePursuit
  4. 04 · StrengthenResolve

Specifications

Resolve
Remediation and proof

Routing
Ticketing, chat, SIEM and SOAR, API
Retest
Automatic on ticket close, or on demand
Reporting
Team views and a board page
History
Every finding keeps its full timeline

Related capabilities

See it run against your estate.

See Resolve on your surface