Security policy · NSP-02
Network Security Policy
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:
| Layer | Where it runs | Boundary |
|---|---|---|
| Edge | Cloudflare global network | All public traffic to app.enigmasuite.com passes through Cloudflare for DNS, TLS and DDoS protection before it reaches our origin. |
| Application | AWS 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 cache | Same application host | Bound to localhost only; never exposed to the network. |
| Database, authentication and storage | Managed 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 storage | AWS S3 (United States) | Private buckets reached only with server-side credentials. |
3. Network segregation
- Tenant segregation. Every customer's data is logically isolated at the database layer: each tenant row carries its organization identifier and row-level security policies deny access across organizations. The application adds a second, organization-scoped filter on every query.
- Tier segregation. The database tier runs outside the application host, and the internal services on the application host (application process, queues, cache) are bound to the loopback interface. Only the reverse proxy accepts connections from outside.
- Environment segregation. Development and testing run as separate application instances with their own domains, configuration and credentials. Production credentials are never used in non-production, and production personal data must not be copied into non-production environments.
- Workload segregation on shared hosts. Where a host runs more than one workload, each workload runs under its own unprivileged operating-system account, application directories and secret files are readable only by the application's own account, and the web server blocks script execution in upload and storage directories.
- Privileged credentials. Service-level credentials for the database and third-party APIs exist only on servers and in the managed secrets vault. They are never sent to browsers or mobile apps.
4. Protection measures
- Encryption in transit. HTTPS (TLS 1.2 or higher) is required on every public endpoint; plain HTTP is redirected to HTTPS. Calls to third-party APIs, including the Amazon Selling Partner API and TikTok Shop, use HTTPS. TLS 1.3 is used wherever both ends support it, and unencrypted protocols are disabled even when unused.
- Edge protection and web application firewall. Every internet-facing endpoint of the Platform sits behind a web application firewall: public traffic to our domains passes through Cloudflare, whose managed rules filter common web attacks (including the OWASP Top 10) and absorb volumetric attacks before they reach the origin server, and the managed database, authentication and storage APIs are protected by our provider's own edge and abuse protections.
- Intrusion detection and prevention. Edge threat detection, the providers' threat monitoring and the detection rules of our security operations module (Enigma Shield) together act as our intrusion detection and prevention capability; suspicious sources are blocked at the edge.
- Firewalls. The provider firewall allows only the ports required for web traffic and administration. Rules are default-deny and changes require Security Lead approval.
- Administrative access. Server administration uses SSH with key-based authentication only. Access to cloud consoles (AWS, Supabase, Cloudflare, GitHub) requires individual accounts with multi-factor authentication.
- Application-layer controls. Security headers on API responses, strict CORS rules, per-key rate limiting on public APIs, signed and time-limited tokens for internal worker calls, and verification of inbound webhooks (signature or shared secret) where the sending platform supports it.
- Hardening. Unused services are disabled, operating system security updates are applied under the Vulnerability and Threat Management Procedure, and default credentials are never used.
5. Monitoring and detection
- Web server, application and database logs are collected and kept access-restricted.
- Authentication events, permission changes and other security-relevant actions are written to an audit log with server-side timestamps.
- Our internal security operations module (Enigma Shield) evaluates security events against detection rules, deduplicates alerts and opens incidents with response deadlines.
- Health checks monitor the availability of the application, database and queues; failures alert the engineering team.
- Edge traffic analytics are reviewed when investigating anomalies, and suspicious sources can be blocked at the edge.
- Alerts are triaged under the Incident Response Policy.
6. Change management and review
- Changes to firewall rules, DNS, TLS settings and reverse-proxy configuration are recorded and approved before they are applied.
- Firewall rules and exposed ports are reviewed every quarter.
- The Security Lead keeps an up-to-date network architecture diagram and the evidence of how each control in this policy is deployed and managed.
- This policy is reviewed at least once a year and after any significant change to the architecture.
7. Exceptions and enforcement
Exceptions follow the process in section 7 of the Information Security Policy. Violations may lead to disciplinary action.