Data breach assessment and RadarFirst Integration ConfigurationBreach Assessment Configuration Privacy breach assessments play an important role whenever there is an incident that threatens the privacy of individuals. These assessments help to determine if there is a breach and then serve as a measure to gauge the extent and impact of a breach. There are two pathways to trigger a breach assessment: it can be initiated directly from a privacy case or you can initiate the breach assessment as a standalone assessment. When an assessment is initiated as a standalone assessment, the results are analysed and a privacy case may be created if required. This flexibility ensures that organizations can promptly respond to potential breaches. You can perform only one breach assessment for each privacy case. In the event of a breach, any specific criteria, for example, a server being compromised with personal data, may prompt the initiation of a breach assessment before creating a privacy case. The primary objective of this assessment is to quickly determine the nature of the compromised data. For example, if the incident is related to security incident, the security analysts are tasked with filling out the breach assessment, providing details on the incident type, impacted locations, and any existing mitigation measures like encryption. Subsequently, privacy analysts review the assessment, delving into the specifics of the incident. Based on this analysis, a privacy case may be created to prevent future occurrences and manage legal obligations linked to the breach. While performing the breach assessment, the below mentioned metrics are collected to understand the impact and nature of breach assessment. Breach factorsData elementsJurisdictions To perform the assessment, one needs to set up the regions first. Create geographic regions based on the data of the residents that is collected as a part of your business operations. Examples of regions are United States, Europe, Asia Pacific, Latin America. While creating these regions, make sure the parent field is empty, all the locations in cmn_location table without the parent field are considered as regions.While performing the breach assessment, one needs to collect the region of which the personal data is impacted. Once the regions are created, one needs to set up the jurisdictions Create jurisdictions for regions for data breach notification obligations as each obligation is broken down by jurisdiction.Jurisdiction can be created two levels below a region.Example: Navigate to 'United States' region which is created, one can find a related list 'Locations', on click of new we can create a location. The location that is created will have the parent field as 'United States'.We consider the locations as jurisdictions to two levels from the region. While performing the breach assessment, one needs to collect the number of individuals impacted in each of the jurisdiction for a particular region. RadarFirst Configuration RadarFirst specializes in privacy and incident response solutions, particularly in the context of data breach incidents. RadarFirst helps organizations manage and respond to data breaches and privacy incidents effectively. To configure RadarFirst integration, follow the Guided set up steps and navigate to Privacy Case Management > RadarFirst Integration > RadarFirst Integration Guided Setup. RadarFirst has its own repository of Risk factors(Breach factors), Data elements and Jurisdictions. We are not using RadarFirst data while performing the data breach assessment, so we need to convert our data breach assessment object to radarfirst incident to perform the analysis. We need to collect the RadarFirst metadata and we need to create the mappings between ServiceNow metadata to that of RadarFirst metadata. As out of the box functionality, we import the required metadata from RadarFirst using APIs, as part of this a manual step is required which is mapping of regions of ServiceNow to that of RadarFirst regions. As part of breach assessment configuration, one needs to create the regions and jurisdictions. These regions and jurisdictions needs to be mapped with RadarFirst regions and jurisdictions. Once we initiated the guided set up, when the configuration state moves to Awaiting regions mapping, one need to perform the above step. Make sure you are mapping the right regions of RadarFirst to that of ServiceNow regions. One can map only one region or jurisdiction of RadarFirst to that of one region or jurisdiction of ServiceNow. The creation of mappings are explained in the guided set up. Once these mappings are done, we can continue with the configuration and all the rest of mappings between Data Elements, Breach Factors will be automatically created. Frequently asked questions I am unable to connect to RadarFirst API, getting invalid credentials? One will be provided with RadarFirst API Key from RadarFirst account and when one configuring this key make sure you add the key as following 'Bearer <key>'. I am not able to import the data from RadarFirst Make sure the key is valid and if there are any errors from RadarFirst while importing the data, they will be populated in the Observations field. Based on the error status, we can perform the next actions accordingly. The Guided Setup is not loading properly, the form is stuck and unable to perform any actions We are expecting users to perform each action in each individual task of Guided Set up, don't try to perform multiple actions on a single task. One can do a hard reload to reflect the changes if they are struck.