EnigmaSuite

Security policy · ISP-01

Information Security Policy

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

1. Purpose

This policy establishes the information security program of Enigmatech Mexico SAPI de CV ("Enigmatech", "we"), the company that develops and operates the EnigmaSuite software-as-a-service platform (the "Platform"). The program protects the confidentiality, integrity and availability of the information we handle, with particular care for personal data that we process on behalf of our customers and data that our customers authorize us to receive from connected platforms such as Amazon (through the Selling Partner API) and TikTok Shop.

2. Scope

This policy applies to:

3. Security objectives

4. Roles and responsibilities

RoleResponsibilities
Executive ManagementApproves this policy and its supporting documents, provides resources, accepts residual risks.
Security LeadOwns the security program: maintains the policies, the risk register and the asset inventory; coordinates incident response and vulnerability management; approves exceptions.
Data Protection Officer (DPO)Oversees personal data processing and privacy compliance, handles data subject and customer privacy requests, leads breach notification assessments. Contact: [email protected].
Engineering LeadEnsures secure development and change management, reviews code and infrastructure changes, keeps dependencies and systems patched.
All personnelFollow this policy and its standards, protect credentials and devices, and report suspected incidents immediately to [email protected].

In a small team one person may hold more than one role. Even so, no one approves their own access request, their own exception or their own code change to production.

5. Program components

5.1 Risk management

The Security Lead maintains a risk register. Risks are assessed at least once a year and whenever there is a significant change (a new data source, a new subprocessor, a new hosting component or a major feature). Each risk is rated by likelihood and impact and has an owner, a treatment decision and a review date. Executive Management reviews the risk assessment process and the register at least once a year and accepts residual risks.

5.2 Asset management

We keep an inventory of cloud accounts, production systems, data stores, domains and endpoints, each with an assigned owner. The inventory, including baseline configurations of production systems, is updated at least every quarter. Information assets are classified according to the Data Classification and Encryption Policy.

5.3 Access control

Access is denied by default and granted on least privilege and need-to-know, requires unique accounts and multi-factor authentication, and is reviewed every quarter for systems that hold Restricted data. See the Access Control Policy.

5.4 Cryptography

Sensitive data is encrypted in transit (TLS) and at rest, and secrets are kept in a managed vault. See the Data Classification and Encryption Policy.

5.5 Network and infrastructure security

Production is protected by an edge network, host firewalls, loopback-only internal services and a managed database isolated from the application host. See the Network Security Policy.

5.6 Endpoints and daily operations

All devices run anti-malware protection, full-disk encryption and automatic updates; personnel follow a security baseline for screen locking, passwords, MFA and a clear desk. See the Endpoint Protection Standard and the Security Baseline Standard.

5.7 Secure development and change management

5.8 Vulnerability and threat management

Dependencies, code and systems are scanned continuously and fixed within severity-based deadlines. See the Vulnerability and Threat Management Procedure.

5.9 Logging and monitoring

The Platform records audit logs of significant actions (authentication, permission and configuration changes) with server-side timestamps. Security events feed our internal security operations module (Enigma Shield), which raises alerts and tracks incidents with response deadlines. Access to logs is restricted, logs are protected against modification, and security logs are kept for at least 12 months. See the Logging and Monitoring Standard.

5.10 Incident management

Incidents are handled under a documented process with defined roles, severity levels and notification timelines. See the Incident Response Policy.

5.11 Business continuity and backups

5.12 Supplier and subprocessor management

Before we engage a provider that will process customer data, we review its security posture (for example SOC 2 or ISO/IEC 27001 reports) and sign data protection terms at least as protective as our own. Each such provider is reassessed at least once a year. Data that partner platforms such as Amazon give us is shared only with providers whose security standards are at least as strict as ours. Our core infrastructure providers maintain independent security certifications. Current subprocessors are listed in the Privacy Policy.

5.13 Personnel security

5.14 Physical security

We do not operate our own data centers. Production runs in the facilities of cloud providers that hold independent certifications for physical and environmental security. Workplace rules are set out in the Security Baseline Standard.

5.15 Privacy

Personal data is processed according to the Personal Data Protection Policy, the Data Retention and Deletion Policy and the public Privacy Policy. Data received from Amazon is also handled under the Amazon Selling Partner API Data Protection Statement.

5.16 Partner platform requirements

When a partner platform sets security or data protection requirements, they become part of this program. We follow the Amazon Services API Developer Agreement, the Amazon Data Protection Policy and the Amazon Acceptable Use Policy for all information received through the Amazon Selling Partner API, as well as the API terms of TikTok Shop, Google and the other platforms we integrate with. We keep the records that show compliance for the term of each agreement and at least 12 months after it ends, certify compliance in writing when a partner asks, and cooperate with partner audits.

6. Compliance and enforcement

Compliance with this policy is checked through access reviews, endpoint attestations, automated CI controls and incident post-mortems. A violation may lead to disciplinary action, up to termination of employment or contract, and to legal action where applicable.

7. Exceptions

Any exception must be requested in writing, justified, approved by the Security Lead, time-limited (maximum 6 months, renewable) and, where possible, covered by compensating controls. Exceptions are recorded in the risk register.

8. Review

This policy and its supporting documents are reviewed at least once a year, and also after a significant incident or a significant change to the Platform, the organization or applicable law. Changes are approved by Executive Management and published in the Trust Center.

9. Supporting documents