Security policy · IRP-07
Incident Response Policy
To report a security incident or vulnerability: [email protected]. For privacy matters and personal data breaches you can also write to our Data Protection Officer at [email protected].
1. Purpose and scope
This policy defines how Enigmatech Mexico SAPI de CV ("Enigmatech") detects, responds to, recovers from and communicates about security incidents affecting the EnigmaSuite Platform, its infrastructure, its personnel or the data it processes, including data our customers authorize us to receive from connected platforms such as Amazon (through the Selling Partner API) and TikTok Shop. It supports the Information Security Policy.
2. Definitions
- Security event: an observable occurrence that may indicate a threat, such as an alert, failed sign-ins or unusual traffic.
- Security incident: an event that compromises, or is reasonably likely to compromise, the confidentiality, integrity or availability of information or systems.
- Personal data breach: a security incident that leads to the accidental or unlawful destruction, loss, alteration, disclosure of, or access to, personal data.
3. Roles and responsibilities
| Role | Responsibilities |
|---|---|
| Incident Commander (Security Lead, or a delegate named by them) | Declares the incident and its severity, coordinates the response, makes containment decisions, keeps the incident record and calls the post-incident review. |
| Technical Lead (Engineering Lead or delegate) | Investigates, contains, eradicates and recovers; preserves evidence; rotates credentials and revokes tokens. |
| Data Protection Officer | Assesses whether personal data is affected, which customers, partners and individuals are involved, and which notifications are required; drafts and sends privacy notifications. |
| Executive Management | Approves external communications, provides resources and makes business decisions (for example, suspending a feature). |
| Legal counsel (external) | Advises on legal obligations and on notifications to authorities. |
| All personnel | Report suspected incidents immediately and follow the Incident Commander's instructions. Do not investigate on your own or discuss the incident outside the response team. |
4. Reporting channels
- Personnel report any suspected incident immediately, and in any case within 1 hour of noticing it, to [email protected] and to the Security Lead directly.
- Customers, partners and researchers can report to [email protected]. We acknowledge reports within 3 business days.
- Automated detection. Alerts from our security operations module (Enigma Shield), health checks, infrastructure providers and vulnerability scanners are routed to the engineering team and triaged under this policy.
5. Severity levels and response times
| Severity | Examples | Response starts within | Status updates |
|---|---|---|---|
| SEV-1 Critical | Confirmed or likely unauthorized access to Restricted data (for example customer personal data, or data obtained from Amazon or TikTok Shop); compromise of production credentials; full outage of the Platform. | 1 hour | Every 4 hours |
| SEV-2 High | Exploitable vulnerability in production; compromise of an employee account or device; major degradation of a module. | 4 hours | Daily |
| SEV-3 Medium | Contained malware on an endpoint; suspicious activity with no evidence of data access. | 1 business day | As needed |
| SEV-4 Low | Policy violations with no data impact; low-risk findings. | 5 business days | As needed |
Severity can be raised or lowered as the investigation progresses. Any incident that may involve personal data is treated as at least SEV-2 until the DPO has assessed it.
6. Response process
- Detection and triage. Confirm whether the event is an incident, assign severity, open an incident record and name the Incident Commander.
- Containment. Limit the damage: isolate affected systems or accounts, block malicious sources, revoke sessions and tokens (including tokens of connected platforms such as Amazon and TikTok Shop), rotate exposed secrets and disable affected features if needed.
- Investigation and evidence. Determine the cause, the timeline, the affected systems and data, and the affected customers and individuals. Preserve logs and artifacts with a documented chain of custody (who collected each item, when, and every hand-off).
- Eradication. Remove the cause: patch the vulnerability, remove malicious code, close unauthorized access paths.
- Recovery. Restore systems from known-good sources or backups, verify integrity, monitor closely for recurrence, and return to normal operation.
- Notification. Notify affected parties as described in section 7.
- Post-incident review. For SEV-1 and SEV-2 incidents, hold a blameless review within 10 business days that documents the root cause, what worked, what did not, and corrective actions with owners and deadlines. Lessons learned update our policies, detections and runbooks.
7. Breach notification
| Who is notified | When | How |
|---|---|---|
| Amazon, when Amazon Information may be involved | Within 24 hours of detecting an actual or suspected security incident, even before it is confirmed. | Email to [email protected], from our Incident Management Point of Contact. |
| Other platform partners whose data is involved (for example TikTok Shop) | Without undue delay, and no later than 24 hours after we confirm an incident affecting data obtained from that partner, or within any shorter period the partner's terms require. | Through the security contact channel the partner designates. |
| Affected customers (for example, sellers who connected TikTok Shop) | Without undue delay, and no later than 72 hours after confirmation, or within any shorter period their contract requires. | Email to the customer's administrators and a notice inside the Platform. |
| Data subjects and authorities | As required by applicable law. Where the customer is the controller of the data, we give the customer the information it needs to notify. Where Enigmatech is the controller, we notify data subjects promptly when the breach significantly affects their rights, as the LFPDPPP requires. | As the law requires. |
Notices include, as far as the information is available: what happened and when; the categories and approximate number of records and individuals affected; the likely consequences; the measures taken and proposed; what the recipient can do to protect themselves; and a contact point. If some information is not yet available, we send an initial notice on time and follow up as the investigation progresses. We cooperate with partners and customers throughout their own investigations and notifications. Notifying regulators is our own responsibility, and we never speak on behalf of Amazon or any other partner unless it asks us to in writing.
7.1 Incidents that may affect Amazon
The incident types that may affect Amazon or Amazon customers, and that always trigger the Amazon notification above, are: unauthorized access to, or disclosure of, Amazon Information (including buyer personal information); compromise of our Amazon application credentials or of a seller's refresh token; loss or theft of a device or document holding Amazon Information; a vulnerability that exposes Amazon Information; and abuse of the Selling Partner API through our application. Each type has its own runbook. When we detect a seller misusing our application to abuse Amazon or its customers, we block that seller's access and report it to [email protected].
7.2 Incident Management Point of Contact
The Security Lead is our Incident Management Point of Contact (IMPOC) for Amazon and the other platform partners, with the Engineering Lead as backup. Their name, email and phone number are registered with each partner and kept up to date, and they can be reached at any time during an active incident.
8. Records
Every incident is recorded with its timeline, severity, affected assets and data, actions taken, notifications sent and corrective actions. Incident records are kept for at least 3 years.
9. Preparation and testing
- Runbooks cover the most likely scenarios: credential leaks and rotation, compromised accounts, database access rollback, authentication lockouts and availability incidents.
- The response team holds a tabletop exercise at least once a year, including at least one scenario that involves Amazon Information.
- Contact details for the response team, infrastructure providers and platform partners are kept up to date.
10. Review
This policy and its runbooks are reviewed at least every six months, after every SEV-1 incident, and after any major change to our infrastructure or systems. Executive Management approves each version.