Threat model, security policies, and audit tooling for the Ann Lite ecosystem.
Documents and manages security across all Ann Lite repositories — this repository holds the analysis and checklists; each individual repository's own SECURITY.md still handles its own vulnerability reporting intake per the organization SECURITY.md.
| Document | Covers |
|---|---|
docs/THREAT_MODEL.md |
Trust boundaries and threats by component, with current mitigations |
docs/POLICIES.md |
Authentication, authorization, input validation, payment and data protection policy |
docs/VULNERABILITY_MANAGEMENT.md |
Severity classification, response targets, remediation process |
docs/INCIDENT_RESPONSE.md |
Detection → containment → eradication → recovery → review |
docs/SECRETS_MANAGEMENT.md |
Full secrets inventory across repositories, rotation guidance |
docs/ACCESS_CONTROL.md |
RBAC model, roles, permission codes, enforcement points |
docs/PAYMENT_SECURITY.md |
Card and CeloHT payment security specifics |
docs/BLOCKCHAIN_SECURITY.md |
Custody model, no-smart-contract stance, confirmation policy |
docs/AUDIT_CHECKLIST.md |
Checklist for reviewing any repository |
docs/PRE_PRODUCTION_CHECKLIST.md |
Must-complete items before accepting real donations |
.github/workflows/codeql.yml and .github/workflows/dependency-audit.yml are canonical templates — each Ann Lite repository with application code copies these into its own .github/workflows/ directory rather than this repository running scans on other repositories' code directly.
Per the organization's core development rule: do not claim the system is fully secure without actual verification. This repository documents the intended security posture and the checklists to verify it — it is not itself a certification that verification has happened. See docs/PRE_PRODUCTION_CHECKLIST.md for what remains before Ann Lite should be considered production-ready from a security standpoint.
Applies to every repository in the organization. Particularly load-bearing for annlite-backend, annlite-payments, annlite-celoht, and annlite-database, given their handling of authentication, payments, and beneficiary data.