Making Security Settings for External Programs 
To ensure the SAP gateway operates securely, you have to be especially aware of interaction with external programs. You can configure the gateway to ensure that undesirable external programs cannot be run.
To make sure SAP programs required for system operation are not blocked by an overly restrictive configuration, we recommend you run gateway logging in order to identify these programs, and then define the configuration files secinfo and reginfo accordingly.
Procedure
Set up gateway logging by setting the following parameters in the profile:
gw/sec_info = $(DIR_DATA)/secinfo
gw/reg_info = $(DIR_DATA)/reginfo
gw/logging = ACTION=S LOGFILE=gw_log-%y-%m%d SWITCHTF=day
NoteIf an SAP system consists of multiple application servers, add the system ID (three-letter SID) and the server name to the file name. This enables the files to be identified when they are collected centrally for analysis. You can use the environment variables $(SAPSYSTEMNAME) and $(SAPLOCALHOST) to set the parameter as follows:
gw/logging = ACTION=S LOGFILE=gw_log_$(SAPSYSTEMNAME)_$(SAPLOCALHOST)-%y%m%d SWITCHTF=day
End of the note.This logs all security-relevant gateway actions in a separate file. You can also make this setting within the system.
For more information, see: Setting Up Gateway Logging
In the $(DIR_DATA) directory, create the secinfo and reginfo files with the following contents:
secinfo contains line USER=* HOST=* TP=* only
reginfo contains line TP=* only
With this secinfo and reginfo configuration all programs can be started from the gateway, and all programs can register in the gateway.
CautionThese settings are only temporary and are intended to find out which programs are to be included in the files. While these settings are active, the gateway is not protected against external programs.
End of the caution.Activate the configuration files secinfo and reginfo by choosing
Goto 
Expert Functions External Security Read Again 
in transaction SMGW. Activate these files on every application server instance of the system. To do this, call the server overview (transaction SM51) and switch the instance by double-clicking.Leave the system running with these settings for a few days, and execute all actions that relate to external programs and registered servers.
Evaluate the log file. Proceed as described in section Evaluating the Log File.
Maintain the files secinfo and reginfo accordingly.
Activate files (see step 3.)
Leave the system running with these settings, but still monitor the logging. Pay particular attention to the entries secinfo denied and reginfo denied. These are external programs and registered servers that, based on the settings, are not allowed to be run. Possibly, a new component that requires additional external programs and registered servers is being tested or introduced. The administrator then has to decide whether these entries should be included in the security files.