Our customers wanted more flexibility and improved access control in reporting outputs, and ConsoleWorks version 4.7 delivers.
ConsoleWorks 4.7 enables greater granularity when defining reports for most any object in the product, allowing the user to select the relevant or desired information for reporting purposes. Report output retention can also be configured to retain any number of report runs, which can be used to comply with regulations that require maintaining historical configuration records. These report outputs can be defined to any depth that may be required for historical reference.
Configuration reports now leverage the same granular permissions model introduced with ConsoleWorks version 4.6, so that access to reports is managed using role-based control access capabilities. Profiles can be customized and defined to view or run reports regarding assets that are not accessible to that profile, such as allowing an auditor to view reports but not interact with an asset.
With ConsoleWorks 4.7, reports can be scheduled to run on a periodic basis using the same scheduling mechanism now available as Baseline Configuration Management. Existing ConsoleWorks reports are automatically upgraded to version 4.7.
For more information on the new capabilities of ConsoleWorks 4.7, check out this recording of the “ConsoleWorks 4.7 – What’s New” webinar.
The recent release of ConsoleWorks Version 4.7 includes a number of new and improved features, including new functionality added to ConsoleWorks Privileged Access Management, Monitoring, and Logging Platform for ensuring auditable security-centered operations of heterogeneous IT environments.
Today I want to talk about the ConsoleWorks Baseline Configuration Management solution. This solution automates the collection of device configurations, allowing administrators to define a master baseline. The current configuration, which can be checked manually or scheduled, is automatically compared to the master – if there are any changes, administrators are automatically alerted. This new feature eliminates the majority of human errors and minimizes the impact of both intentional and unintentional erroneous activity.
The ConsoleWorks Baseline Configuration Management solution addresses key security regulations pertaining to notification of device configuration changes. It can be configured to monitor active ports, services enabled, account & account permissions, installed software & patches, configuration files, and more. Of course, everything that’s monitored is also logged, providing records of changes to the defined baselines that can be used in the event of an audit.
For more information and to see the new Baseline Configuration Management solution in action, check out this recording of the “ConsoleWorks 4.7 – What’s New” webinar.
In the most comprehensive implementations, ConsoleWorks is the single pane of glass for managing and helping to integrate the foundation of the IT enterprise.
To support these robust implementations, ConsoleWorks has an enormous amount of flexibility for managing the standard IT hardware devices and applications, and also enabling less common devices to be brought under the same management environment through its integration capabilities.
In addition, ConsoleWorks provides a number of methods that enable the product to be adapted to the specific IT enterprise requirements for the day-to-day security and management of hardware, virtual machines, and applications.
All of these advanced capabilities help to integrate ConsoleWorks into the tools, processes, and requirements of our customers rather than forcing our customers’ processes to work with the product. Some of these capabilities relate to:
- Intelligent Event Modules (IEMs)
- Controlled Automation
- Command Control
- Expect-Lite Routines
For more information on the flexibility of ConsoleWorks, read The ConsoleWorks® Difference – Flexibility of Enterprise-Wide Integration