SECURITY

Category: 09. Cybersecurity
Section: Phase 3: Execution & Quality

12. SECURITY.md

Purpose: The core security document (encryption, key management, access control, compliance).

Act as a senior security architect.
Using the System Architecture and Authentication Flow below, create the master Security document for a cybersecurity hackathon project.

ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]
AUTHENTICATION_FLOW: [PASTE AUTHENTICATION_FLOW]

Provide:
1. Security principles (Least privilege, Defense in depth, Zero trust)
2. Encryption (At rest, In transit, Key management)
3. Access control (RBAC, ABAC, Permissions)
4. Network security (Firewalls, Segmentation, IDS/IPS)
5. Application security (OWASP Top 10, Input validation, Output encoding)
6. Data privacy (PII handling, Anonymization, Retention)
7. Logging and monitoring (What to log, SIEM integration)
8. Incident response readiness (Playbooks, Contacts)
9. Compliance considerations (GDPR, HIPAA, PCI-DSS, SOC 2)
10. Third-party and supply chain security
11. A pre-submission security checklist

Keep the security measures practical and easy to implement within a hackathon timeframe.
Explain each concept in beginner-friendly language.
Do not include illegal or unethical techniques.