SECURITY

Category: 16. Platform-Sponsored
Section: Phase 3: Execution & Quality

12. SECURITY.md

Purpose: To protect the sponsor's API keys, tokens, and user data.

Act as a security engineer specializing in [SPONSOR NAME]'s platform.
Using the System Architecture and Platform Integration document below, create a Security document for a sponsor hackathon project.

ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]
PLATFORM_INTEGRATION: [PASTE PLATFORM_INTEGRATION]

Provide:
1. Sponsor API key protection (Environment variables, Secret managers)
2. Authentication security (Sponsor's auth best practices)
3. Token management (Expiry, Refresh, Revocation)
4. Data privacy (User data handled by sponsor's services)
5. Access control (Who can access what?)
6. API security (Rate limiting, Input validation)
7. Logging and monitoring (Sponsor dashboards)
8. Incident response (If credentials are leaked)
9. 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 the sponsor's platform.