Threat Model (Lite)

Assets

• Marketing content and brand reputation.
• Internal documentation (architecture, security plans, ADRs).
• Deployment pipeline (Docker, pnpm, Cloudflare Pages configuration).

Actors

Actor	Motivation	Access Level
External visitor	Browse marketing site	Public
Internal admin	Maintain docs and releases	Authenticated
Malicious insider	Exfiltrate information	Elevated
Automated bot	Crawl or attack public surface	Public

Key Risks

1. Data leakage — Internal docs accidentally exposed publicly.
2. Supply chain — Compromised dependencies in pnpm ecosystem.
3. Misconfiguration — Incorrect Cloudflare settings leading to disabled security headers.
4. Credential theft — Developers mishandling secrets locally.

Mitigations

• Enforce Cloudflare Access before docs launch.
• Keep pnpm lockfile reviewed during dependency updates; run pnpm audit regularly.
• Add security header validation to release checklist.
• Store secrets only in approved secret stores; monitor with periodic scans.

Follow-Up Actions

• Expand to a full STRIDE analysis once backend services or Workers are introduced.
• Integrate automated dependency monitoring in future CI/CD.