Ability to shortlist key risks in risk assessments

We’ve added the ability to create a shortlist of key risks as part of a risk assessment, allowing you to highlight important risks and those requiring follow-up. You can choose to include only key risks as part of your risk assessment report, in lieu of displaying the full list of risks. To learn more see How to complete a risk assessment.

API flexible permissions

We’ve revised API permissions to allow a finer-grained set of permissions and visibility:

Added a Read/Read&Write flag to allow a given API key to only access GET functions or to be able to access GET/PUT/POST and DELETE functions.
Expanded on the current Data Leaks permission to allow an API key to be defined by role.
To protect existing integrations all existing API Keys will be granted full access. The new model will only relate to keys generated after this release.

To learn more see UpGuard’s API documentation.

Vendor monitoring API changes

We’ve created specific API endpoints to start monitoring and stop monitoring a vendor. This allows us to follow more established and consistent API design practices as well as restrict the monitoring to only those API Keys that have Vendor Risk Read&Write permissions. In subsequent releases, we will deprecate the “start_monitoring” flag in the /vendor API endpoint and remove that feature:

Vendor ID or Primary Host Name) to the list of monitored vendors. This supports the same functionality as our existing /vendor API when start_monitoring = true, such as:

- The ability to apply labels and tiers;

- A wait for a scan feature that scans the vendor before returning the results;

- Checks on UpGuard licenses maximum Vendor counts.