Security policy · VTM-08
Vulnerability and Threat Management Procedure
1. Purpose and scope
This procedure describes how Enigmatech Mexico SAPI de CV ("Enigmatech") identifies, assesses, fixes and verifies vulnerabilities, and how it keeps track of threats relevant to the EnigmaSuite Platform. It covers application code, third-party dependencies, servers, cloud configuration, the database and endpoints. It supports the Information Security Policy.
2. Sources of vulnerabilities and threats
| Source | What it covers | Frequency |
|---|---|---|
| Automated dependency alerts (GitHub Dependabot) | Known vulnerabilities in open-source packages; update pull requests are opened automatically. | Weekly, plus immediate security alerts |
| Dependency audit gate in CI | Every pull request is checked, and the build fails if the number of known dependency vulnerabilities goes up. | Every pull request |
| Static application security testing (CodeQL) | Security flaws in our own code, such as injection and unsafe data flows, checked against the OWASP Top 10. | Before every production release, weekly, and on demand |
| Vulnerability scanning of production | The Platform's internet-facing endpoints, servers and cloud configuration. | At least every 30 days, and after every significant change |
| Secret scanning in CI | Credentials committed by mistake; the build fails if one is found. | Every pull request |
| Database security advisors | Tables without row-level security, overly broad function grants and similar misconfigurations. | After schema changes, and monthly |
| Code review | Every change to production goes through a pull request review before it is merged, with attention to authorization, tenant isolation and data handling. | Every pull request |
| Vendor and community advisories | Security notices for the operating system, Node.js, PostgreSQL, our infrastructure providers and the platforms we integrate with. | Continuous |
| Security monitoring (Enigma Shield) | Detections and alerts on security events in production. | Continuous |
| External reports | Reports from customers, partners and researchers to [email protected]. | Continuous |
3. Assessment and prioritization
Each finding is recorded and rated by the Security Lead or the Engineering Lead. The rating starts from the CVSS score where one exists, and is adjusted for:
- whether the vulnerable code or component is reachable in our deployment;
- whether it is exposed to the internet or only internally;
- whether exploitation is known to be happening; and
- the classification of the data at risk (findings that could expose Restricted data, such as customer personal data or data obtained from Amazon or TikTok Shop, are rated at least High).
4. Remediation deadlines
| Severity | Deadline to fix or mitigate |
|---|---|
| Critical, or any vulnerability being actively exploited | Mitigation within 72 hours; fix within 7 days |
| High | 30 days |
| Medium | 90 days |
| Low | 180 days, or the next planned maintenance |
Deadlines start when the finding is confirmed. Operating system security updates on production servers are applied at least monthly, and critical ones within the deadlines above.
5. Remediation and verification
- The fix is developed on a branch and goes through the normal review and CI checks.
- It is deployed through the automated pipeline, which can roll back automatically if the deployment fails.
- The finding is verified as closed (rescan, test or manual check) and the record is updated.
- If the vulnerability may have been exploited before the fix, it is handled as an incident under the Incident Response Policy.
6. Exceptions and risk acceptance
If a deadline cannot be met (for example, no fix exists yet), the owner documents compensating controls and a new target date, and the Security Lead approves the exception for a limited period. Exceptions for Critical findings also require Executive Management approval.
7. Security assessments
Significant architectural changes, new integrations with external platforms and new public endpoints receive a security review before release. An independent penetration test of the Platform (network, cloud configuration, web application, APIs, database and storage, and the mobile apps) is performed at least every 365 days using an industry-recognized methodology such as the OWASP Testing Guide or PTES, and also after major architectural changes. Its findings are handled under this procedure, and a second test confirms that Critical and High findings were fixed.
8. Responsible disclosure
We welcome reports of security issues at [email protected]. We acknowledge them within 3 business days, keep the reporter informed, and do not take action against researchers who act in good faith, avoid privacy violations and service disruption, and give us reasonable time to fix the issue before disclosing it.
9. Reporting
The Security Lead reviews open findings and deadlines every month and reports overdue items and trends to Executive Management.