One connection, multiple trust boundaries
The client initiates communication and the server executes a function. The destination defines the connection and logon method, while the Gateway handles RFC communication. Controls across these layers complement one another.
RFC destinations
Organize SM59 connections and reduce privilege escalation risk.
Trusted RFC
Control the direction of trust and the ability to log on as another user.
Encryption and SNC
Protect partner identities, data integrity and connection confidentiality.
S_RFC and role maintenance
Replace broad privileges with roles based on actual RFC execution.
UCON: reducing remote exposure
Expose only the RFC modules required by business processes.
SACF: switchable authorization checks
Introduce additional checks after assessing their impact on users.
RFC client-side controls
Restrict who can use destinations containing stored credentials.
RFC callback
Control return calls executed with the initiating user’s privileges.
RFC Gateway and ACLs
Separate registration, startup, proxy and network access controls.
RFC security monitoring
Detect configuration drift across the integration landscape.
From discovery to enforcement
- Inventory. Identify destination owners, trust directions and required scenarios.
- Observe. Collect traces and UCON, callback and Gateway logs across business cycles.
- Design. Prepare roles, allowlists, ACLs and transport protection.
- Test and activate. Use available simulation modes, adjust rules and enforce controls.
- Monitor. Detect drift and repeat the assessment after system changes.
Assess impact and test integrations before enforcing restrictions.