Reconnex's iGuard 2600 allows for powerful forensic searching of past network data, without the higher cost associated with its big brother, the iGuard 3600. The device monitors your network to find potential leaks.
Sensitive data must be tracked no matter where it is on the network. Content-monitoring devices detect specific data types as they move along, and send alerts when sensitive data leaves the network through e-mail, Web forms, file sharing or chat sessions.
IGuard's ability to capture and retain data as it travels is extremely useful for investigating potential leaks. Its protocol analysis is strong and the user interface is extremely well-laid-out for both simple quick access to high level data and in-depth technical analysis. Beware, however, that the process may subject the enterprise to certain legal consequences.
Early content-monitoring packages helped keep spam and porn from entering the network. That same technology now tracks Social Security numbers and other sensitive data that could leave you equally vulnerable when it leaves your network.
Reconnex's iGuard 2600 appliance is the latest evolution of this content-monitoring technology. When iGuard was introduced two years ago, it monitored and recorded network traffic that could violate any number of policies, and stored that traffic on a terabyte drive array. The iGuard 2600 makes that same technology available to organizations that don't need the flagship model's terabyte of storage or high-end, high-availability features, such as hot failover. The 2600 holds 400 GB of data and has a simplified set of built-in policies that focus primarily on privacy data and compliance.
IGuard doesn't actively block the potential data leaks, but its broad capture and logging capabilities are suited for in-depth analysis of traffic and incident investigation. That's useful for finding the people behind the problems--a different, but no less important, task. In contrast, products such as Fidelis' XPS attempt to stop traffic that violates a set of rules.
Problem solving vs. Prevention
Click to enlarge in another window