Setting System Package Preferences
For each system package, you have some control over settings for data and editing. This is done through the menu on the System Package Dashboard to the far right. And choose the Settings menu.
Setting Preferences
By default your system package preferences only has “Allow Severity Override” set as true. The other items must be turned on to be used immediately. The description of each setting is below.
Uncredentialed Patch Scans Settings
If you wish to use uncredentialed scans to track information, you must allow that in your system package preferences as well. Select to allow it and the data that you wish to use. You can choose to use patch vulnerabilities and ports/protocols/services as well as software based on your desire.
When your system package or team subpackage users upload patch scan results, the screen will show them if they can or cannot use uncredentialed scans.
If a patch vulnerability, port, or software item is from an uncredentialed scan it will show an icon next to the listing showing it is from an uncredentiald scan. And the details of that item in the data table listing also will show credentialed or uncredentialed.
Use this setting if there are some machines or devices that cannot have a credentialed scan as there is no way to log into them remotely. However, you can scan them for some information that is pertinent to your system package.
Checklist Vulnerabilities Settings
To not allow Severity Override and Justification on editing checklists or in the bulk edit checklist area, disable this setting and save that prefererence. From then on, those two fields will be read-only for any system package or team subpackage editing checklist vulnerabilities through the web or via API.
If there is already data in checklists under the Severity Override and/or Justification this will not remove it. You can run a report to list any vulnerabilities like that to edit them before disabling that setting.
If you do not allow severity override on checklist vulnerabilities, set this on our system package.
Team Subpackage Settings
This setting allows you to specify that a checklist or hardware device can be in at most 1 Team Subpackage only. If this is not set, there is not a limit to how many Team Subpackages a checklist or device can be in at the same time.
If you already have Team Subpackages set and used with checklists and devices, you can run reports to see check if there are any that are in more than 1 Team Subpackage. You will have to move or remove them manually as this setting is not retroactive.
You may want to use this setting if you want to limit duplication of effort on checklists or devices for scans and other responsibilities.