According to the SAP Help Portal, you can collect two types of logs for an Emergency Access Management session: usage procedure log and security audit log. Usage procedure log is a log that records the actions performed by a firefighter during a firefighting session, such as transactions executed, reports generated, or changes made. Security audit log is a log that records the security-related events that occur during a firefighting session, such as logon attempts, password changes, or authorization checks.

According to the SAP Help Portal, you can use a custom end-user personalization configuration for various purposes, such as assigning it to an access request template, determining roles that can be assigned on a request, and determining fields shown in a workflow item. Assigning it to an access request template means that you can customize the user interface and functionality of a specific template. Determining roles that can be assigned on a request means that you can restrict or allow certain roles based on criteria such as role type, role level, or role owner. Determining fields shown in a workflow item means that you can hide or display certain fields in the access request form.

According to the SAP Help Portal2, two of the standard roles that SAP delivers for use by the EAM Owner or EAM Controller or both are: SAP_GRAC_SPM_FFID (A) and SAP_GRAC_SUPER_USER_MGMT_CNTLR . These roles allow the EAM Owner or EAM Controller to perform tasks such as maintaining Firefighter IDs, assigning Firefighter Owners and Controllers, reviewing Firefighter session logs, and so on. Therefore, A and C are the correct answers. B and D are not valid standard roles for EAM Owner or EAM Controller, as they are related to other scenarios, such as Internal Audit Management or Super User Management User. Reference: 2 https://help.sap.com/doc/e2ccae7ee6354b169cf845cd665e07fe/1.0%202016-07/en-US/frameset.htm?frameset.htm

According to the SAP blog, you need to assign a package to the application before you generate a BRFplus routing rule for MSMP process ID SAP_GRAC_ACCESS_REQUEST using transaction GRFNMW_DEV_RULES. This ensures that your rule is transportable and can be moved across different systems.

According to the SAP Help Portal3, you can incorporate and enforce three actions in a role methodology in Business Role Management: derivation, testing, and certification. Derivation is an action that allows you to create derived roles based on reference roles using predefined criteria. Testing is an action that allows you to test business roles for functionality and risk analysis using predefined test cases. Certification is an action that allows you to certify business roles for compliance using predefined certification campaigns.