Tables for control objective and config tests mapping
There are three tables that aid in shipping the mapped data between the control objective and configuration tests to the customers.
Staging table for control objective and configuration test mappings
The Control objective to object staging table [sn_grc_pci_control_objective_object_staging] holds the mapping data of a control objective with that of any object record. However, in this case the object record is the configuration test from the configuration test object table.
- Control objective reference: This column is indicative of the control objectives that originate from CAM or CIS and are available with their sys IDs as reference. Navigate to the Control objective to object staging table and filter the records with Control objective reference in the search field. After you run the search, all record mappings related to CAM and CIS control objectives and configuration tests appear, which are shipped to the GRC: Cloud Security Compliance Accelerator.
- Control objective source Id: The column indicates control objectives that originate from Unified Compliance Framework (UCF), and their sys IDs are not readily available. The source ID is generated at the time when the user imports the control objective from the Shared Lists, and a sys ID is generated based on the source ID. You can filter the records with Control objective source ID to get all the mapping records between the UCF control objectives and configuration tests with reference to the source ID are listed
The Status field displays the status of the records in Pending, Processed, or Inactive states.
Target table for staging configuration information
The Control objective mapping import configuration [sn_grc_pci_control_objective_mapping_import_configuration] is the target m2m metadata table, the records of which cannot be updated. The fields in this table – Source app configuration name, Control objective field, Object field, Object field type, Object table field values – are static and for viewing only. The static configuration aligns with the configuration of the staging table and hence, while processing the staging record the data moves to the corresponding columns in the target table. The compliance administrator can, however, view the records to understand where the field values go into the main target table columns. For example, the reference of Source app configuration name in the target table comes from the Source app configuration of the staging table. Object field type can be Document ID or Reference. When the scheduled job runs, it stores the staging record information in the appropriate columns of the target table.
Related list for additional m2m table information
The Control objective mapping import additional fields configuration [sn_grc_pci_control_objective_mapping_import_additional_fields_configuration] table is a related list that has additional reference columns. When controls are generated or entities are created there are additional column values that are specific to a configuration, which might need to be accommodated in the m2m table. For such downstream process, the Additional field name holds the additional column name information from the Source app configuration's target table. Similarly, the Additional field value captures the column value for the additional field name. Therefore, this table stores the key-value pairs with respect to the additional columns in the target m2m table.