Security model

Prototype v1 includes a static front end and local image processing. It does not require server-side image storage. Security headers are supplied for hosts supporting a _headers file. HTTPS is mandatory for deployed camera capture.

UMF verification

UMF uses SHA-256 hashes of manifest and image/report entries, ZIP CRC-32 checks and strict ZIP limits. This checks package integrity, not image truth or author identity. Documents may still contain private health information. The parser requires independent security assessment before production use with hostile files.

Hardening still required

Production requires a penetration test, dependency/security monitoring, upload-independent architecture review, image decoder fuzzing, tested legal notices, source-code review, client-side memory testing, and verified device compatibility. No promise of zero vulnerabilities is made.

Reporting

The operator must publish an active security contact and vulnerability disclosure procedure before public launch. Do not submit patient records to a public vulnerability report.