Network World
Friday, February 10, 2012
DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools
Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

OPSWAT, security vendor to the security vendors

Related links

Security Notes RSS feed

E-mail Ellen Messmer

Security Notes archive.

Security forum
Discuss Security Notes and other Security topics.


San Francisco-based OPSWAT, founded by Benny Czarny four years ago, is a small firm comprised of a few software engineers doing a lot of detail work in network-access control on behalf of much larger security vendors. In that role, OPSWAT has turned out to be a neutral party among the many vendors now supporting the network-access control security technologies from either Microsoft, Cisco, or both.

Network-access control is commonly defined as policy-based methods for deciding what users are to be allowed onto the corporate network, generally after determining that anti-virus, VPN, patch management or other security-related procedures are in order.

As consultant Joel Snyder recently wrote in Network World, there is a formidible competition for NAC right now, with Cisco's Network Admission Control (NAC) program and Microsoft's Network Access Protection (NAP) being among the most discussed, with vendors often supporting one or both.

Czarny, whose company we profile this week,
says his firm is a member of both Cisco NAC and Microsoft NAP. Czarny's own view is that everyone, vendors and customers alike, would benefit if both initiatives came together.

"The NAC and NAP camps basically use the same tools to see if a machine is clean or not," Czarny points out.

The only significant difference between the Microsoft and Cisco specifications for endpoint security is that for the equipment contact point, Microsoft wants you to communicate with Radius servers while Cisco's focus is on edge devices, Czarny said.

"It really makes sense for NAC and NAP to join forces," Czarny noted.

Microsoft and Cisco continue to hold out the chance that could happen, and customers might want to ask them why it hasn't yet.

Back to Security Notes

Comments

Post a comment

Name:


E-mail address:


URL:


Comments:


Remember info?