> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snapsec.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Organize security testing, scan configurations, and target scopes into manageable project units.

A **Project** in Snapsec defines a concrete target boundary for security assessments, continuous scanning, or penetration tests.

***

## Project Structure

Each project encapsulates:

1. **Target Scopes**: Specific domain names, URL paths, CIDRs, IP lists, code repositories, or API collections.
2. **Scan Profiles**: Scan policies, schedules, rate limits, and custom detection rules.
3. **Authentication Profiles**: Injected credentials, OAuth2 flows, API keys, or session tokens.
4. **Assigned Team Owners**: DevSecOps and product engineers responsible for remediating findings.

***

## Project Types

| Project Type | Target Types | Common Use Cases |
| :- | :- | :- |
| **External Perimeter** | Domains, Subdomains, Public IPs | Continuous ASM and perimeter defense |
| **Web Application** | URLs, Single Page Apps, Admin Portals | OWASP Top 10 testing and DAST scanning |
| **REST & GraphQL API** | OpenAPI/Swagger, Postman collections | API fuzzing, auth validation, BOLA testing |
| **Source Code & Repo** | GitHub, GitLab repositories | SAST, secret scanning, and SCA audits |
| **Autonomous Pentest** | Defined hybrid scopes | Multi-stage AI penetration testing |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.