Container Vulnerable Item form fields
Container vulnerable items (CVITs) are automatically created during third-part vulnerability integration imports.
Container vulnerable item form fields
Except for the Assignment group, Assigned to fields and Notes, all other fields in the CVIT are read only.
|
Field |
Description |
|---|---|
|
Number |
Automatically generated CVIT identifier for this record. |
|
Source |
Scanner that has identified the vulnerability. |
|
Risk rating |
Quantified Risk Score separating vulnerable items into Critical, High, Medium, Low, and None. |
|
Risk score |
Calculated amount of risk the CVIT poses to your environment. |
|
Remediation target rule |
Remediation target rule according to which the remediation target date is calculated. |
|
Remediation target |
Date by which the CVITs should be remediated, since first identified. Only appears when applicable. |
|
Remediation status |
Status of the remediation for the CVIT. |
|
Vulnerability |
ID of the vulnerability associated with this application vulnerable item. |
|
Docker Image |
Template file that contains code, required libraries, configurations, and so on. The file is used to launch container instances. It consists of a union of layered file systems. |
|
Discovered Container Image |
Unique record for each image ID. |
|
Base Image |
A foundational image used to create containerized applications, containing the essential operating system and libraries. It serves as the starting point for building and customizing applications in environments like Docker. |
|
Image Clusters |
Groups of related images used in various contexts, such as clustering similar images in machine learning or container images in a repository. |
|
Image namespace |
Used to organize and isolate container images within a registry, enabling different teams or projects to maintain separate collections. |
|
State |
This field defaults to Open when created. See Application Vulnerable Item (AVI) states for more information on how states are mapped. |
|
Assignment group |
Group selected to work on this CVIT. |
|
Assigned to |
Individual from the selected assignment group that works on this CVIT. Can be manually added or edited by an App-Sec Manager. |
|
Created |
Date and time at which a CVIT is created. |
|
Last Opened |
Latest date and time at which the CVIT is reopened. |
|
Updated |
Date and time at which the CVIT is last modified. |
|
First found (v2.12.1) |
Date the vulnerability was first found.Starting with v2.12.1, you can see the precise date and time when it was first discovered, ensuring clarity and accounting for different time zones. To populate the first found date and time details, the integration must be rerun. |
|
Last found (v2.12.1) |
Date the vulnerability was last found.Starting with v2.12.1, you can see the precise date and time when it was last found, ensuring clarity and accounting for different time zones. To populate the last found date and time details, the integration must be rerun. |
|
Resolution date(v2.12.1) |
Date the vulnerability was resolved.Starting with v2.12.1, you can see the precise date and time when it was resolved, ensuring clarity and accounting for different time zones. The resolution date is populated when the CVIT is resolved as part of the workflow. |
|
Last opened (v2.12.1) |
Date the vulnerability was last opened.Starting with v2.12.1, you can see the precise date and time when it was last opened, ensuring clarity and accounting for different time zones. The scheduled job Add default values for last_opened_dt_tm from last _opened populates the data in this field. It must be executed only once on-demand. |
|
Vulnerability | |
|
Summary |
Description of the vulnerability. |
|
Severity |
Normalized degree of severity of this vulnerability. Severity maps are provided for National Vulnerability Database (NVD) and with ServiceNow third-party integrations. |
|
Vulnerability score (v3) |
Common Vulnerability Scoring System (CVSS) v3 score. |
|
Vulnerability score (v2) |
CVSS v2 score. |
|
Exploit exists |
Yes, if at least one exploit is associated with the vulnerabilities associated with this vulnerable item. |
|
Exploit attack vector |
Most vulnerable attack vector of the exploits for the vulnerabilities associated with this vulnerable item. |
|
Exploit skill level |
Lowest skill level required to exploit the vulnerabilities associated with this vulnerable item. |
|
Date published |
Date the vulnerability was published. |
|
Last modified |
Date the vulnerability was last modified. |
|
Threat |
Relevant information about the threat. Pulled from the vulnerable entry record.Note: Any changes made here update the vulnerable entry record. |
|
Remediation notes |
Relevant solution to the threat, pulled from the vulnerable entry record. |
|
Notes | |
|
Work notes |
Any relevant information. Select the text box for Work notes to add information. |
|
Image Findings |
Results of scanning container images for vulnerabilities. |
|
Requested Approvals |
Approvals request raised for the CVIT. |
|
State Change Approvals |
State change approvals request raised for the CVIT. |
- The Age column in the CVITs' list displays the duration (format: Days HH:MM:SS) for which a CVIT is active. The Age value is zero for a closed CVIT.
- The Age closed column in the CVITs' list displays the duration (format: Days HH:MM:SS) for which a CVIT is active before it’s closed. For CVITs, other than in the Closed state, the Age closed value is zero.
For more information on how to customize the calculation of Age and Age closed durations, see the KB1703270 article.
Parent Topic:Container Vulnerability Response reference
--- title: Container Vulnerable Item form fields description: Container vulnerable items \(CVITs\) are automatically created during third-part vulnerability integration imports. locale: en-US canonical_url: https://www.servicenow.com/docs/r/security-management/container-vulnerability-response/container-vul-items-fields.html release: brazil product: Container Vulnerability Response classification: container-vulnerability-response topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 4 breadcrumb: [Reference, Container Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # Container Vulnerable Item form fields Container vulnerable items \(CVITs\) are automatically created during third-part vulnerability integration imports. ## Container vulnerable item form fields Except for the **Assignment group**, **Assigned to** fields and **Notes**, all other fields in the CVIT are read only. <table id="table_t4d_4bd_5s"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> Automatically generated CVIT identifier for this record. </td></tr><tr><td> Source </td><td> Scanner that has identified the vulnerability. </td></tr><tr><td> Risk rating </td><td> Quantified **Risk Score** separating vulnerable items into Critical, High, Medium, Low, and None. </td></tr><tr><td> Risk score </td><td> Calculated amount of risk the CVIT poses to your environment. </td></tr><tr><td> Remediation target rule </td><td> Remediation target rule according to which the remediation target date is calculated. </td></tr><tr><td> Remediation target </td><td> Date by which the CVITs should be remediated, since first identified. Only appears when applicable. </td></tr><tr><td> Remediation status </td><td> Status of the remediation for the CVIT. </td></tr><tr><td> Vulnerability </td><td> ID of the vulnerability associated with this application vulnerable item. </td></tr><tr><td> Docker Image </td><td> Template file that contains code, required libraries, configurations, and so on. The file is used to launch container instances. It consists of a union of layered file systems. </td></tr><tr><td> Discovered Container Image </td><td> Unique record for each image ID. </td></tr><tr><td> Base Image </td><td> A foundational image used to create containerized applications, containing the essential operating system and libraries. It serves as the starting point for building and customizing applications in environments like Docker. </td></tr><tr><td> Image Clusters </td><td> Groups of related images used in various contexts, such as clustering similar images in machine learning or container images in a repository. </td></tr><tr><td> Image namespace </td><td> Used to organize and isolate container images within a registry, enabling different teams or projects to maintain separate collections. </td></tr><tr><td> State </td><td> This field defaults to **Open** when created. See [Application Vulnerable Item \(AVI\) states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/application-vulnerability-response/avm-states.md) for more information on how states are mapped. </td></tr><tr><td> Assignment group </td><td> Group selected to work on this CVIT. </td></tr><tr><td> Assigned to </td><td> Individual from the selected assignment group that works on this CVIT. Can be manually added or edited by an App-Sec Manager. </td></tr><tr><td> Created </td><td> Date and time at which a CVIT is created. </td></tr><tr><td> Last Opened </td><td> Latest date and time at which the CVIT is reopened. </td></tr><tr><td> Updated </td><td> Date and time at which the CVIT is last modified. </td></tr><tr><td> First found \(v2.12.1\) </td><td> Date the vulnerability was first found.Starting with v2.12.1, you can see the precise date and time when it was first discovered, ensuring clarity and accounting for different time zones. To populate the first found date and time details, the integration must be rerun. </td></tr><tr><td> Last found \(v2.12.1\) </td><td> Date the vulnerability was last found.Starting with v2.12.1, you can see the precise date and time when it was last found, ensuring clarity and accounting for different time zones. To populate the last found date and time details, the integration must be rerun. </td></tr><tr><td> Resolution date\(v2.12.1\) </td><td> Date the vulnerability was resolved.Starting with v2.12.1, you can see the precise date and time when it was resolved, ensuring clarity and accounting for different time zones. The resolution date is populated when the CVIT is resolved as part of the workflow. </td></tr><tr><td> Last opened \(v2.12.1\) </td><td> Date the vulnerability was last opened.Starting with v2.12.1, you can see the precise date and time when it was last opened, ensuring clarity and accounting for different time zones. The scheduled job **Add default values for last\_opened\_dt\_tm from last \_opened** populates the data in this field. It must be executed only once on-demand. </td></tr><tr><td colspan="2"> **Vulnerability** </td></tr><tr><td> Summary </td><td> Description of the vulnerability. </td></tr><tr><td> Severity </td><td> Normalized degree of severity of this vulnerability. Severity maps are provided for National Vulnerability Database \(NVD\) and with ServiceNow third-party integrations. </td></tr><tr><td> Vulnerability score \(v3\) </td><td> Common Vulnerability Scoring System \(CVSS\) v3 score. </td></tr><tr><td> Vulnerability score \(v2\) </td><td> CVSS v2 score. </td></tr><tr><td> Exploit exists </td><td> Yes, if at least one exploit is associated with the vulnerabilities associated with this vulnerable item. </td></tr><tr><td> Exploit attack vector </td><td> Most vulnerable attack vector of the exploits for the vulnerabilities associated with this vulnerable item. </td></tr><tr><td> Exploit skill level </td><td> Lowest skill level required to exploit the vulnerabilities associated with this vulnerable item. </td></tr><tr><td> Date published </td><td> Date the vulnerability was published. </td></tr><tr><td> Last modified </td><td> Date the vulnerability was last modified. </td></tr><tr><td> Threat </td><td> Relevant information about the threat. Pulled from the vulnerable entry record.**Note:** Any changes made here update the vulnerable entry record. </td></tr><tr><td> Remediation notes </td><td> Relevant solution to the threat, pulled from the vulnerable entry record. </td></tr><tr><td colspan="2"> **Notes** </td></tr><tr><td> Work notes </td><td> Any relevant information. Select the text box for Work notes to add information. </td></tr><tr><td> **Image Findings** </td><td> Results of scanning container images for vulnerabilities. </td></tr><tr><td> **Requested Approvals** </td><td> Approvals request raised for the CVIT. </td></tr><tr><td> **State Change Approvals** </td><td> State change approvals request raised for the CVIT. </td></tr></tbody> </table>Age calculations of a CVIT: - The Age column in the CVITs' list displays the duration \(format: Days HH:MM:SS\) for which a CVIT is active. The Age value is zero for a closed CVIT. - The Age closed column in the CVITs' list displays the duration \(format: Days HH:MM:SS\) for which a CVIT is active before it’s closed. For CVITs, other than in the Closed state, the Age closed value is zero. For more information on how to customize the calculation of Age and Age closed durations, see the [KB1703270](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1703270) article. **Parent Topic:**[Container Vulnerability Response reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/container-vulnerability-response/cvr-reference.md)
| title | Container Vulnerable Item form fields |
| description | Container vulnerable items \(CVITs\) are automatically created during third-part vulnerability integration imports. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/security-management/container-vulnerability-response/container-vul-items-fields.html |
| release | brazil |
| product | Container Vulnerability Response |
| classification | container-vulnerability-response |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 4 |
| breadcrumb | ReferenceContainer Vulnerability ResponseUnified Security Exposure ManagementSecurity Operations |