Incident Response Policy
What counts as a security incident, who handles it, the steps from first report to closing review, and when customers are told.
| Policy owner | Persiv Technology |
|---|---|
| Approved by | Harsh Jain and Ankit Kumar |
| Effective from | 1 November 2026 |
| Reviewed | At least once a year, and after any significant change or incident. Next review: 1 November 2027 |
What Is an Incident
A security incident is any event that has, or may have, put the confidentiality, integrity or availability of customer data or of PersivX at risk. Examples: a user acting as someone else, data from one customer seen by another, a leaked key or password, malware on a server, an unexplained admin change, or an outage caused by an attack.
Anyone who suspects one reports it at once to support@persivx.com, even if unsure. Reporting a false alarm is never a mistake.
Roles
| Role | Responsibility | Who |
|---|---|---|
| Incident lead | Runs the response, decides severity, keeps the timeline | Whoever is on call that week: Harsh Jain and Ankit Kumar alternate weekly, and the other is deputy |
| Technical responders | Investigate, contain and fix | Harsh Jain and Ankit Kumar |
| Communications | Customer, regulator and public notices | Harsh Jain and Ankit Kumar |
| Management | Approves notices and spending; legal advice | Harsh Jain and Ankit Kumar |
Severity
| Severity | Meaning | Response starts within |
|---|---|---|
| Critical | Customer data exposed or changed, or an attacker has access | 1 hour |
| High | A serious weakness in use, or a key or password exposed | 4 hours |
| Medium | A contained event with no sign of data exposure | 1 business day |
| Low | A policy breach or suspicious event with no impact | 5 business days |
Steps
- Record. Open an incident record as an email thread with the time, who reported it and what is known. Keep a timeline from here on.
- Assess. Set the severity and the people and data affected. Raise it if in doubt.
- Contain. PersivX gives these levers:
- block a user (ends their sessions everywhere at once);
- end every session on a server:
manage.py revoke_auth_tokens; - reset a user's two-step verification:
manage.py reset_mfa --user <id>; - turn AI off for an organization, or switch off custom Python (
ALLOW_USER_PYTHON_CODE=0); - rotate keys and datasource credentials as in Data Protection.
- Preserve evidence. Copy the relevant security events, activity log rows and server logs before anything is cleaned up or rebuilt.
- Fix and recover. Remove the cause, restore from backup if needed, and confirm the service works.
- Notify. See below.
- Review. Within 5 business days of closing a High or Critical incident, hold a blameless review: what happened, why, what changes. Track each change to completion.
Telling Customers and Authorities
- Customers whose data is affected are told within 72 hours of confirming it, or the contract's time if shorter, with what happened, what data, what Persiv has done and what they should do.
- Regulators are notified where the law requires it, within its deadline. The law that applies is India's Digital Personal Data Protection Act, 2023.
- Notices are approved by Harsh Jain or Ankit Kumar.
Practice
The plan is rehearsed at least once a year with a realistic scenario, and contact details are checked at the same time. The exercise and what it changed are recorded.
