Scoring and Remediation

Once the relevant fields have been captured, the next step in the lifecycle of a risk is to identify its true urgency by assigning values for Likelihood and Impact. The combination of these two fields produces the Urgency score, which sets a Due Date based on the SLA.

AI Suggest Score

You can score risks in three ways: manually, with AI for a single risk, or with AI in bulk.

Manual Scoring

Open the risk and select Likelihood and Impact values. The Urgency score is assigned automatically based on the combination selected. Click Save to populate the Due Date.

Single-Risk AI Scoring

Navigate to the risk in the detailed view and click the purple star icon (top-right) to run the AI Suggest Score feature. The AI proposes values for Likelihood and Impact, highlighting those fields with a purple border. If the rationale resonates, click Save to accept or Cancel to discard. If saved, the reasoning is memorialized within the Comments section. After saving, the status updates to Urgency Proposed.

Tip

When scoring and wanting to add additional details, ensure changes to AI-relevant fields are saved first. One approach is to add new details in Comments, then rerun AI Scoring. To avoid previous AI comments influencing the new run, users can delete previously memorialized comments before rescoring.

Bulk AI Scoring

Navigate to the table view and select one or more risks using the checkboxes. A toolbar will display the option for AI Scoring. Click the purple star to start bulk scoring. If any items were previously scored, you will see a notice. Click Proceed to rescore, review the results, and Save. The status of scored risks updates to Urgency Proposed.

Jira Integration

After assigning Urgency and the Due Date of a risk, the next step is remediation. In the Adversarial platform, you can enable integrations with service ticketing tools — such as Jira — to create relationships and manage remediation work. Once the integration is enabled, you can either create a new ticket or link to an existing ticket. A single risk can have one or multiple tickets associated.

To associate a ticket, open an RSK that requires remediation and scroll to the ticketing integration section towards the bottom of the detailed view.

Create a New Ticket

Select +Create Issue. The ticket is automatically populated with the Title and Description from the RSK. Within Jira, the Label field will show identifiers such as “Adversarial”, the RSK ID, and any assigned Tags.

Link an Existing Ticket

In the Link Issues section, begin searching for the ticket name or key, and select it to associate with the RSK.

Once a ticket is associated and the RSK is in progress, update the RSK status to Remediation.

Remediation Agility Chart

The Remediation Agility chart illustrates how effectively your organization reduces residual risk over time. It presents a rolling 365-day view of High and Critical risks opened and closed each day, mapped against their assigned SLA.

The chart is driven by five fields: Urgency, Status, Discovered Date, Due Date, and Closed Date. Each column represents a snapshot of the risk register on a particular day:

• A gray point represents an open risk that has not passed its due date.
• A red point represents an open risk that has passed its due date.

The chart shifts conversation to a high-level overview of realized remediation outcomes for senior leadership and the Board of Directors. Instead of debating thousands of granular findings, you can focus on whether classification of High vs. Critical is appropriate, whether SLAs are meaningful, and what may be driving delays.

The chart is included as the primary risk slide in the Board Deck and the CyberGov Report, both exported as editable PPTX files.

Tip

Risks populated with a Closed Date — regardless of whether they are set as Closure Proposed or Closed — will be reflected in the chart. The influencing factor is that a Closed Date is assigned.