iSecurity Command provides total control over system & user defined CL commands, regardless of how the CL command was entered. Command provides the ability to control CL commands, their parameters, origin, context (i.e. the program which initiated the CL command), the user issuing the CL command, etc., and provides easy-to-define ways to react to these situations.
CL commands control nearly all IBM i functionality. As such, monitoring, controlling and logging CL commands is essential for both the on-going functioning of the company as well as to comply with regulations such as SOX, HIPAA, PCI and auditor-mandated policies.
A minor change in a CL command parameter can cause severe damage, yet it is difficult to control the use of CL commands and their parameters.
CL commands are entered in different ways: from the CL command line, by selecting an option from a menu, as part of a program, via FTP and more.
Unauthorized and uncontrolled use of CL commands and its parameters pose a major corporate risk. Companies and their auditors require greater control of CL commands.
During CL command processing, Command can:
And, as Command is totally integrated into the infrastructure of products in the iSecurity suite, it can send real-time alerts as event-specific e-mails or SMS, Syslog, Twitter and other forms of messages. Command can even trigger the execution of a CL script.
The structure of CL command parameters can be complex; for example, some of the Change User Profile (CHGUSRPRF) parameters are:
To properly analyze a CL command parameter, accurate referral is required. Command is the only product that has the ability to refer, for analysis or change, to each part of a complex parameter separately, as well as to the parameter as a whole. Command includes a variety of selection criteria which enable replacing, adding or removing qualifiers, elements and list elements!
The software is available for a FREE Proof of Concept evaluation, for more details email [email protected] or call +61-3 9572-5869