IPLocks Suite

Keeping Data Safe

IPLocks mission is to Keep Data Safe. IPLocks was designed to meet the challenge of data security in enterprise environments. IPLocks prevention and detection measures are often used to support compliance, security, and privacy initiatives.

Thieves focus on databases, why don’t you?

Historically, security measures have been network-centric. Firewalls to stop external threats are a great example. But research shows that the lion’s share of threats are internal – even the best firewall won’t help stop these threats. Worse, internal threats often aren’t sophisticated hacks, they are normal users abusing their privileges!

Patented, Award-Winning Software to the Rescue.

IPLocks can stop data theft in its tracks. IPLocks approach divides data safety into a three step approach:

Harden Databases
Monitor Activity
Analyze Audit Data

Unlike many competing products, IPLocks can provide full prevention and detection benefits and be “application-safe”, allowing production applications to run unaltered and without introducing new points of failure.

Compare IPLocks to network-based products. Here are a couple of examples which highlight the risk, incompleteness and inaccuracy, and costs that can occur with network-centric products:

Claim: Network-based products provide full functionality without adding points of failure.
Database-oriented network products can’t do both at the same time. In passive mode, which relies on port-forwarding, network sniffers are safe, but have limited functionality. One of their key benefits, Intrusion Prevention, is unavailable in passive mode. The alternative is to install the network sniffer in-line, which adds a new point-of-failure to applications.

Network-based products give you a choice -- get partial functionality at full price or put production applications at risk.
Claim: Network-based products claim to capture all database events required for auditing and compliance programs.
Network sniffers can miss entire classes of database statements. Network sniffers look at the text of commands going to the database, so they can recognize standard SQL statements such as SELECT, INSERT, GRANT, REVOKE, etc. But, network sniffers are clueless as to the impact of stored procedures. A network sniffer can’t tell if the stored procedure “sp_ignoreme” is deleting every transaction in your order entry table or modifying user privileges.

Incomplete and inaccurate information compromises both compliance and security.