{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":17327,"path":"governance-risk-compliance/grc-risk-management-workspace/configure-risk-event-integration.md","title":null,"bundle":null,"doc_type":null,"release":null,"body":"---\ntitle: Configure risk event integration\ndescription: Configure risk event integration with other upstream ServiceNow applications. This integration enables all users in an organization to report and track the risk events.\nlocale: en-US\ncanonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/grc-risk-management-workspace/configure-risk-event-integration.html\nrelease: australia\nproduct: GRC: Risk Management Workspace\nclassification: grc-risk-management-workspace\ntopic_type: task\nlast_updated: \"2026-03-12\"\nreading_time_minutes: 5\nbreadcrumb: [Use Risk Events, Use, Risk Management, Governance, Risk, and Compliance]\n---\n\n# Configure risk event integration\n\nConfigure risk event integration with other upstream ServiceNow applications. This integration enables all users in an organization to report and track the risk events.\n\n## Before you begin\n\nRole required: sn\\_risk.admin and user\\_admin\n\n## About this task\n\nWhen you configure the risk event integration with another upstream application, then users of that application can directly report risk events from the application. For example, if you configure risk event integration in the ServiceNow® IT Service Management \\(ITSM\\) application, all users of ITSM can report risk events from the ITSM application. By default, this configuration is provided for the IT Incidents application and the Security incidents application.\n\nThe two modes that enable the creation of a risk event are **Simple** and **Advanced**. The **Simple** mode enables you to define filter conditions on the application table so that users of the Incidents application can report a risk event. For example, you can define that a financial event with a high impact must be reported as a risk event. In contrast, the **Advanced** mode enables users with GRC developer role to write scripts.\n\nIncident managers with the incident\\_manager role are able to see the **Report Risk Event** option in an incident, whereas Security Managers with the sn\\_si.manager role are able to see the **Report Risk Event** option in a security incident.\n\n## Procedure\n\n1. Navigate to **Risk Events** > **Administration** > **Integration Configuration**.\n\n2. Click **New**.\n\n3. On the form, fill in the fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nNumber\n\n\n\nConfiguration number. This field is automatically set.\n\n
\n\nActive\n\n\n\nOption to enable the creation of a risk event from the application table.\n\n
\n\nIntegration name\n\n\n\nShort and unique title for the integration. For example, to report a risk event from an incident table, you can type `Incident-risk-event-integration`.\n\n
\n\nApplication table\n\n\n\nApplication table that is used for reporting risk events. The table determines the upstream application that will be used for reporting risk events.\n\n
\n\nSource for name\n\n\n\nHow the name of risk events are set. The choices are as follows:- **Form field**: Select this option if you want the value from a specific selected field to be used as the risk event name.\n- **Default value**: Enter a custom value. The risk event is created with the name you enter here.\n\n\n
\n\nSource for description\n\n\n\nHow the description of risk events are set.\n\n
\n\nSource for entity\n\n\n\nHow the entity of risk events are set.\n\n
\n\nSource for date of discovery\n\n\n\nHow the date of discovery for risk events are set.\n\n
\n\nName\n\n\n\nField in the application table that is used to set the name of risk events. This field appears only when **Form field** is selected from the **Source of name** field.\n\n
\n\nDefault Name\n\n\n\nDefault name for risk events. This field appears only when **Default value** is selected from the **Source of name** field.\n\n
\n\nDescription\n\n\n\nField in the application table that is used to set the description of risk events. This field appears only when **Form field** is selected from the **Source of description** field.\n\n
\n\nDefault description\n\n\n\nDefault description for risk events. This field appears only when the **Default value** is selected from the **Source of description** field.\n\n
\n\nEntity\n\n\n\nField from the application table that refers to a GRC entity or to a record in a GRC entity. This field appears only when **Form field** is selected from the **Source of entity** field.\n\n
\n\nDefault Entity\n\n\n\nDefault entity for risk events. Default entities are created from the table in the **Application table** field. This field appears only when **Default value** is selected from the **Source of entity** field.\n\n
\n\nDate of discovery\n\n\n\nField in the application table that is used to set the date of discovery of risk events. This field is visible only when **Form field** is selected from the **Source of date of discovery** field.\n\n
\n\nDefault date of discovery\n\n\n\nDefault date of discovery of risk events.\n\n
\n\nDefault event type\n\n\n\nDefault event type of risk events. For example, if the event is financial or non-financial.\n\n
\n\nEvent subtype\n\n\n\nSubtype of the risk event. For example, if the event is actual or potential.\n\n
\n\nSource for Non-Financial impact\n\n\n\nHow the non-financial impact of risk events is set.\n\n
\n\nNon-Financial impact\n\n\n\nField in the application table that is used to set the non-financial impact of risk events. This field appears only when **Form field** is selected from the **Source of non-financial field** field.\n\n
\n\nDefault non-financial impact\n\n\n\nDefault severity of risk events. The choices are **Low**, **Medium**, or **High**.\n\n
\n\nSource for expected loss\n\n\n\nHow the expected loss of risks events is set.\n\n
\n\nExpected loss\n\n\n\nField in the application table that is used to set the expected loss of risk events. This field appears only when **Financial impact** is selected from the **Default event type** is field and only when **Form field** is selected from the **Source of expected loss** field.\n\n
\n\nDefault expected loss\n\n\n\nDefault monetary value of the loss. This field appears only when the **Financial impact** is selected from the **Default event type** field and only when **Default value** is selected from the **Source of expected loss** field.\n\n
\n\nDisplay UI Action Based On\n\n
\n\nMode\n\n\n\nMode that is used to create the UI action. The choices are as follows:- **Simple**: Mode to set simple filter conditions. For example, if the impact of an incident is **High**, the **Report a Risk Event** UI action must be created.\n- **Advanced**: Mode to write a script to query tables, including the table from the **Application table** field.\n\n\n
\n\nRole condition\n\n\n\nRoles that can report risk events from the upstream application.\n\n
\n\nFilter condition\n\n\n\nBuild the filters as per the requirement.\n\n
\n\nScript\n\n\n\nField to write a custom script to query any table. **Note:** The option to write a script is only available to users who also have the sn\\_grc.developer role. This field appears when the **Mode** field has **Advanced**.\n\n
4. Click **Submit**.\n\n Any other application table which extends the task table can configure this integration. For details, see the [Risk Event Ingestion \\[KB0780985\\]](https://hi.service-now.com/kb_view.do?sysparm_article=KB0780985) article in the Now Support Knowledge Base. You must log in to view the article.\n\n\n## Result\n\nThe application that is configured to report risk events displays the **Create Risk Event** button.\n\n**Parent Topic:**[Use Risk Events](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-risk-management-workspace/use-risk-events.md)\n\n"}}