FORUM SYSTEMS · FS SENTRY

Version 10 / The API foundation of QS Platform 10

Where AI meets
your enterprise.
Securely, at scale.

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.

Named a Leader in the KuppingerCole 2025 Leadership Compass for API security and management.
SECURITY GATEWAY FOR APIS AND AI AGENTS10
FSSentry

Protocols

HTTP(S) · MQ · SOAP

Identity

Keys · mTLS · SAML

PKI

FIPS 140-2

Threat protection · Validation · Data protection · Full-context logging
AI agents
Tools via MCP
Enterprise systems
REST · SOAP · MQ
Identity stores
Okta · LDAP
Security in the gateway. Business logic in the code.
SECURITY IN THE GATEWAY.
LOGIC IN THE CODE.
Any protocol

From HTTP(S) to IBM MQ channel handling

Any identity

From API keys to mutual TLS and signed SAML

Any format

From legacy SOAP XML to REST JSON

01

WHERE AI MEETS THE ENTERPRISE

Without robust API middleware,
AI is meaningless.

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.

Agents need real systems.

The answers enterprises care about live in systems of record. Reaching them means speaking their protocols, formats and security models.

Every call is a security decision.

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.

Hundreds of APIs, one control point.

Certificates, consumers and policies are managed centrally, so a change is made once instead of in every service and agent.

SEPARATION OF CHURCH AND STATE

Security, identity and transformation belong in the gateway.
Business logic belongs in the code, whether a person or an AI wrote it.

02

THE HARD PARTS

The hard parts,
handled once.

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.

PROTOCOLS

Deep protocol mediation

From simple HTTP(S) to IBM MQ channel handling, with protocol break and translation between transports.

IDENTITY

Any-to-any identity

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.

CONTENT

Content transformation

Modernize the interface, not the backend. Legacy SOAP XML to REST JSON and back, with header and body mapping, schema validation and XML signatures.

PKI

Built-in PKI

A PKI engine with FIPS 140-2 cryptography for keys, certificates, signing, encryption and TLS, managed centrally.

Transport security

Protocol break, built-in PKI, FIPS 140-2 and protocol translation

Message security

Bi-directional transaction correlation and full payload analysis

Threat mitigation

AV and malware scanning, OWASP Top 10, RegEx patterns, rate and size controls

Data integrity

Request and response schema validation, XML signatures

Data privacy

Encryption, decryption, encoding and redaction

Authentication and SSO

Any-to-any conversion across PKI, HTTP auth, SAML, OAuth and OpenID

Data translation

Header and body mapping between XML and JSON

Auditing

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 datasheet
03

ARCHITECTURE

One gateway between AI
and everything it touches.

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.

CONSUMERSAI agentsTools called via MCPBusiness applicationsREST and SOAP clientsPartners and SaaSB2B integrationFS SentryVersion 10 security gateway01Identity inAPI keysOAuth · OIDCmTLS · SAML02ProtectOWASP Top 10AV scanningRate and size03TransformSOAP XMLto REST JSONSchema checks04MediateHTTP(S)IBM MQProtocol break05Identity outToken mappingSigned SAMLmTLS outboundPKI engine · FIPS 140-2 cryptographyKeys, certificates, signing, encryption and TLS, managed centrallyPolicy and zero trustContinuous authentication, multi-factor authentication and SSOFull-context logging and monitoringEvery transaction correlated and recorded, including AI logsENTERPRISE SYSTEMSREST servicesJSON APIsSOAP servicesXML and WS-SecurityIBM MQQueues and channelsLegacy and mainframeSystems of recordIdentity storesOkta · AD · PingLDAP directoriesQS DevXAPI catalog · gateway registration · runtime statistics
Conceptual architecture. One policy engine enforces on both the request and the response. Policies, protocols and identity integrations are configured per API.
  1. 01

    Agents call tools

    Agents running on QS Platform 10 call tools generated from your API catalog. Each call enters FS Sentry like any other governed request.

  2. 02

    FS Sentry does the hard parts

    Identity, threat protection, transformation, protocol mediation and PKI are applied by policy, not by agent code.

  3. 03

    Systems see a trusted caller

    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

Inspect the call. Constrain the tool.
Validate the data. Audit the decision.

The same default-deny model applies to every MCP tool call, from the connection to the response the agent receives.

  1. 01ConnectIdentity and TLS
  2. 02MethodProtocol allowlist
  3. 03ToolTool allowlist
  4. 04ArgumentsSchema and range checks
  5. 05ResponseRedact and limit

Denied by default: unknown methods, unknown tools, invalid arguments and sensitive output.

04

GATEWAY VS. CODE

Generate it yourself?
Then you own it forever.

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 written into every app and agentApp or agentApp or agentApp or agentApp or agentRESTSOAPIBM MQMainframe16 integrations, each with its own auth, TLS, parsing and certificatesSecurity in FS SentryApp or agentApp or agentApp or agentApp or agentRESTSOAPIBM MQMainframeFS Sentryone control point8 governed connections, one tested platform
Illustrative. Connections grow with every app and system you add; a gateway keeps them governed in one place.

SECURITY IN EVERY APP AND AGENT

Brittle, costly and unknown.

  • Protocol, identity and crypto code repeated across hundreds of services
  • Every certificate rotation or protocol change becomes a code change
  • An attack surface nobody can see as a whole
  • Maintenance cost that grows with every API
  • Security code no one has proven in production

SECURITY IN FS SENTRY

Tested, measured and managed.

  • Implemented once in hardened product code
  • Measured releases, tested and proven across many enterprises
  • Certificates rotated and consumers onboarded without code changes
  • One known, hardened control point
  • FIPS 140-2 cryptography and full-context audit trails
05

PROVEN IN PRODUCTION

This is what separates
a gateway from a prototype.

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.

AT SCALE

10B+ a day

Mission-critical transactions secured daily across government and commercial enterprises.

RECOGNIZED

KuppingerCole Leader

Named a Leader in the 2025 Leadership Compass for API security and management.

CERTIFIED

Built for high assurance

FIPS, DoD PKI, NIAP NDPP and HITRUST validations support regulated and high-assurance environments.

SINCE 2001

25 years

Patented technology, purpose-built for securing, integrating and governing enterprise APIs.

PROOF POINT · IRS MODERNIZED E-FILE

All U.S. electronic tax filings.

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.

$70T+processed
20+ yearsin production

PROOF POINT · FAA

One platform across very different trust boundaries.

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+.

12Ktransactions per second
~20Kcertificates
2security domains

Trusted by

  • Pepsi Bottling
  • Evergy
  • Belden
  • UK Department for Work and Pensions
  • FAA
  • UK Home Office
  • DISA
  • WellCare
  • AAMC
  • Network Rail

06 · DEPLOY ANYWHERE

Deploy where your systems live.
On-premises, in the cloud or both.

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 10
Hardware appliancesPurpose-built
VMwareVirtual image
DockerContainer image
AWS and AzureCloud images
Windows and LinuxSoftware install
ManagedManaged deployment
07

EDITIONS

Start with the gateway.
Grow into the platform.

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

FS Sentry Flex

  • Any virtual form factor
  • No version lock
  • No per-user costs
  • No per-API costs
  • No per-CPU costs
Go Flex

Annual subscription

FS Sentry Flex+

  • Any virtual form factor
  • No version lock
  • No per-user costs
  • No per-API costs
  • No per-CPU costs
  • Testing and simulation tools
Go Flex+

Product plus annual support

FS Sentry Hardware

  • Purpose-built hardware
  • No version lock
  • No per-user costs
  • No per-API costs
  • No per-CPU costs
  • Testing and simulation tools
Go Hardware

Enterprise platform

QS Platform 10

  • FS Sentry, QS Cortex and QS DevX
  • Agents on the APIs you already secure
  • Public and private models, one set of policies
  • Licensed by capacity, not by token
Explore QS Platform 10

THE DETAILS

Questions,
answered.

Protocols, identity, transformation and how FS Sentry fits QS Platform 10.

Talk to our team
What is FS Sentry?

FS 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.

Is FS Sentry the same as Forum Sentry?

FS Sentry is Forum Sentry at version 10, renamed to align with QS Platform 10. Existing deployments, APIs, policies and integrations carry forward.

Why not let agents call APIs directly?

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.

Which protocols does FS Sentry support?

From HTTP(S) to IBM MQ channel handling, with protocol break and translation between transports.

Which identity methods are supported?

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.

Can FS Sentry secure MCP tool calls?

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.

Can FS Sentry convert SOAP to REST?

Yes. It transforms legacy SOAP XML to REST JSON and back, with header and body mapping, schema validation and XML signatures.

How does FS Sentry relate to QS Platform 10?

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.

Can FS Sentry replace our existing gateway?

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

Where AI meets your enterprise.
Securely, at scale.

See how FS Sentry connects agents to your hardest systems without putting security in their code.