Secure logging - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

Share may include detailed replicated transaction data in messages displayed in Listener logs, Kernel logs, the Console logs and MonCon logs, when errors occur or the SQLDEBUG option is turned on. This data may include names, addresses, social security numbers and other information that could be regarded as sensitive.

You can secure your data from unauthorized access by preventing sensitive data from appearing in logs or on the terminal screen. By default, the Secure Logging option is not enabled. The Secure Logging option will only allow the SQLDEBUG option to be turned on when Secure Logging has been deactivated in the kernel by a user with administrator privileges.

1. To enable the Secure Logging option in the model:

   1. Navigate to the Model security section of the Model Properties dialog.

   2. Enable model security. This is a required action for the Secure Logging option.

   3. Provide a User id and Password for the model. Adding an administrative user will allow you to temporarily enable or disable Secure Logging while the kernels are running.

2. To enable and disable the Secure Logging option when the kernel is running:

   1. Once the Secure Logging option is enabled in the model, then the kernel will start in Secure Logging mode.

      You can temporarily disable Secure Logging once the kernel has started. This can only be accomplished if you load the model with the Connece CDC Console client, and log into the model with administrator privileges. Use the following command:

      Command> SetSecureLogging [ON|OFF] [host] [host] ...

      This command:

      • Sets the logging of user data to ON or OFF.

      • If no host is specified, or an asterisk (*) is entered for the host, then all hosts in the model will have the action applied.

   2. Once the Secure Logging option is disabled, the administrator will have permissions to turn on the SQLDEBUG option.

If you attempt to turn on the SQLDEBUG option without turning off Secure Logging then the following message displays:

“Kernel-Could not turn SQL debugging ON because Secure Logging is currently in force”

If you attempt to enable or disable the Secure Logging option without sufficient privileges, the following message displays:

“You do not have sufficient privileges to execute the command: SETSECURELOGGING with this model.”