Map regions and jurisdictions to RadarFirst regions and jurisdictions

Map the configured breach assessment regions and jurisdictions in your instance to those imported from RadarFirst.

Before you begin

Role required: sn_privacy.admin or sn_privacy_case.privacy_case_admin

Import data elements, risk factors, and jurisdictions from RadarFirst. For steps, see Import RadarFirst data.

About this task

In breach assessment configuration, regions are the top-level locations. Each region contains one or more levels of jurisdictions. For example, APAC is a region that contains Japan as a first-level jurisdiction, which in turn contains Tokyo as a second-level jurisdiction.

Each jurisdiction might have its own set of configured data elements and breach factors that are used during breach assessments. Because privacy regulations differ by jurisdictions, the data elements and breach factors considered in an assessment depend on the jurisdictions associated with the breach.

To use RadarFirst for risk analysis, you must map each region and jurisdiction in your instance to the corresponding RadarFirst region or jurisdiction record. This mapping ensures that when a breach assessment references a jurisdiction in your instance, the correct data elements and breach factors are matched to the equivalent jurisdiction in RadarFirst.

To view the regions and jurisdictions configured in your instance, navigate to All > Privacy Case Management > Breach Assessment Configuration > Regions. Each region record lists its first-level jurisdictions in the Locations tab. Open a jurisdiction to view any further jurisdictions nested within it. To add a region, see Create a region.
To view the regions imported from RadarFirst, navigate to All > Privacy Case Management > RadarFirst Integration > RadarFirst Regions.
To view the jurisdictions imported from RadarFirst, navigate to All > Privacy Case Management > RadarFirst Integration > RadarFirst Jurisdictions.

Procedure

Navigate to All > Privacy Case Management > Breach Assessment Configuration > Regions.

This opens the list of regions configured for breach assessments in your instance.

Note: You may also complete this task as part of the RadarFirst integration guided setup by navigating to All > Privacy Case Management > RadarFirst Integration > RadarFirst Integration Guided Setup. Select Start on the Map RadarFirst Data to Breach Assessment step.
Map the regions in your instance to their corresponding records in RadarFirst.
1. Select a region.
  
  The record displays the jurisdictions configured within it in the Locations tab. These jurisdictions have to be mapped to their corresponding records in RadarFirst as well.
2. On the Breach Assessment Payload mapping tab of the selected region, select New.
3. On the form, fill in the fields.

Field	Description
Source table	Location table (cmn_location) that hosts the configured breach assessment regions in your ServiceNow® instance.
Source record	Region selected to map to a RadarFirst region. For example, consider `APAC`.
Provider table	RadarFirst region table (sn_privacy_rf_region) that hosts its location records.
Provider record	Corresponding region in RadarFirst that you want to map to the source record chosen.For example, if you chose `APAC` as the source record, search for its corresponding value in the sn_privacy_rf_region table, which might be listed as `APAC` or `Asia Pacific`.

4. Select the **Active** option.

5.  Select **Submit**.

    This maps the selected region in your instance to its corresponding RadarFirst region.

Map a jurisdiction within the selected region to its corresponding record in RadarFirst.
1. Return to the Locations tab of the selected region.
2. Select a jurisdiction.
3. On the Breach Assessment Payload mapping tab of the selected jurisdiction, select New.
4. On the form, fill in the fields.

Field	Description
Source table	Location table (cmn_location) that hosts the configured breach assessment jurisdictions in your ServiceNow® instance.
Source record	Jurisdiction selected to map to a RadarFirst jurisdiction. For example, consider that `APAC` has `Japan` as one of its jurisdictions that need to be mapped.
Provider table	RadarFirst jurisdiction table (sn_privacy_rf_jurisdiction) that hosts its jurisdiction records.
Provider record	Corresponding jurisdiction in RadarFirst that you want to map to the source record chosen.For example, if you chose `Japan` as the source record, search for a matching value in the sn_privacy_rf_jurisdiction table.

5. Select the **Active** option.

6.  Select **Submit**.

    This maps the selected jurisdiction in your instance to its corresponding RadarFirst jurisdiction.

    **Note:** Each jurisdiction might further have jurisdictions listed within the **Locations** tab. You can map those to their corresponding records in RadarFirst as well.

To map additional regions and their jurisdictions, repeat the previous steps.

Result

This marks the completion of the Map regions and Map jurisdictions activities of the Map RadarFirst Data to Breach Assessment step of the guided setup. All the configured mappings appear in the Breach assessment payload mapping table. To view this table:

Navigate to All > System Definition > Tables.
Search for Breach assessment payload mapping by Label.
Open the record and select the Show List from the Related Links section.

What to do next

Map the breach assessment data associated with these regions to that of RadarFirst. For steps, see Map breach assessment data to RadarFirst data elements and risk factors.

title	Map regions and jurisdictions to RadarFirst regions and jurisdictions
description	Map the configured breach assessment regions and jurisdictions in your instance to those imported from RadarFirst.
locale	en-US
canonical_url	https://www.servicenow.com/docs/r/governance-risk-compliance/privacy-workspace/map-regions-to-rf.html
release	brazil
product	Privacy Workspace
classification	privacy-workspace
topic_type	task
last_updated	2026-09-10
reading_time_minutes	4
breadcrumb	RadarFirst configurationIntegrate with RadarFirstPrivacy Case ManagementPrivacy ManagementGovernanceRiskand Compliance