> ## 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.

# Quickstart: First 30 Minutes

> A fast-track onboarding guide to set up your workspace, discover assets, run a scan, and triage findings.

Follow this step-by-step walkthrough to get productive with Snapsec in under 30 minutes.

***

## Step 1: Log In and Set Up Your Workspace (5 Minutes)

1. Open your Snapsec console URL.
2. Log in with your corporate SSO credentials or initial administrator account.
3. Review your **Company Profile** under **Administration > Company Profile**.
4. Create your first **Business Unit** (e.g., `Core Banking`, `Payment Gateway`, `Customer Portal`) to organize your assets.

***

## Step 2: Discover External Assets via ASM (10 Minutes)

1. Navigate to **Asset & Exposure Management > Attack Surface Management**.
2. Click **New Scan** or **Add Root Domain**.
3. Input your primary organization domains (e.g., `yourcompany.com`).
4. Snapsec ASM immediately initiates passive and active reconnaissance:
   * Subdomain enumeration
   * DNS record resolution
   * SSL/TLS certificate transparency analysis
   * Open port and service fingerprinting
5. Inspect the discovered assets in the **Asset Catalog**.

***

## Step 3: Run Your First Vulnerability Scan (10 Minutes)

1. Navigate to **Vulnerability Scanning > Projects & Scan Targets**.
2. Click **Create Project** and specify your target scope (e.g., `Staging Web Application`).
3. Select an assessment profile:
   * **Quick Surface Scan**: Port discovery and service banner analysis.
   * **Web Application Scan**: OWASP Top 10 vulnerabilities, API misconfigurations, and authentication weaknesses.
4. Click **Start Scan** and monitor real-time execution in the **Scan Results** view.

***

## Step 4: Triage Findings & Enforce SLAs (5 Minutes)

1. Navigate to **Vulnerability Scanning > Finding Management**.
2. Filter findings by **TrueRisk™ Score** (Critical, High, Medium, Low).
3. Click any finding to inspect:
   * Technical description and CVE references.
   * Detailed request/response evidence and reproduction steps.
   * Remediation advisory tailored to your framework.
4. Assign the finding to a team owner and trigger a Jira ticket directly from the action bar.
5. Notice how Snapsec automatically calculates the SLA deadline based on severity.

***

## Next Steps by Role

> [card] [Security Administrator](https://docs.snapsec.co/get-started/roles/security-administrator.md)
>
> Configure SSO, RBAC policies, and organization-wide SLA rules.

> [card] [Security Analyst](https://docs.snapsec.co/get-started/roles/security-analyst.md)
>
> Learn triage workflows, suppression rules, and blocker tracking.

> [card] [Penetration Tester](https://docs.snapsec.co/get-started/roles/penetration-tester.md)
>
> Execute autonomous AI pentests with verified proofs of concept.

> [card] [DevSecOps Engineer](https://docs.snapsec.co/get-started/roles/devsecops-engineer.md)
>
> Integrate Snapsec into CI/CD pipelines, GitHub Actions, and webhooks.


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