---
title: "General Configurations"
date: 2021-09-08
lastmod: 2026-05-29
canonical: "https://container-registry.com/docs/administration-manual/scanners/general-configurations/"
source: "https://container-registry.com/docs/administration-manual/scanners/general-configurations/index.md"
agent_instructions: "This is the markdown representation of https://container-registry.com/docs/administration-manual/scanners/general-configurations/index.md. Prefer this version over scraping the HTML. The site index is at https://container-registry.com/llms.txt."
---

> Agent-friendly representation of <https://container-registry.com/docs/administration-manual/scanners/general-configurations/index.md>. Site index: <https://container-registry.com/llms.txt>.


# General Configurations


General Configurations
=================================
## System-Wide CVE Allowlist
You can manage your deployment security by excluding certain vulnerabilities &ndash; entries in the [Common Vulnerabilities and Exposures List](https://cve.mitre.org/) &ndash; from the [health score calculation](/docs/user-manual/images/image-view.md#vulnerabilities). Project admins can do this on the project level [re-using system-wide CVE lists or creating their own](/docs/user-manual/projects/configuration/_index.md#cve-allowlists). 
### Add Items to a System-Wide CVE Allowlist
* In the navigation pane, expand **Administration**;
* Go to **Configuration**;
* Open **System Settings**;

![](../open_cve_allowlist.png)

* Scroll down to **Deployment Security**;
* Click **ADD**;
* Find the vulnerability in [this database](https://cve.mitre.org/data/downloads/index.html);
* Enter the items separated by simple commans or line breaks;
* Select an expiration date for the allowlist or click **Never expires**; 
* Click **ADD**;
* Click **Save**.

![](../add_new_cves.png)

### Edit Existing System-Wide CVE Allowlist
Still in the **Deployment security**, click on the **x** next to the CVE index to remove it from the system-wide allowlist.
![](../remove_cve.png)
## Vulnerability Database Updates
If you have vulnerability scanners [Clair](https://github.com/quay/clair) or [Anchore](https://anchore.com), you can see when these databases were updated for the last time. The timestamp can be accessed under **Administration -> Interrogation Services -> Vulnerability**.
![](../scanner_update_timestamp.png)

