---
updatedAt: 2026-08-24T23:18:58.000Z
agentTools:
  projectIndex: https://docs.censys.com/llms.txt
---

# Configure Risks

One of the primary objectives of the Censys Attack Surface Management (ASM) platform is to shrink your organization’s attack surface area. To accomplish this, ASM identifies risks to draw your attention to vulnerable places in your internet-facing infrastructure.

Start by tuning risk default settings to fit your organization’s needs. Then, investigate and remediate risks in your network to improve your security posture.

## Configure risk types

ASM maps and monitors your attack surface and detects more than 700 exposures and misconfigurations and over 7,000 vulnerabilities.

You can set each type’s default severity to fit your security policies and investigative priorities. You can disable a risk type if you don't want ASM to detect any instances of it.

<Callout icon="📘" theme="info">
  ### Note

  Not all risks are enabled by default because not all customers want all risk types enabled. Review the risk types and decide what's right for your organization and your environment.
</Callout>

By default, the following risk types are disabled:

<Accordion title="Risk types disabled by default" icon="fa-info-circle">
  - Exposed AlienVault Secret
  - Exposed CloudFlare API Token
  - Exposed CloudPlan Secret
  - Exposed Confluent Secret
  - Exposed GitLab API Token
  - Exposed IBM Cloud User Key
  - Exposed LaunchDarkly API Access Token
  - Exposed Typeform API Access Token
  - Exposed Azure Client ID or Tenant ID
  - Exposed CloudFlare Global API Key
  - Exposed CoinAPI Secret
  - Exposed DigitalOcean Secret Token
  - Exposed Heroku Secret
  - Exposed IEX Cloud Secret API Token
  - Exposed PagerDuty API Key
  - Host Not Present in VM Solution
  - Exposed CarbonInterface Secret
  - Exposed CloudImage Secret
  - Exposed Coinbase Secret
  - Exposed Fastly Personal Token
  - Exposed Hubspot API Key
  - Exposed Kanban API Token
  - Exposed Terraform Cloud Personal Token
  - Wildcard Certificate
</Accordion>

<Callout icon="📘" theme="info">
  ### Note

  You cannot create a new risk type. However, you can show or hide existing risk types to identify the risk types your organization cares about most. You can also change the risk type severity level to better suit your environment.
</Callout>

### View risk types

1. Go to the ASM web console and click **Risks > Configure Risk Types**. Here, you can view all risk types that Censys Attack Surface Management detects.

<Image src="https://files.readme.io/b36d1e447d90c4e9b6b1629465c53b2d65c308892c1b7d261149d17ea6baa837-uuid-d2d1e880-c9ea-45e0-c540-e738dd7f28f2.gif" align="center" border={true} />

### Enable and disable risk types

To enable or disable risk types, first filter the risks to view all currently enabled and disabled risks.

#### Enable disabled risks

1. From the State dropdown, select **Disabled**.

   <Image src="https://files.readme.io/cd02305b2b303e3e942658c5dcd0478b789e214e1840dc649a0a2d115c664726-Screenshot_2025-02-26_at_3.42.49_PM.png" align="center" border={true} />

2. Scroll the list and find a risk type you want to enable for your environment.

3. Click the risk type. The risk type opens.

   <Image src="https://files.readme.io/2eef1ebb75c1f1e39ca7943b30826ccc8a3df27c78ba0443b9a294dcadfaee91-risk_type.png" align="center" border={true} />

4. Perform the following:
   1. Click **Enabled**.
      1. If needed, use the slider to change the Censys Recommended Severity to suit your organization's needs better.
         1. **Critical**: Indicates a severe risk that may result in compromise of the affected system or interruption of business objectives. Remediate critical risks as soon as possible.
         2. **High**: Indicates a risk that can result in remote code execution or sensitive information disclosure. Prioritize high risks when creating a risk remediation roadmap.
         3. **Medium**: Indicates a risk that can be exploited in combination with other vulnerabilities to perform an attack. Treat medium risks as a standard priority on a risk roadmap.
         4. **Low**: Indicates a vulnerability that can provide an attacker with some information about or access to the affected system. Deal with low risks at the lowest priority.
      2. Make an optional note. It is helpful to note what changed and for what reason for future reference. Comments are visibile in the Change History for the selected risk type.

5. Click **Save**.

#### Disable enabled risks

1. From the State list, select **Enabled**.

2. Scroll the list and find a risk type you want to disable for your environment.

3. Click the risk type.

   <Image src="https://files.readme.io/1081856127f98e601c00bb68da889a2f10d201452b34ab243a2e289a772b51ba-uuid-eca5aed3-56b8-11e6-fcd2-971f66997a06.png" align="center" width="500px" border={true} />

4. Click **Disabled**. Make an optional note. While it's not required, it's helpful to note what changed and why in the future. These comments are viewed in the Change History for the selected risk type.

5. Click **Save**.

### View the history for a risk type

1. Go to the ASM web console and click **Risks > Configure Risk Types**.

2. Select **View only Edited Risk Types**.

   <Image src="https://files.readme.io/33d860341b8d9332f263664323f334cfc8097b42b7140d4c818fbe81c85a1f62-view_risk.jpg" align="center" width="300px" border={true} />

3. Click the risk type you want to view. Then, scroll down the page to the **Change History** area.

## Search, sort, and filter risks

As you refine your risk configurations, you can search, sort, and filter the risks based on when the risk was added to the ASM list of detections. You can also sort risks by their prevalence in your attack surface.

<Image src="https://files.readme.io/5fa0de3edad36558a13e73ba946dd0325a112fb4240872fbe7c2084d953e42bf-uuid-02172f1a-804e-56c0-d0e7-149c2df2b92d.gif" align="center" width="700px" border={true} />

Click **View Only Edited Risks** to refine the list to previously edited risks. Sort the columns to bring important rows to the top of your view.

<Image src="https://files.readme.io/8ce29ca3a1057635ef1a99d8acb289ac239236293db74dafedca6ceb81ce746f-uuid-d507e836-447e-2ec0-7cfe-6e4c1395a773.gif" align="center" border={true} />

## Change risk severity to match your organization's risk tolerance

You can customize most risks' default severity to suit your organization's needs. You can also disable the risk type entirely.

Select from the list to see details and remediation recommendations.

<Image src="https://files.readme.io/a32c130115a473f53e908d0db26ee8fdfb33327f771c3a7e5a8382e99afd5cfb-uuid-43baea25-0a21-6ef5-d2b0-f00ecfdbaba4.gif" align="center" border={true} />

The Censys-recommended severity for each risk type is noted with the Recommended text. Use the Severity Selection menu to specify the severity classification that fits your organization’s policies. From highest to lowest, the options include:

* **Critical**: Indicates a severe risk that may result in compromise of the affected system or interruption of business objectives. Remediate critical risks as soon as possible.
* **High**: Indicates a risk that can result in remote code execution or sensitive information disclosure. Prioritize high risks when creating a risk remediation roadmap.
* **Medium**: Indicates a risk that can be exploited in combination with other vulnerabilities to perform an attack. Treat medium risks as a standard priority on a risk roadmap.
* **Low**: Indicates a vulnerability that can provide an attacker with some information about or access to the affected system. Deal with low risks at the lowest priority.

The default severity set for a type is assigned to any instance of that risk type found on any of your assets.