Important Updates to Cybersecurity Software
HelpSystems is updating the names of our cybersecurity software, including the Powertech product line. Don’t worry—the functionality of your products won’t change.
See the new names here > New, Clearer Names for HelpSystems Security Software.
Please review the following information before installing Command Security.
Note: When installing Command Security in an HA environment:
Command Security requires that you enter a valid license key. Contact [email protected] if you need to request a new license key.
Command Security requires the following:
Note: During installation an FTP connection is initiated. The FTP server responds with messages that prompt for FTP login credentials. The standard port reserved to establish an FTP connection to the IBM i is port 21. Consequently, it is required that this port is open and ‘listening’ on the server in order to establish a connection with the Installation Wizard and facilitate a successful installation.
If FTP is not available, you must install the product manually. See Manual Installation of Powertech IBM i Products.
It is Powertech’s goal not to change system values on customer systems because we recognize that security-conscious organizations have rigorous change control processes in place for even small changes to system values. Therefore, we ask you to make any system value changes that are needed. However, the Command Security installation process could change a system value to allow the install to proceed if a system value is not set as specified below. If the Installation Wizard changes a system value during install, it changes it back to its original value when the install completes. If the installation wizard cannot make the change due to other security settings, the administrator will be expected to locate and manually make the change required.
To install Powertech Command Security on your system, the following system values that control object restores must be configured as shown.
The Command Security installation process is completely automated.
Ensure the following servers are available and running prior to installation:
Do the following to install Command Security:
Note: Make sure the user profile is a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ, *SECADM, *JOBCTL, *IOSYSCFG, and *AUDIT. The user profile should have Limit capabilities set to *NO.
The installation process displays the job log name, user, and job log number. Use the WRKSPLF command to display the job log for complete information on the Command Security install.
Command Security installs the following product libraries, user profiles, authorization list, and command on your system. It also creates the PTWRKMGT subsystem if it doesn’t already exist and adds a job queue entry to the subsystem.
Installed on System | Description |
---|---|
Product Libraries |
PTCSLIB |
User Profiles |
|
Authorization Lists |
PTADMIN |
Command |
WRKPTCS |
Subsystem |
PTWRKMGT The subsystem is created at install if it doesn’t already exist on the system |
Job queue entry |
PCSJOBQ Added to PTWRKMGT subsystem. |
To start Command Security, enter the following command:
PTCSLIB/WRKPTCS
Note: The Command Security Administrator's Guide can be found at Powertech Product Manuals.
Still have questions? We can help. Submit a case to Technical Support.