Publishing Internal APIs from DMZ Without Direct LAN Connections: Five Tested Architectures
When an API gateway is placed in the DMZ and corporate security policy prohibits any connections from the DMZ into the internal LAN, the most obvious proxying pattern becomes impossible. Business requirements nevertheless demand that consumers receive synchronous HTTP responses, making a full rewrite of integration contracts prohibitively expensive.
Over the past year the team at Neoflex evaluated five architectural options on the NEOMSA APIM platform, which is built on WSO2 components including the gateway, Micro Integrator, and developer portal. Three patterns reached working laboratory environments, one underwent full load testing, and the remaining two were validated through architecture reviews and security approvals.
Variant 1: Custom request-reply over Kafka
Kafka is deployed in the DMZ. The gateway writes requests to a topic; an internal Micro Integrator instance connects outbound to consume them, invokes the target system, and publishes replies to a second topic. Because Kafka lacks native reply-to semantics, the team implemented correlation, partition-based routing, dead-letter handling, and offset management in approximately 2,500 lines of Java packaged as a custom mediator. The solution works but introduces significant maintenance obligations and removes centralized policy enforcement.
Variant 2: JMS request-reply with ActiveMQ Artemis
Replacing Kafka with ActiveMQ Artemis eliminates all custom code. Both sides use standard JMS mediators inside Micro Integrator. The broker handles correlation identifiers, message expiration, and selective consumption. Load tests demonstrated a sustained 50 requests per second with 95th-percentile latency near 100 ms. Limitations include the inability to stream large or unknown-size responses and the requirement for idempotency keys on state-changing operations.
Variant 3: Reverse HTTP via HAProxy
An internal node initiates a persistent HTTP/2 connection to the DMZ gateway; roles are then reversed so the gateway treats the tunnel as an upstream. No DMZ-to-LAN firewall rule is required, no custom code is written, and the call remains ordinary synchronous HTTP. The mechanism is still marked experimental in HAProxy 2.9+, requiring careful configuration of connection reuse and keep-alive parameters.
Variant 4 & 5: Dual gateways with narrow DMZ-to-LAN rule
When security permits a tightly scoped rule allowing mTLS-authenticated traffic on specific ports, two simpler topologies become viable: a single management plane controlling gateways in both zones, or two independent NEOMSA APIM installations. Both preserve full policy, throttling, and key-management capabilities in one administrative domain.
The decisive question for any organization facing the same constraint is whether a narrow DMZ-to-LAN firewall exception with mutual certificate authentication can be obtained. The answer immediately eliminates or validates half of the candidate architectures.
Related articles
Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour
A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.
Yandex Tests Compass Device for Taxi Navigation During GPS Outages
Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.
Apple Attributes Widespread Service Outage to Faulty Internal IT Update
Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.
Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay
On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.