Hands-On Lab: Part 1: A beginners guide to the post-installation configuration of SAP Access Control
Kurt Hollis, David Jayne, and Phil Dunbar
[email protected] [email protected] [email protected]
1
SECTION 1 - Lab Contents Section 1: o Lab Overview o Lab Schedule o Lab User Access Information
Section 2: Section 3: Section 4: Section 5:
GRC Post-Installation Setup Steps and Verification GRC Risk Analysis Configuration and First Risk Analysis GRC Emergency Access Configuration and First Emergency Access GRC Access Request Configuration and First Access Request
SECTION 1 - Lab Overview GRC System for this lab is running locally on the laptops and not on a server across the network. We have 50 GRC systems running here, one per laptop. o This was done to guarantee good performance and complete independence from others working on the same system. The system is strictly yours and not shared. Laptop is running VM Workstation 10. The GRC system is running on Windows 2008 R2 Enterprise Server and uses MS SQL 2012 database. The GRC system is based on SAP NetWeaver 7.40 SP09. The GRC system is running GRCFND_A 10.1, SP07 The GRC plug-in is installed and is version 10.1, SP07. The SAP GUI is installed and is version 7.30 SP4.
2
SECTION 1 - Lab Schedule Wednesday, March 18th 2015 (8:30-11:45) Lab Overview I 15 Minutes (8:30-8:45) Lab – Part 1 75 Minutes (8:45-10:00) Short Break 15 Minutes (10:00-10:15) Lab Overview-II 15 minutes (10:15-10:30) Lab – Part 2 75 Minutes (10:30-11:45) SECTION 1 - Lab User Access Information •
SAP System SID is “GRD”
•
Client number is 200
•
Server host is “grc10train” in domain grc2014.com, Instance number is 00
•
Login to start the SAP System is grdadm, password is “Deloitte.1” (alternate login is user grctrain)
•
Use the MMC Console to start the system
•
Start the SAP GUI
•
Launch the GRD system GUI
•
Login to client 200 as grctrain1, grctrain2, and grceamadm (for Section 4 only) with password of “grc2015lab"
•
Launch Transaction “NWBC” for the GRC Web Interface
3
Steps to Bring Up the Lab System: Note: The steps below for starting up the lab system may have been done already in the classroom. The instructors will notify the entire class about the status of the laptop systems. Log in to the laptop Navigate to folder C:\DRIVERS\SAP.OVF Launch the GRC10_NEW.vmx by double clicking it in the above folder The VMWARE Workstation control panel launches Then power on the VM GRC10_TRAIN (USSLTCSNW1513) system (click the power on button) Use the menu drop-down to log in (Control+Alt+Delete) from the menu, not from the keyboard, and then log in to the system You may want to go to the control panel display and increase the display size to 1024x768 or slightly greater, but not too much or you will be scrolling windows around to see everything Start the SAP system using the MMC console Launch the SAP GUI and login to GRD Screen prints are in Section 2 of this lab guide 4
SECTION 2 - GRC Post-Installation Setup Steps and Verification
Bring System up and Login to the System
Workflow Setup
EMAIL Setup
Verify the Client Copy is Completed
Test NWBC user Interface
System Connections Setup
Activate Applications in Client
New UI5 Odata Services
Maintain Web Services in SMICM (HTTP)
STRUST SSO Setup 5
Steps
Steps to be performed
Section 2 Step 1
The lab system should have the Lab Image “GRC10TRAIN” loaded for you already. If not, contact the instructor. Start the SAP system using the MMC console in Windows.
STARTUP LOGIN
Log in to the SAP system using grdadm, password is “Deloitte.1”. Using the MMC console, right-click on GRD and select Start from the menu.
System starts in a few minutes. Start SAP GUI and connect to GRD System.
6
SAP Login screen. Log in to the GRD system. Log in client 200 with user grctrain1 (or grctrain2 for some parts of the lab) and password “grc2015lab”.
7
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 2
After logging into the system, perform the post-installation steps for GRC.
CLIENT COPY
First check is to verify the client copy from client 000 to client 200 has completed successfully. We previously made this copy using client copy profile SAP_ALL. This is the recommended way to copy the client for a new system. Navigate the menu tree, Tools Administration Client Administration Copy Logs.
8
Verify the copy was successful. Screen is as shown above.
9
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 3
Next step is done using transaction SPRO. Transactions are entered into the blank field in the upper left.
SPRO Activate GRC Apps
10
Click on the button “SAP Reference IMG.” NOTE: Much of the configuration is done using transaction SPRO and the SAP Reference IMG during this session.
11
In the menu that comes up, go to the area Governance, Risk and Compliance General Settings Activate Applications in Client. Three applications exist in this setting: GRC-AC, GRC-PC, and GRC-RM. We are activating only GRC-AC for this system.
Verify the setting only, no changes needed.
Exit this screen. 12
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 4
We are done with SPRO for a moment. Exit SPRO. Now enter transaction SICF. Click the EXECUTE button under Maintain Services.
ICF SETTING
Verify the Services are activated. See the screen below: public, bc, grc. (Just check it, no need to do any changes here.) Maintain Services for Web Applications allows the content to be used in the system. It must be activated.
13
See that the public, bc, grc, iwbep, and opu are bold, this means they are activated. No changes needed here, verify only. Exit this screen.
14
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 5
Now enter transaction SMICM. Go to menu Goto Services.
ICM SETTING
15
Check the services. Verify the HTTP, HTTPS, and SMTP services are enabled. Verify the timeout settings are 3600 for Keep Alive, 1800 for Process Timeout. No changes needed here, verify only. Exit this screen.
16
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 6
Now enter transaction STRUSTSSO2. Check that the System PSE is green and the SSL server, client, and client SSL are green. This setup requires entries in the system profiles and the SAPCRYPTO libraries to be installed in the Kernel at the operating system level of the SAP system. This is needed for NWBC operation. No changes needed here, verify only. Exit this screen.
SSO SETTING
17
This is an example of settings in the system profile needed for NWBC and GRC. No need to verify this (provided as FYI).
18
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 7
Set up new User Interface (UI5) views and SAP Netweaver Gateway. This is required for the new Access Control Request Screens in the NWBC and the Remediation View for the User Level Risk Analysis.
UI5 ODATA Gateway SETTING
Go back into SPRO again. Navigate to SAP Netweaver Gateway OData Channel Administration General Settings and execute Activate and Maintain Services
.
19
Look at the ICF Nodes and System Aliases at the bottom of the screen. The ICF Node needs to be active and the System Alias needs to have assigned LOCAL Alias. No need to make any changes here, this step is verify only. Exit this screen.
20
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 8
Launch and test the NWBC interface. Now that all the previous steps have been completed, it is possible to test the NWBC interface.
NWBC SCREEN
Enter transaction NWBC in the transaction window to the right of the green check. If you are currently not at the main menu and inside another screen, enter /nNWBC to run the transaction.
The NWBC screen should appear in a new browser window (pop up).
21
Navigate to each sub menu My Home, Setup, Access Management, Reports, and Analytics one at a time to test this access. See each sub-menu appear. No need to make any changes here, this step is verify only. Exit this screen.
22
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section 2 Step 9
Workflow Customizing. Go back into SPRO IMG again. Navigate to GRC General Settings Workflow, and execute Perform Automatic Workflow Customizing.
WORK FLOW SETUP
23
Before it looked like screen print below on the left. After it should look like screen print below on the right.
BEFORE
AFTER
We need to verify a few items. The following are just checks, no changes are needed. Please see the sections of this menu, click on them, and read the text in the right-hand pane for instructions followed during setup.
24
Check that the jobs are scheduled. These should all have green checks. The Event Queue job is optional and sometimes will not be running; this is OK.
The RFC destination is important, see the USER used for this function. Please take note of this user. No changes required.
25
Steps
Steps to be performed (requires changes during this step)
Section 2 Step 10
Go to transaction SPRO again, into the IMG. Enter into Workflow, Perform Task Specific Customizing by selecting Governance, Risk and Compliance General Settings Workflow Perform Task-Specific Customizing.
WORK FLOW TASKS
26
Expand the GRC area. We will explore the GRC-SPC agents and event linking. Click on Assign Agents across from the GRC-SPC area.
27
Select the line and click the Attributes button. A pop-up displays. This procedure is only done for the tasks with IDs starting with letters TS, not WS.
28
Set General Task and click the Transfer button.
Check the setting in the screen. It should now say General Task Now, go back to the screen before and select the “Activate event linking” for the GRC-SPC workflow. Scroll down to the bottom of the list until you see the WS Events.
29
Click on the Deactivated button for the WS 75900005 event to activate it. You will need to create a transport request as part of this process. Click the white paper icon.
30
Enter a Short Description and click Save.
Click the save icon to save the request.
31
Click the Puzzle piece Icon. In the pop-up, change the error feedback to “Do not change linkage” and click save. Then click the green check button.
Exit this application.
Click the note with the glasses and review the documentation for this IMG activity. This exercise was an example of the settings needed in this area for the Workflow setup. Note: For Access Control, more steps need to be completed when the system has the plug-in installed. These are not covered in this lab due to time constraints. These settings have already been made for your systems.
32
Steps
Steps to be performed (PARTS OF THIS STEP ARE PERFORMED)
Section 2 Step 11
Set up the connectors to the other systems. Go back into the SPRO IMG and navigate to the Integration Framework under Governance, Risk and Compliance Common Component Settings Integrated Framework. Setup of the connectors involves settings made in seven places. These steps are very important for the integration of SAP systems with the GRC applications. We are not covering the Portal integration, LDAP integration, or non-SAP integration in this lab due to time constraints and level of complexity.
CONNECT SYSTEMS
The first part is in this area of the IMG. Many of the settings are done already for you. However, you will have to make certain settings. These are pointed out to you.
33
Part 1 - IMG area we are focusing on first. Enter the first IMG activity step “Create Connectors.” This is actually transaction SM59. Look at the ABAP connections and find GRDCLNT200. This step is already done for you. Please verify the settings.
34
CREATE CONNECTORS - RFC Connection is GRCCLNT200. Double-click and verify the settings. We are actually connecting back to the same system GRC system to GRC system. This is possible because we have the GRC Plug-In installed is this system. Verify the settings.
35
Exit the connector settings after verifying them.
36
See the details under the Login and Security tab. The correct client 200 is filled in. The user must have the correct roles assigned in the remote system. No changes, verify only. The next setting is the “Maintain Connectors and Connection Types.” Here we are assigning the connectors to the connection types and the connector groups.
37
Click Define Connectors after selecting the SAP box on the left side.
Verify the connector is GRDCLNT200. This is how you assign the connector to each connector type. We are only using SAP type here.
38
After clicking into the DEFINE CONNECTOR GROUP, select the line SAP_BAS_LG, and then click the ASSIGN CONNECTORS TO CONNECTOR GROUP FOLDER
The connector group is based on the rule sets loaded. See below for guidance. We are using only the GRAC_RA_RULESET_SAP_BASIS rule set for this training (SAP_BAS_LG). Please only assign the SAP_BAS_LG for this training class. 39
Assign connector type SAP if blank.
Rule Sets (EXAMPLE ONLY) GRAC_RA_RULESET_SAP_R3: Rules for ERP including Basis and HR (SAP_R3_LG) GRAC_RA_RULESET_SAP_HR: Rules for HR only (SAP_HR_LG) GRAC_RA_RULESET_SAP_NHR: Rules for ERP excluding HR and Basis (SAP_NHR_LG) GRAC_RA_RULESET_SAP_BASIS: Rules for Basis (SAP_BAS_LG) We are only using this one GRAC_RA_RULESET_SAP_APO: Rules for APO (SAP_APO_LG) GRAC_RA_RULESET_SAP_CRM: Rules for CRM (SAP_CRM_LG) GRAC_RA_RULESET_SAP_ECCS: Rules for ECCS (SAP_ECC_LG) GRAC_RA_RULESET_SAP_SRM: Rules for SRM (SAP_SRM_LG) GRAC_RA_RULESET_JDE: Rules for JD Edwards (JDE_LG) GRAC_RA_RULESET_ORACLE: Rules for Oracle Apps (ORACLE_LG) GRAC_RA_RULESET_PSOFT: Rules for PeopleSoft HRMS (PSOFT_LG)
The last step in this top section of the connector settings is one of the most important.
Maintain Connectors Settings: In the Work Area pop-up, select each of the integration scenarios one at a time. YOU MUST SET UP THE CONNECTOR FOR SCENARIO ROLMG! The connectors for AUTH, PROV, and SUPMG have already been set up for you. Verify these. Please set up the connector GRDCLNT200 with integration scenario ROLMG. Steps are below.
40
Select the ROLMG scenario and get to the screen below. Now click the box next to the ROLMG sub scenario definition and click the Scenario-Connector Link on the right. This brings up a screen where you assign the connector GRDCLNT200.
41
Click New Entries on the screen.
From the selection box that pops up, select the connector GRDCLNT200
Click the Save icon on the top menu bar. A transport request comes up. Click the white paper icon and create a new request and fill in the description as shown below. Click the green check and save it.
42
This is done. Now use the arrow keys to exit this step until you are back at the IMG menu. This same process would be repeated for each scenario. According to an SAP Note, it is needed to fill them out for all scenarios even if you are using only one of them.
43
Part 2 of the connector settings is under the Access Control area and contains four steps. Perform the validation of this next. Click on configuration item “Maintain Connector Settings” and verify the target connector GRDCLNT200 is assigned. Click in the Application Type area to see what the drop-down list provides. We are only using SAP type for this system. No changes needed. 44
When done reviewing, exit this screen.
In the next step in the IMG, open Maintain Mapping for Actions and Connector Groups. Notice the connector group(s). We are working with the SAP_BAS_LG group. Select the SAP_BAS_LG group and click on the right side Assign default connector.
45
Here we have to fill in multiple entries. One entry for each action 1, 2, 3, 4. Verify this is correct. Click the Action drop-down to see the list of actions available. These are assigned for the connector group we are using, which is SAP_BAS_LG. Exit this screen. Click the green arrow back a few times to get to the IMG menu again. Now for the last item, Plugin settings. Verify the Plugin settings. It needs one single entry for GRDCLNT200.
Exit this screen back to the IMG menu. The connection is now setup for the applications and will appear in the application screens when choosing the system. This section is very important for all applications in Access Control to function, and must be done before configuring the applications. This system is also connected to itself using the GRC Plug-In. So we are using the same GRC system to manage the GRC systems for Access Control applications, such as Risk management, Super User management, and user provisioning functions. END OF LAB SECTION 2 – Congratulations, this was a big section to complete. 46
SECTION 3 - GRC Risk Analysis Configuration and First Risk Analysis
Activate BC Sets (Rule Sets)
Run the Full Batch Risk Analysis
Run the Batch Risk Analysis Monitor
Generate the Rules
Test Risk Analysis
Run the Risk Violation Dashboards
Maintain Configuration Settings for ARA
Run the Synchronization Jobs
Check the Application Logs SLG1
47
Steps
Steps to be performed
Section 3 Step 1
Activate BC Sets. At the main menu of the system (out of the IMG/SPRO screen), enter transaction SCPR20.
BCSET ACTIVATE
We are only activating the two rules sets we are using. The full table is shown for reference. The other BCSETS will be actived during other lab steps when needed. DO NOT ACTIVATE THE GREYED OUT BCSETS YET. Only the two needed for this section. Access Risk Analysis GRAC_RA_RULESET_COMMON GRAC_RA_RULESET_JDE GRAC_RA_RULESET_ORACLE GRAC_RA_RULESET_PSOFT GRAC_RA_RULESET_SAP_APO GRAC_RA_RULESET_SAP_BASIS GRAC_RA_RULESET_SAP_CRM
SOD Rules Set (We activate this one now) JDE Rules Set ORACLE Rules Set PSOFT Rules Set JDE Rules Set SAP BASIS Rules Set (We activate this one now) SAP CRM Rules Set 48
GRAC_RA_RULESET_SAP_ECCS GRAC_RA_RULESET_SAP_HR GRAC_RA_RULESET_SAP_NHR GRAC_RA_RULESET_SAP_R3 GRAC_RA_RULESET_SAP_SRM
SAP ECCS Rules Set SAP HR Rules Set SAP R/3 less HR Basis Rules Set SAP R/3 AC Rules Set SAP SRM Rules Set
Access Request Management GRAC_ACCESS_REQUEST_REQ_TYPE* GRAC_ACCESS_REQUEST_EUP* GRAC_ACCESS_REQUEST_APPL_MAPPING* GRAC_ACCESS_REQUEST_PRIORITY*
Request Type EUP (Note: Only the value EU ID 999 is valid for this BC set.) Mapping BRF Function IDs and AC Applications Request Priority
Business Role Management GRAC_ROLE_MGMT_SENTIVITY* GRAC_ROLE_MGMT_METHODOLOGY* GRAC_ROLE_MGMT_ROLE_STATUS* GRAC_ROLE_MGMT_PRE_REQ_TYPE*
Sensitivity Methodology Process and Steps Role Status Prerequisite Types
Superuser Management GRAC_SPM_CRITICALITY_LEVEL*
Criticality Levels
Workflow GRC_MSMP_CONFIGURATION*
MSMP Workflow Configuration Rules Set
49
Steps to activate the BCSETS
Fill in the name GRAC_RA_RULESET_COMMON and click the Activation button. A transport request may pop up, fill this in and save using green check mark. If it is to be a new request, click the white paper icon to create a new request. Then fill in and save it.
50
After activating this BC Set. You get the below message at the bottom of the screen.
51
Perform the steps again for the other BC Set GRAC_RA_RULESET_SAP_BASIS.
Activate it. That concludes the rule set activation.
52
Steps
Steps to be performed
Section 3 Step 2
Generate Access Rules.
Generate Rules
Generate the rules by going to IMG under Governance, Risk and Compliance Access Control Access Risk Analysis SoD Rules Generate SoD Rules. There are alternative methods to generating the rules. In the NWBC interface, in the RULESET sub-menu, you can generate the rule set rules there. For this exercise, we are using the IMG method below.
53
Fill in the full range in the drop-down, from the first entry on the left to the last entry on the right. Execute this. A small message appears at the very bottom of the screen showing program is completed.
54
Steps
Steps to be performed (No changes needed, verify only)
Section 3 Step 3
Maintain Configuration Settings. Use SPRO to review the configuration settings. Answer one question below, no changes needed.
Config Settings
55
Note the setting for the Risk Analysis. What is the Default Rule Set used? HINT – Look at Param ID 1025. FYI – SAP has a guide dedicated to the configuration settings available for download. No changes needed here, only look at them.
56
Steps
Steps to be performed (No changes needed, verify only, important step)
Section 3 Step 4
Run the NWBC and check that the rules are loaded.
Check Rules
The Web browser launches.
57
Check that the Access Risks, Functions, and Rule Set exists. See next three screens.
58
Check that the Access Risks exist.
Check that the Functions exist. 59
Check that the Rule Set exists. What is the Rule Set Name? If any of the above screens are empty, contact the instructor in the room immediately! This needs to be correct before proceeding.
60
Steps
Steps to be performed
Section 3 Step 5
We need to run the Synchronization jobs to get the user, role, profile, and authorizations data from the source systems. In our case, the source system is also the same GRC system. This is fine for learning purposes, such as this training. We run two jobs.
Sync Jobs
In IMG go to Access Control Synchronization Jobs and run Authorization Synch (program GRAC_PFCG_AUTHORIZATION_SYNC). It is recommended you run it in the background, but we will run it in foreground during this lab exercise. This program contains three jobs: Org. Value sync, Transaction Sync, and Objects sync.
1st Job to run = Authorization Data Synchronization 61
Fill in the Connector name and click Execute. We run this in the foreground. NOTE: These jobs can be scheduled to run in background using SM36 to create the background job, and SE38 to create the varients to store the values in the fields so they can be used over and over again.
The result screen comes up in about three to five minutes. It should not take that long for these systems. Note: Larger ERP systems may take 30-40 minutes to run. That is why background processing is usually preferred.
(Note – screen above has GRDCLNT100 for example, your screen should have GRDCLNT200)
62
In the same path go to Repository Object Synch (program GRAC_REPOSITORY_OBJECT_SYNC).
Be sure to select the Full Sync Mode.
This job runs in one to three minutes. NOTE: On larger systems with many users and roles, this job may take 10-20 minutes to run. 63
NOTE: These jobs can be scheduled to run in background using SM36 to create the background job, and SE38 to create the varients to store the values in the fields so they can be used over and over again. Usually a full sync is done weekly and an incremental sync is done daily. More frequent jobs can be scheduled to allow new users and roles to be used in the GRC analysis jobs, reports, and ad-hoc analysis.
(Note – screen above has GRDCLNT100 for example, your screen should have GRDCLNT200) Completed job output above. 64
Steps
Steps to be performed
Section 3 Step 6
Now you should be able to run a risk analysis. Go to Access Management Workcenter and run a User Level Risk Risk Analysis on a specific user.
Run Risk Analysis
Let’s test this. Go to the main menu of the system and run the NWBC transaction. Run the NWBC again.
In the NWBC Browser window, Click the Access Management sub-menu.
65
Run the User Level anaylsis first. Use system GRDCLNT200 and user GRCTRAIN1. Fill out as shown below. Use the minus button to remove unwanted items from the query screen.
Fill in the screen. Run in foreground. Check the settings carefully. 66
View the results. Example below:
67
Run the same Risk Analysis – User Level, change the Report Options for REMEDIATION VIEW only.
68
After choosing Remediatation view, it will look like the above. It may take longer to come up. (Note – screen above shows system GRDCLNT100 in this example, your screen will be actual system GRDCLNT200)
69
Perform the same steps for the Role Level analysis. Use role SAP_GRC_SPC_SETUP for this analysis test.
70
Results of ROLE analysis above.
71
Steps
Steps to be performed
Section 3 Step 7
Set up Parallel Jobs capability. This is in preparation of running the full batch risk analysis.
Setup Parallel Jobs
Run RZ12 transaction (not in the IMG menu). Check if the Login Group parallel_generators exists. If so, verify the settings as shown below. Otherwise, click the white paper icon to create the group assignment. The name must be “parallel_generators” to be used in the applications.
72
Click Save. A message will appear at bottom in yellow. You must press enter to save and get past this screen! INGORE WARNING and press enter to save it. Go in and check the entry again to make sure it saved.
73
Steps
Steps to be performed
Section 3 Step 8
To run the Full Batch Risk Analysis, go into the SPRO transaction again and click on the Execute Batch Risk Analysis menu item.
Run Full Batch Risk Analysis
Fill out the screen as shown and execute the job. It will take about 10-15 minutes to complete it. You will monitor the job during this time. After running this job, move immediately to the next step on how to monitor the job. NOTE: It is possible to also run using a transaction GRAC_BATCH_RA (or program GRAC_BATCH_RISK_ANALYSIS) as an alternative.
74
Fill out the Batch Risk Analysis screen as shown above and execute it. 75
Steps
Steps to be performed
Section 3 Step 9
Monitoring the Batch Risk Analysis.
Monitor Batch Risk Analysis
Using SPRO (IMG) go to the menu Access Risk Analysis and run Monitor Batch Risk Analysis. Change the dates so the start date is one day earlier. We have noticed some time issues with the system time not matching the time in Vegas. With time out of sync, you may miss picking up the jobs in the search. Making the date range larger will help to pick up the jobs.
76
Note: You can monitor the batch risk analysis job with transaction GRACRABATCH_MONITOR.
Click the box in front of the job row and click Show Details. Drill into the details to see the detailed status.
77
You can see what is going on while it is running. For large systems, this job can take a long time.
78
Check that the job is using parallel processes. Use transaction SM50 while the job is executing in the background to see the two batch work processes running the job. Below is SM50 screen.
79
80
Steps
Steps to be performed
Section 3 Step 10
View the Risk Analysis dashboards. The data in the dashboards are only visible after running the batch risk analysis jobs. In the NWBC screen, go to the Reports and Analytics menu. We will run the Risk Violations, User Analysis, and Role Analysis dashboards. These pop up in another window. Run each one, one at a time. See below screens for examples.
View Dash Boards
81
The Risk Violations screen is interactive. You can click into the pie chart or bar chart items to see the detail below them. Try this for both the pie chart HIGH and MEDIUM and BS00 in the bar chart. Be sure to drill down in the next screens that open. Check out the details. Try changing the Analysis Type from User to Role.
82
Check the User Analysis dashboard too. Explore the details.
83
Find the GRC roles in the Role Analysis dashboard. They begin with SAP_GRC. The data in the dashboards is based on the Batch Risk Analysis job. This job needs to be scheduled nightly to get the data updated.
84
Steps
Steps to be performed
Section 3 Step 11
Check the Application logs for errors. Run transaction SLG1 in the GRD system. Fill the screens as shown below and execute.
SLG1 Appl Errors
85
See examples of log output below. This is a very useful tool for GRC applications when problems are occurring.
86
SECTION 4 - GRC Emergency Access Configuration and First Emergency Access Special User Instructions: 1) The steps to configure the “Emergency Access Management” component of GRC 10.1 are illustrated in this section. 2) Please log in using GRCEAMADM for all the steps except for Step 10, where you will use GRCTRAIN1 and GRCTRAIN2 for configuration and testing the EAM functions. The users to be used for each step are pointed out in the documentation.
87
High Level Overview of the Configuration Steps A pictorial depiction of the high-level configuration steps is shown below:
Activate BC Sets (Emergency Access)
Assign Firefighter IDs to Firefighters
Access Firefighter ID
Add Connectors to Firefighting Scenario (SUPMG)
Define Owners and Controllers
Run Log Collection Job
Maintain Configuration Settings
Complete Synchronization
Access and Review Firefighter Logs
Maintain Criticality Levels
Create Firefighter IDs in Target Systems
88
Steps
Steps to be performed
Section 4 Step 1
Activate BC Sets. (Logged in as user GRCEAMADM)
Activate BCSETS
Enter transaction code SCPR20. Enter GRAC_SPM_CRITICALITY_LEVEL in the BC Set field and press F7 or click Activate. Create a new transport request or assign to an existing one. Use the Expert Mode under the Activation Options window and click OK to complete the activation.
On successful activation, a confirmation message is shown as below.
89
Steps
Steps to be performed
Section 4 Step 2
Maintain Plug-in settings. (Logged in as user GRCEAMADM)
Plug-In Settings
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and Compliance (Plug-in)Access ControlMaintain Configuration Settings. Review and ensure the values for the following parameters exist: 1089 1 1090SAP_GRAC_SPM_FFID
90
Steps
Steps to be performed
Section 4 Step 3
Add Connectors to the Super user Management Scenario (SUPMG) (Logged in as user GRCEAMADM)
SUPMG Connector
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and ComplianceCommon Component SettingsMaintain Connection Settings. Enter SUPMG in Integration Scenario and click OK.
Highlight the row that indicates the SUPMG scenario and double-click the Scenario-Connector Link folder.
Review and confirm the entry for the target connection as shown in the screen below. If no entry exists, click on New Entries and add the Target Connector.
91
Steps
Steps to be performed
Section 4 Step 4
Review Criticality Levels for Emergency Access Management. (Logged in as user GRCEAMADM)
Criticality Levels
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and ComplianceAccess ControlEmergency Access Management Maintain Criticality Levels for Emergency Access Management. Confirm that criticality levels are populated in the table as indicated in the screen below.
Changes can be made and saved, but would require the creation of a new transport or addition to an existing transport.
92
Steps
Steps to be performed
Section 4 Step 5
Review Key Configuration Settings for Emergency Access Management. (Logged in as user GRCEAMADM)
Config Settings For EAM
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and ComplianceAccess ControlMaintain Configuration Settings.
Changes can be made and saved, but would require the creation of a new transport or addition to an existing transport.
93
Steps
Steps to be performed
Section 4 Step 6
Create Firefighter IDs. (Logged in as user GRCEAMADM) Use Tcode SU01
Create FF IDs
Enter FF_TRAIN01 in the User field. Click Users (Top menu) and click Copy. In the To field, enter FF_TRAINGRC. Check all the boxes in the copy screen and click Copy (F5).
In the Logon data tab, click on the Wizard button next to the Initial password field. Save the changes to complete the creation of the Firefighter ID.
94
Steps
Steps to be performed
Section 4 Step 7
Synchronize Created Firefighter IDs using Tcode GRAC_REP_OBJ_SYNC. In the Connector field, use the Search button to choose the connector. (Logged in as user GRCEAMADM)
Run FULL Repository Sync Job
Choose Full Sync Mode.
Click Execute (F8) to complete the sync.
95
Steps
Steps to be performed
Section 4 Step 8
Define Owners and Controllers for the created Firefighter ID. (Logged in as user GRCEAMADM)
Define Owners And Controllers
Execute Tcode NWBC to launch the SAP NetWeaver Business Client window. Navigate to the Setup tab and click “Access Control Owners” under Access Owners Sub menu.
Confirm that GRCTRAIN2 is setup as a Firefighter ID Owner and a Firefighter ID Controller. Once confirmed close the window.
Navigate back to the Setup tab and click Owners. Within the Owners window, click Assign at the top of the window.
96
Search for user GRCTRAIN2. To choose the user, highlight it on the search screen and then click on it. Click on Add within the Firefighter ID table and click Go to show the list of Firefighter IDs.
Choose FF_TRAIN01 and move it to the selected pane by highlighting it and using the directional arrow (shown above).
Click Save on the Owner Assignment screen.
To assign controllers, without leaving the Setup tab, click Controllers under Superuser maintenance. Within the Owners window, 97
click Assign at the top of the page.
Search for user GRCTRAIN2. To choose the user, highlight it on the search screen and then click on it. Click on Add within the Firefighter ID table and click Go to show the list of Firefighter IDs. Add the Firefighter ID FF_TRAIN01 and set the ‘Notification by’ to Log Display.
98
Steps
Steps to be performed
Section 4 Step 9
Define Reason Codes for Firefighter Usage. (Logged in as user GRCEAMADM)
Define Reason Codes
Execute transaction NWBC. Within the Setup folder tab, locate the Reason Codes link under Superuser Maintenance menu (bottom of the page) and click on it. Within the Reason Code window, click on Create to define a new reason code.
Add the Reason Code and a long description within the respective text fields. To define the systems for which the created reason code is applicable, click Add within the system table. Click Save to save your changes once all the fields have been defined.
99
Steps
Steps to be performed
Section 4 Step 10
Assign Firefighter ID to Firefighter User. (Logged in as user GRCEAMADM)
Assign Firefighter
Execute Transaction NWBC. Within the Setup folder tab, locate the Firefighters link under Superuser Maintenance menu (bottom of the page) and click on it. Click Assign at the top of the Firefighter window. Search for user GRCTRAIN2, highlight it on the search screen, and click on it to choose it.
Click on Add within the Firefighter ID table and click Go to show the list of Firefighter IDs. Choose FF_TRAIN01 and move it to the selected pane by highlighting it and using the directional arrow. Choose the Owner (GRCTRAIN1) from the search screen and click Save to save the assignment.
100
Steps
Steps to be performed
Section 4 Step 11
Using a Firefighter ID. ** (Logged in as user GRCTRAIN1 now) **
Use Firefighter
Logout as GRCEAMADM. Ensure you are logged in as GRCTRAIN1. Execute transaction GRAC_EAM. Click the Logon button within the Emergency Access Management Dashboard.
Choose a reason code from the Reason Code dropdown. Enter the planned activity within the text area (use your own). Enter transaction codes to be used (eg. PFCG, SU01, SU10, SE38 etc.) within the Actions field. Click OK to launch the remote session.
101
Steps
Steps to be performed
Section 4 Step 12
Execute the Firefighter Log Synchronization job to complete collection of the Activity log. (Logged in as user GRCEAMADM)
Run Log Sync Job
Execute Tcode GRAC_SPM_LOG_SYNC. Enter the connector name and click Execute (F8) to initiate the job that collects the activities performed under the Firefighter ID.
102
Steps
Steps to be performed
Section 4 Step 13
View the Firefighter logs. Execute Tcode NWBC. Click the Reports and Analytics folder tab.
View FF Logs
Locate the Firefighter Log Summary Report link under the Emergency Access Management Reports menu and click on it.
Click on ‘Run in foreground’ to view the generated log list.
View the log by highlighting the item on the list and click Open to see the details.
103
SECTION 5 - GRC Access Request Configuration and First Access Request
Activate BC Sets (User Provisioning)
Create Access Request
Approve Access Request
Add Connectors to Firefighting Scenario (PROV)
Complete Synchronization
Review Auto Provisioning
Maintain Configuration Settings
Import Roles
Maintain Provisioning Settings
Activate MSMP Workflow
104
Steps
Steps to be performed
Section 5 Step 1
Activate BC Sets.
Activate BCSETS
Enter transaction code SCPR20. Enter the BC Sets below, one by one in the BC Set field and use F7 or click Activate. Create a new transport request or assign to an existing one. Select Expert Mode under the Activation Options window and click OK to complete the activation.
GRAC_ACCESS_REQUEST_APPL_MAPPING GRAC_ACCESS_REQUEST_EUP GRAC_ACCESS_REQUEST_PRIORITY GRAC_ACCESS_REQUEST_REQ_TYPE
On successful activation, a confirmation message is shown as below.
105
Steps
Steps to be performed
Section 5 Step 2
Add Connectors to the User Provisioning scenario (PROV).
Add Connector for Prov.
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and ComplianceCommon Component SettingsMaintain Connection Settings. Enter PROV in Integration Scenario and click OK.
Highlight the row that indicates the PROV scenario and double-click the Scenario-Connector Link folder.
Review and confirm the entry for the target connection as shown in the screen below. If no entry exists, click on New Entries and add the Target Connector.
106
Steps
Steps to be performed
Section 5 Step 3
Maintain Provisioning Settings.
Maintain Prov. Settings
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and ComplianceAccess ControlUser Provisioning Maintain Provisioning Settings.
Double-click Maintain Global Provisioning Settings. Set the values as shown below. Role provisioning Type Direct Auto Provisioning Auto provisioning at end of request Role assignment Check Provisioning Effective Immediately Save the settings and add to transport request.
107
Steps
Steps to be performed
Section 5 Step 4
Activate the MSMP Workflow.
Activate MSMP Workflow
Navigate to Tcode SPROSAP Reference IMG expand Governance, Risk and ComplianceAccess ControlWorkflow for Access Control Maintain MSMP Workflows.
Go to Change mode and click on Step 7 (Generate Versions) and choose Activate.
108
Confirm activation of the approval workflow.
109
Steps
Steps to be performed
Section 5 Step 5
Import Roles. Execute Tcode NWBC. In the Access Management tab, under Role Mass Maintenance, click Role Import.
NWBC Role Import
In the Role Import screen, populate the screen as indicated below for Stage 1.
110
For Stage 2, enter the details as shown below:
For Stage 3, click Next to move to Step 4. In Step 4, set the job as a background job using the parameters shown below.
A confirmation message is shown in Stage 5 indicating successful scheduling. 111
Steps
Steps to be performed
Section 5 Step 6
Run the Synchronization job. Execute Tcode GRAC_REP_OBJ_SYNC to initiate a repository sync job on completion of the background job from Step 5.
Run Sync Jobs
Click Execute (F8) to initiate the job. On completion, the log is shown (example below).
112
Steps
Steps to be performed
Section 5 Step 7
Create an Access Request. Execute Transaction NWBC. Within the My Home tab, click on Access Request to launch the Access Request screen.
Create Access Request
In the Access Request screen, fill in the fields as shown below. To add roles, click on Add and choose Role.
113
Navigate to the User Details tab and fill in the First Name, Last Name and Email for the user.
In the Add Role screen, click on Search to search for a role. Highlight one of the search results and use the arrow buttons to move them to the selected screen.
114
Click OK to return to the Access Request screen. Click Submit to submit the access request.
\
115
Steps
Steps to be performed
Section 5 Step 8
Approve the Access Request. Login as GRCTRAIN2. Execute Tcode NWBC. From the My Home tab, click on Work Inbox.
Approve Access Request
In the Work Inbox, locate the request number and click on it to open the Request Approval window.
116
In the Approval window, review the request and click on Submit to approve the request.
117
Enter comments in the Comments tab prior to approval. A confirmation message is shown on the approval.
118
Steps
Steps to be performed
Section 5 Step 9
Review the Auto Provisioning. Execute Tcode SU01. In the User field, enter GRCCONF01 and click Display.
Review Auto Provision.
Navigate to the Roles tab and review the request role. Confirm that it was assigned to the user.
End of Lab – Great Job, you made it, and thanks for attending!! 119
APPENDIX – FOR YOUR REFERENCE:
Steps
Steps to be performed (VERIFY STEP ONLY, NO CHANGES)
Section Appendix
Enter Transaction SCOT to set up email. (Validation Only in this section, no changes!)
Step A
Click on SMTP Node under the Settings Folder, Outbound Messages Folder.
EMAIL SETUP
120
Verify the settings in the screen below (NO CHANGES).
121
No changes needed, verify the settings. The settings for Internet should have * in the SET button.
Check that the job is running. You can double click the Job Name to open the popup panel. See the job runs every ten minutes. Exit this transaction, SCOT.
(DO NOT PERFORM THE FOLLOWING COMMAND, READ ONLY)
122
Wellesley Information Services, 20 Carematrix Drive, Dedham, MA 02026 Copyright © 2015 Wellesley Information Services. All rights reserved.
