Agents need real systems.
The answers enterprises care about live in systems of record. Reaching them means speaking their protocols, formats and security models.
FORUM SYSTEMS · FS SENTRY
Without robust API middleware, AI is meaningless. FS Sentry connects agents and applications to every enterprise system, from HTTPS to IBM MQ, SOAP to REST and API keys to signed SAML.
The security gateway for APIs and AI agents, securing more than 10 billion transactions every day. Protocols, identity, transformation and PKI live in the gateway, not in your code.
HTTP(S) · MQ · SOAP
Keys · mTLS · SAML
FIPS 140-2
From HTTP(S) to IBM MQ channel handling
From API keys to mutual TLS and signed SAML
From legacy SOAP XML to REST JSON
WHERE AI MEETS THE ENTERPRISE
Agents reason in the model, but they act through your APIs, into systems built over decades: message queues, SOAP services, mainframes and deep directory structures. Every one of those calls is a security decision. FS Sentry is where those decisions are made, consistently, for every agent and application.
The answers enterprises care about live in systems of record. Reaching them means speaking their protocols, formats and security models.
Who is calling, with what credential, under which policy, carrying which data. FS Sentry decides once, in one place, and denies anything not explicitly allowed.
Certificates, consumers and policies are managed centrally, so a change is made once instead of in every service and agent.
Security, identity and transformation belong in the gateway.
Business logic belongs in the code, whether a person or an AI wrote it.
THE HARD PARTS
This is the work that separates an enterprise gateway from a prototype. FS Sentry does it in tested, certified product code, so no application or agent has to. And it starts from positive security: define what is allowed, deny everything else.
From simple HTTP(S) to IBM MQ channel handling, with protocol break and translation between transports.
Basic auth, API keys, OAuth, OpenID, mutual TLS and signed SAML. Okta, AD, Ping and LDAP integrations are built in, so no agents run on clients or services, and RBAC, ABAC and CBAC authorization is checked on every transaction.
Modernize the interface, not the backend. Legacy SOAP XML to REST JSON and back, with header and body mapping, schema validation and XML signatures.
A PKI engine with FIPS 140-2 cryptography for keys, certificates, signing, encryption and TLS, managed centrally.
Protocol break, built-in PKI, FIPS 140-2 and protocol translation
Bi-directional transaction correlation and full payload analysis
AV and malware scanning, OWASP Top 10, RegEx patterns, rate and size controls
Request and response schema validation, XML signatures
Encryption, decryption, encoding and redaction
Any-to-any conversion across PKI, HTTP auth, SAML, OAuth and OpenID
Header and body mapping between XML and JSON
Full-context transaction logging and AI logs
Also built in: API management, multi-factor and continuous authentication, data leakage protection, TLS acceleration and zero trust policy enforcement.
Download the datasheetARCHITECTURE
Every request from an agent, an application or a partner passes the same pipeline: identity in, protection, transformation, protocol mediation and identity out. Responses are inspected on the way back too. QS DevX catalogs and monitors it all.
Agents running on QS Platform 10 call tools generated from your API catalog. Each call enters FS Sentry like any other governed request.
Identity, threat protection, transformation, protocol mediation and PKI are applied by policy, not by agent code.
Back-end systems receive the protocol, format and credentials they expect. Responses are inspected, redacted or transformed before they return, and every transaction is logged in full context.
SECURING MCP AND AGENT TOOL ACCESS
The same default-deny model applies to every MCP tool call, from the connection to the response the agent receives.
Denied by default: unknown methods, unknown tools, invalid arguments and sensitive output.
GATEWAY VS. CODE
Imagine asking an AI to write MQ channel handling, SAML signing, mutual TLS and PKI into every application and agent. Even if it works on day one, you now maintain hundreds of copies, each with its own bugs and its own attack surface.
SECURITY IN EVERY APP AND AGENT
SECURITY IN FS SENTRY
PROVEN IN PRODUCTION
For 25 years, Forum Systems has focused on API security and integration. FS Sentry is trusted by government and commercial enterprises worldwide for mission-critical traffic.
Mission-critical transactions secured daily across government and commercial enterprises.
Named a Leader in the 2025 Leadership Compass for API security and management.
FIPS, DoD PKI, NIAP NDPP and HITRUST validations support regulated and high-assurance environments.
Patented technology, purpose-built for securing, integrating and governing enterprise APIs.
PROOF POINT · IRS MODERNIZED E-FILE
FS Sentry has been the enforcement and mediation layer for the IRS Modernized e-File program since 2005: SOAP with attachments, schema and AV checks, SAML with RBAC and ABAC, HTTPS to MQ mediation and PKI on one transaction path.
PROOF POINT · FAA
Secure messaging for NWS and NOAA weather feeds with HTTP to JMS mediation, PKI automation through an ACME security proxy, and air-gapped multi-factor authentication with TOTP, RADIUS and TACACS+.
Trusted by
06 · DEPLOY ANYWHERE
FS Sentry runs in every major form factor, including air-gapped and federal environments, with the same policy model everywhere. Hundreds of pre-built templates put common industry use cases into production in minutes.
Active/active high availability means no single gateway dependency. Policies are automated through the CLI and REST API, promoted through Git and hot-swapped without downtime.
Your APIs, policies and integrations carry forward as you extend to AI: FS Sentry is the API foundation of QS Platform 10, alongside QS Cortex and QS DevX.
Explore QS Platform 10EDITIONS
Every FS Sentry edition is priced by instance, with no per-API or per-transaction meter. As agents multiply API traffic, your usage can grow without a new charge on every call. Enterprises extending their APIs to AI deploy FS Sentry as part of QS Platform 10.
Annual subscription
Annual subscription
Product plus annual support
Enterprise platform
THE DETAILS
Protocols, identity, transformation and how FS Sentry fits QS Platform 10.
Talk to our teamFS Sentry is the Forum Systems security gateway for APIs and AI agents. It connects agents and applications to enterprise systems, with protocol mediation, identity, transformation and PKI handled by the gateway.
FS Sentry is Forum Sentry at version 10, renamed to align with QS Platform 10. Existing deployments, APIs, policies and integrations carry forward.
Because every agent would then carry its own protocol, identity and cryptography code. That multiplies the attack surface and the maintenance burden. FS Sentry keeps security in the gateway and business logic in the code.
From HTTP(S) to IBM MQ channel handling, with protocol break and translation between transports.
Basic auth, API keys, OAuth, OpenID, mutual TLS and signed SAML. Integrations with Okta, AD, Ping, LDAP and other identity providers are built into FS Sentry, so no agents are deployed on clients or back-end services, and authorization is evaluated on every transaction.
Yes. FS Sentry applies its default-deny model to MCP: it checks identity and TLS on connection, allows only defined methods and tools, validates arguments against schema and range, and redacts or limits sensitive data in responses.
Yes. It transforms legacy SOAP XML to REST JSON and back, with header and body mapping, schema validation and XML signatures.
FS Sentry is the API foundation of QS Platform 10. QS DevX catalogs APIs and gateways and generates the tools agents use, QS Cortex runs the agents, and every tool call reaches enterprise systems through FS Sentry.
Yes. Forum Systems has replaced gateways such as IBM DataPower, Axway, CA and MuleSoft. Talk to our team about a migration plan.
FS SENTRY · VERSION 10
See how FS Sentry connects agents to your hardest systems without putting security in their code.