01 · Continuous discovery
Sight
Give Saluki a name. It maps everything that name exposes: domains, cloud, certificates, services, identities. The map stays current as the estate changes.
04Platform / Resolve
Fixed, and proven fixed.
Findings arrive owned, prioritised and with a fix plan, in Saluki or in the tools your team already uses. When the fix lands, Saluki retests and says so.
01From finding to closure
Every finding has a plan, a timeline, and an end.
A verified finding arrives in Resolve with its owner, its heat-ranked priority and a fix plan Saluki wrote for it. Mirror it into Jira or ServiceNow, tell the channel in Slack or Teams, or work it entirely in the platform. When the fix lands, Pursuit retests from a clean session and only then marks it fixed, here and in the ticket. The board page updates itself. The number that matters at the end is how long all of that took.
Use ours. Use yours. Or both.
Remediation lives where your team does.
Every verified finding arrives in Resolve with an owner, a heat-ranked priority and a fix plan Saluki writes for it: what to change, where, and how to confirm it. Run remediation entirely in the platform, connect the tools you already use, or do both. Close the ticket in Jira and Saluki retests. Mark it fixed in Saluki and the ticket closes. The finding keeps one timeline either way.
- Ours
- Owner, priority, fix plan and retest, all inside Resolve.
- Yours
- The same finding as a Jira or ServiceNow ticket, a Slack or Teams thread, a PagerDuty page.
- Both
- Status flows both ways, so nobody updates two systems and nothing closes until the retest passes.
- Planned
- A fix plan with every finding: what to change, where, and how to confirm it
- Routed
- Ticket raised in Jira or ServiceNow, owner assigned, evidence attached; status flows both ways
- Retested
- Closing the ticket, or marking it fixed in Saluki, triggers a retest from a clean session
- Reported
- The board page shows hot to fixed, every month, on one page
02Features
- 01
A fix plan with every finding
Every finding knows its asset, its owner and its priority, and comes with a plan: what to change, where, and how to confirm it. Nothing waits in an inbox.
- 02
Automatic retest
When a ticket closes, Pursuit retests. A finding is only closed when it is fixed.
- 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.
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