Public Key Infrastructure
Public Key Infrastructure
Public Key Infrastructure
1
This is quite important in financial transactions where someone may
wish to refuse a bill claiming that they hadn’t requested the service in
the first place. Using a system that provides non-repudiation, the
service or data provider can produce irrefutable evidence that the
request was in fact made and therefore the bill is legitimate. In a
secure system, entity authentication is required so that each user can
be satisfied that they are communicating with only the person,
corporation, or server, they wish to be communicating with. For
example, users sending their credit card number across a network to
make a purchase want to be certain that they are dealing with a
trustworthy merchant rather than a fraud who wishes to steal their
credit card number for a private spending spree. If the user verifies the
identity of the merchant, they will send their credit information with
greater confidence. Sensitive data stored on a network requires
policies to administer access rights. Access control enables an
administrator to ascertain access privileges of an entity before allowing
them access to the data, or even before verifying the existence of the
data.
Public-Key Infrastructure
2
certificate. In the digital world of the PKI a certificate is a file that
contains a user’s public key and identifying information about that
user. This identifying information is usually data such as their name,
address, phone number, etc. The creation of the digital certificates is a
process of binding the identification data to the public key data. The
CA accomplishes this by digitally signing the information with its’
private key. Before signing the certificate, the CA verifies the
information contained in it, for example by meeting the applicant in
person. This verification process is known as vetting the certificate.
Vetting or verification processes will vary according to the security
policy of the organization. Since the CA is a fundamental part of the
PKI, its public key is widely known and trusted. Once the certificate is
created it is stored in a certificate repository, the CA then distributes
copies to authorized users as required. Although all certificates are
issued with a validity period, immediate certificate revocation may also
be a necessity. Should the information reflected in the certificate
change, or if the key pair should no longer be trusted, it is the
responsibility of the CA to rescind the authority granted by the
certificate through the process of certificate revocation. Many
implementations use a Certificate Revocation List (CRL) to control
certificate revocation. Periodically the CA publishes a list the CRL of
certificates that are no longer valid within the PKI. In some cases a CRL
may be an acceptable method for certificate revocation.
There are, however, difficulties inherent in the use of a CRL that must
be accepted or overcome in a secure implementation. The CRL can
grow large over the lifespan of a PKI, as many certificates may need to
be revoked. Publishing a large list may be a problem for some limited
bandwidth systems. Sending CRL updates saves bandwidth when
updating the CRLs. In this case a full CRL is sent out periodically,
during times of lower demand on the available resources. It is also
possible to distribute a list containing the certificates revoked since the
last full publication is published.
These smaller updates keep the CRL fresher while creating less
network traffic. Another technique is to use distributed CRLs, which
spread the entire CRL over several locations so that the lists are
smaller in each place. Unfortunately smaller lists create additional
management and synchronization problems. Another issue to be
considered when using a CRL is that the data contained in the list may
be out of date as soon as it is published. A certificate is revoked
moments after a CRL or CRL update is published will be considered
valid until the next publication.
3
queries for up to date certificate revocation data. A particular response
to an OCSP query contains only the information about the certificates
in question, saving bandwidth. PKI security may also be increased
using OCSP as features may more easily applied which will ensure
strong access to the OCSP system. OCSP allows for real-time certificate
status checking supplying immediate revocation information on a given
certificate.
The Policy
Conclusion
Generally speaking PKI usage can be put into three categories:
4
• Securing communications between authenticated parties.
• Providing for authentication and data integrity in computerized
applications and making possible digital signatures, the strongest
form of electronic signature now available.