Security policy · SDL-14
Secure Development and Credential Management Standard
1. Purpose and scope
This standard sets the rules Enigmatech Mexico SAPI de CV ("Enigmatech") follows to develop and change the EnigmaSuite Platform securely, and to keep the credentials it uses (API keys, client secrets, refresh tokens, database keys and webhook secrets) from being exposed. It applies to all code, infrastructure configuration and automation, and to everyone who writes or approves changes. It supports the Information Security Policy.
2. Development lifecycle
- Design. Features that handle personal data or connect a new partner platform get a security and privacy review before they are built, covering data flows, the minimum data needed, tenant isolation and retention.
- Secure coding. Code follows the OWASP Top 10 guidance: parameterized queries, output encoding, server-side authorization on every request, tenant filters on every query, validation of every input, and verification of inbound webhooks.
- Review. Every change reaches production through a pull request reviewed by someone other than its author. The person who approves a change is not the same person who tests and releases it.
- Automated checks before every release. Linting, type checking, unit tests, secret scanning, a dependency vulnerability gate and static application security testing (CodeQL) run before code is released to production. A failed check blocks the release.
- Release. Deployments run through an automated pipeline that takes a snapshot first and rolls back automatically if the release fails. Manual changes to production are not allowed outside an approved incident procedure.
3. Environments
- Development, testing and production are separate, with their own domains, configuration and credentials.
- Production credentials are never used outside production.
- Production personal data, including any data received from Amazon, is never copied into development or testing; tests use synthetic data.
4. Credential management
- Never in code. Credentials are never written in source code, configuration files committed to a repository, documentation, wikis, tickets, spreadsheets, chat or email. This includes Login with Amazon client secrets and refresh tokens, which are credentials.
- Where they live. Credentials are stored in the managed secrets vault, or in server configuration files readable only by the application's own account. Database tables keep only references to vault entries.
- Automatic blocking. A pre-commit check and the CI pipeline scan every change for credentials and block it if one is found. A credential that reaches a repository is treated as compromised: it is rotated, not just deleted.
- Private repositories. Our source code repositories are private, with access granted individually and reviewed every quarter.
- Rotation. Credentials are rotated at least once a year, immediately when a compromise is suspected, when a person who could read them leaves, and whenever a partner platform requires it.
- Least privilege. Each service gets its own credential with the minimum permissions it needs. Credentials that bypass row-level security are used only on servers, never in browsers or mobile apps.
- Partner tokens. Sellers authorize partner platforms through the platform's own consent flow; we never ask for their passwords or access keys. Tokens are used only for the seller that issued them.
5. Dependencies
Third-party packages come only from official registries, are pinned through lockfiles, and are monitored for vulnerabilities and fixed within the deadlines of the Vulnerability and Threat Management Procedure.
6. Review
This standard is reviewed at least once a year and after any incident caused by a code change or an exposed credential.