|
Tembria Server Monitor Menu
= Introduction and Overview= 100% Agentless Monitoring = Screenshots and Videos = Dashboards = Event Monitors = Notifications = System Requirements = Download Now Step-by-Step Evaluation
= Installation= Adding Network Devices = Adding Event Monitors = Sending Notifications = Viewing Dashboards = Viewing Reports = Advanced Topics Resources
= Pricing and How to Order= Scenarios = 1. Monitoring Critical Servers = 2. Finding Bandwidth Hogs = 3. Detecting Rogue Machines = 4. Monitoring Event Logs = 5. Monitoring Through VPNs = 6. Monitoring Through Firewalls = 7. Monitoring Switches w/ SNMP = FAQs = Version History |
Tembria Server Monitor - Detecting Rogue MachinesScenario Summary: Tembria's Rogue Machine event monitor was used to continually watch for machines connecting to the network without permission. Scenario 3: Detecting Rogue Machines After much effort tracing odd network events, it was finally discovered that a contractor had brought their own laptop with them and connected it to the network without permission. To have advance warning of this the next time, the customer used Tembria Server Monitor to perform periodic scans looking for machines that have connected to the network without permission. The following week Tembria Server Monitor warned that it found a new unrecognized machine on the network. The host name was close to that of a newly hired employee and contacting the employee revealed that they had re-installed Windows on the machine because it was acting strangely. Company policy is that all re-installs are done by the IT department in order to ensure that all patches and company authorized software is installed. Soon after, warnings appeared again indicated the presence of new machines on the network. The machine names and IP addresses were traced to the company's quality assurance department where it was found that employees were experimenting with software that allows multiple virtual machines to run on one physical machine. The virtual machines had unpatched installations of various versions of Windows which represented a substantial security risk. This led to the adoption of corporate policies to establish the safe use of virtual machine software within the organization. Back to Scenarios List |
|
| copyright(c) 2003-2008, all rights reserved | ||