diff --git a/modules/checking-job-status-and-downloading-a-vulnerability-report-in-csv-format.adoc b/modules/checking-job-status-and-downloading-a-vulnerability-report-in-csv-format.adoc index 1deed884df37..81d6385afa31 100644 --- a/modules/checking-job-status-and-downloading-a-vulnerability-report-in-csv-format.adoc +++ b/modules/checking-job-status-and-downloading-a-vulnerability-report-in-csv-format.adoc @@ -6,6 +6,7 @@ [id="checking-job-status-and-downloading-a-vulnerability-report-in-csv-format_{context}"] = Checking job status and downloading a vulnerability report in CSV format +[role="_abstract"] You can check the job status and download a vulnerability report in CSV format when it is ready for download. [NOTE] @@ -20,12 +21,12 @@ You can check the job status and download a vulnerability report in CSV format w . Optional: Choose the appropriate method to re-organize the view-based vulnerability report list: * To filter the list according to the job status, click *Report job status*, and then select one or more job statuses. + -The following values are associated with the job status: +The following values apply to the job status: + ** `Waiting` ** `Preparing` ** `Report ready for download` ** `Report failed to generate` -* To sort the list in ascending or descending order according to the date and time the jobs are completed, click the *Completed* column heading. +* To sort the list in ascending or descending order according to the date and time the jobs complete, click the *Completed* column heading. * To view only the jobs that you created, set *View only my jobs* to on. \ No newline at end of file diff --git a/modules/user-permissions-for-vulnerability-reports.adoc b/modules/user-permissions-for-vulnerability-reports.adoc index 6ed80193960f..7b3814001b31 100644 --- a/modules/user-permissions-for-vulnerability-reports.adoc +++ b/modules/user-permissions-for-vulnerability-reports.adoc @@ -6,6 +6,7 @@ [id="user-permissions-for-vulnerability-reports_{context}"] = User permissions for vulnerability reports +[role="_abstract"] To access and manage vulnerability reporting features in {rh-rhacs-first}, you must have the following permissions: .Vulnerability report permissions @@ -24,6 +25,6 @@ To access and manage vulnerability reporting features in {rh-rhacs-first}, you m | `WorkflowAdministration` | `Write` a|* Create and delete report configurations. -* Initiate new report jobs. +* Start new report jobs. * Download the generated reports. |=== \ No newline at end of file diff --git a/modules/vulnerability-management-reporting.adoc b/modules/vulnerability-management-reporting.adoc index 5ea12537fbec..5217078c4dc6 100644 --- a/modules/vulnerability-management-reporting.adoc +++ b/modules/vulnerability-management-reporting.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: CONCEPT [id="vulnerability-management-reporting_{context}"] @@ -21,13 +21,13 @@ For sending these communications, consider the following questions: Vulnerability reports include information such as the following items: -* Cluster, namespace, deployment, or image that contains the vulnerability. +* Cluster, namespace, deployment, or image that has the vulnerability. * Component version: Lists the component that includes the discovered CVE. * CVE number: The unique identifier for the CVE. * Fixable: Indicates whether the CVE is fixable. -* Version: If applicable, lists the component version in which the CVE was fixed. +* Version: If applicable, lists the component version that fixes the CVE. * Severity: Originates directly from the upstream vulnerability data source specific to the affected package or operating system. If no severity label exists in the upstream source, but there is a raw Common Vulnerability Scoring System (CVSS) base score, {product-title-short} calculates a rating. If {product-title-short} cannot calculate the severity because information is incomplete or missing, it assigns an `unknown` severity. * CVSS: The single numerical CVSS base score assigned to that specific vulnerability. -* EPSS probability percentage: The likelihood that the vulnerability could be exploited according to the link:https://www.first.org/epss/[Exploit Prediction Scoring System (EPSS)]. This EPSS data provides a percentage estimate of the probability that exploitation of this vulnerability will be observed in the next 30 days. The EPSS collects data of observed exploitation activity from partners, and exploitation activity does not mean that an attempted exploitation was successful. Use the EPSS score as a single data point _along with other information_, such as the age of the CVE, to help you prioritize the vulnerabilities to address. For more information, see link:https://access.redhat.com/articles/7106599[{product-title-short} and EPSS]. This information is visible only when using Scanner V4. -* Discovered at: The time a CVE was first discovered in the associated image. If the image existed before the deployment was created, for example, as part of another deployment, then the "Discovered At" time will precede the deployment time. You can use this to determine the age of the CVE in an image. +* EPSS probability percentage: The likelihood that the vulnerability could be exploited according to the Exploit Prediction Scoring System (EPSS). This EPSS data provides a percentage estimate of the probability that exploitation of this vulnerability will be observed in the next 30 days. The EPSS collects data of observed exploitation activity from partners, and exploitation activity does not mean that an attempted exploitation was successful. Use the EPSS score as a single data point _along with other information_, such as the age of the CVE, to help you prioritize the vulnerabilities to address. For more information, see "{product-title-short} and EPSS". This information is visible only when using Scanner V4. +* Discovered at: The time a CVE was first discovered in the associated image. If the image existed before the deployment was created, for example, as part of another deployment, then the "Discovered At" time will precede the deployment time. You can use this to find the age of the CVE in an image. * Reference: Provides a URL to the upstream data source from which {product-title-short} obtains the vulnerability information. Depending on the type of package affected, the reference points to different sources such as the Red Hat CVE database, the National Vulnerability Database (NVD), or the Open Source Vulnerabilities database (OSV.dev). You can use this URL to manually verify the impact, read detailed descriptions, or review mitigation instructions directly from the source that provided the rating. \ No newline at end of file diff --git a/modules/vulnerability-management20-clone-reports.adoc b/modules/vulnerability-management20-clone-reports.adoc index 5e651667eac6..3c9e4f806ef1 100644 --- a/modules/vulnerability-management20-clone-reports.adoc +++ b/modules/vulnerability-management20-clone-reports.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-clone-reports_{context}"] diff --git a/modules/vulnerability-management20-configure-report-delivery-destinations-schedule.adoc b/modules/vulnerability-management20-configure-report-delivery-destinations-schedule.adoc index 60f3702e4d06..2934f0c6c404 100644 --- a/modules/vulnerability-management20-configure-report-delivery-destinations-schedule.adoc +++ b/modules/vulnerability-management20-configure-report-delivery-destinations-schedule.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-configure-report-delivery-destinations-schedule_{context}"] @@ -10,16 +10,16 @@ Configuring destinations and delivery schedules for vulnerability reports is optional. You can configure email destinations and schedule delivery. .Procedure -. To email reports, you must configure at least one email notifier. Select an existing notifier or create a new email notifier to send your report by email. For more information about creating an email notifier, see "Configuring the email plugin" in the "Additional resources" section. +. To email reports, you must configure at least one email notifier. Select an existing notifier or create a new email notifier to send your report by email. + -When you select a notifier, the email addresses configured in the notifier as *Default recipients* appear in the *Distribution list* field. You can add additional email addresses that are separated by a comma. +When you select a notifier, the email addresses configured in the notifier as *Default recipients* appear in the *Distribution list* field. You can add additional email addresses, separated by a comma. . A default email template is automatically applied. You can change the following values: * Custom subject * Custom body + [NOTE] ==== -When reviewing the report jobs for a specific report, you can see whether the default template or a customized template was used when creating the report. +When reviewing the report jobs for a specific report, you can see whether the system used the default template or a customized template when creating the report. ==== . In the *Configure schedule* section, select the frequency, days, and time for generation of the report. . Click *Next* to review your vulnerability report configuration and finish creating it. \ No newline at end of file diff --git a/modules/vulnerability-management20-creating-report.adoc b/modules/vulnerability-management20-creating-report.adoc index cf1ce0902eff..d2fc1605cfbb 100644 --- a/modules/vulnerability-management20-creating-report.adoc +++ b/modules/vulnerability-management20-creating-report.adoc @@ -1,18 +1,18 @@ // Module included in the following assemblies: // -// * operating/vulnerability-reporting.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-creating-report_{context}"] = Creating vulnerability management report configurations [role="_abstract"] -{product-title-short} guides you through the process of creating a vulnerability management report. Your configuration determines the information that the report includes. You can run report jobs at a scheduled time or on-demand. +{product-title-short} guides you through the process of creating a vulnerability management report. Your configuration determines the information that the report includes. You can run report jobs at a scheduled time or on-demand. .Procedure . Do one of the following actions: -* In the {product-title-short} portal, click *Vulnerability Management* -> *Reports* and ensure that the *Report configurations* tab is active, then click *Create report*. -* In *Vulnerability Management* -> *Results*, click *Create report* and select *Create a scheduled report*. +* In the {product-title-short} portal, click *Vulnerability Management* -> *Reports* and ensure that the *Report configurations* tab is active, then click *Create report*. +* In *Vulnerability Management* -> *Results*, click *Create report* and select *Create a scheduled report*. . In *Details*, enter the following information: ** *Name*: Enter a name for the report. ** *Description*: Enter text describing the report. This is optional. @@ -20,7 +20,7 @@ * *Deployed images* * *Watched images* . Configure the scope of the report by selecting the scope method. This is irrelevant for watched images, which typically are not part of a namespace. Deployed images require a scope. -* *Collection scope*: Choose the collection you want to use when collecting data for the report. This option is deprecated and will be removed in a future release. +* *Collection scope*: Choose the collection you want to use when collecting data for the report. This option is deprecated and will be removed in a future release. * *Custom scope*: Select *Custom scope* to add clusters, deployments, or namespaces to use when collecting data for the report. You can identify clusters by name, ID, or label. You can identify deployments and namespaces by annotation, ID, label, or name. Add more than one scope criteria to narrow down the vulnerabilities reported. . In *Filters*, configure the following items: * *CVEs discovered in image since*: Select the time period for which you want to include the CVEs in the report configuration. @@ -30,7 +30,7 @@ ** *Deferred* ** *False positives* * *CVE severity*: Select the severity of CVEs that you want to include in the report configuration. -* *CVE status*: Select one or more CVE statuses: +* *CVE status*: Select one or more CVE statuses: ** *Fixable* ** *Unfixable* . To filter for a specific CVE, image, or image component, use the selection criteria and enter the information to filter. For example, you can filter for a specific CVE name by selecting *CVE*, selecting *Name*, and entering the name of a CVE. You can use wildcards. Add additional filters to further narrow down the information included on the report. diff --git a/modules/vulnerability-management20-delete-reports.adoc b/modules/vulnerability-management20-delete-reports.adoc index 992c9a3bf921..56f16330c9cf 100644 --- a/modules/vulnerability-management20-delete-reports.adoc +++ b/modules/vulnerability-management20-delete-reports.adoc @@ -1,13 +1,13 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-delete-reports_{context}"] = Deleting vulnerability report configurations [role="_abstract"] -Deleting a report configuration deletes the configuration and any reports that were previously run using this configuration. +Deleting a report configuration deletes the configuration and any reports already run using this configuration. .Procedure . In the {product-title-short} portal, click the *Vulnerability Management* -> *Reports* -> *Report configurations* tab. diff --git a/modules/vulnerability-management20-download-reports.adoc b/modules/vulnerability-management20-download-reports.adoc index 500248be22f2..d70f60c254d2 100644 --- a/modules/vulnerability-management20-download-reports.adoc +++ b/modules/vulnerability-management20-download-reports.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-download-reports_{context}"] diff --git a/modules/vulnerability-management20-edit-reports.adoc b/modules/vulnerability-management20-edit-reports.adoc index 70b35f1de639..6a62c641c325 100644 --- a/modules/vulnerability-management20-edit-reports.adoc +++ b/modules/vulnerability-management20-edit-reports.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-edit-reports_{context}"] diff --git a/modules/vulnerability-management20-permissions.adoc b/modules/vulnerability-management20-permissions.adoc index 3c0c27da79f1..6a3cd9adb1d4 100644 --- a/modules/vulnerability-management20-permissions.adoc +++ b/modules/vulnerability-management20-permissions.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: CONCEPT [id="vulnerability-management20-permissions_{context}"] @@ -12,4 +12,4 @@ The ability to create, view, and download reports depends on the access control For example, you can only view, create, and download reports for data that your user account has permission to access. In addition, the following restrictions apply: * You can only download reports that you have generated; you cannot download reports generated by other users. -* Report permissions are restricted depending on the access settings for user accounts. If the access settings for your account change, old reports do not reflect the change. For example, if you are given new permissions and want to view vulnerability data that is now allowed by those permissions, you must create a new vulnerability report. \ No newline at end of file +* Report permissions depend on the access settings for user accounts. If the access settings for your account change, old reports do not reflect the change. For example, if you receive new permissions and want to view vulnerability data that is now allowed by those permissions, you must create a new vulnerability report. \ No newline at end of file diff --git a/modules/vulnerability-management20-report-review-create.adoc b/modules/vulnerability-management20-report-review-create.adoc index 8e104f12b8cb..3dc00ad7ad73 100644 --- a/modules/vulnerability-management20-report-review-create.adoc +++ b/modules/vulnerability-management20-report-review-create.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-report-review-create_{context}"] @@ -10,5 +10,5 @@ You can review the details of your vulnerability report configuration before creating it. .Procedure -. In the *Review* section, you can review the report configuration parameters, delivery destination, and delivery schedule. To make any changes, click *Back* to go to the previous section and edit the fields that you want to change. +. In the *Review* section, you can review the report configuration parameters, delivery destination, and delivery schedule. To make any changes, click *Back* to go to the earlier section and edit the fields that you want to change. . To create the report configuration and save it, click *Save*. \ No newline at end of file diff --git a/modules/vulnerability-management20-retention-settings.adoc b/modules/vulnerability-management20-retention-settings.adoc index f7ca56cb6afd..71c081358a81 100644 --- a/modules/vulnerability-management20-retention-settings.adoc +++ b/modules/vulnerability-management20-retention-settings.adoc @@ -1,13 +1,13 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-retention-settings_{context}"] = Configuring vulnerability management report job retention settings [role="_abstract"] -You can configure settings that determine when vulnerability report job requests expire and other retention settings for report jobs. +You can configure settings that decide when vulnerability report job requests expire and other retention settings for report jobs. [NOTE] ==== @@ -22,10 +22,10 @@ These settings do not affect the following vulnerability report jobs: .Procedure . In the {product-title-short} web portal, go to *Platform Configuration* -> *System Configuration*. You can configure the following settings for vulnerability report jobs: -* *Vulnerability report run history retention*: The number of days that a record is kept of vulnerability report jobs that have been run. This setting controls how many days that report jobs are listed in the *Report configurations* tab under *Vulnerability Management* -> *Vulnerability Reporting* when a report configuration is selected. The entire report history after the exclusion date is deleted, with the exception of the following jobs: +* *Vulnerability report run history retention*: The number of days that the system keeps a record of vulnerability report jobs. This setting controls how many days report jobs appear in the *Report configurations* tab under *Vulnerability Management* -> *Vulnerability Reporting* when you select a report configuration. The system deletes the entire report history after the exclusion date, with the exception of the following jobs: ** Unfinished jobs. ** Jobs for which prepared downloadable reports still exist in the system. ** The last successful report job for each job type (scheduled email, on-demand email, or download). This ensures users have information about the last run job for each type. -* *Prepared downloadable vulnerability reports retention days*: The number of days that prepared, on-demand downloadable vulnerability report jobs are available for download on the *Report configurations* tab under *Vulnerability Management* -> *Vulnerability Reporting* when a report configuration is selected. -* *Prepared downloadable vulnerability reports limit*: The limit, in MB, of space allocated to prepared downloadable vulnerability report jobs. After the limit is reached, the oldest report job in the download queue is removed. +* *Prepared downloadable vulnerability reports retention days*: The number of days that prepared, on-demand downloadable vulnerability report jobs remain available for download on the *Report configurations* tab under *Vulnerability Management* -> *Vulnerability Reporting* when you select a report configuration. +* *Prepared downloadable vulnerability reports limit*: The limit, in MB, of space allocated to prepared downloadable vulnerability report jobs. After the system reaches the limit, it removes the oldest report job in the download queue. . To change these values, click *Edit*, make your changes, and then click *Save*. \ No newline at end of file diff --git a/modules/vulnerability-management20-send-reports.adoc b/modules/vulnerability-management20-send-reports.adoc index c3ec1fd42743..e78e6e49cb80 100644 --- a/modules/vulnerability-management20-send-reports.adoc +++ b/modules/vulnerability-management20-send-reports.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * operating/manage-vulnerabilities.adoc +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc :_mod-docs-content-type: PROCEDURE [id="vulnerability-management20-send-reports_{context}"] diff --git a/modules/vulnerability-reporting-overview.adoc b/modules/vulnerability-reporting-overview.adoc new file mode 100644 index 000000000000..1335a0658336 --- /dev/null +++ b/modules/vulnerability-reporting-overview.adoc @@ -0,0 +1,19 @@ +// Module included in the following assemblies: +// +// * operating/manage-vulnerabilities/vulnerability-reporting.adoc + +:_mod-docs-content-type: CONCEPT +[id="vulnerability-reporting-overview_{context}"] += Vulnerability reporting overview + +[role="_abstract"] +You can create and download on-demand image vulnerability reports that include a comprehensive list of common vulnerabilities and exposures (CVEs) in clusters, deployments, and namespaces. + +Vulnerabilities reported include the following: + +* Workload CVEs: Vulnerabilities in the application images of a deployment +* Platform CVEs: Vulnerabilities related specifically to the orchestrator itself, such as the kube-api-server or generic OpenShift vulnerabilities; limited to container images that appear in namespaces designated as "Platform Components" + +To share vulnerability reports with auditors or internal stakeholders, you can schedule emails in {product-title-short} or download the report and share it by using other methods. + +In addition to creating reports from the *Image vulnerability reports* page, you can also begin a new report configuration directly from your active workflow filters in the *Vulnerability Management* -> *Results* page. You can select *Create report* -> *Scheduled report* after you apply your filter criteria, and the system creates a report that uses the filters you have selected. diff --git a/operating/manage-vulnerabilities/vulnerability-reporting.adoc b/operating/manage-vulnerabilities/vulnerability-reporting.adoc index a324a491c426..28c52a28a146 100644 --- a/operating/manage-vulnerabilities/vulnerability-reporting.adoc +++ b/operating/manage-vulnerabilities/vulnerability-reporting.adoc @@ -7,29 +7,33 @@ include::modules/common-attributes.adoc[] toc::[] [role="_abstract"] +You can create and download on-demand image vulnerability reports by clicking *Vulnerability Management* -> *Reports* and selecting the *Report configurations* tab in the {rh-rhacs-first} portal. -You can create and download an on-demand image vulnerability report by clicking *Vulnerability Management* -> *Reports* and selecting the *Report configurations* tab in the {rh-rhacs-first} portal. This report includes a comprehensive list of common vulnerabilities and exposures (CVEs) in clusters, deployments, and namespaces. - -Vulnerabilities reported include the following: - -* Workload CVEs: Vulnerabilities in the application images of a deployment -* Platform CVEs: Vulnerabilities related specifically to the orchestrator itself, such as the kube-api-server or generic OpenShift vulnerabilities; limited to container images that appear in namespaces designated as "Platform Components" - -To share vulnerability reports with auditors or internal stakeholders, you can schedule emails in {product-title-short} or download the report and share it by using other methods. - -In addition to creating reports from the *Image vulnerability reports* page, you can also begin a new report configuration directly from your active workflow filters in the *Vulnerability Management* -> *Results* page. You can select *Create report* -> *Scheduled report* after you apply your filter criteria, and the system creates a report that uses the filters you have selected. +//Vulnerability reporting overview +include::modules/vulnerability-reporting-overview.adoc[leveloffset=+1] +//Reporting vulnerabilities to teams include::modules/vulnerability-management-reporting.adoc[leveloffset=+1] -//creating the report +[role="_additional-resources"] +.Additional resources +* link:https://www.first.org/epss/[Exploit Prediction Scoring System (EPSS)] +* link:https://access.redhat.com/articles/7106599[{product-title-short} and EPSS] + +//Creating vulnerability management report configurations include::modules/vulnerability-management20-creating-report.adoc[leveloffset=+1] -//configuring destinations and scheduling +//Configuring delivery destinations and scheduling include::modules/vulnerability-management20-configure-report-delivery-destinations-schedule.adoc[leveloffset=+2] +[role="_additional-resources"] +.Additional resources +* xref:../../integration/integrate-with-email.adoc#configure-acs-email_integrate-with-email[Configuring the email plugin] + +//Reviewing and creating the report configuration include::modules/vulnerability-management20-report-review-create.adoc[leveloffset=+2] -//report permissions +//Vulnerability report permissions include::modules/vulnerability-management20-permissions.adoc[leveloffset=+2] //User permissions for vulnerability reports @@ -37,7 +41,6 @@ include::modules/user-permissions-for-vulnerability-reports.adoc[leveloffset=+3] [role="_additional-resources"] .Additional resources - * xref:../../operating/manage-user-access/manage-role-based-access-control-3630.adoc#resource-definitions_manage-role-based-access-control[Resource definitions] //Vulnerability report row limit @@ -46,12 +49,11 @@ include::modules/vulnerability-report-row-limit.adoc[leveloffset=+2] //Configuring the vulnerability report row limit include::modules/configure-vulnerability-report-row-limit.adoc[leveloffset=+3] -//Exporting vulnerability report as a CSV file +//Exporting a vulnerability report as a CSV file include::modules/exporting-vulnerability-report-as-a-csv-file.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources - * xref:../../operating/manage-vulnerabilities/vulnerability-reporting.adoc#configure-vulnerability-report-row-limit_vulnerability-reporting[Configuring the vulnerability report row limit] //Checking job status and downloading a vulnerability report in CSV format @@ -59,25 +61,24 @@ include::modules/checking-job-status-and-downloading-a-vulnerability-report-in-c [role="_additional-resources"] .Additional resources - * xref:../../operating/manage-vulnerabilities/vulnerability-reporting.adoc#configure-vulnerability-report-row-limit_vulnerability-reporting[Configuring the vulnerability report row limit] -//editing reports +//Editing vulnerability report configurations include::modules/vulnerability-management20-edit-reports.adoc[leveloffset=+2] -//downloading reports +//Downloading vulnerability reports include::modules/vulnerability-management20-download-reports.adoc[leveloffset=+2] -//sending reports +//Sending vulnerability reports on-demand include::modules/vulnerability-management20-send-reports.adoc[leveloffset=+2] -//cloning reports +//Cloning vulnerability report configurations include::modules/vulnerability-management20-clone-reports.adoc[leveloffset=+2] -//deleting reports +//Deleting vulnerability report configurations include::modules/vulnerability-management20-delete-reports.adoc[leveloffset=+2] -//report settings +//Configuring vulnerability management report job retention settings include::modules/vulnerability-management20-retention-settings.adoc[leveloffset=+2] [role="_additional-resources"] @@ -86,5 +87,4 @@ include::modules/vulnerability-management20-retention-settings.adoc[leveloffset= * xref:../../operating/create-use-collections.adoc#create-use-collections[Creating and using deployment collections] * xref:../../operating/create-use-collections.adoc#migrate-scope-collections_create-use-collections[Migration of access scopes to collections] -* xref:../../integration/integrate-with-email.adoc#configure-acs-email_integrate-with-email[Configuring the email plugin] * xref:../../installing/installing_ocp/install-central-config-options-ocp.adoc#central-configuration-options-operator_install-central-config-options-ocp[Central configuration options using the Operator] \ No newline at end of file