Monitoring and Logging When Nothing Can Be Lost

October 17, 2012Comments Off on Monitoring and Logging When Nothing Can Be Lost

By Pam Johnson

Organizations that must meet stringent compliance standards like NERC-CIP, SOX, HIPAA, and PCI DSS may be subject to fines or even criminal actions if they don’t meet the requirements. In order to be compliant, logging and monitoring must be configured such that they are always running and monitoring everything possible, even in the case of hardware or software failure.

Unlike most technology approaches, 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 meets the most stringent of compliance practices.

Additionally, for organizations with a fault tolerant environment, one with redundancy built into the infrastructure, ConsoleWorks can be used to strengthen that redundancy.

This Redundant Automatic Failover configuration consists of two ConsoleWorks invocations, which under normal operating conditions are simultaneously connected to each managed device in the environment, making the solution fully redundant with no single point of failure. If the primary invocation fails, the secondary invocation continues to monitor and manage the enterprise.

For more information, download the free solution brief: Monitoring and Logging When Nothing Can Be Lost

About author:

Pam Johnson is the Director of Solutions Marketing for TDi Technologies in Plano, TX. Her role at TDi Technologies allows her to work with customers to learn about and help solve business problems. She received her B.S. In Engineering Technology from Cameron University and has pursued graduate courses towards an M.B.A. at the University of Texas at Dallas. Since graduation, she has held various positions in engineering, product marketing and even direct sales.

All entries by

Google Analytics Alternative