Incident Response
6MM maintains a structured incident response framework to ensure system stability, partner confidence, and rapid recovery in the event of security or operational incidents.
As a professional trading infrastructure, 6MM prioritizes containment, transparency, and continuous improvement when handling incidents.
What Is a Security Incident?
An incident may include, but is not limited to:
Unauthorized system access
Abnormal trading behavior or system anomalies
Infrastructure outages or service degradation
Data integrity or configuration issues
API or integration-related security events
Incidents are evaluated based on impact, scope, and urgency.
Incident Detection
6MM employs multiple detection mechanisms:
Real-time system monitoring and alerts
Automated anomaly detection
Access and activity logging
Partner and internal reporting channels
Early detection is critical to limiting impact.
Response Workflow
When an incident is identified, the following steps are taken:
Identification
Confirm the nature and severity of the incident
Containment
Isolate affected systems or components
Mitigation
Apply temporary or permanent fixes
Recovery
Restore normal system operations
Review
Conduct post-incident analysis and improvements
Communication & Coordination
Internal teams coordinate through predefined escalation paths
Affected partners may be notified when relevant
Communication prioritizes accuracy and timeliness
End-user communication is handled by partners within their own platforms.
Post-Incident Review
After resolution:
Root cause analysis is conducted
Security policies and controls are reviewed
Preventive measures are implemented
Documentation is updated
Lessons learned are incorporated into future security planning.
Partner Responsibilities During Incidents
Partners are expected to:
Report suspected incidents promptly
Cooperate during investigation and resolution
Maintain their own user-facing incident procedures
Clear coordination reduces recovery time and systemic risk.
Last updated