OpportunityIQSimulated blood-drive support

DRM participation is off. MVP route: an RDSE flags, and the ED or RE responds. District recruitment managers stay on the roster.

SECURITY.md

Before any real data

This is the security note for the prototype. The same text is SECURITY.md in the repository. The help section points here.

What it is defending

If these screens ever held real operations, the sensitive parts would be drive schedules, sponsor names, chapter comments, and which staff cover which ZIPs. The prototype assumes a curious visitor, a demo user who can switch roles, and a later editor who might paste a real staff file into the lists. It does not claim to solve the production pilot’s hosting or network findings.

What the prototype already does

What it is not

The persona menu is not single sign-on. Anyone who can open the site can choose the admin. The action log is not a retention-grade audit trail. Inline scripts are still allowed because the framework emits them. Development also allows unsafe-eval.

Required before real records

  1. Red Cross sign-in through Entra ID, with roles from an authoritative source.
  2. Written data-use approval from Biomedical Services and Humanitarian Services.
  3. Hosting in an approved Red Cross tenant, not a personal site and not jbf.com.
  4. Mail only through the approved Red Cross mail service.
  5. Audit logging, retention, and a privacy review.
  6. A security scan and a penetration test, then fixes.
  7. A recorded decision on the 7-day activity window and on how support is counted.

Leave the @example.test lock in place until that move. Removing it early makes a mistake easier.

Back to help