Use Risk Events

Report risk events and monitor their workflow to prevent losses in your organization.

• Configure risk event integration
  Configure risk event integration with other upstream ServiceNow applications. This integration enables all users in an organization to report and track the risk events.
• Create a risk event response template
  Automatically assign the risk event owner, create and assign issues, and route approvers based on entity, event type, category, and impact thresholds in the risk event response template.
• Define a threshold amount for the risk event response template
  Define a threshold limit for assigning risk event approvers. A threshold limit is defined to determine if a risk event needs an approver.
• Report risk events from the Service Portal
  When you identify any event that might have a financial or non financial impact on your organization, report it from the ServiceNow, Inc. Service Portal. You can also report any event that has already occurred with a financial or non financial impact.
• Report a risk event from Employee Center
  When you identify any event that might have a financial or non financial impact on your organization, report it from the ServiceNow, Inc. Employee Center. You can also report any event that has already occurred with a financial or non financial impact.
• Report a risk event from an incident
  If risk event integration is configured, users can report risk events from any upstream application such as IT Incidents. This ability to report risk events saves the time of users and helps to prevent losses for organizations.
• Create a risk event task
  A risk event might require associated tasks. Unless these tasks are created and eventually closed, the risk event cannot be closed.
• Analyze a risk event
  Analyze user-submitted risk events to determine if the risk event is valid and needs further processing.
• Create a risk event entry
  Create a risk event entry to determine the monetary or non-monetary impact of the risk event. A risk event can have multiple risk event entries.
• Approve a risk event
  A user with the sn_risk.manager role must approve a valid risk event. If any risk approver rejects the event, the state of the risk event changes to rejected.
• Close a risk event
  Close a risk event to complete the risk events life cycle. A user with the sn_risk.manager role must close the risk event after verifying that all associated open issues and remedial tasks are closed.
• Reopen a closed risk event
  Reopen closed risk events to identify and address overlooked or underestimated risks, updating existing risk events instead of creating another risk event.
• Add a risk event cause to the cause library
  A cause library is a centralized library of the possible causes that can lead to a risk event. Adding causes helps to identify the reason for a risk event and prevent future events.
• Add a risk event consequence to the consequence library
  A consequences library is a centralized library of the possible consequences of a risk event.
• Set up GRC Virtual Agent to report risk events
  Use a Virtual Agent chatbot to report risk events from the Service Portal. A virtual agent chatbot helps customers to quickly report a risk event. The chatbot assists the customers by saving their time. The information exchanged during the conversation flow enables the chatbot to fulfill a user request or assist the user in completing a task.

Parent Topic:Using Risk Management