Solutions · Threat protection Stop the attacks, fraud and agent abuse that look like valid traffic.
Attackers and compromised agents use real credentials and well-formed calls. Salt learns how your APIs, MCP servers and agents normally behave, detects abuse by intent and blocks it through the controls you already run. No signatures. No rules.
“The platform’s behavioral analysis has been key in detecting business logic attacks that other tools missed.”
Salt customer · via Gartner Peer Insights
The challenge
Your WAF sees requests. Attackers abuse behavior.
Fraud, account takeover, BOLA and agent hijacking all look legitimate one request at a time.
01 Business logic abuse
Scraping, enumeration and account takeover use valid calls and real credentials.
02 Agents become the attacker
Prompt injection and compromised tools end in API calls with real tokens.
03 Alerts without the story
The SOC gets signals, not the sequence that explains them.
The shift
Stop chasing signatures. Catch intent.
How Salt solves it
From normal behavior to a blocked attacker.
Step 01 · Salt Collect Learn what normal looks like
Salt builds behavioral baselines from runtime traffic for every API, user, agent and MCP server.
- Per API and per user
- Per session and sequence
- Per agent and MCP server
Step 02 · Salt Protect Detect by intent
Patented behavioral analysis reads sequences over time, catching logic abuse and low-and-slow attacks that single-request tools miss.
- BOLA and enumeration
- Scraping and account takeover
- Prompt injection and tool abuse
Step 03 · Salt Protect Respond with confidence
Block through gateways and WAFs, alert the SOC with full context, and replay the session for the investigation.
- Block via gateways and WAFs
- Alert to SIEM, SOAR and XDR
- Session replay for investigation
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 Build securely, find what was missed
- Fix the logic flaws attackers exploit
- Feed runtime findings back into code
- Test new APIs against known abuse patterns
For SOC Detect and stop abuse with context
- Trace attacker behavior across a session
- Feed behavioral models into threat hunting
- Block known bad patterns without writing rules
For GRC and compliance Prove control, stay audit-ready
- Protect payments, refunds and account changes
- Report on blocked fraud and abuse
- Keep incident evidence for regulators
Go deeper · Solutions brief
Stopping business logic abuse and agent hijacking
A short read for the team evaluating this problem.
Get the solutions brief
FAQ
Frequently asked questions about API threat protection.
Behavioral API threat protection detects attacks by how traffic behaves over time, not by signatures. Salt learns normal behavior for every API, user, AI agent and MCP server, detects abuse by intent and blocks it through the controls you already run.
In a broken object level authorization (BOLA) attack, an attacker changes an object ID in a request to reach data that isn’t theirs. Salt detects BOLA and enumeration by reading sequences of calls, and blocks the attacker.
A WAF judges each request on its own. Fraud, account takeover, BOLA and agent hijacking look legitimate one request at a time. Salt reads sequences over time, so it catches logic abuse and low-and-slow attacks.
Yes. Prompt injection and compromised tools end in API calls with real tokens. Salt detects prompt injection and tool abuse in those calls, whoever or whatever is behind them.
Salt blocks attackers through the gateways and WAFs you already run, alerts your SIEM, SOAR and XDR with full context, and replays the session for investigation. There are no rules to write.
Catch the attack that looks legitimate.
Watch Salt catch abuse that looks like valid traffic.