Skip to content
AskFlorence
Main Navigation ArchitectureFlorence AIAgentsMembersAgent PlatformValidationInfrastructure

Appearance

Sidebar Navigation

Overview

Home

Glossary

System Architecture

Consumer & Agent Flow

Florence AI

Overview

Principles

Runtime

Tool surface

Adding a tool

Tool registry

Knowledge: SBC scenarios & CSR

Voice

Evals & observability

Provider risk & portability

Outage playbook

Roadmap

Build plan

Agents

Overview

Workflows & pain points

Members

Overview

Medicaid coverage gap

Carriers

Overview

Marketplaces

Overview

Agency

Overview

Regulations

Overview

Agent Platform

Overview

Auth Architecture

MongoDB Permissioning

Compliance Model

Data Models

Data Sources

Overview

CMS Marketplace API

CMS dependency map

PUF Data

State Subsidies

SBE Ingestion Playbook

SBE State Watchouts + Decisions

CA Phase C/D Playbook

NY Phase C/D Playbook

Validation

Overview

Methodology

APTC Formula

California 2026

New York 2026

CAPS Formula

Scenario Results

Infrastructure

Account Inventory

AWS Setup Runbook

AWS Organizations

CloudTrail

GuardDuty

Security Hub

Config

CloudFront + WAFv2

Data sources & ingest

Phase 4 DNS

Change Log

Vulnerability Management

MongoDB Setup

Access Control

Data Classification

Documentation Hosting

Post-deploy Smoke

Development

Preflight (local CI mirror)

Testing strategy

Compliance

Overview (auditor entry point)

SOC 2 Control Mapping

HIPAA Control Mapping

CMS EDE Appendix A Mapping

Risk Assessment

Encryption Policy

Data Retention Policy

Privacy Impact Assessment

Consent Capture & Versioning

Incident Response Plan

Access Control Policy

Marketing vs. Portal Analytics

Vendor / Subprocessor Register

Dependency Vulnerability Policy

BAA / Compliance Evidence

Compliance-Automation Integration

Compliance-Automation Vendor Evaluation

Penetration Test Reports

Architecture

Portal entry handoff

Mobile app strategy

Deferred architecture decisions

Session cookie architecture

Share flows

Decisions (ADRs)

Index

0001 — Atlas project isolation

0002 — Append-only audit log

0003 — Narrow-scoped Mongo users

0004 — Cross-cluster Atlas PrivateLink

0005 — Delayed-job architecture

0006 — Mongo user simplification

0007 — Terraform owns ECS task def

0008 — E2E testing strategy

0009 — Self-hosted analytics + observability (superseded)

0010 — PostHog HIPAA Cloud (supersedes 0009)

Runbooks

Security Incident Response

Break-Glass Root Login

Onboard Team Member

Offboard Team Member

Atlas user provisioning

Deploy via Terraform (ENG-277)

Rollback via Terraform (ENG-277)

S3 data bucket migration (planned Phase 11)

Access Reviews

2026-Q2 Review

Session log

Index

2026-04-23 — Phase 10 DNS cutover

2026-04-22 — Phase 8 prod AWS mirror

2026-04-22 — Phase 7 Atlas VPC peering

2026-04-22 — Phase 6 CloudFront + WAF

2026-04-21 — Phase 5 staging go-live

2026-04-17 — Atlas staging

Briefs

Index

Member portal plan (ENG-187)

2026-04-16/17 handoff

2026-04-17 Atlas handoff

System briefing (2026-04-17)

Creative AdBundance proposal brief

Creative AdBundance analytics brief

ElevenLabs RN integration research

Policies

Overview

On this page

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
Pager
Previous pageChange Log
Next pageMongoDB Setup

AskFlorence Internal Documentation. Not for public distribution.

AskFlorence

Internal Documentation

Access restricted. Not for public distribution.