By default, the TCP/IP network provider initializes with TCP/IP end system security
-
Enabled (if TCPIPSECURITY has been correctly SLed)
-
Disabled (if TCPIPSECURITY has not been SLed)
If TCP/IP end system security is enabled, the default rules file is *SYSTEM/TCPIPSECURITY/RULES.
You can enter commands in the TCP/IP initialization file to enable or disable TCP/IP end system security or to reload a specific (non-default) rules file.
As soon as TCP/IP end system security becomes enabled (at startup or by the OI command), a secure environment is established and no TCP/IP activity can occur unless explicitly allowed by a rule. Therefore, conditions such as an unloaded, invalid, or nonexistent rules file can completely, and unexpectedly, disable your TCP/IP environment. For additional information, see Verifying That TCP/IP End System Security Is Operable.
| Note: | The *SYSTEM/TCPIPSECURITY/RULES file is factory-configured to allow all TCP/IP requests. Therefore, the first TCP/IP default state is equivalent to running with security disabled. Unisys recommends that you update *SYSTEM/TCPIPSECURITY/RULES to include your primary set of security rules. This will enable a default initialization into your primary TCP/IP end system security environment. |
