01
Evidence before severity
An observation keeps its source, timestamp, affected asset, and replayable context.
SCARP methodology
The paths decide what to fix first; the score summarizes posture over time. The graph, evidence, ownership, and re-check state stay inspectable beside both.
01
An observation keeps its source, timestamp, affected asset, and replayable context.
02
Connected control gaps and reachable impact outrank isolated finding volume.
03
A remediation changes status only after a re-check finds the findings on its route gone.
How a run works
Passive observation of your internet-facing estate — services, sign-in pages, DNS, certificates, leaked credentials — plus active checks where you have authorized them. Each finding keeps its source, timestamp, and affected asset.
Findings are chained by attack technique, from an entry point to an impact. SCARP sees from outside: a hop behind your perimeter is inferred from what was observed, and the report labels it inferred.
Findings that sit on many routes are choke points. Changes are ranked by how many routes each one is expected to cut, with severity and exploitability as inputs, so one fix at a shared hop can outrank a worse finding on a single route.
After your team ships a change, SCARP scans again. Projected, verified, and still-open routes are reported as three numbers, and a route that is still open stays on the report.
The exposure score
Every assessment also produces a 0–1000 score with a letter grade across eleven categories, for trend lines and reporting. It does not set fix order. The scorecard below is illustrative: move the slider to see how grade and tier bands map to the score.
Illustrative score-only view. The score summarizes external posture for trend lines and reporting; what to fix first comes from the attack paths, not from this number. Category bars are illustrative.