Maintaining Configuration Settings in Access Control

Transcription

1 Maintaining Configuration Settings in Access Control Applies to: SAP BusinessObjects Access Control 10.0 SP05 Summary: This guide contains additional information about the parameters used when configuring the access control application. The information covers the configuration parameters available as of SP05. Created: August 2011 Version SAP AG

2 Document History Document Version Description 1.00 Initial release 2011 SAP AG

3 Typographic Conventions Icons Type Style Description Icon Description Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Caution Note or Important Example Recommendation or Tip Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> EXAMPLE TEXT Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER SAP AG

4 Table of Contents 1. Maintain Configuration Settings Standard Settings Activities Details of Configuration Parameters Copyright SAP AG

5 1. Maintain Configuration Settings This document covers the use of the Customizing activity Maintain Configuration Settings under Governance, Risks, and Compliance > Access Control. In this Customizing activity, you maintain the global configuration settings and parameters used in the access control application. The activity includes settings for the following parameter groups: 01 Change Log 10 Role Management 02 Mitigation 11 Risk Analysis - Risk Terminator 03 Risk Analysis 12 Access Request Role Selection 04 Risk Analysis - Spool 13 Access Request Default Roles 05 Workflow 14 Access Request Role Mapping 06 Superuser Management 15 SOD Review 07 UAR Review 17 Assignment Expiry 08 Performance 18 Access Request Training Verification 09 Risk Analysis - Access Request 19 Authorizations Note: The numbering is part of the parameter group name. In the above list, number 16 is not used. 1.1 Standard Settings The following table lists the delivered parameters and default values. Note: Values labeled as <empty> have no default value. Parameter Group Parameter ID Description Default Value Change Log 1001 Enable Function Change Log Change Log 1002 Enable Risk Change Log Change Log 1003 Enable Organization Rule Log Change Log 1004 Enable Supplementary Rule Log Change Log 1005 Enable Critical Role Log Change Log 1006 Enable Critical Profile Log Change Log 1007 Enable Rule Set Change Log Change Log 1008 Enable Role Change Log Mitigation 1011 Default expiration time for mitigating control assignments (in days) 365 August

6 Parameter Group Mitigation 1012 Mitigation 1013 Risk Analysis 1021 Risk Analysis 1022 Parameter ID Description Default Value Consider Rule ID also for mitigation assignment Consider System for mitigation assignment Consider Org Rules for other applications Allow object IDs for this connector to be case sensitive Risk Analysis 1023 Default report type for risk analysis 2 Risk Analysis 1024 Default risk level for risk analysis 3 <empty> Risk Analysis 1025 Default rule set for risk analysis <empty> Risk Analysis 1026 Default user type for risk analysis A Risk Analysis 1027 Enable Offline Risk Analysis Risk Analysis 1028 Include Expired Users Risk Analysis 1029 Include Locked Users Risk Analysis 1030 Include Mitigated Risks Risk Analysis 1031 Ignore Critical Roles and Profiles Risk Analysis 1032 Risk Analysis 1033 Risk Analysis 1034 Risk Analysis 1035 Include Reference user when doing user analysis Include Role/Profile Mitigating Controls in Risk Analysis Max number of objects in a package for parallel processing Send notification to the monitor of the updated mitigated object Risk Analysis 1036 Show all objects in Risk Analysis Risk Analysis 1037 Use SoD Supplementary Table for Analysis 100 Risk Analysis 1046 Extended objects enabled connector <empty> Risk Analysis - Spool 1051 Max number of objects in a file or database record Risk Analysis - Spool 1052 Spool File Location <empty> Risk Analysis - Spool 1053 Spool Type D Workflow 1061 Mitigating Control Maintenance Workflow 1062 Mitigation Assignment Workflow 1063 Risk Maintenance Workflow 1064 Function Maintenance Risk Analysis - Access Request Risk Analysis - Access Request Enable risk analysis on form submission Mitigation of critical risk required before approving the request Risk Analysis - Risk 1080 Connector enabled for Risk <empty> August

7 Parameter Group Terminator Parameter ID Description Default Value Terminator Risk Analysis - Risk Terminator 1081 Enable Risk Terminator for PFCG Role Generation Risk Analysis - Risk Terminator 1082 Enable Risk Terminator for PFCG User Assignment Risk Analysis - Risk Terminator 1083 Enable Risk Terminator for SU01 Role Assignment Risk Analysis - Risk Terminator 1084 Enable Risk Terminator for SU10 multiple User Assignment Risk Analysis - Risk Terminator 1085 Stop role generation if violations exist Risk Analysis - Risk Terminator 1086 Comments are required in case of violations Risk Analysis - Risk Terminator 1087 Send Notification in case of violations Risk Analysis - Risk Terminator 1088 Default report type for Risk Terminator 2 Authorizations 1100 Enable authorization logging Workflow 1101 Create Request for Risk Approval 12 Workflow 1102 Update Request for Risk Approval 13 Workflow 1103 Delete Request for Risk Approval 14 Workflow 1104 Workflow 1105 Workflow 1106 Workflow 1107 Workflow 1108 Workflow 1109 Create Request for Function Approval Update Request for Function Approval Delete Request for Function Approval Create Request for Mitigation Assignment Approval Update Request for Mitigation Assignment Approval Delete Request for Mitigation Assignment Approval Workflow 1110 High 2 Workflow 1111 High 3 Workflow 1112 High 4 Workflow 1113 Access Control Sender WF-BATCH Performance 1120 Batch size for Batch Risk Analysis 1000 Performance 1121 Batch size for User Sync 1000 Performance 1122 Batch size for Role Sync 1000 Performance 1123 Batch size for Profile Sync 1000 UAR Review 2004 Request Type for UAR <empty> UAR Review 2005 Default Priority 005 August

8 Parameter Group Parameter ID Description Default Value UAR Review 2006 Who are the reviewers? MANAGER UAR Review 2007 Access Request Default Roles Access Request Default Roles Access Request Default Roles Access Request Default Roles Access Request Default Roles Access Request Role Mapping Access Request Role Mapping Admin. review required before sending tasks to reviewers 2009 Consider Default Roles 2010 Request type for default roles <empty> 2011 Default Role Level <empty> 2012 Role Attributes <empty> 2013 Request Attributes <empty> 2014 Enable Role Mapping 2015 Applicable to Role Removals SOD Review 2016 Request Type for SoD <empty> SOD Review 2017 Default priority for SoD <empty> SOD Review 2018 Who are the reviewers? MANAGER SOD Review 2019 Admin. review required before sending tasks to reviewers SOD Review 2023 Is actual removal of role allowed? Access Request Training Verification Access Request Role Selection Access Request Role Selection Access Request Role Selection Access Request Role Selection Access Request Role Selection Access Request Role Selection Access Request Role Selection Access Request Role Selection Access Request Role Selection 2024 Training and verification <empty> 2031 Allow All Roles for Approver 2032 Approver Role Restriction Attribute <empty> 2033 Allow All Roles for Requestor 2034 Requestor Role Restriction Attribute <empty> 2035 Allow Role Comments 2036 Role Comments Mandatory Assignment Expiry 2041 Display expired roles for existing roles Auto Approve Roles without Approvers Search Role by Transactions from Backend System Duration for assignment expiry in Days <empty> August

9 Parameter Group Performance 2050 Performance 2051 Parameter ID Description Default Value Enable Realtime LDAP Search for Access Request User Enable User ID Validation in Access Request Against Search Data Sources Role Management 3000 Default Business Process <empty> Role Management 3001 Default Subprocess <empty> Role Management 3002 Default Criticality Level <empty> Role Management 3003 Default Project Release <empty> Role Management 3004 Default Role Status <empty> Role Management 3006 Role Management 3007 Role Management 3008 Role Management 3009 Role Management 3010 Role Management 3011 Role Management 3012 Role Management 3013 Role Management 3014 Role Management 3015 Role Management 3016 Role Management 3017 Role Management 3018 Role Management 3019 Role Management 3020 Role Management 3021 Allow add functions to an authorization Allow editing organizational level values for derived roles A ticket number is required after authorization data changes Allow Role Deletion from back-end system Allow attaching files to the role definition Conduct Risk Analysis before Role Generation Allow Role Generation on Multiple Systems Use logged-on user credentials for role generation Allow role generation with Permission Level violations Allow role generation with Critical Permission violations Allow role generation with Action Level violations Allow role generation with Critical Action violations Allow role generation with Critical Role/Profile violations Overwrite individual role Risk Analysis results for Mass Risk Analysis Role certification reminder notification Directory for mass role import server files Workflow 3022 Request Type for Role Approval 21 Workflow 3023 Priority for Role Approval 5 10 <empty> August

10 Parameter Group Workflow 3024 Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Superuser Management Parameter ID Description Default Value Enforce methodology process for derived roles during generation 4000 Application Type Default Firefighter Validity Period (in days) <empty> 4002 Send Immediately 4003 Retrieve Change Log 4004 Retrieve System Log 4005 Retrieve Audit Log 4006 Retrieve O/S Command Log 4007 Send Log Report Execution Notification Immediately 4008 Send FirefightId Logon Notification 4009 Log Report Execution Notification 4010 Firefighter ID Role Name ZSAP_GRAC_SMP_FFID 1.2 Activities To maintain the configuration settings: 1. Choose the New Entries pushbutton and select a parameter group from the dropdown list. 2. In the Parameter ID column, select a parameter ID for use with the parameter group. The short description appears on the right-hand side. 3. Select a Parameter Value from the dropdown list, or enter values in the field. 4. In the Priority field, enter a number for the priority. 5. Choose Save. 1.3 Details of Configuration Parameters The information in this section explains in further detail the configuration parameters. The table is formatted and ordered to match the table displayed in the actual Customizing activity. For each parameter, the table includes information about the purpose of the parameter, the available option values, and screenshots to provide context about how the parameter affects the application. August

11 Note: The application provides a standard set of work centers, however, your system administrator can customize them according to your company s corporate processes and structures. Additionally, Access Control is available both as a standalone application and as part of the GRC 10.0 application. Depending on the GRC applications you have licensed, different areas of the access control application are displayed. The navigation paths included in this document and in the screenshots may differ from yours. # Parameter Group Parameter ID Description DEFAULT Value Change Log 1001 Enable Function Change Log Set to to display the Change History tab on the Function screen. 1 Change Log 1002 Enable Risk Change Log Set to to display the Change History tab on the Access Risk screen. 2 August

12 Change Log 1003 Enable Organization Rule Log Set to to display the Change History tab on the Organization Rules screen. 3 Change Log 1004 Enable Supplementary Rule Log Set to to display the Change History tab on the Supplementary Rules screen. 4 August

13 Change Log 1005 Enable Critical Role Log Set to to display the Change History tab on the Critical Role screen. 5 Change Log 1006 Enable Critical Profile Log Set to to display the Change History tab on the Critical Profile screen. 6 August

14 Change Log 1007 Enable Rule Set Change Log Set to to display the Change History tab on the Rule Sets screen. 7 Change Log 1008 Enable Role Change Log Set to to display the Change History link on the Additional Details tab of the Role Maintenance screen. 8 August

15 Mitigation 1011 Default expiration time for mitigating control assignments (in days) The default quantity of days you are allowed to mitigate any object (selection on service map). You can overwrite this quantity in the Valid To field August

16 Mitigation 1012 By default the application includes all rules when it mitigates the access risk. Consider Rule ID also for mitigation assignment Setting the value to allows you to specify the specific Rule ID to be included when mitigating the risk. 10 August

17 Mitigation 1013 Consider System for mitigation assignment Setting the value to allows you to apply mitigating controls to risks originating from specific systems. 11 August

18 Risk Analysis 1021 Consider Org Rules for other applications Setting the value to automatically selects the Consider Org Rule checkbox on the Risk Violations tab of the Access Request and Role Maintenance screens. 12 August

19 Risk Analysis 1022 Allow object IDs for this connector to be case sensitive <empty> On the Risk Analysis screen you can perform risk analysis. You specify the system and the analysis criteria such as User, Risk Level, and so on. This parameter allows you to specify for which systems the information entered is case sensitive. In the example below, z_cup_usr001 is case sensitive for system NCACLNT Note: To enter more than one system or connector, enter additional instances of the parameter. August

20 Risk Analysis 1023 Default report type for risk analysis 2 The Risk Analysis screen allows you to select several options for the risk analysis, such as analysis criteria, report options, and additional criteria. This parameter allows you to choose the type of report that is selected by default. Note: In the value cell, press F4 to display the available types, such as Permission Level, and so on. 14 Note: This setting does not affect the Risk Analysis Type fields on the Batch Risk Analysis screens; you must set these separately. August

21 Risk Analysis 1024 Default risk level for risk analysis The Risk Analysis screen allows you to select several options for the risk analysis, such as analysis criteria, report options, and additional criteria. This parameter allows you to choose the Risk Level that is selected by default. Risk Analysis 1025 Default rule set for risk analysis <empty> The Risk Analysis screen allows you to select several options for the risk analysis, such as analysis criteria, report options, and additional criteria. This parameter allows you to choose the Rule Set that is selected by default. Risk Analysis 1026 Default user type for risk analysis A The Risk Analysis screen allows you to select several options for the risk analysis, such as analysis criteria, report options, and additional criteria. This parameter allows you to choose the User Type that is selected by default. Risk Analysis 1027 Enable Offline Risk Analysis The Risk Analysis screen allows you to select several options for the risk analysis, such as analysis criteria, report options, and additional criteria. Set the parameter value to to include Offline Data in risk analysis by default. On the Risk Analysis screen the Offline Data checkbox is automatically selected Risk Analysis 1028 Include Expired Users Set to to include expired users from plug-in systems for risk analysis. Risk Analysis 1029 Include Locked Users Set to to include locked users from plug-in systems for risk analysis. Risk Analysis 1030 Include Mitigated Risks The Risk Analysis screen allows you to select several options for the risk analysis, such as analysis criteria, report options, and additional criteria. Set the parameter value to to include Mitigated Risks in the risk analysis by default. The application displays the SoD violations, the mitigated risks, and the mitigating control assigned to it. On the Risk Analysis screen, the Include Mitigated Risks checkbox is automatically selected Risk Analysis 1031 Ignore Critical Roles and Profiles Set the value to to exclude critical roles and profiles for risk analysis. Risk Analysis 1032 Include Reference user when doing user analysis Set the value to to include referenced users when performing SoD risk analysis for users. This is also valid for Batch Risk Analysis. Risk Analysis 1033 Include Role/Profile Mitigating Controls in Risk Analysis Set the value to to include the mitigating controls assigned to the user s roles and profiles for risk analysis. Risk Analysis 1034 Maximum number of objects in a package for parallel processing The application uses this parameter in conjunction with the Number of Tasks specified in the Customizing activity Distribute Jobs for Parallel Processing to determine the distribution of objects that are processed per job. For example, if there are 10,000 users to analyze and this value is 100, then there will be 100 packages created each having 100 users. Each package is submitted to a separate background process which is available to the application via the application group If instead, we specify three background processes are available to GRAC_SOD, 100 packages are submitted one by one to these processes. Three packages initially and then one by one to each process which complete the package execution. Note: The RZ10 parameter rdisp/wp_no_btc overrides this configuration. Therefore, if the RZ10 parameter is set to 2, then the application ignores the parameter in this setting and uses the value 2 instead. August

22 Risk Analysis 1035 Send notification to the monitor of the updated mitigated object Set the value to to send notifications to the owner of the mitigating control when the mitigated object is updated, such as the user/role. 26 August

23 Risk Analysis 1036 Show all objects in Risk Analysis Set the value to to select the Show All Objects checkbox on the Risk Analysis screen by default. 27 The objects that do not have violations are displayed with the Action: No Violations. Note: This setting applies to SoD Batch Risk Analysis. Risk Analysis 1037 Set value to to use supplementary rules for SoD risk analysis. Use SoD Supplementary Table for Analysis 28 August

24 29 Risk Analysis 1046 Extended objects enabled connector <empty> Extended objects are objects from non-sap systems. This parameter allows you to specify the connectors for non-sap systems. The connectors can have object lengths greater than SAP objects. For example, SAP User ID length is 12, but the extended object length may be 50. Note: You can set multiple connectors by adding multiple instances of the parameter. 30 Risk Analysis - Spool 1051 Max number of objects in a file or database record You can use this parameter to specify the maximum number of analytics data objects the application stores. If parameter 1053 is set to F, the value is the maximum number of objects stored in the file If parameter 1053 is set to D, the value is the maximum number of objects stored in the REPCONTENT column of the GRACSODREPDATA table. Note: You can use the GRAC_DELETE_REPORT_SPOOL program to clean up the analytics data from the file system or table. Prerequisite: You have configured parameters 1052 and Risk Analysis - Spool 1052 Spool File Location <empty> You can specify the file location the application stores the analytics data, such as \\<ip_address>\public\sod\. Note: This parameter is only valid if parameter 1053 is set to F. Prerequisite: You have configured parameter Risk Analysis - Spool 1053 Spool Type D You can use this parameter to set whether the application uses the file system or the database table to store the analytics data for access control, such as ad hoc SoD violations. Set the value to F to store the data on the file system. (You set the file location in parameter 1052). Set the value to D to store the data inthe GRACSODREPDATA table. Note: You see the intermediate results while risk analysis is running. This gives you an opportunity to see if the desired records are created and choose to stop or cancel the job. If you change the location type (such as from D to F) in mid-course, the report will still read the previously generated files or database records. Index tables keep track of the source of the records when the data was generated. If you cancel the job before the report is finished, you can still read the data up to the point the files or database records were created. August

25 Workflow 1061 Mitigating Control Maintenance The application allows users to create and change mitigating controls. Set the value to to require that when users create or change mitigating controls, the application sends a workflow item to an approver to approve the action. Note: On the Mitigating Control screen, the Create button is replaced by a Submit button. You can configure the role that receives the workflow item for approving the mitigating control changes using the Customizing activity Maintain MSMP Workflows under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. Figure A below shows that on the control Owners tab the Mitigation Control Approver points to the Approver. Figure B below shows you can use Maintain MSMP Workflows to change the approver agent ID (GRAC_CONTROL_APPROVER). Figure A Figure B August

26 Workflow 1062 Mitigation Assignment The application allows users to mitigate risks for objects (user, role, profile, and so on). Set the value to to require the application send an approval workflow item to the mitigating control approver. The screen displays a Submit button. Note: You can configure the role that receives the workflow item for approving the mitigating control changes using the Customizing activity Maintain MSMP Workflows under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. Set the value to and the users can mitigate risks without approval. The screen displays a Save button. 34 August

27 Workflow 1063 Risk Maintenance The application allows users to create and modify risks. Set the value to to require the application send an approval workflow item to the Risk Owner (or to any alternate workflow agent you set) for approval. The screen displays a Submit button. Note: You can configure the role that receives the approval workflow item using the Customizing activity Maintain MSMP Workflows under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. Set the value to and then users can create and modify risks without approval. The screen displays a Save button. 35 August

28 Workflow 1064 Function Maintenance The application allows users to create and change functions. Set the value to to require the application send an approval workflow item to the specified workflow agent for approval when functions are created or modified. Note: Workflow agents are users who have been assigned the role SAP_GRAC_FUNCTION_APPROVER. You can change the approver agent by using the Customizing activity Maintain MSMP Workflows under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. 36 August

29 Risk Analysis - Access Request 1071 Enable risk analysis on form submission The application automatically performs risk analysis when the requestor submits the request. Note: The risk analysis results are intended for the approver. Therefore, the risk analysis results appear on the approver s screens but not on the requestor s screens Risk Analysis - Access Request 1072 Mitigation of critical risk required before approving the request Set the value to to require mitigation of Risks that are of the type Critical Access. Risk Analysis - Risk Terminator 1080 Connector enabled for Risk Terminator Enter the name of the connector in the value field to enable it for risk terminator. You can enter multiple values by entering multiple instances of the parameter, as follows: <empty> Note: The Plug-in Connector is maintained in parameter The GRC Connector is maintained in parameter August

30 Risk Analysis - Risk Terminator 1081 Set to to trigger the risk terminator service for PFCG Role Generation. Enable Risk Terminator for PFCG Role Generation The Risk Terminator service is a tool that resides in the back end SAP ABAP system and notifies you when a risk violation occurs. Risk Analysis - Risk Terminator 1082 Set to to trigger the risk terminator service for PFCG User Assignment. Risk Analysis - Risk Terminator 1083 Set to to trigger the risk terminator service for SU01 Role Assignment. Risk Analysis - Risk Terminator 1084 Enable Risk Terminator for PFCG User Assignment Enable Risk Terminator for SU01 Role Assignment Enable Risk Terminator for SU10 multiple User Assignment Set to to trigger the risk terminator service for SU10 Multiple User Assignment. Risk Analysis - Risk Terminator 1085 Set to the risk terminator service stops generating roles if violations exist. Risk Analysis - Risk Terminator 1086 Stop role generation if violations exist Comments are required in case of violations Set the value to to require the user to enter comments if SoD violations are reported and the user wants to continue with role generation or role assignment. Risk Analysis - Risk Terminator 1087 Send Notification in case of violations Set the value to to enable the application to send notifications to the role owner when violations occur. Risk Analysis - Risk Terminator 1088 Default report type for Risk Terminator Select the default report type the risk terminator service uses to report SoD violations. Use F4 help to display the available report types. Authorizations 1100 Enable the authorization logging If set to, the application logs all occurrences of insufficient authorizations on the GRC box in transaction SLG1. For example, an owner wants to perform an action and is missing the necessary authorizations. Workflow 1101 Create Request for Risk Approval 12 Use F4 help and choose the request type the workflow uses to create requests for risk approval. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. This request type is associated with an MSMP process ID such as SAP_GRAC_RISK_APPR August

31 Workflow 1102 Update Request for Risk Approval Use F4 help and choose the request type the workflow uses to update requests for risk approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1103 Delete Request for Risk Approval 14 Use F4 help and choose the request type the workflow uses to delete requests for risk approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1104 Create Request for Function Approval Use F4 help and choose the request type the workflow uses to create requests for function approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1105 Update Request for Function Approval Use F4 help and choose the request type the workflow uses to update requests for function approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1106 Delete Request for Function Approval Use F4 help and choose the request type the workflow uses to delete requests for risk approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1107 Create Request for Mitigation Assignment Approval Use F4 help and choose the request type the workflow uses to create requests for mitigation assignment approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1108 Update Request for Mitigation Assignment Approval Use F4 help and choose the request type the workflow uses to update requests for mitigation assignment approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1109 Delete Request for Mitigation Assignment Approval Use F4 help and choose the request type the workflow uses to delete requests for mitigation assignment approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 1110 High 2 You use this parameter to set the default workflow request priority for Updating and Creating Risks. Use F4 help to display the list of available priorities. You maintain the list of available priority values in the Customizing activity Maintain Priority Configuration under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_RISK_APPR to risk approval priorities August

32 Workflow 1111 High You use this parameter to set the default workflow request priority for Creating and Updating Functions. Use F4 help to display the list of available priorities. You maintain the list of available priority values in the Customizing activity Maintain Priority Configuration under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_FUNC_APPR to function approval priorities. Workflow 1112 High 4 You use this parameter to set the default workflow request priority for Mitigation Control Assignments. Use F4 help to display the list of available priorities. You maintain the list of available priority values in the Customizing activity Maintain Priority Configuration under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_CONTROL_ASGN to mitigation control assignment priorities. Workflow 1113 Access Control sender WF-BATCH The application uses the of this user as defined in SU01 to send the workflow s to the approvers. See the Access Control 10.0 Security Guide for information about required authorizations for the WF-BATCH user. Performance 1120 Batch size for Batch Risk Analysis 1000 The application uses this value to determine the size of the batch when performing batch risk analysis. (See also parameter 1121 for an example). Performance 1121 Batch size for User sync 1000 The application uses this value to determine the size of the batch when synchronizing users to the GRC AC Repository. For example, if the batch size is 1000 and there are 10,000 users, the application divides the total users (10,000) by the batch size (1000), and then processes the job in 10 batches of the range 0 to 1000, 1001 to 2000 so on. Each batch is processed in its entirety before continuing with the next. To synchorinize users to the GRC AC Repository, you use the Customizing activity Repository Object Synch under Governance, Risks, and Compliance > Access Control > Synchronization Jobs Performance 1122 Batch size for Role sync 1000 The application uses this value to determine the size of the batch when synchronizing roles to the GRC AC Repository. Each batch is processed in its entirety before moving on to the next. See also parameter Performance 1123 Batch size for Profile sync 1000 The application uses this value to determine the size of the batch when synchronizing profiles to the GRC AC Repository. Each batch is processed in its entirety before moving on to the next. See also parameter August

33 UAR Review 2004 Request Type for UAR <empty> All Request Types that are defined for SAP_GRAC_USER_ACCESS_REVIEW are visible by pressing F4. 66 This is important for tagging the workflow in MSMP for UAR Review. UAR Review 2005 Default Priority 005 You use this parameter to set the default priority for user access request reviews. Use F4 help to display the list of available priorities for UAR Requests. 67 You maintain the list of available priority values in the Customizing activity Maintain Priority Configuration under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_USER_ACCESS_REVIEW to UAR Review priorities. In this example, priority IDs 10, 22, 24, and 36 are relevant for UAR. Review. August

34 UAR Review 2006 Who are the reviewers? MANAGER Select either Manager or Role Owner as the approver type for user access review requests. The application creates a review workflow for the specified approver type. Managers receive review requests sorted by USER, and Role Owners receive review requests sorted by ROLE. 68 August

35 UAR Review 2007 Admin. review required before sending tasks to reviewers Set the value to to require that users who are assigned the role of access request administrator (such as SAP_GRAC_ACCESS_REQUEST_ADMIN) must review the request before the workflow goes to the reviewers. (You specify reviewers in parameter 2006). 69 Access Request Default Roles 2009 Consider Default Roles If set to, the application automatically adds the relevant Default Roles to the access request. Prerequisites: You have maintained the following parameters as needed: 2011, 2012, and In this example, the value for the attribute Functional Area maps to a relevant default role, so the application adds the role to the request. 70 August

36 71 Access Request Default Roles 2010 Request type for default roles <empty> Enter the request types that are relevant for default roles functionality. The application adds default roles only for the specified roles. Enter multiple request types by adding additional instances of the parameter. Use F4 help to display the available request types. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. See also parameters 2009, 2011, 2012, and Access Request Default Roles 2011 Default Role Level <empty> Select which attribute type the application uses to determine the relevance of the default roles. Role The application uses the role attributes to determine the relevant default roles and adds the default roles at the time the user adds the roles to the request. That is, the user does see the added default roles at the time they create the request. You define the relevant role attributes in parameter Request - The application uses the request attributes to determine the relevant default roles and adds the default roles when the request is displayed for the approver. That is, the user does not see the added default roles at the time they create the request. You define the relevant request attributes in parameter In this example, the value is set to Request. The manager receives a request with the default role z_user_admin already added, because Functional Area is a relevant attribute. 72 In this example, the value is set to Role. On the request screen, the application shows the default roles as Existing and adds them to the request. August

37 73 See also parameters 2009, 2010, 2012, and Access Request Default Roles 2012 Role Attributes <empty> Enter the role attributes the application considers for Default Role Attribute mapping. These are mutually exclusive of the request attributes maintained in parameter You can add multiple role attributes by adding additional instances of the parameter. See also parameters 2009, 2010, 2011, and August

38 Access Request Default Roles 2013 Request Attributes <empty> 74 Enter the request attributes the application considers for Default Role Attribute mapping. These are mutually exclusive of the request attributes maintained in parameter You can add multiple role attributes by adding additional instances of the parameter. See also parameters 2009, 2010, 2011, and Access Request Role Mapping 2014 Enable Role Mapping The application allows you to assign roles as child roles (or map the roles). This allows anyone who is assigned this role to also be assigned the authorizations and access for the child roles. Set the parameter value to to enable this functionality. The role mappings are applicable for provisioning access requests. Note: On the Role Maintenance screen, you can select the Consider Parent Role Approver checkbox to use only the approvers associated with the parent roles and ignore any approvers associated with the child roles. In the following example, the user is requesting the role BS_BS_123 of system GF1->GO7. The mapped role AC_C_ROLE1 is automatically added to the request. The user can choose to remove the role from the request. Note: The Source System dropdown list is from the same landscape you chose on the Detail tab. 75 Access Request Role Mapping 2015 Applicable to Role Removals Set the value to to allow users to include mapped roles in requests for role removal. For example, if a user creates a request to remove a role assigned to them, and the role has mapped roles, then the mapped roles are automatically included in the request. The user can choose to keep the mapped roles by deleting them from the removal request. SOD Review 2016 Request Type for SoD <empty> Use F4 help and select the request type when SoD review requests are created. You maintain the list of available request type values in the Customizing activity Define Request Types under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_SOD_RISK_REVIEW. August

39 SOD Review 2017 Default priority for SoD <empty> 78 Use F4 help and select the default priority used for SoD review requests. You maintain the list of available priority values in the Customizing activity Maintain Priority Configuration under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_SOD_RISK_REVIEW. 79 SOD Review 2018 Who are the reviewers? MANAGER Select either Manager or Risk Owner as the approver type for user access review requests. The application creates a review workflow for the specified approver type. Managers receive review requests sorted by USER, and Risk Owners receive review requests sorted by Risk. SOD Review 2019 Admin. review required before sending tasks to reviewers Set the value to to require that users who are assigned the role of access request administrator (such as SAP_GRAC_ACCESS_REQUEST_ADMIN) must review the request before the workflow goes to the reviewers. (You specify reviewers in parameter 2018). 80 SOD Review 2023 Is actual removal of role allowed 81 You use this parameter to configure whether the reviewers of SoD risks are allowed to remove the actual roles associated with a SoD risk or only propose removal of the roles. Set value as This is the default setting, and the recommended setting. On the SoD Review screen, the application displays the Propose Removal button. Reviewers can only propose the removal of roles associated with a SoD risk violation. The workflow goes to the security administrator who is able to view the source of the risk before deciding whether or not to remove the role. Set value as This setting is not recommended. On the SoD Review screen, the application displays the Remove Role button. This allows the reviewer to delete the roles directly without going through approval by the security administrator. Warning: Reviewers do not have the ability to view the source of the risks; therefore have the risk of potentially deleting relevant roles. August

40 Access Request Training Verification 2024 Training and verification <empty> The application allows you to require that users complete specific training courses before the application provisions specific roles to them. You enable this functionality by : 1. Setting training requirements (See Example 1 below.) 2. Configuring MSMP routing rule 3. Configuring the data source systems for verifying if the training requirements are completed Example 1: The user is requesting a role that has a TRAINING prerequisite, and Verify on Request is set to Yes. The application will not allow them to submit the request until all the prerequisites are met. 82 The application has a Routing rule for Training and Verification in MSMP (GRAC_MSMP_DETOUR_TRG_VERIF). The routing checks this parameter to determine the data source for verifying if the user has completed the training required for the roles they are requesting to add. If the required training is not completed for a particular role the application does not provision the role, and instead, sends the request to the routing path. Leave the value field empty to disable the function. The workflow does not take any routing paths. Set the value to BAdI and the application uses the specified BadI to perform the verification. Set the value to WS and the application uses the specified web service to perform the verification. You specify the prerequisite system in the connector configuration. To configure the connectors, use the Customizing activity Maintain Connectors and Connector Types under Governance, Risk, and Compliance > Common Component Settings > Integration Framework. The connector must be of the type WS and associated with a logical port. You can define the logical port in transaction SOAMANAGER. Prerequisite: You have implemented the BadI or webservice (WS) as needed. Yes, it correct to say that to disable this function, leave the value field empty. So if the value is empty Note: You can configure the routing in the Customizing activity Maintain MSMP Workflows under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. Access Request Role Selection 2031 Allow All Roles for Approver 83 The application allows approvers to add additional roles to access requests when reviewing them. Set the value to to allow approvers to view and select all roles. Set the value to to restrict the roles the approvers can view and select for request creation. You specify the restriction criteria in parameter August

41 Access Request Role Selection 2032 Approver Role Restriction Attribute <empty> The application allows approvers to add additional roles to access requests when reviewing them. You can restrict the roles approvers can view and select for request creation. Set the value to A to Restrict on Role Approver. Approvers can view and select only those roles for which they are the role approver. Set the value to B to Restrict on Business Process. Approvers can view and add only those roles with business process attributes that match those in the request Set the value to F to Restrict on Functional Area. Approvers can view and add only those roles with functional area attributes that match those in the request. Prerequisite: You have set parameter 2031 to. If parameter 2031 is set to, the application ignores the restrictions specified here. You can add multiple restriction values by adding additional instances of the parameter Access Request Role Selection 2033 Allow All Roles for Requestor Set the value to to allow the user to view all roles for request creation. Set the value to to restrict the roles the user can view for request creation. You specify the restriction criteria in parameter August

42 Access Request Role Selection 2034 Requestor Role Restriction Attribute <empty> This parameter allows you to require that, for access request creation, the application displays only the roles that have attributes that match the specified requestor attributes. Set the value to B to Restrict on Business Process. The application displays only the roles that match the requestor s business process attribute. Set the value to F to Restrict on Functional Area. The application displays only the roles that match the requestor s functional area attribute. Prerequisite: You have set parameter 2033 (Allow All Roles for Requestor) to. If parameter 2033 is set to, the application ignores the restrictions specified here. You can add multiple restriction values by adding additional instances of the parameter Access Request Role Selection 2035 Allow Role Comments Set value to to allow the user to enter Role Comments when creating access requests. Access Request Role Selection 2036 Role Comments Mandatory Set value to to require Role Comments when creating access requests. Note: This is a GLOBAL setting and is required for all roles included on requests. Mandatory comments can also be determined at the individual role level. Prerequisite: Parameter 2035 must be set to. August

43 Access Request Role Selection 2037 Display expired roles for existing roles Set the value to to include the roles for which the user assignment is expired when the user chooses the Existing Assignment button on the Access Request Access Request Role Selection 2038 Auto Approve Roles without Approvers Set the value to to allow the application to automatically approve access requests for roles without role owners. Access Request Role Selection 2039 Search Role by Transactions from Backend System Set the value to to allow users to search for roles using the role information in the GRC AC Repository. Set the value to to allow users to search for roles by transactions on a specific backend system in real time. This has the following effect: It adds the Transaction from Backend System criteria to the Select Roles screen. It makes the System criteria mandatory. It fetches role information from the specified system in real time, which may have an effect on performance. 91 August

44 92 Assignment Expiry 2041 Duration for assignment expiry in Days <empty> On the My Profile and Existing Assignment screens, the application displays the Status field for the roles. Roles that are about to expire displays the status of Expiring. You use this parameter to specify the timeframe (in days) that triggers the application to display the status as Expiring. In the following example, the My Profile and Existing Assignment screens will show the status of Expiring for all roles assigned to the user that is about to expire in 1 to 45 days. 93 Performance 2050 Enable Realtime LDAP Search for Access Request User. If set to, the application searches for the access request user on the specified LDAP source and in real time. Prerequisite: You have specified the data source as LDAP, or else the application ignores this parameter. Note: Be aware that because the search is performed in real time, it impacts performance. Workflow 2051 Enable User ID Validation in Access Request against Search Data Sources If set to, the application validates the UserID exists on the specified source system. If the user does not exist, the application does not allow the request to continue. The validation is performed when you choose Submit or press Enter. 94 August

45 Role Management 3000 Default Business Process <empty> Select the business process the application displays by default on the Role Import screen. Use F4 help to display the available business processes. You maintain the list of business processes in the Customizing activity Maintain Business Processes and Subprocesses under Governance, Risk and Compliance > Access Control. 95 Role Management 3001 Default Subprocess <empty> Select the subprocess the application displays by default on the Role Import screen. Use F4 help to display the available subprocesses. You maintain the list of subprocesses in the Customizing activity Maintain Business Processes and Suprocesses under Governance, Risk and Compliance > Access Control. Role Management 3002 Default Criticality Level <empty> Select the criticality level the application displays by default on the Role Import screen. Use F4 help to display the available criticality levels. You maintain the list of subprocesses in the Customizing activity Specify Criticality Level under Governance, Risk and Compliance > Access Control > Role Management. Role Management 3003 Default Project Release <empty> Select the project release the application displays by default on the Role Import screen. Use F4 help to display the available project releases. You maintain the list of project releases in the Customizing activity Maintain Project and Product Release Name under Governance, Risk and Compliance > Access Control > Role Management. Role Management 3004 Default Role Status <empty> Select the role status the application displays by default on the Role Import screen. Use F4 help to display the available role status. You maintain the list of project releases in the Customizing activity Maintain Role Status under Governance, Risk and Compliance > Access Control > Role Management. August

46 Role Management 3006 Allow add functions to an authorization Set the value to to display the Add/Delete Function button on the Maintain Authorizations tab of the Role Maintenance screen Role Management 3007 Allow editing organizational level values for derived roles The maintenance screen for derived roles displays organizational levels from the parent role. Set the value to to allow the derived roles to change the values for the organizational levels. Role Management 3008 A ticket number is required after authorization data changes Set the value to to require a ticket number when role authorizations are modified in PFCG and the user chooses the Synch with PFCG button. Note: The Ticket Number field is a free text entry field. The application only provides the field and does not have any specific requirements. You can enter information appropriate for your company s change request processes. 102 August

47 Role Management 3009 Allow Role Deletion from back-end system Set the value to to allow users the option to roles from both Access Control and relevant plug-in systems. Setting this value to Yes deletes the roles in each of the systems the role resided individually. For example the role is DELETED directly from PRD instead of having a delete request transported through CTS. Set the value to to allow users to delete roles only from Access Control. 103 Role Management 3010 Allow attaching files to the role definition Set the value to to allow users to attach files by displaying the Attachments tab on the Role Maintenance screen. 104 August

48 Role Management 3011 Conduct Risk Analysis before Role Generation Set the value to to automatically perform risk analysis when the user generates roles. 105 Role Management 3012 Allow Role Generation on Multiple Systems Set the value to to allow users to select multiple systems when generating roles. The application displays systems in the landscape which are available for role generation 106 action. August

49 107 Role Management 3013 Use logged-on user credentials for role generation When generating a role, the application connects to back-end systems to push the authorization data. The applicatiion needs a username/password to open the connection to the back-end ERP system. You can use this parameter to specify whether the application uses a generic username/password for all role generation connections to the ERP system, or the username/password of the person generating the role. Set the value to to use a generic username/password for the connection to the ERP system. You maintain the generic username/password for the connector in the Customizing activity Create Connectors under Governance, Risk, and Compliance > Common Component Settings > Integration Framework. Set the value to to allow the application to use the username/password of the person who is generating the role. The advantage of setting this parameter to Yes is that when someone opens a role in the ERP system, they can view exactly who generated it. If the parameter is set to No they can see only that the connector, with the generic username/password, has generated it. Role Management 3014 Allow role generation with Permission Level violations Set the value to to allow the application to generate roles even if Permission Level violations are present. Set the value to to prohibit role generation if permission level violations are present Role Management 3015 Allow role generation with Critical Permission violations Set the value to to allow the application to generate roles even if permission level violations are present. Set the value to to prohibit role generation if permission level violations are present. Role Management 3016 Allow role generation with Action Level violations Set the value to to allow the application to generate roles even if action level violations are present. Set the value to to prohibit role generation if action level violations are present. Role Management 3017 Allow role generation with Critical Action violations Set the value to to allow the application to generate roles even if critical action violations are present. Set the value to to prohibit role generation if critical action violations are present. Role Management 3018 Allow role generation with Critical Role/Profile violations Set the value to to allow the application to generate roles even if critical role/profile violations are present. Set the value to to prohibit role generation if critical role/profile violations are present. August

50 Role Management 3019 Overwrite individual role Risk Analysis results for Mass Risk Analysis The application allows you to perform ad hoc risk analysis for multiple roles under Access Management > Role Mass Maintenance > Run Risk Analysis. The application stores the results of the analysis. (See also parameters 1052, 1053). When you next perform mass risk analysis, the application searches the stored data to determine if there are previous risk analysis results for each role. You can choose whether or not the application overwrites the risk analysis results. Set the parameter value to to overwrite previous results. Set the parameter value to to not overwrite previous results. Note: This is done per individual role; it does not automatically overwrite the results for all roles. 113 Role Management 3020 Role certification reminder notification You use this parameter to set how many days prior to the Next Certification date the application sends a reminder to the role owner. For example, if the next certification is June 15, xxxx, and this parameter value is 10, then the application sends the reminder notification to the role owner on June 5, xxxx. You set the Certification Period in Days and Next Certification date in the Define Role phase, on the Properties tab Note Additional information about Certification Notifications: You can use the following Customizing activities to maintain custom notification s under Governance, Risks, and Compliance > Access Control > Workflow for Access Control: August

51 Maintain Custom Notification Messages Maintain Text for Custom Notification Messages Maintain Background Job for Reminders The following is an example of a notification The application provides notification templates. You can choose to assign your own custom notification templates in the Customizing activity Maintain Custom Notification Messages under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. You can customize the notification text by using the Customizing activity Maintain Text for Custom Notification Messages under Governance, Risks, and Compliance > Access Control > Workflow for Access Control. For certification notifications to be delivered, you must run the GRAC_ERM_ROLE_CERTIFY_TIF program either in the foreground or the background. You can schedule background jobs to run periodically using the Customizing activity Maintain Background Job for Reminders under Governance, Risk, and Compliance > Access Control > Workflow for Access Control. August

52 If you run the program in the foreground, the application displays the following results screen: Role Management 3021 Directory for mass role import server files <empty> The application allows you to perform mass role import under Access Management > Role Mass Maintenance > Role Import. You can select the Import Source as File on Server. You use this parameter to specify the location of the files on the server. Workflow 3022 Request Type for Role Approval 21 Use F4 help and choose the request type the workflow uses for role approval. The request type is associated with an MSMP process ID. You maintain the list of available request types in the Customizing activity Define Request Type under Governance, Risk, and Compliance > Access Control > User Provisioning. (See also parameter 1101). Workflow 3023 Priority for Role Approval 5 Priority of the request for Role Approval You use this parameter to set the default workflow request priority for Role Approvals. Use F4 help to display the list of available priorities. You maintain the list of available priority values in the Customizing activity Maintain Priority Configuration under Governance, Risk, and Compliance > Access Control > User Provisioning. You assign the MSMP Process ID of SAP_GRAC_ROLE_APPR to role approval priorities. August

53 Role Management 3024 Enforce methodology process for derived roles during generation You use this parameter to determine the derived roles displayed in the role generation phase of the master role. Set the value to to display only the derived roles that reach the role generation phase of the methodology process. Set the value to to display all derived roles, regardless of their phase in the methodology process. In the following example, Figure A shows five derived roles available; two of the roles are in Role Generation phase. Figure B shows that if the value is set to, only the two roles in Role Generation phase are displayed. 118 Superuser Management 4000 Application type 1 You use this parameter to set the firefighting configuration: Choose 1 for ID-based firefighting. Choose 2 for Role-based firefighting. 119 August

54 Superuser Management 4001 Default Firefighter Validity Period (Days) Set the default validity period (in days) of firefighter ID assignments to a firefighter. <empty> Note: This is only the default period. You can override the validity period for each assignment as needed in the front-end. 120 Superuser Management 4002 Send Immediately The application sends notifications to the controller. Set the value to to send the notifications immediately. Set the value to and the application sends notifications only when the user chooses the Update Firefighter Log button or runs the program GRAC_SPM_LOG_SYNC_UPDATE. The Update Firefighter Log button is available on the Consolidated Log Report under Superuser Management Reports. 121 Superuser Management 4003 Retrieve Change Log 122 If set to then the application fetches the Change Log when the user chooses the Update Firefighter Log button or runs the program GRAC_SPM_LOG_SYNC_UPDATE. The Update Firefighter Log button is available on the Consolidated Log Report under Superuser Management Reports. (See also parameter 4002.) Note: Plug-in system must have the O/S time and R/3 time zone matched for the logs to be properly collected. This is because STAD stores the logs in O/S files. August

55 Superuser Management 4004 Retrieve System Log If set to then the application fetches the System Log (debug changes) when the user chooses the Update Firefighter Log button or runs the program GRAC_SPM_LOG_SYNC_UPDATE. The Update Firefighter Log button is available on the Consolidated Log Report under Superuser Management Reports. (See also parameter 4002.) Superuser Management 4005 Retrieve Audit Log If set to then the application fetches the audit (security) logs when the user chooses the Update Firefighter Log button or runs the program GRAC_SPM_LOG_SYNC_UPDATE. The Update Firefighter Log button is available on the Consolidated Log Report under Superuser Management Reports. Note: You can activate Audit Logs using the transaction SM19. (See also parameter 4002.) Superuser Management 4006 Retrieve O/S Command Log 125 If set to then the application fetches the O/S Command Log when the user chooses the Update Firefighter Log button or runs the program GRAC_SPM_LOG_SYNC_UPDATE. The O/S Command Log tracks information when O/S commands (SM49) are created, changed, or executed. The Update Firefighter Log button is available on the Consolidated Log Report under Superuser Management Reports. (See also parameter 4002.) Superuser Management 4007 Send Log Report Execution Notification Immediately The application can send log reports controllers. The application sends the notifications as s or workflow items based on the configuration of the controllers. (See figure below.) Set the value to and the application sends notifications when the user chooses the Update Firefighter Log button or runs the program GRAC_SPM_LOG_SYNC_UPDATE. The Update Firefighter Log button is available on the Consolidated Log Report under Superuser Management Reports. Set the value to and the application only collects the logs when the user chooses the Update Firefighter Log button or runs the GRAC_SPM_LOG_SYNC_UPDATE program. The application sends the notifications when the GRAC_SPM_WORKFLOW_SYNC program is run Superuser Management 4008 Send FirefightId Logon Notification Set to and the application sends notification to the controller whenever a firefighter logs onto a system. Superuser Management 4009 Log Report Execution Notification Set to and the application sends notification to the controller when a user runs a log report. Superuser Management 4010 Firefighter ID Role Name ZSAP_GRAC_SMP_FFID Enter the name of the role assigned to the firefighter ID in the target systems. This is identifies to the application that the user who is logging on to the target system is a firefighter ID. The target system makes a call to the GRC Box and reads this configuration to check if the user has this role assigned to them. August