Use case · API incident response
Accelerate API attack incident response.
Salt connects every step of an attack into one timeline, across APIs, MCP servers and agents, so your team spends less time investigating and responds with confidence, inside the tools you already use.
“Salt has been a game-changer for our API security. We now have the visibility and control to protect our data.”
Peter Rios · Infrastructure and Information Security Manager, CISM · Kingston
The challenge
Investigations take too long, and attacks don’t wait.
API attacks unfold over days of quiet reconnaissance. Most tools see each request on its own, so analysts piece the story together by hand.
01 Scattered evidence
The steps of one attack sit in different logs, gateways and tools.
02 Too many false positives
One-off user mistakes look like attacks, and real attacks look like normal traffic.
03 Blocking breaks things
Without per-user context, blocking an attacker can block legitimate users too.
The shift
Stop reconstructing attacks by hand. Start from the whole timeline.
How Salt solves it
From first probe to blocked attacker.
Step 01 · Salt Collect · Salt Protect See the whole attack timeline
Salt connects every step of an attack sequence in one consolidated timeline, so investigations take less time.
- One consolidated timeline per attacker
- Fewer false positives from a large behavioral baseline
- Per-user context for accurate blocking
Step 02 · Salt Protect Catch attacks early
Salt keeps a behavioral baseline across millions of users and flags malicious behavior during reconnaissance, before an attack progresses.
- Early detection during reconnaissance
- Coverage of the OWASP API Security Top 10
- A baseline that adapts as APIs change
Step 03 · Salt Protect Respond inside your tools
Salt gives remediation guidance, feeds attack timelines into your SIEM and blocks attackers through your API gateways and firewalls.
- Detailed remediation guidance
- Attack timelines in your SIEM
- Automatic blocking through gateways and firewalls
The modules behind it
Built on the Agentic Security Platform.
Salt gives you breadth across every agent, MCP server and API, and depth across exposure, source code, configuration and runtime behavior. This solution brings together Salt Collect and Salt Protect.
By role
What it means for your team.
For AppSec and DevSecOps Investigate faster, respond with confidence
- Start every investigation from a full attacker timeline
- Spend less time on false positives
- Block attackers without disrupting real users
Fix the flaws attackers found
- Get remediation steps for each exploited vulnerability
- See which APIs attackers targeted, and how
- Close OWASP API Top 10 gaps found at runtime
For GRC and compliance Show every incident was handled
- Keep a complete record of each attack and response
- Share attack timelines with auditors and leadership
- Show coverage of the OWASP API Security Top 10
Go deeper · Case study
Kingston case study
How Kingston’s security team gained the visibility and control to protect its data.
Read the case study
FAQ
Frequently asked questions about API incident response.
API incident response is how security teams investigate and contain attacks on their APIs. Salt speeds it up by connecting every step of an attack into one timeline and blocking attackers through your existing gateways and firewalls.
Salt compares activity against a large behavioral baseline, so it can separate one-off user mistakes from genuinely malicious behavior.
Yes. Salt flags malicious behavior while attackers are still probing, before an attack progresses.
Yes. Salt feeds attack timelines into the SIEM you already use, such as Microsoft Sentinel or Splunk.
Yes. Salt blocks attackers through integrations with your API gateways and firewalls, using per-user context so legitimate traffic keeps flowing.
Respond to API attacks with the full story.
Book a demo to see an attack timeline from the first probe to a blocked attacker.