Last updated Mar 19, 2026
This page summarizes how TKO SOLUTIONS L.L.C (doing business as “Trac”) responds to security incidents and how we provide breach-related notifications. It is intended to support customer security and compliance reviews.
Where there is a signed agreement that contains incident or breach terms, the signed agreement controls if terms differ.
Incident response objectives#
Our incident response process is designed to:
- Detect and contain potential security events quickly.
- Preserve evidence for investigation and remediation.
- Restore service availability and integrity safely.
- Notify affected customers in accordance with law and contract.
Incident lifecycle#
We use an incident lifecycle that typically includes:
- Detection and triage: monitor alerts, logs, and reports from users, employees, and vendors.
- Classification: determine whether the event is a security incident and assign severity based on impact and scope.
- Containment and mitigation: isolate affected systems, rotate credentials, apply temporary controls, and block malicious activity.
- Eradication and recovery: remove root causes, patch vulnerabilities, and validate system recovery.
- Post-incident review: document lessons learned and track corrective actions to completion.
Severity model (general)#
Severity is assigned using factors including:
- Data sensitivity and volume involved.
- Scope of affected systems or customers.
- Impact on confidentiality, integrity, and availability.
- Ongoing threat activity and exploitability.
Response urgency, stakeholder communication, and escalation paths are adjusted based on severity.
Customer notification#
If we confirm a security incident involving customer personal data or other protected customer data, we notify affected customers without undue delay and as required by applicable law and contractual commitments.
Notification generally includes, as available at the time:
- A description of the incident.
- Categories of affected data.
- Approximate timeframe and known scope.
- Mitigation steps taken by Trac.
- Recommended customer actions.
As investigations evolve, we may provide follow-up updates with additional details.
Communication channels#
Incident and breach notifications are typically delivered through:
- Designated account owner or security contacts on file.
- Email notice from Trac security or legal channels.
- Other agreed channels in enterprise contracts.
Customers are responsible for maintaining current security contact information.
Customer responsibilities during active incidents#
To support coordinated response, customers should:
- Maintain up-to-date administrator and security contacts.
- Promptly review incident notices and follow recommended actions.
- Rotate credentials or revoke sessions when requested.
- Notify Trac of suspected compromise in customer-managed environments.
Regulatory and law enforcement coordination#
Where required, we coordinate with regulators, supervisory authorities, and law enforcement. We may limit or delay disclosure if legally required to preserve investigations or public safety.
Testing and preparedness#
We periodically evaluate incident readiness through training, tabletop exercises, and operational reviews to improve response quality over time.
Contact#
For security reports and incident coordination, contact security@trac.bot. For
legal notices, contact legal@trac.bot.