SECURITY

Category: 14. Open Innovation / Corporate
Section: Phase 3: Execution & Quality

12. SECURITY.md

Purpose: To define enterprise-grade security, SSO, IAM, and data encryption.

Act as an enterprise security engineer.
Using the System Architecture and Compliance Specification below, create a Security document for a corporate hackathon project.

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

Provide:
1. Data classification (Public, Internal, Confidential, Restricted)
2. Encryption (At rest, In transit, Key management)
3. Authentication and authorization (SSO, OAuth, SAML, IAM)
4. Access control (RBAC, ABAC, Least privilege)
5. API security (API Gateway, Rate limiting, Threat protection)
6. Data privacy (Consent, Anonymization, Retention)
7. Audit logging (What to log, Where to store)
8. Third-party security (Vendor risk, Integration security)
9. Incident response readiness
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 enterprise compliance.