Network World

research center:

Security

Search / DocFinder:
Advanced search
Research Centers
Vendor Solutions
Site Resources
Special Issues

Signature SeriesEnterprise All-Stars
Enterprise All-Stars NEW

You in action
You in action

New Data Center The New Data Center: Wireless & Mobility
Wireless & Mobility NEW

The New Data Center: Server Virtualization
Server Virtualization

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.

OCSP (Online Certificate Status Protocol)

An IETF standard for checking the validity of digital certificates in an X.509 PKI authentication system.

Under OSCP, issued certificates carry an OCSP "authority identifier" field. Certificate applications use OCSP "requestor" software to request status from an OCSP "responder."

The goal is to provide a more efficient way of distributing certificate authentication information than an earlier method in which a potentially large "certificate revocation list" was periodically posted to the network - and downloaded by clients on the network.

When an OSCP-enabled certificate is presented to a security application, such as a Web browser during initiation of an SSL session, the software checks the certificate to make sure it is valid before the associated operation can proceed. The certificate contains control information to show when it is valid (start and end time) and, optionally, address information to access a CRL or an OCSP responder. The certificate-processing software - the browser or other application - can use an OCSP responder it has been configured for, or the one listed in the certificate, to check the status.

The process of checking a certificate's status has always been part of the design of certificate infrastructures. It was there to allow for revocation, to ensure that the identity information represented by a certificate is valid at the time the certificate is used. Historically, because CRLs were hard to use, this part of the design was omitted from early deployments. Now that OCSP is a standard, and now that vendors such as CoreStreet, RSA, VeriSign and others support OCSP, it makes sense to start upgrading your certificate infrastructure to add certificate-status-checking capability. This does require OCSP support in the security systems that use it, including browsers and other software, but most modern Certificate Authority products support OCSP, and there are OCSP add-on tools to provide requestors.

From http://www.nwfusion.com/reviews/2004/0809revside.html">Fitting OCSP into your Certificate Infrastructure, Network World, 08/09/04.

Additional resources

RFC 2560
Defines OCSP.

CoreStreet scales digital certificates
We test an OCSP certificate system. Network World, 08/09/04.

Security research center
Latest security news, analysis and resource links.


Add a comment

NOTE: Comments are reviewed by an editor before being posted.

Your rating of this resource (with 5 the best)
1 2 3 4 5

Subject:

Your user name (what other users will see on the review):

Your real name (for our records only):

Your e-mail (ditto):

Your comments (Use a blank line to separate paragraphs):

TOP STORIES

Newsletters
Sign up for one of NWW's Network Security newsletters.

Security in Practice
Virus and Bug Patch Alert
Security Strategies
Security News Alert
VPNs
Messaging
View all newsletters

Email Address:

Vendor Solutions

White Papers

What Developers Want: The End of Application Redeploys
- Zero Turnaround

More...


Research Centers: Applications | Application Development | Applications-Standards | Applications Vendor Solutions | Collaboration | CRM / ERP | Databases | Directories | Grid Computing | Java | Messaging | .Net | RFID | SOAP | Web Services | XML | Convergence & VoIP | Convergence Regulatory | Convergence Services | Convergence Standards | Convergence VoIP Vendor Solutions | Video | IP PBX | SIP | VoIP | VoIP Services | E-Business | DNS | RFID | Supply Chain | Web security LANs & Routers | Acceleration | Gigabit Ethernet | Lans-Standards | Routers | Wireless LANs | Network Management | Application Management | Desktop Management | Management Test Patch Management | Operating Systems | Linux | NetWare | Unix | Windows Outsourcing | Managed Services | Offshoring Security | Firewalls - VPN - Intrusion | Identity management | Patch Management | Microsoft Security | Privacy | Security Standards | Spam & Phishing | Viruses & worms | Web Security | Wireless Security | Servers & Desktop | Backup-Recovery | DataCenter | Desktops | Desktop Management | Grid | Servers | Server Blades | Servers Desktops | Utility Computing | Small & Medium Business | Broadband | Telework | Handhelds & PDAs | Home Networking | Security | Storage | Compliance | Infiniband | Network-Attached Storage | SANs | Storage Management | Storage Virtualization | Virtualization | Vendor News | Bankruptcy | Earnings | Lawsuits | Layoffs | Standards | Start Ups | Vendor Markets | Education | Financial | Healthcare | HIPAA | Manufacturing | Retail | Wide Area Network | Broadband | Carriers | Frame Relay | Metro Ethernet | MPLS | Service providers | Wireless services | Wireless & Mobile | Wireless LANs | PDAs & handhelds | Wireless Security | Wireless Services | Wireless Standards | Wireless Switches | All Company Profiles