EnigmaSuite

Security policy · NSP-02

Network Security Policy

Document
NSP-02
Version
1.1
Effective
November 18, 2026
Next review
November 2027
Owner
Security Lead
Approved by
Executive Management

1. Purpose and scope

This policy sets the rules Enigmatech Mexico SAPI de CV ("Enigmatech") follows to segregate the networks that carry EnigmaSuite production traffic and to monitor, detect and prevent network threats. It applies to all production and non-production environments, the cloud accounts that host them, and the administrative access used to operate them. It supports the Information Security Policy.

2. Architecture overview

EnigmaSuite production is built from separate layers, each with its own access boundary:

LayerWhere it runsBoundary
EdgeCloudflare global networkAll public traffic to app.enigmasuite.com passes through Cloudflare for DNS, TLS and DDoS protection before it reaches our origin.
ApplicationAWS virtual server (United States)A provider-level firewall exposes only the ports we need. A reverse proxy (nginx) is the only public entry point; the application process listens on the loopback interface and cannot be reached from the internet directly.
Queues and cacheSame application hostBound to localhost only; never exposed to the network.
Database, authentication and storageManaged provider (Supabase, United States)Runs in the provider's network, separate from the application host. It is reached only through authenticated APIs over TLS, and every tenant table is protected by row-level security.
Fiscal file storageAWS S3 (United States)Private buckets reached only with server-side credentials.

3. Network segregation

4. Protection measures

5. Monitoring and detection

6. Change management and review

7. Exceptions and enforcement

Exceptions follow the process in section 7 of the Information Security Policy. Violations may lead to disciplinary action.