AutoCore Vulnerability Management
Defines dependency, image, SBOM, triage, and release security expectations.
Vulnerability evidence is time-bound. The reviewed RC closeout reported zero unresolved critical/high findings in its packaged evidence, but every later dependency, image, provider, and deployment change requires fresh assessment.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Inventory | Use the generated CycloneDX SBOMs and lockfiles to identify package and image scope. |
| Triage | Classify exploitability, exposure, affected edition, mitigation, and release impact. |
| Remediation | Patch, pin, isolate, or accept with an accountable decision and expiry date. |
| Verification | Repeat the relevant tests and inspect the final package rather than relying on source-only results. |
| Disclosure | Do not publish exact unpublished vulnerability details in public documentation. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.