PAGES
← all tools
◆ WAF, Bot & API Protection

Salt Security

Salt Debuts First AWS WAF Managed Ruleset for AI Agent and API Protection (2026-08-04) commercial

Summary

Salt Security is a commercial web-app-security tool that provides API discovery and runtime protection by adding managed rulesets directly to existing AWS WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. web ACLsACLsAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource.. It is run via subscription through the AWS Marketplace and is for practitioners managing API security posture, and its documentation positions it alongside native WAF rules for AWS WAF environments. The project launched in 2016 and had its last release eighteen days ago.

Salt Security publishes no documentation we track, so the description above is written from general knowledge rather than the vendor's own words.

How Salt Security helps

Which of my API endpoints are exposed to attacks that standard WAF rules would not catch?

inspects API traffic for patterns like credential brute force, excessive GraphQL queries, SSRF, prototype pollution, and JWT anomalies, and flags the requests matching those patterns inside the existing web ACL

Which MCP servers are actually running against my Claude organization, and are any of them gone now?

polls Anthropic's Compliance API Activity Feed and lists each server's name, identity, status as active or removed, and first- and last-seen times in the inventory

Is anything talking to my MCP endpoints without authenticating first?

labels MCP traffic passing through the web ACL and blocks the requests that lack authentication, giving visibility into what was attempted

Can my existing detection stack tell which requests carried real user identity versus which were anonymous?

tags requests with attributes like auth headers, user identifiers, and GraphQL query contents so downstream analytics can key off them without re-parsing traffic

Where did a newly discovered MCP server come from, and can I trust that source?

records the discovery source such as Claude Connect alongside the server's status and lifecycle timestamps, so provenance is visible in the inventory rather than assumed

all 5 features, with the evidence for each →

Languages

Not documented

Features

5 capabilities

Built from Salt Security's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What Salt Security offers you

  • GraphQL API support2
All capabilities 5 capabilities
MCP endpoint awareness shipped Identifies and labels MCP traffic, blocks unauthenticated MCP access, and provides observability into MCP interactions within AWS WAF environments. 4 releases · 2 other sources · first seen Aug 2026

release

  • Adds the Claude Connect integration in the Salt Data Source Hub, authenticating to Anthropic's Compliance API with a read:compliance_activities-scoped Compliance Access Key to continuously inventory organization-managed MCP servers.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
  • Polls Anthropic's Compliance API Activity Feed at https://api.anthropic.com/v1/compliance/activities to surface each MCP server's name, identity, status (active vs. removed), and lifecycle timestamps into the Salt Agentic inventory. announced · Sep 2026 · source · release history
  • Discovered MCP servers appear in the Salt Agentic inventory labeled with the source Claude Connect, showing server name, status, and first- and last-seen times. announced · Sep 2026 · source · release history
  • Adds industry-first MCP endpoint awareness: identifies and labels MCP traffic, blocks unauthenticated MCP access, and provides observability into MCP interactions inside AWS WAF environments. Salt Debuts First AWS WAF Managed Ruleset for AI Agent and API Protection (2026-08-04) · Aug 2026 · source · release history

example

  • Connect Salt to your Claude Enterprise org so MCP server discovery starts immediately. In the Salt dashboard, go to Data Source Hub > Claude Connect tile. announced · Sep 2026 · source
  • Confirm your Claude organization UUID before entering it into Salt — retrieve it from any Compliance API activity record. curl -s "https://api.anthropic.com/v1/compliance/activities?limit=1" \ -H "x-api-key: <your-compliance-access-key>" announced · Sep 2026 · source
Automated attack response workflows shipped A visual drag-and-drop workflow builder with 200+ connectors that lets users trigger automated blocking, access revocation, guardrail updates, and data redaction across WAFs, API gateways, MCP endpoints, and other enforcement points when Salt detects exploitation or risky configurations. 4 releases · first seen Oct 2026

release

  • Salt Security now uses Salt Workflows to block active attacks at connected WAFs, API gateways, and other enforcement points when Salt detects exploitation in progress.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Salt Workflows can now revoke agent and MCP tool access — disabling unauthorized MCP connections, quarantining shadow tools, or removing excess privilege — when Salt finds a risky agent configuration. announced · Oct 2026 · source · release history
  • Salt Workflows can now update connected guardrail policies, block unsafe AI requests, or redact sensitive data through connected gateways to enforce AI and data protections at runtime. announced · Oct 2026 · source · release history
  • Salt Security adds a visual drag-and-drop workflow builder directly into the Agentic Security Platform, with 200+ out-of-the-box connectors and a marketplace of integrations spanning security, infrastructure, IT, and collaboration systems. announced · Oct 2026 · source · release history
Salt Managed Rules for AWS WAF shipped A partner-managed AWS WAF ruleset subscribable from AWS Marketplace that attaches to existing web ACLs to protect APIs and AI agents without additional infrastructure. 2 releases · first seen Aug 2026

release

  • Introduces Salt Managed Rules for AWS WAF, the first AWS WAF Partner Managed Ruleset built specifically to protect APIs and AI agents — subscribable from AWS Marketplace and attachable to existing web ACLs with no new infrastructure. Salt Debuts First AWS WAF Managed Ruleset for AI Agent and API Protection (2026-08-04) · Aug 2026 · source · release history
  • Available across all commercial AWS Regions and globally via Amazon CloudFront. Salt Debuts First AWS WAF Managed Ruleset for AI Agent and API Protection (2026-08-04) · Aug 2026 · source · release history
API-layer attack detection shipped Detects API-specific threats such as credential brute force, excessive GraphQL queries, SSRF, prototype pollution, and JWT anomalies that standard WAF rules miss. 1 release · first seen Aug 2026

Also counts toward: GraphQL API support

release

  • Detects API-layer attack vectors missed by standard WAF rules — including credential brute force, excessive GraphQL queries, SSRF, prototype pollution, and JWT-based anomalies. Salt Debuts First AWS WAF Managed Ruleset for AI Agent and API Protection (2026-08-04) · Aug 2026 · source · release history
Request attribute labeling shipped Labels critical request attributes — including auth headers, user identifiers, and GraphQL queries — to enrich downstream analytics and detection stacks. 1 release · first seen Aug 2026

Also counts toward: GraphQL API support

release

  • Enriches downstream analytics by labeling critical request attributes including auth headers, user identifiers, and GraphQL queries, flowing security signals into existing detection stacks. Salt Debuts First AWS WAF Managed Ruleset for AI Agent and API Protection (2026-08-04) · Aug 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Salt Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Salt Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

salt.security, every change

Salt Security's home page and 29 more pages as they looked each month from September 2021 to October 2026: 42 renders, 7 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

3 entries

  1. October 20261
  2. September 20261
  3. August 20261

    3 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →