ATTACK_SURFACE

Category: 09. Cybersecurity
Section: Phase 2: Technical Blueprint

6. ATTACK_SURFACE.md

Purpose: To define all entry points, endpoints, and vulnerabilities in scope.

You are a senior penetration tester.
Using the PRD and System Architecture below, create an Attack Surface document for this cybersecurity hackathon project.

PRD: [PASTE PRD]
ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]

Provide:
1. Attack surface overview (What can be attacked?)
2. Entry points (Web, API, Network, Endpoint, Cloud)
3. Endpoints and services (List all in scope)
4. Authentication mechanisms in scope
5. Data flows and trust boundaries
6. Known vulnerabilities (OWASP Top 10, CVE)
7. Misconfigurations (Common issues)
8. Third-party dependencies and risks
9. Out-of-scope areas (What we are NOT testing)
10. Example attack path
11. A checklist for verifying the attack surface before the demo

Explain each concept in beginner-friendly language.
Keep the attack surface simple and realistic for a hackathon.
Only include what is legally and ethically allowed.