Define background job configurations in Vulnerability Response
Define how many tasks you want to run concurrently for a given background job. You can also set the job to import partitions of data so the tasks complete more quickly and easily and use less of your system resources. If you determine it’s running too long, you can also cancel a job.
Before you begin
Role required: sn_vul.vulnerability_admin or Vulnerability managers with the sn_sec_cmn.manage_background_job granular role
See the section below the steps for an example.
Procedure
Navigate to All > Security Operations > Background Job Configurations.
In the Name column, select a record to open it.
Edit the fields.
Background job record view.
| Field | Description |
|---|---|
| Name | Name of the job. |
| Configuration ID | Read-only. Unique ID used to identify the job. |
| Background Job Capability | Choose one. - Partition and Concurrency Enabled: A job with a long run time can be split up, and the job can be run in parallel with another job of the same type. - Concurrency Enabled: The job can be run in parallel with another job of the same type. - Cancel Enabled: The job can be canceled. - Concurrency and Cancel Enabled: The job can be run in parallel with another job and be canceled. - Partition, Concurrency, and Cancel Enabled: A job with a long run time can be split up, the job can be run in parallel with another job of the same type, and the job can be canceled. - None The displayed value indicates if a job supports partitioning, concurrency, and cancellation. |
| Max Concurrent Threads | This field is displayed only if concurrency is supported. Enter the maximum number of jobs that you want this configuration to run in parallel. The number of scheduled jobs supported by your instance is by default 10. You can lower this value if you believe that you might use, or have lower system resources available to run your background jobs. |
| Active | Enable or disable the jobIf a job is inactive, you can’t create jobs of this type. Any existing jobs in the queue are not processed. |
| Enable Partition | This field is displayed only if partitioning is supported. This option permits you to limit and define the number of items this job can process at one time. The Size of Partition field is also displayed. If you leave this field turned off, background jobs that support partitioning process all the items in your instance with this job. |
| Size of Partition | This field is displayed only if partitioning is supported. Default is 10,000 items. Enter a value for the number of items according to data chunk you want this job to process. This option is available for jobs that process large numbers of records such as vulnerable items \(VIs\), remediation tasks, test results, and test result groups. |
| Execution script | Displays the job processor that is used to run this job. A default method for jobs that support partitioning is provided. |
| Enable Cancel | This field is only displayed if job cancellation is supported. This option is supported for jobs that process discovered items and reapply CI rules. |
Select Update to save your changes.
Verify results for your configuration changes.
The application includes one Remediation Target Rules job configuration - Reapply Remediation Target Rules.
If you have made changes to your remediation target rules and need to reapply them while conserving system processing resources, you can optimize performance through the Background Job Configurations module. This module allows you to control:
- The number of concurrent background jobs
- The number of items processed per job By adjusting these settings, you can reapply your remediation target rules without consuming excessive system resources.
To define these settings, navigate to Security Operations > Background Job Configurations and select Reapply Remediation Target Rules to open the configuration job record.
Background job record view.
For the sake of the example, say you know you have just over 300 VIs.
On the open configuration job record, change the Partition size value from 4 to 10.
Navigate to Vulnerability Response > Remediation Target Rules, locate the Reapply vulnerability remediation rule you changed, select the record from the list and select Apply Changes to reevaluate your target rules for your existing VIs.
The Reapply vulnerability remediation rules job is queued.
Select the View status link to view the Background job record and verify that the jobs are queued, as shown in the following image.
For this example, 33 jobs are created to process target rules for 327 VIs (a maximum of 10 items per job). These jobs are child jobs of the primary background job. The child jobs process the records sequentially.
Background child jobs listed.
When all the jobs are successfully completed, the fields are updated on the Background Job record.
Status complete with updated fields on the Background Job record.
- Navigate to the vulnerable items and verify that they reflect your new rule change.
Parent Topic:Vulnerability Response background job framework configuration