Skip to main content

How to configure the risk acceptance workflow

This guide explains how to customize the risk acceptance workflow in Snyk API & Web to align with your organization's internal security and compliance processes.

Written by Claudio Gamboa

By configuring this feature, you can require users to provide specific information—such as an expiration date or an approver's name—when they move a finding to the Accepted Risk state. This ensures that risk acceptance is consistently documented and periodically reviewed.

Part 1: Configure the risk acceptance workflow

As the Account Owner, you can define which fields are mandatory when a user accepts the risk of a finding.

  1. From the side menu in your Snyk API & Web account, navigate to Settings > Scan Settings.

  2. Locate the RISK ACCEPTANCE WORKFLOW module.

  3. Select the checkboxes for the fields you want to require:

    • Expiration date: Requires the user to set a date on which the risk acceptance will automatically expire. If you select this, you can also set a maximum acceptance period (in days) to limit how far in the future the expiration date can be.

    • Approver name: Requires the user to enter the name of the person who approved the finding.

    • Approval date: Requires the user to enter the date when the finding was approved.

  4. Click Save to apply your changes.

Part 2: How to accept a finding's risk

Once the workflow is configured, any user accepting a finding's risk is prompted to provide the required information.

  1. Navigate to any page where findings are listed (e.g., the global Findings page or a target's details page).

  2. Select one or more findings you wish to accept.

  3. From the State drop-down menu, select Accepted Risk.

  4. A dialog box is displayed, listing the custom fields you configured in Part 1.

  5. Fill out the required information and click Accept risk.

Verify the outcome

After you submit the form, the state of the selected findings changes to Accepted Risk. This action, along with all the information you provided, is recorded in both the individual finding logs and the account audit log.

If an expiration date was set for a finding, its state is automatically reverted from Accepted Risk back to Not Fixed once that date is reached, ensuring it is re-evaluated in future scans.

Did this answer your question?