haven SAP Security
Browse knowledge
Knowledge base
RFCGW / SECURITY BASELINE

Gateway registration, startup and proxy

Restrict connections to external RFC servers and disable simulation after rollout.

Risk

Overly permissive ACLs allow unauthorized registrations and access to external programs.

ABAPJavaStandalone Gateway

Settings and priorities

Technology / priorityParameter or mechanismSetting and purpose
ABAP
Critical
secinfo ; reginfoMaintained ACLs without allow-all rules
Permit only expected sources.
ABAP
Critical
gw/sec_info ; gw/reg_infoCorrect ACL file paths
Verify that every instance loads the files.
ABAP
Critical
gw/reg_no_conn_infoRecommended 255
From kernel 7.40, use an odd value; older kernels require the relevant bits.
ABAP
Critical
gw/acl_mode1
Enables the Initial Security Environment.
ABAP
Critical
gw/monitor1
Allows local monitoring only.
ABAP
Critical
gw/sim_mode0 in the target configuration
Enforces controls instead of only simulating them.
ABAP
Extended
gw/rem_startDISABLED or SSH_SHELL
Controls the method used to start programs.
ABAP
Extended
gw/acl_mode_proxy ; gw/prxy_info1 and a maintained prxyinfo file
Restricts RFC proxy according to kernel requirements.
Java
Critical
RFC Gateway ACLs and operating modeApply the same Critical requirements as ABAP
Protects the Gateway in a Java system.
Standalone Gateway
Critical
RFC Gateway ACLs and operating modeApply the same Critical requirements as ABAP
Protects standalone Gateway installations.

How to verify

  1. Confirm ACL rules and file paths on every instance.
  2. Check bit settings for the installed kernel.
  3. Disable simulation after testing.
  4. Verify registration, startup and proxy use.

Related topics

RFC · RFC Gateway and ACLs ↗

Authentication and communication ↗

Baseline priorities and implementation ↗