How to publish an internal API from a DMZ when LAN connections are prohibited: five approaches

In this article, experts from Neoflex address the challenge of ensuring network security during API integration. The authors share their experience in publishing internal APIs from a demilitarized zone (DMZ) under strict security policies where direct connections to the local area network (LAN) are prohibited. All five architectural schemes presented are implemented using NEOMSA APIM, a Russian API management platform. The material serves as a practical guide for system architects and DevOps engineers facing the need to organize secure communication between network segments. The article explores various approaches to traffic proxying and routing that maintain perimeter integrity while ensuring service availability. This content is valuable for professionals involved in designing corporate API gateways and configuring network policies within secure infrastructures.
This is a summary. Read the full article at the original source:
HabrRelated stories
The DRP no one tested: why recovery plans fail when you need them most
The author, Ilya, an expert in information systems support, addresses the critical issue of testing Disaster Recovery Plans (DRP). The article emphasi…
SeverVersum: How Severstal Created a Russian Replacement for VersionDog with an AI Assistant for Industry
Severstal has introduced 'SeverVersum,' a proprietary version control system for industrial automation designed as an import-substituting alternative…
A recent discussion on Hacker News explores the unique design language and technical constraints of DVD menus. Often overlooked in the era of streamin…



