SAP security note 2026939, "Switchable Authorization Checks for RFC in IS-U", is a note. Below are the SAP recommended solution and the affected software components.
Description
Solution
The new authorization checks are delivered inactive to maintain compatibility. To activate them, follow the steps below using transaction SACF:
- Create authorization scenario definition: start transaction
SACFand check for the scenario definitionISU_CA_GETLIST. If it doesn’t exist, download the attached file ISU_CA_GETLIST.TXT and upload it viaSACF_TRANSFER. Assign the scenarioISU_CA_GETLISTto the development packageEE03. Repeat forISU_UCES_CA_GET_BANKDATAusing ISU_UCES_CA_GET_BANKDATA.TXT and assign toEWEBIAC. - Create productive authorization scenario: in transaction
SACF, select the scenario definitions and transfer them to productive scenarios. Choose the initial status: “Active” (activates authorization checks and logs to the Security Audit Log) or “Logging” (logs attempts without enforcing checks, useful for identifying required authorizations). - Activate Security Audit Log: ensure Security Audit Log is active via transaction
SM19. Create a new filter for relevant audit messages: non-critical DUO (successful authorization), DUP (failed authorization); critical DUQ (changes to authorization scenarios). - Adjust user roles: use report
RSAU_SELECT_EVENTSto identify users needing additional authorizations. Update roles accordingly to comply with the new authorization scenarios.
References
- SAP Note 2078596: Further improvements for RFC security
- SAP Note 1624291: Syntax error when implementing a security note
Affected components
- IS-UT: Versions 600, 602, 603, 604, 605, 606, 616, 617
Full note on SAP: SAP Support Launchpad note 2026939
Detailed exploitation and proof-of-concept material for this note is maintained in the RedRays Security Platform. For access, contact [email protected].
