Vulnerability Management Policy
How security weaknesses in PersivX and the servers it runs on are found, ranked and fixed, and by when.
| 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 |
Finding Weaknesses
- On every push: automatic scans for committed secrets, insecure code patterns and vulnerable Python dependencies.
- Before each release: the security checklist in Change Management.
- When a customer asks for one: a penetration test (VAPT) by an independent firm. The report and the fix for each finding are kept.
- Servers: operating system and database updates are applied every month, and a server vulnerability scan (OpenVAS or similar) runs every 3 months.
- Outside reports to support@persivx.com, as described on the overview.
- Advisories for bundled libraries and services are watched by Harsh Jain and Ankit Kumar.
Fix Deadlines
Severity is set from the impact and how easy the weakness is to use (a CVSS score is a guide, not the rule).
| Severity | Fixed or mitigated within |
|---|---|
| Critical | 7 days |
| High | 30 days |
| Medium | 90 days |
| Low | 180 days |
Each finding is tracked by email from discovery to fix. A finding that can't be fixed in time needs an approved exception, with the compensating control and a new date. A finding that is being exploited is handled as an incident.
Customer-Run Servers
Persiv publishes fixes as new releases and describes security fixes in the changelog. Customers running their own servers learn of security fixes from the changelog, and are responsible for installing them and keeping their servers patched.
