Trust
Security
Effective date: 15 October 2026
1. Our approach
CRAFT holds governance, fiduciary and evidence records that organisations rely on with funders and regulators. We design for least privilege, tenant isolation, verifiable records and transparency about limits.
2. Safeguards in place
- Encryption: HTTPS everywhere with HSTS; sensitive fields (contact details, reviewer notes, sensitive findings, multi-factor secrets) encrypted at rest with AES-256-GCM and rotatable keys.
- Sign-in: password sign-in plus optional multi-factor sign-in with an authenticator app and single-use recovery codes; organisations can require it for all members. Sessions time out after inactivity.
- Access control: roles per organisation (owner, admin, assessor, viewer); every request is checked server-side; other organisations’ records are not discoverable.
- Segregation of duties: creators cannot approve their own assessments, uploaders cannot approve their own evidence, and corrective actions close only on verified evidence.
- Verification of restricted roles: national public health institutes are verified by institute email domain or by a platform operator before health-security assessments unlock.
- Audit trail: changes and sensitive reads are logged with actor, time, IP address and browser; finalised reports are frozen snapshots.
- Abuse protection: shared rate limits on every endpoint, stricter limits on multi-factor code attempts, and an organisational email domain to create an organisation.
- Uploads: file-type allow-list, 10 MB limit, image metadata stripped, content checked against the document’s name, downloads served as attachments.
- Browser protections: Content Security Policy (no third-party scripts), frame blocking, MIME sniffing protection, a strict referrer policy and a Permissions-Policy that disables camera, microphone, location and payment features.
- Engineering: code review, automated tests, static analysis (CodeQL), dependency auditing and automated dependency updates on every change; secrets are kept only in the hosting provider’s environment settings.
3. Your part
- Turn on multi-factor sign-in, and keep your recovery codes somewhere safe.
- Give people the lowest role they need, and remove members who leave.
- Avoid uploading personal data that is not needed.
4. Reporting a vulnerability
Email craftframework@becomechange.institute with a description, the affected page or endpoint, steps to reproduce and the impact. Please do not open a public issue. Our machine-readable contact is at /.well-known/security.txt.
We aim to acknowledge reports within five working days, keep you informed during triage and fix, and credit you if you wish.
5. Safe harbour
We will not pursue action against good-faith research that follows these rules: only test accounts and data you own or are authorised to use; do not access, change or keep other people’s data; avoid service disruption (no denial-of-service, spam or heavy automated scanning); and give us reasonable time to fix an issue before disclosing it.
6. Incidents
If a breach affects personal data, we will notify the affected organisations without undue delay so they can meet their own obligations, and notify regulators where the law requires — for example within 72 hours under the Nigeria Data Protection Act and the GDPR.
© 2026 DiBadili Institute. CRAFT (ICARF v4.0) is an open-source public good. Software GPL-3.0 | Framework CC BY-SA 4.0.