Crivora · Vulnerability Management Procedure
Vulnerability Management
How Crivora identifies, prioritizes and remediates vulnerabilities.
- Policy owner
- Crivora
- Effective date
- Last reviewed
- Review cadence
- at least annually and when material changes occur
- Version
- 1.0
- Contact
- contato@usecrivora.com
- URL
- https://usecrivora.com/security/vulnerability-management/en
1. Sources
- Dependency review, using package audit reports as a signal (without blindly force-applying fixes).
- Security advisories for the framework and libraries in use.
- Code review of changes before release.
- External reports received through the responsible disclosure channel (/security/en).
2. Prioritization and remediation
- Each finding is assessed by severity and by its real exposure in Crivora (is the component used in production? is it reachable?).
- Critical and high findings with real exposure take priority over other changes.
- Fixes are applied through updates, configuration or code changes, as appropriate.
3. Verification
- Before release, we run linting, type checking, automated tests and the production build.
- After remediation, the finding is re-verified.
- Secrets are not version-controlled; if a secret is suspected to be exposed, it is revoked and replaced.
4. Current limits
Crivora does not currently run periodic third-party penetration tests.
Crivora · Vulnerability Management · https://usecrivora.com/security/vulnerability-management/en · contato@usecrivora.com