WordPress database error: [Duplicate entry '62552' for key 1]
INSERT INTO wp_bas_visitors (visit_ip, referer, osystem, useragent, lasthere) VALUES (644300604, 1, 745, 3655, '2008-10-11 19:50:48');

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND referer = referer_id AND osystem = os_id AND useragent = ua_]
SELECT * FROM wp_bas_visitors, wp_bas_refer, wp_bas_ua, wp_bas_os WHERE visit_id = AND referer = referer_id AND osystem = os_id AND useragent = ua_id

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' '2008-10-11 19:50:48', 0, 6879)' at line 1]
INSERT INTO wp_bas_log (visit, stamp, outbound, page) VALUES (, '2008-10-11 19:50:48', 0, 6879);

The Sys-Security Group » Blog Archive » NAC Agents – Not The Solution To Look For
« NAC deployment must be complete
Virtualization: The Enemy of Most NAC Solutions »

NAC Agents – Not The Solution To Look For

I have been speaking about this for some time now - a NAC solution that relies on agents is a solution, which would be bound to fail in deployment. The problem is more emphasized on large-scale deployments.

I can count several reasons like the problem of identifying all the elements that the agent needs to be installed on (organizations do not know what they have on the network as is. …And most of the NAC vendors do not know that to…), the NAC agent is one among many other agents that may already be installed on the element, a performance impact that may result from the agent, management overhead, and the fact that the agent is a target for a security breach.

Seems like I am not alone talking against the NAC agent approach. Tim Green of Network World published in his newsletter an article about issues with NAC agents.

This entry was posted on Tuesday, March 18th, 2008 at 9:54 pm and is filed under NAC, Security. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply

You must be logged in to post a comment.