Security policy · ACP-05
Access Control Policy
1. Purpose and scope
This policy defines how Enigmatech Mexico SAPI de CV ("Enigmatech") grants, reviews and removes access to its systems and to personal data. It covers personnel access to internal and production systems, and the access controls the EnigmaSuite Platform enforces for customers and their users. It supports the Information Security Policy.
2. Principles
- Least privilege. Each person and each service gets only the permissions needed for its task, for as long as it needs them.
- Need to know. Personal data is accessible only to those who need it to deliver the service, provide support at a customer's request, or handle an incident.
- Deny by default. Access that has not been explicitly granted is denied.
- Individual accountability. Every account belongs to one identified person or to one documented service with a named owner. Generic, shared or default accounts are not allowed.
- Segregation of duties. No one approves their own access request or deploys their own unreviewed change to production.
3. Personnel access to Enigmatech systems
3.1 Provisioning
- Access is requested in writing, stating the system, the role and the business reason.
- The system owner approves it; privileged access (production servers, database administration, cloud account administration, secrets) also requires Security Lead approval.
- Every grant is recorded so it can be reviewed later.
3.2 Authentication
- Unique named accounts with multi-factor authentication. MFA is required on every system that stores or processes Amazon Information or other Restricted data (see the Security Baseline Standard, which also sets password length, complexity, age, expiration and reuse rules).
- Accounts lock after no more than 10 consecutive failed sign-in attempts on every system that supports it.
- Server administration uses personal SSH keys; password login is not used.
- Service credentials (API keys, database service keys) are held in the managed secrets vault or in server configuration readable only by the application's account, and are rotated when a person with access leaves or a compromise is suspected.
3.3 Access to production data
- Direct access to the production database is limited to a small number of named engineers.
- Personnel access customer data only to deliver or support the service, at the customer's request, to investigate an incident, or to meet a legal obligation.
- Personnel do not export customer data to personal devices or tools. See the Data Classification and Encryption Policy.
3.4 Reviews
- Privileged access, and all access to systems that store or process Amazon Information or other Restricted data, is reviewed every quarter, with documented evidence of the review and of the changes it produced. All other access is reviewed at least every six months.
- Access that is no longer needed is removed as soon as the review finds it.
3.5 Changes and removal
- When a person changes role, access that the new role does not need is removed.
- When a person leaves, all access is revoked within 24 hours (privileged access the same business day), and any shared secret they could read is rotated.
4. Access control inside the Platform
EnigmaSuite is a multi-tenant platform. Each customer (an "organization") can reach only its own data.
- Tenant isolation. Every tenant table carries an organization identifier, and PostgreSQL row-level security policies restrict every read and write to the organization in the user's signed session token. The application adds a second organization filter to every query.
- Two-layer authorization. An action is allowed only if (1) the module is enabled for the organization and (2) the user's role grants that action. Roles are managed by each customer's administrators, down to individual sections and actions of each module (view, create, edit, delete and others).
- Authentication. Users sign in through our managed authentication provider. Passwords are stored only as salted hashes. Multi-factor authentication (TOTP) is available to every user. Sessions use short-lived signed tokens that are refreshed automatically.
- Privileged operations. Operations that bypass row-level security run only on the server, check the caller's permissions themselves, and are never exposed to anonymous users unless they are designed as public endpoints.
5. Access to data from connected platforms (including Amazon and TikTok Shop)
- A connection to Amazon, TikTok Shop or any other sales channel is created only by an administrator of the customer organization, through that platform's own authorization flow. We never ask a seller for its passwords or access keys.
- The resulting access and refresh tokens are stored encrypted in the managed secrets vault. The database keeps only references to them, and they are never sent to browsers.
- Tokens are used only by our servers, only for the shop that authorized them, and only for the features the seller uses.
- For Amazon, our application's Login with Amazon client secret is kept in the vault and rotated at least every 12 months, immediately when a compromise is suspected, and whenever Amazon requires it. Restricted data, such as a buyer's shipping address, is requested with a short-lived Restricted Data Token for a single order and only for merchant-fulfilled shipping.
- Data received from the channel is stored under the seller's organization and protected by the same tenant isolation and role permissions as the rest of the seller's data.
- When a seller disconnects the channel or asks us to, the stored tokens are deleted within 30 days (see the Data Retention and Deletion Policy).
6. Logging
Sign-ins, failed sign-ins, role and permission changes, and other security-relevant actions are recorded in the audit log with a server-side timestamp. Audit logs are restricted to authorized administrators and are reviewed during incident investigations and access reviews.
7. Exceptions and enforcement
Exceptions follow the process in section 7 of the Information Security Policy. Unauthorized access, or an attempt to get around access controls, is a serious violation and may lead to disciplinary and legal action.