SECURITY

Category: 11. Domain / Industry Hackathons
Section: Phase 3: Execution & Quality

12. SECURITY.md

Purpose: To define industry-specific security (PII, PHI, financial data).

Act as a security engineer specializing in [INDUSTRY NAME].
Using the System Architecture and Compliance Specification below, create a Security document for an industry hackathon project.

ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]
COMPLIANCE_SPEC: [PASTE COMPLIANCE_SPEC]

Provide:
1. Data classification (PII, PHI, Financial, Public)
2. Encryption (At rest, In transit, Key management)
3. Authentication and authorization (Industry standards)
4. Access control (RBAC, ABAC, Least privilege)
5. API security (Industry standards)
6. Data privacy (Consent, Anonymization, Retention)
7. Audit logging (What to log, Where to store)
8. Third-party security (Vendor risk, API security)
9. Industry-specific security controls
10. 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.
Flag any security measures that are mandatory for compliance.