Access Control with ConsoleWorks
By Tom Kearns 
When it comes to security, ConsoleWorks offers many unique features to ensure consistent security practices across the entire IT infrastructure, including robust Access Control capabilities using a role-based/task-based permissions model.
Privileged users should be able to access only those interfaces needed to perform their work. Role-based access and control in the IT foundation ensures that interfaces cannot be accessed without permission. Users only see the interfaces assigned to them.
ConsoleWorks provides advanced role-based access and control capabilities with LDAP integrations for fine-grained control of access rights and privileges across all managed connections. Access Control Rules enable administrators more granular and graduated control over what specific users can do inside ConsoleWorks and how they can use ConsoleWorks to access and interact with managed assets.
In ConsoleWorks 4.6, the permissions model has been completely re-engineered. Significant enhancements have been made with new capabilities that allow very granular control over what any one person is allowed to do in ConsoleWorks, particularly with separation of duties. Read more about Access Control in the latest version of ConsoleWorks here: Permissions Model in ConsoleWorks 4.6
The ConsoleWorks Difference
By Pam Johnson 
ConsoleWorks® is the leading IT foundation management solution on the market. The ConsoleWorks Server is the high-performance engine that handles information flow processing, business rule execution, pattern-matching, role-based security, and signed log-file generation. It handles all input and output across the enterprise on the devices and application that it manages, serving this data up as needed.
ConsoleWorks is capable of managing more than 1000 connections per server invocation. The ConsoleWorks Server is a complete solution package for managing the IT foundation of the enterprise.
Some of the key features of ConsoleWorks include role-based access and control, secure remote management and monitoring, in-band and out-of-band management, bi-directional data capture, digitally signed logs and forensic files, and comprehensive automation. ConsoleWorks is also agentless and persistent to facilitate IT operations, enforce security, and maintain comprehensive audit trails.
For more information, read The ConsoleWorks® Difference
Change Management with ConsoleWorks
By Pam Johnson
One of the biggest compliance challenges organizations must address is documenting the actions of privileged users. But this challenge often falls into the change management bucket as well. When implementing organizational change, documentation is key in ensuring that things are going according to plan.
Unfortunately, traditional change management often requires privileged users to manually document their activity. This practice fails to meet one of the primary goals of change management – to minimize the impact of organizational change on workers. Not to mention the margin for error – missing records, inaccuracies, and inconsistencies will exist in this scenario.
Fortunately, ConsoleWorks solves this problem. By sitting between privileged users and privileged interfaces, ConsoleWorks can capture every keystroke of privileged users and automatically produce digitally signed records. This eliminates the need for manual documentation, and provides an accurate way to verify practices across the entire IT foundation.
ConsoleWorks can also be used to directly enforce policies with real-time control capabilities. Privileged user activity is captured in real-time and can be scanned for out-of-policy activity. Control capabilities range from generating an email or text message to programmatically terminating a user session.
Tags
Access Control Audit Automation Best Practice Change Management Compliance Configuration Configuration Ports Cyber Asset Cyber Security Detect Event Detection Event Lifecycle Management Events Forensic Records Healthcare HIPAA IEM Isolate IT Foundation IT Infrastructure IT Operations Log Files Monitoring MTTR NERC-CIP Out-of-Band Patching Patterns PCI Persistence Privileged Interfaces Privileged User Real-Time Records Remediation ROI Root Cause Security Security Risk Simplifying Work Solaris System Administrators Utilities Virtual Machine-
More Blog Posts
-
By Terry Schurter I’m a big fan of the Matrix movies with Neo as the ONE and agents as the overseers in the programmed world
-
By Pam Johnson With version 5, the proposed NERC CIP standards have adopted new content in a number of areas. One of those areas is
-
By Pam Johnson CIP-005-4 is focused on Electronic Security Perimeter(s). Section R3 is titled “Monitoring Electronic Access” and is further defined as: R3. Monitoring Electronic
-
