NEOMSA APIM

Publishing Internal APIs from DMZ Without Direct LAN Connections: Five Tested Architectures

When an API gateway resides in the DMZ but security policies forbid outbound connections into the LAN, organizations must adopt alternative patterns to expose internal services synchronously. The article examines five production-ready approaches built on the NEOMSA APIM platform, ranging from custom request-reply logic over Kafka to zero-code solutions using ActiveMQ Artemis and experimental reverse HTTP in HAProxy. Each pattern is evaluated against criteria such as the need for DMZ-to-LAN firewall rules, volume of custom code, support for streaming responses, and measured performance. Load tests on the Artemis-based bridge reached 50 requests per second with a 95th percentile latency of approximately 100 ms, while the Kafka implementation required roughly 2,500 lines of Java to emulate missing reply semantics. The analysis highlights trade-offs in operational complexity, vendor support implications, and security posture, particularly the benefit of preventing any outbound initiation from the DMZ.

How to Grant AI Agents Access to Internal APIs via MCP: Key Questions Security Teams Will Ask

As AI agents increasingly need to call internal APIs, security teams focus on three core questions: who granted access, how to revoke it, and how to investigate incidents after the fact. The answers lie in operation-level access control rather than traffic inspection alone. MCP, now managed by the Agentic AI Foundation under the Linux Foundation, has become the standard for connecting AI agents to enterprise systems with hundreds of millions of SDK downloads monthly. The article details how NEOMSA APIM implements MCP servers, tool publication from OpenAPI specs, subscription-based scopes, and 15 independent security checks. It explains why classic traffic filters fail against valid but unauthorized tool calls and stresses the need for owner approval, application-specific identities, and proper identity propagation through token exchange. Rate limiting at the subscription level and business-object validation are presented as essential controls to prevent overreach and duplication.

NEOMSA APIM 4.6.0 Eliminates All Critical and High Vulnerabilities Registered in FSTEC BDU

Neoflex has released NEOMSA APIM 4.6.0 with a primary focus on strengthening the security of the platform's supply chain. The team generated an SBOM in CycloneDX format, scanned components and dependencies using Grype, and cross-referenced findings against the FSTEC BDU database. This process reduced total registered vulnerabilities from 57 to 7, completely removing all 10 Critical and 24 High issues. The platform now meets the formal Security Gate criterion requiring zero Critical or High vulnerabilities from the FSTEC database in the final build. Remaining Medium findings are documented and tracked for future updates. The release provides customers with a verified, transparent component inventory that simplifies compliance and integration reviews.