Skip to content

Security

Ankit Upadhyay edited this page Aug 25, 2026 · 3 revisions

Security

How to report a vulnerability, and how security is engineered into the platform.

Reporting a vulnerability

Canonical source: SECURITY.md.

  • Email security at yosemitecrew.com with a description and reproduction steps.
  • You'll get a response within one business day.
  • Please keep the issue confidential until users have had reasonable time to patch, and don't exploit it.
  • There's no formal bug-bounty program yet (early-stage project), but reports are handled confidentially, contributors are credited if they wish, and Yosemite Crew commits not to pursue legal action for good-faith, non-exploitative research.

Do not open a public issue for a vulnerability — use the email process above.

Security posture

Security is designed in at several layers, documented across this wiki:

  • No financial custody. The platform is never the merchant of record and never holds clinic funds (Payments Architecture / ADR-0002).
  • Provider-neutral auth with self-hosted identity (Authentication and Identity / ADR-0003).
  • Org-scoped access control — cross-tenant access is a bug class, not a feature (Multi-Tenancy and RBAC).
  • AI agent least privilege — the developer AI editing agent is draft-only, config-scoped, human-promoted, and designed assuming the model is compromised (ADR-0005).
  • Data residency posture is explicit and contractual (ADR-0004).
  • Federation trust boundary - clinic-to-clinic ActivityPub traffic is HTTP-signature verified, gated to verified organisations, and outbound fetches carry SSRF / DNS-rebinding defences (ActivityPub Federation).

Secure development practices

  • Secrets never committed — Secretlint + staged-secret scanner (and gitleaks if installed) on pre-commit; Gitleaks in CI. Rotate immediately on any suspected leak.
  • SAST + secrets via Aikido before every push / PR (Code Quality Gates).
  • CodeQL and dependency-review run in CI (CI/CD Pipeline).
  • Explicit validation at boundaries (Zod on the backend), secure defaults, least privilege.

Always-on operational controls

A small set of standing workflows exists to catch classes of quiet failure early:

  • supply-chain.yml - SBOM, vulnerability (Grype) and license (Grant) scanning of the dependency tree.
  • tls-expiry.yml - daily certificate-expiry check on the public hostnames, so a failed renewal is flagged weeks before it bites.
  • promotion-guard.yml and back-merge.yml - branch-integrity enforcement: main takes changes only from dev, and anything reaching main is merged back so dev always contains it.
  • asc-key-check.yml - on-demand check that the App Store Connect API key still authenticates, surfacing a credential problem in seconds instead of after a full release build.

Active security work

  • IDOR / object-authorization fixes are handled as they're found (e.g. mobile task-detail access scoping).

Delivered hardening

  • Supply-chain security (epic #1721) is delivered: the supply-chain.yml workflow backed by scripts/security/supply-chain.sh, policy files .grype.yaml / .grant.yaml, pinned pnpm.overrides for transitive dependencies, and the process doc docs/security/supply-chain.md.
  • The security-hardening workstream - cross-tenant authorization, RBAC scoping, and CI supply-chain (#1796, remediating the automated-scan findings in #1638) - closed on 2026-07-14. Its successor, the 292-finding triage, landed in PR #1860 (merged 2026-07-18), which hardened cross-tenant authorization and permission checks repo-wide: tenant scope is now derived from the resource being accessed.
  • A further backend authorization hardening sweep landed across 2026-08: org scoping derived from the resource on routes that previously trusted caller-supplied ids, cross-tenant binding checks on invoices, bookings, clinical records and uploads (e.g. proving companion ownership before a booking is written, binding an invoice to its Stripe payment intent), unforgeable rate-limit keys, complete user deletion, and clinical-record reads put behind their own permission with an audit trail.

Compliance

SOC 2 Type 1, ISO 27001:2022, GDPR alignment, and EU accessibility obligations are covered in Compliance and Certifications.

Related

Product & Domain
Architecture
Applications
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Roadmap
Operations
Meta

Canonical code & docs: main repo · Auto-generated companion: DeepWiki

Clone this wiki locally