PKI(Public Key Infrastructure) allowing use of Public Key Cryptograph and certificates is required to meet the security requirements in the open network and distributed network environment. A key task in PKI is Certificate Status Validation. Certifica...
PKI(Public Key Infrastructure) allowing use of Public Key Cryptograph and certificates is required to meet the security requirements in the open network and distributed network environment. A key task in PKI is Certificate Status Validation. Certificates can be revoked even before the validity period expires, for reasons such as changes in the certificate holder's personal data, damages to or exposure of the private key and cancellation of user authority, and they can be revoked on the expiration of the validity period.
Certificate Status Validation is an important and mandatory task for the validating party based on the PKI. Certificate validation methods under the PKI environment include the CRL(Certificate Revocation List), OCSP(On-line Certificate Status Protocol), SCVP(Simple Certificate Validation Protocol) and DVCS(Data Validation and Certification Server). CRL contains problems in that revocation information is created on a regular basis, real-time referencing is not supported, and the traffic is increased along with file sizes. Although the OCSP Server method provides real-time validation, validation process efficiency could be compromised with the increasing number of users.
Distributed OCSP server method can cause problems including distribution CRL, load on a particular server, slow validation process, and consistency and security concerns. This paper suggests ways to resolve some of the problems raised in the existing methods, using distributed OCSP server based on group, such as reducing load, maintaining consistency and receiving and transmitting data with enhanced security.
This paper proposed a model for conducting certificate validation procedures, which had been processed by a single OCSP server, by grouping a number of distributed OCSP servers. Experiments indicated that the Distributed OCSP Server based on Group method outperforms other methods in terms of traffic reduction and average service request response time. The main reason for the proposed model not yielding a better response time is the duration required for receiving certificate revocation information issued by the CA(Certification Authority) in real time.
In the proposed model, consistency is the key. All OCSP servers must have the same information at all times and CA allows all OCSP servers to use the updated information only after it receives the confirmation message from all OCSP servers.
There are a few important factors in the proposed model. First is the reduction of traffic. Traffic of all OCSP servers in the same group will be measured based on the threshold and the server with the least load will perform the validation service, thereby reducing the traffic.
Second is consistency. CA transmits the updated Updated CRL to all OCSP servers in the group and conducts the validation service only after it has received the message that the information has been received successfully by all OCSP servers.
Third is security. When CA and OCSP servers send and receive information on certificate suspension and revocation, CA uses private key for encryption and transmission, and the recipient OCSP server uses public key to decryptand validate the information, thereby ensuring the security.
Lastly, in the all or nothing method used to maintain consistency, a time gap can be created when receiving the confirmation message, depending on the status of individual OCSP servers. Due to this time gap, an OCSP server in normal operation can be disregarded or the transmitted Updated CRL can be ignored, which is an issue that needs to be further discussed.