There's a new wave of Antivirus solutions coming our way; at least in the corporate world, which promise to deliver ways to stop hacking in it's tracks.
I'm curious what exactly DLP appliances that attach to network core switches and respective Antivirus agents with DLP plugins (on workstations) can and can't do.
For example, McAfee Prevent DLP product and other sister products:
http://www.ndm.net/dlp/McAfee/mcafee-dlp-prevent
Wording like that can even make an innocent ✌ grey-hat hacker nervous; who is probably just SSL tunneling into their home web server.
I would be curious to know how much marketing is behind these products; and, if they can "hack the hacker" by tracking a user's behavior each day; looking for:
- If a user is using SSL to get through to their home web server for extended periods.
- If a user is running a socks proxy on their workstation or forwarding ports on localhost
- Or, maybe even a legitimate MITM attack to see what's in that SSL connection.
Not sure what methods can at least protect the user's privacy a little; by at least feeling they can save files or have local TCP ports open on a workstation without detecting the type of server listening on localhost (socks, http, etc); even if on uncommon ports (stuff like what nmap does).
I'm curious what exactly DLP appliances that attach to network core switches and respective Antivirus agents with DLP plugins (on workstations) can and can't do.
For example, McAfee Prevent DLP product and other sister products:
http://www.ndm.net/dlp/McAfee/mcafee-dlp-prevent
Wording like that can even make an innocent ✌ grey-hat hacker nervous; who is probably just SSL tunneling into their home web server.
I would be curious to know how much marketing is behind these products; and, if they can "hack the hacker" by tracking a user's behavior each day; looking for:
- If a user is using SSL to get through to their home web server for extended periods.
- If a user is running a socks proxy on their workstation or forwarding ports on localhost
- Or, maybe even a legitimate MITM attack to see what's in that SSL connection.
Not sure what methods can at least protect the user's privacy a little; by at least feeling they can save files or have local TCP ports open on a workstation without detecting the type of server listening on localhost (socks, http, etc); even if on uncommon ports (stuff like what nmap does).

