Consul Insight zLock

Consul Insight zLock's architecture comprised several key components designed to enforce security policies on RACF commands within a z/OS environment. The core components included a policy engine, command interceptors, and configuration files. The policy engine was responsible for processing security rules defined by administrators.

These rules dictated which RACF commands were allowed, denied, or modified based on various criteria such as user ID, terminal, or command parameters. Command interceptors were the mechanisms that monitored and intercepted RACF commands as they were issued. These interceptors would then pass the commands to the policy engine for validation.

Configuration files, typically in a proprietary format, stored the security policies. Administrators used these files to define the rules that governed command execution. The communication between components was primarily internal, with command interceptors interacting with the policy engine to validate commands.

There were no external APIs. The product did not use any databases or external storage mechanisms. The product operated within the z/OS environment, and its network requirements were minimal, primarily relying on internal communication within the mainframe.

The product was replaced by Tivoli zSecure Command Verifier, Tivoli zSecure Alert, and Tivoli Compliance Insight Manager Enabler. These replacements offer similar functionality with enhanced features and integration within the z/OS security ecosystem. Migration involves transitioning from Consul Insight zLock's command verification and security policy enforcement to the capabilities provided by the replacement products.