Security expectations and requirements are a reality for every business. Here at TDi Technologies, our software engineers work hard to ensure that ConsoleWorks meets or exceeds all of the security needs of our customers and prospects.
Since the release of ConsoleWorks Version 4.6 last year, we’ve introduced a number of changes to ConsoleWorks that improve our Security capabilities. These changes include:
- Improved security of CWClient (CWterm) when used in Actions by improving the Authorization method.
- Reduced vulnerabilities between the server and User Interface and between the server and monitored devices by staying current with SSL and SSH security patches.
- Added visibility within the User Interface of last successful login and any failed login attempts.
- Allowed administrators to set the minimum password length to as long as 32 characters.
- Added a new Windows Event Forwarder (WEF) that uses an encrypted and authenticated connection between the server and Windows systems rather than the unencrypted syslog connection of the past.
- Added new password security controls to meet US Government and other requirements, including: Inactive Password Expiration, Minimum Time Between Password Changes, and Login Lockout after a specified number of failed login attempts.
TDi Technologies uses industry standard development methods including required coding reviews to ensure that new software vulnerabilities are not introduced during the development process. They monitor many sources of information concerning software vulnerabilities and attacks and act to change ConsoleWorks when the need arises.
Requests and inquiries concerning security and ConsoleWorks are given every consideration and almost always result in changes that meet our customers’ needs, especially when related to security standards such as NIST, SOX, NERC CIP, and HIPAA.
If you have any questions concerning ConsoleWorks security please contact Support at Support@TDiTechnologies.com
Virtually all computers, networks, and similar devices have a communication port through which they send boot and status messages. Usually, this console information is lost because it is impractical to monitor and respond to the geographically scattered computing infrastructures common in modern-day businesses.
ConsoleWorks puts an end to this data loss. It monitors information coming from all parts of a networked environment, and, in real time, extracts key events and notifies support staff. ConsoleWorks brings all of the once-discarded console information, status updates, error messages, and anything else in the data stream to a single web-enabled server, scans the data, and responds intelligently.
Furthermore, ConsoleWorks remains fully functional in all modes, including single user, standby, and failure modes. By monitoring and logging consistently and constantly, not just under normal operating conditions, ConsoleWorks also meets the most stringent of compliance practices.
For more information on device monitoring, read The ConsoleWorks® Difference For Monitoring & Management.
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