Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

SECURITY

Category: 13. Social Impact / Civic
Section: Phase 3: Execution & Quality


12. SECURITY.md

Purpose: To define data privacy for vulnerable populations, consent, and compliance.

Act as a security and privacy engineer specializing in civic tech.
Using the System Architecture and Data Ethics document below, create a Security document for a social impact hackathon project.

ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]
DATA_ETHICS: [PASTE DATA_ETHICS]

Provide:
1. Data classification (Sensitive, Personal, Public)
2. Encryption (At rest, In transit, Key management)
3. Authentication and authorization (Simple, accessible)
4. Consent management (How consent is stored and respected)
5. Data minimization (Only collect what is needed)
6. Anonymization and pseudonymization
7. Access control (Who can view what?)
8. Audit logging (Who accessed what, when)
9. Breach notification plan
10. Compliance (GDPR, Local data protection laws)
11. A pre-submission security and privacy checklist

Keep the security measures practical and easy to implement within a hackathon timeframe.
Explain each concept in beginner-friendly language.
Prioritize the safety of vulnerable populations.