Change Management & Secure Development Policy

How a change to PersivX goes from an idea to production: how it is written, what it is checked against, who approves it and how it is released or rolled back.

Policy ownerPersiv Technology
Approved byHarsh Jain and Ankit Kumar
Effective from1 November 2026
ReviewedAt least once a year, and after any significant change or incident. Next review: 1 November 2027

Writing Changes

  • All code lives in source control. Every change is made on its own branch, never directly on the production branch.
  • Every new or changed feature is checked against the security checklist kept in the repository (the VAPT and SOC 2 check): the server takes the user from the sign-in token; each route declares the right it needs; SQL uses bound parameters; user text is escaped; no inline script; no path parts from requests; outbound addresses go through the guard; user code only in the sandbox; no secrets in code; errors don't reveal internals; expensive routes are rate-limited. Any gap is written up with the change.
  • A change that adds an outside service receiving customer data also needs an entry in Vendors before release.
  • Documentation for users and for developers is updated in the same change.

Checking Changes

  • Every push is scanned automatically for committed secrets (gitleaks), insecure Python patterns (bandit) and dependencies with known vulnerabilities (pip-audit). A failing scan is fixed or formally accepted as an exception before release.
  • PersivX has no automated functional tests. The author therefore tests every change in a running copy of the app and writes down what was checked, in the commit message. That record is the evidence that the change was tested.
  • Every change is reviewed and approved by one person other than the author before it is merged. Changes to sign-in, permissions, encryption or the sandbox are reviewed by Harsh Jain or Ankit Kumar.
  • Python packages are pinned to exact versions, and bundled browser libraries are listed with their versions. Upgrades are checked for known advisories first.

Releasing

  • Each release has a version number and a changelog entry.
  • Releases to Persiv-run production servers are approved and carried out by Harsh Jain or Ankit Kumar. The approval and the release time are recorded by email.
  • Before an upgrade: back up the database and files, then run manage.py upgrade_check, which lists anything that would break or be unsafe on that server. Run it again after the upgrade. Upgrades from the pre-1.7.29 code run deploy/upgrade/upgrade_persivx.py, which takes the backup, runs both checks, makes the required changes and writes a log of every change into the backup folder. Production keeps AUTH_ENFORCEMENT and WORKSPACE_ISOLATION at enforce and DEBUG off.
  • If a release goes wrong, the previous version is restored from source control, and the data from the pre-upgrade backup where a migration changed it.
  • Production customer data is never used for development or testing.

Emergency Changes

A fix for an active incident or a critical vulnerability may be released before review, with approval from Harsh Jain or Ankit Kumar. It is reviewed within 2 business days afterwards, and the record says why it couldn't wait.