Skip to content

Vulnerability Management Policy

Status: Active. Last updated April 11, 2026. Purpose: SOC 2 evidence for CC7.1 (Vulnerability Monitoring), CC8.1 (Change Management)


Policy

AskFlorence monitors all application dependencies for known security vulnerabilities and remediates them based on severity within defined timeframes.

Scanning

ToolScopeFrequencyConfiguration
GitHub Dependabotnpm dependencies (package.json)Continuous (automated)Enabled on askflorencehealth/ask-florence repo
npm auditnpm dependency treeOn every npm installDefault behavior

Dependabot automatically creates alerts when vulnerabilities are published in the GitHub Advisory Database or the National Vulnerability Database (NVD).

Remediation SLAs

SeverityResponse TimeRemediation TimeExample
CriticalSame day24 hoursRemote code execution, auth bypass
HighSame day48 hoursDoS, data exposure
Medium3 business days7 business daysLimited-scope vulnerabilities
LowNext sprint30 daysTheoretical or low-impact issues

"Response time" = acknowledge and assess the alert. "Remediation time" = patch deployed to production.

Process

  1. Detection: Dependabot creates an alert on the repo's Security tab
  2. Assessment: Review severity, affected component, and exploitability
  3. Remediation: Update the vulnerable dependency to the patched version
  4. Verification: Confirm build passes and no regressions
  5. Deployment: Push to production
  6. Evidence: Git commit references the CVE and Dependabot alert number

Evidence Trail

All vulnerability remediations are tracked via git history. Each security patch commit includes:

  • The CVE identifier
  • The Dependabot alert number
  • The version change (before → after)
  • Build verification (must pass before push)

Git is the remediation log. No separate spreadsheet or ticket required — the commit history is the auditable record.

Remediation History

DateCVESeverityPackageFixCommit
April 11, 2026CVE-2026-23869Highnext 16.2.2 → 16.2.3DoS via Server Components37c3054

This table is updated with each remediation. For complete history, see git log --grep="CVE" on the repo.

SOC 2 Control Mapping

ControlEvidence
CC7.1 (Vulnerability Monitoring)Dependabot enabled, continuous scanning, SLA table
CC8.1 (Change Management)Remediation process, git commit trail with CVE references
CC7.2 (Anomaly Detection)Dependabot alerts surface anomalous dependency states

AskFlorence Internal Documentation. Not for public distribution.