1. Purpose and Scope
This Incident Response Policy ("Policy") establishes the procedures for detecting, reporting, containing, investigating, and remediating security incidents and data breaches affecting the NezenX Platform, User data, or business operations.
This Policy supplements the Privacy Policy Section 10 (Data Security and Breach Notification) and the Information Security Policy Section 14. Where this Policy provides additional procedural detail, it takes precedence.
This Policy applies to all NezenX personnel, contractors, and any individual who becomes aware of a security incident or suspected breach involving NezenX systems or data.
Current state: This Policy formalizes NezenX's incident response procedures. Prior to this Policy, incident response was handled on an ad-hoc basis by senior management and the development team. This Policy establishes a structured framework to improve response effectiveness.
2. Incident Classification
NezenX classifies security incidents into three severity levels:
Critical
Active, confirmed breach of User data or Platform security. Immediate threat to operations, data, or funds.
Unauthorized access to User accounts, data exfiltration, wallet compromise, Platform-wide outage, ransomware
Immediate (within 1 hour of detection)
High
Confirmed or likely security incident with significant potential impact. No confirmed data loss yet.
Unauthorized access attempt (partially successful), vulnerability actively exploited, single-account compromise, suspicious admin activity
Within 4 hours of detection
Medium
Suspected or low-impact incident requiring investigation. No confirmed compromise.
Failed brute-force attempts, phishing targeting team members, minor vulnerability discovered, unusual system behavior
Within 24 hours of detection
Severity | Description | Examples | Response Time |
|---|---|---|---|
Critical | Active, confirmed breach of User data or Platform security. Immediate threat to operations, data, or funds. | Unauthorized access to User accounts, data exfiltration, wallet compromise, Platform-wide outage, ransomware | Immediate (within 1 hour of detection) |
High | Confirmed or likely security incident with significant potential impact. No confirmed data loss yet. | Unauthorized access attempt (partially successful), vulnerability actively exploited, single-account compromise, suspicious admin activity | Within 4 hours of detection |
Medium | Suspected or low-impact incident requiring investigation. No confirmed compromise. | Failed brute-force attempts, phishing targeting team members, minor vulnerability discovered, unusual system behavior | Within 24 hours of detection |
Severity classification is determined by the incident lead (see Section 3) based on initial assessment. Severity may be escalated or de-escalated as investigation progresses.
3. Incident Response Roles
Incident Lead — senior management (or the Compliance Officer when appointed). Responsible for:
- classifying the incident severity;
- coordinating the response;
- making decisions on containment and remediation actions;
- authorizing external communications and regulatory notifications;
- conducting or overseeing the post-incident review.
Technical Lead — development team. Responsible for:
- technical investigation (log analysis, system forensics);
- implementing containment measures (blocking access, isolating systems);
- applying technical fixes and patches;
- restoring systems from backups if needed.
Operations Lead — operations team. Responsible for:
- identifying affected User Accounts;
- communicating with affected Users;
- coordinating with Card Issuing Partners on card-related incidents;
- documenting the incident timeline and actions taken.
All personnel — responsible for immediately reporting any suspected incident per Section 4.
4. Detection and Reporting
Internal detection: Incidents may be detected through:
- monitoring of system logs and alerts;
- reports from team members who observe unusual activity;
- automated security alerts from infrastructure providers;
- reports from Card Issuing Partners or card networks;
- routine security reviews.
External reports: Incidents may be reported by:
- Users who notice unauthorized activity on their Accounts;
- security researchers via responsible disclosure ([email protected]);
- third-party service providers;
- regulatory authorities or law enforcement.
Reporting obligation: Any NezenX personnel who suspects a security incident must report it immediately to senior management through the fastest available channel (Telegram direct message or phone call for Critical/High; email acceptable for Medium). The report should include:
- what was observed;
- when it was observed;
- which systems or data may be affected;
- any immediate actions already taken.
Do not attempt to investigate or remediate independently. Do not discuss the incident with external parties until authorized by the Incident Lead.
5. Containment
Upon confirming an incident, the immediate priority is containment to prevent further damage:
Critical incidents:
- isolate affected systems or accounts immediately;
- suspend affected Virtual Cards;
- revoke compromised credentials or access tokens;
- block the attack vector if identified (IP blocking, firewall rules);
- preserve evidence (do not delete logs or modify affected systems).
High incidents:
- restrict access to affected systems pending investigation;
- enforce password resets for potentially compromised accounts;
- increase monitoring on related systems.
Medium incidents:
- document the observed activity;
- increase monitoring on the affected area;
- assess whether escalation to High is warranted.
Evidence preservation: During containment, all logs, screenshots, and system state information must be preserved. Do not restore from backup until evidence has been captured and documented.
6. Investigation
The Technical Lead conducts the investigation to determine:
- the root cause of the incident;
- the attack vector or vulnerability exploited;
- the scope of impact (which systems, data, or Users affected);
- whether data was accessed, modified, or exfiltrated;
- the timeline of the incident (when it started, when it was detected, how long it lasted);
- whether the incident is ongoing or has been contained.
Investigation activities may include:
- log analysis (authentication logs, access logs, error logs);
- review of system configurations and recent changes;
- analysis of network traffic patterns;
- review of affected User account activity;
- consultation with cloud infrastructure providers;
- engagement of external forensic specialists if the incident exceeds internal capabilities.
The investigation is documented in an Incident Report (see Section 9).
7. Remediation and Recovery
Based on investigation findings, the Technical Lead implements remediation measures:
- patching the vulnerability that was exploited;
- removing unauthorized access or malicious code;
- restoring affected systems from verified clean backups;
- resetting credentials for all potentially affected accounts;
- updating security controls to prevent recurrence.
System recovery: Systems are restored to normal operation only after:
- the root cause has been identified and addressed;
- containment measures confirm the threat is neutralized;
- the Incident Lead authorizes the return to normal operations.
User remediation: For incidents affecting Users:
- affected Users are notified (per Section 8);
- affected Virtual Cards are reissued if compromised;
- Account credentials are reset;
- Account activity is reviewed for unauthorized transactions;
- affected Users are offered guidance on protective measures.
8. Communication and Notification
8.1. Internal communication
The Incident Lead maintains communication with all response team members through designated secure channels throughout the incident.
8.2. User notification
For incidents involving User data:
- affected Users are notified as soon as practicable after the scope of the breach is assessed;
- notifications include: a description of what happened, what data was affected, what NezenX is doing, and what Users should do (e.g., change passwords, monitor accounts);
- notifications are delivered via email and, where urgent, via the User's Telegram support group.
8.3. Regulatory notification
For data breaches likely to result in significant harm:
- the Personal Data Protection Commission (PDPC) of Singapore is notified within three (3) calendar days of NezenX's assessment that the breach meets the notification threshold, as required by the PDPA;
- other regulatory authorities are notified as required by applicable law.
8.4. Card Issuing Partner notification
For incidents affecting card data or card operations:
- the Card Issuing Partner is notified immediately;
- NezenX cooperates with the Partner's own incident response procedures;
- card network notification requirements are handled by the Card Issuing Partner.
8.5. Public communication
Public statements about security incidents are authorized only by senior management. NezenX does not disclose incident details publicly unless required by law or where disclosure is necessary to protect Users.
9. Incident Documentation
Every confirmed incident (High and Critical) is documented in an Incident Report containing:
- incident reference number;
- date and time of detection;
- date and time of containment;
- severity classification;
- description of the incident;
- root cause analysis;
- scope of impact (systems, data, Users affected);
- containment and remediation actions taken;
- notifications sent (Users, regulators, partners);
- timeline of key events and decisions;
- lessons learned and recommendations.
Medium-severity incidents are documented in a simplified incident log with key details and outcome.
Incident Reports are retained in accordance with the Data Retention Policy (minimum five (5) years).
10. Post-Incident Review
Within fourteen (14) days of incident closure, the Incident Lead conducts a post-incident review to:
- evaluate the effectiveness of the response;
- identify what worked well and what could be improved;
- determine whether existing controls were adequate;
- recommend policy, process, or technical changes to prevent recurrence;
- update the Risk Assessment Framework if the incident reveals previously unidentified risks.
Findings from the post-incident review are documented and shared with senior management. Action items from the review are tracked to completion.
11. Testing and Preparedness
NezenX intends to test its incident response procedures through periodic exercises, including:
- tabletop exercises simulating different incident scenarios;
- review of roles and contact information to ensure they are current;
- verification that communication channels and escalation paths function as expected.
Testing will be conducted at least annually once the Compliance Officer is appointed, with results documented and used to improve this Policy.
12. Amendments
NezenX may update this Policy at any time. Material changes will be communicated to Users via email and/or Platform notification at least thirty (30) days prior to the effective date.
Continued use of the Platform after the effective date of an amendment constitutes acceptance of the updated Policy.
13. Contact
To report a security incident or suspected breach:
- General complaints: [email protected]
- Formal complaints: [email protected]
- Escalation: [email protected] (subject line: "Complaint Escalation — [Reference Number]")