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

# Devin Security 2.0

> Use Devin Security 2.0 to scan repositories, review security findings across your organization, and assign vulnerabilities to Devin for fixes.

Devin Security 2.0 finds vulnerabilities and helps you ship fixes. Open **Security** in the app at `/security` to start.

The current experience has an organization-wide **Findings** page and a **Basic** / **Advanced** scan setup pane. This page replaces the Security Swarm guide.

## Access and permissions

Your organization must have access to security scans. Your role also controls whether you can start scans, manage scans, or manage findings. If Security is not available, ask an administrator to check your access.

## Start a scan

1. Open **Security** and select **Start a scan**.
2. In the **Basic** tab, select the repositories to scan under **Target repository**.
3. Select the scan effort.
4. Use the submit button at the bottom of the pane to continue.

The **Advanced** tab exposes more scan settings, including a scan profile. The available options depend on your organization's access.

### Scan profiles

Use the profile selector in **Advanced** to select an existing security scan profile. You can also create a profile from the selector.

For recurring scans, see [Automations](https://docs.devin.ai/product-guides/automations.md).

## Review findings

1. Open **Findings** in Security at `/security/findings`.
2. Select **Open**, **Reviewed**, or **Dismissed**.
3. Filter by repository, scan, severity, or pull request state to narrow the list.
4. Open a finding to inspect its details, affected code, and remediation recommendation when available.

Use the finding's actions to mark it **Reviewed**, dismiss it, or return it to **Open**. You can also select multiple findings for bulk actions.

**Reviewed** is a finding status. It does not mean that a pull request has merged. Use the pull request state to check the fix.

## Assign fixes to Devin

Select **Assign to Devin** in a finding's details, or select multiple findings and select **Fix with Devin**. Devin starts remediation sessions for eligible findings. If a finding already has a session, use **View session** to open it.

You can also inspect scan results from the scan session's **Findings** tab.

## Use the API

The [Code Scans API guide](https://docs.devin.ai/api-reference/v3/code-scans/triggering-code-scans.md) covers scan creation, status, and findings at organization and enterprise scopes.

* [Remediate a finding with the organization API](https://docs.devin.ai/api-reference/v3/code-scans/organizations-code-scans-remediate.md).
* [Remediate a finding with the enterprise API](https://docs.devin.ai/api-reference/v3/code-scans/enterprise-code-scans-remediate.md).


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