Panoverse

SECURITY / POLICY

Vulnerability & Patch Management Policy

How we review changes and find and fix weaknesses in our code, dependencies and infrastructure.

Last updated: November 7, 2026 · Owner: Data Protection Officer, lin@kolect.ai

Purpose

Find and fix security weaknesses in our code, dependencies and infrastructure before they can be exploited.

Secure change management

  • All code lives in private repositories. Production branches are protected: only our automated release application can update them, and changes arrive through pull requests.
  • Changes run automated checks before release, including builds, type checks and focused tests. For the Panoverse platform these include permission and tenant-isolation tests and migration-safety checks.
  • Changes that touch money, permissions, data migrations or release tooling receive an independent review before merging. In the Panoverse platform an author cannot record their own independent approval.
  • Database changes are made only through versioned, checksummed migrations applied by the release workflow with a dedicated migration role.
  • Releases are built from a specific commit, deployed as immutable release artifacts, checked with automated smoke tests after deployment, and can be rolled back. New or risky features ship behind workspace feature flags that can be turned off without a deployment.

Dependencies

Dependencies are pinned through lock files, and Panoverse build pipelines pin third-party build actions to exact versions, so builds are reproducible and dependency changes are visible in review. Dependency vulnerability alerts and automated security updates on our production repositories are being rolled out in November 2026.

Infrastructure

We use managed services whose underlying platforms are patched by the provider. Our production servers run a supported long-term-support operating system release, and operating-system security updates are applied automatically or at least monthly. Restricting administrative network access, together with a quarterly review of firewall rules, is being rolled out in November 2026.

Remediation timelines

  • Critical or actively exploited: fixed or mitigated within 7 days.
  • High: fixed or mitigated within 30 days.
  • Medium and low: addressed in the next routine dependency upgrade.

Severity follows the CVSS score or the vendor’s rating. If a fix is not available, we apply a mitigation, such as disabling the feature, restricting access or adding a compensating control, and record the decision.

Reporting vulnerabilities

Anyone can report a suspected vulnerability to lin@kolect.ai. We acknowledge reports within 3 business days and handle confirmed issues under our Incident Response Policy.

Review

The Data Protection Officer reviews open security alerts at least monthly and this policy at least once a year.

Related

All security policies · Privacy policy · Subprocessors

PrivacyTermsSecuritySupport