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

# Set a repository's risk profile

A finding on a public, customer-facing service is more urgent than the same finding on an internal tool. A repository's risk profile is how you tell Sourcery which kind of repository it's looking at, so it weights severities to match.

## The two dimensions

A risk profile has two dimensions:

| Dimension        | Choices                             |
| ---------------- | ----------------------------------- |
| Network exposure | Public network, internal only       |
| Data sensitivity | Critical, high, standard, low, none |

The more exposed the network and the more sensitive the data, the more Sourcery raises the severity of findings in that repository. A repository with no profile set is treated as standard data sensitivity, with no network-exposure adjustment.

## Set the profile


    <Step title="Open the repositories page">
        Go to [**Repositories**](https://app.sourcery.ai/dashboard/security/repositories) and
        find the repository.
    </Step>

    <Step title="Choose its exposure and sensitivity">
        Set the network exposure and data sensitivity that describe how this repository is deployed
        and what data it handles.
    </Step>

    <Step title="Save">
        Save the profile. It applies on the repository's next scan.
    </Step>



## When it takes effect

A risk profile feeds severity scoring, which happens at scan time. Setting a profile does not re-score what is already on screen. On the next scan, Sourcery re-scores the repository's findings using the new profile, so existing findings pick up the change then. If you'd rather not wait for the schedule, [queue a scan](/security/scan-schedule/) to pick it up sooner.

## What's next