AOL Member Security Certificate Policy Certification ... - AOL.com
AOL Member Security Certificate Policy Certification ... - AOL.com
AOL Member Security Certificate Policy Certification ... - AOL.com
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
FOR PUBLIC DISTRIBUTION<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong><br />
<strong>Certificate</strong> <strong>Policy</strong><br />
and<br />
<strong>Certification</strong> Practice Statement<br />
<strong>AOL</strong> LLC<br />
22000 <strong>AOL</strong> Way<br />
Dulles VA 20166 USA<br />
IT <strong>Security</strong> Department
© Copyright 2006 <strong>AOL</strong> LLC. All rights reserved.<br />
<strong>AOL</strong> LLC hereby permits each participant using <strong>AOL</strong>® <strong>Member</strong> <strong>Security</strong> PKI services to<br />
copy this document in its entirety as necessary in the ordinary course of acting as a<br />
participant, but not including publication in any medium, the making of any derivative<br />
work, or use in any system other than an <strong>AOL</strong>® <strong>Member</strong> <strong>Security</strong> PKI service.<br />
“Participant” is used here in the sense defined in this document.<br />
<strong>AOL</strong> and America Online are registered trademarks of <strong>AOL</strong> LLC.<br />
All trademarks, service marks, and copyrights are property of their respective owners.
Contents<br />
1. INTRODUCTION ....................................................................................................................................... 1<br />
2. CONTEXT AND COMMUNITY ............................................................................................................. 1<br />
2.1. THE <strong>AOL</strong> MEMBER SECURITY PUBLIC KEY INFRASTRUCTURE ........................................................... 1<br />
2.2. THE <strong>AOL</strong> COMMUNITY AND <strong>AOL</strong> MEMBER SECURITY PKI PARTICIPATION..................................... 2<br />
2.2.1. <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Participation ..................................................................................... 2<br />
2.2.2. PKI Roles......................................................................................................................................... 3<br />
2.2.3. <strong>AOL</strong> <strong>Certification</strong> Authorities ........................................................................................................ 3<br />
2.2.4. Applicability and Use of <strong>Certificate</strong>s............................................................................................. 3<br />
2.3. LIMITATIONS ...................................................................................................................................... 4<br />
2.3.1. Services Are For Participants Only............................................................................................... 4<br />
2.3.2. Disclaimer of Warranties and Limitation of Liability .................................................................. 4<br />
2.3.3. Enrollment Process for Non-Participants ..................................................................................... 5<br />
2.3.4. Relying Party Obligations .............................................................................................................. 5<br />
3. CERTIFICATE CONTENT AND CONFIRMATION......................................................................... 5<br />
3.1. IDENTIFYING AND AUTHENTICATING <strong>AOL</strong> MEMBER SECURITY PKI CERTIFICATES ......................... 5<br />
3.2. FORM AND CONTENT OF CERTIFICATES GENERALLY ........................................................................... 6<br />
3.3. FIELDS SUPPORTED FOR USE IN <strong>AOL</strong> MEMBER SECURITY PKI ........................................................... 7<br />
3.3.1. Fields Identifying the Subject ......................................................................................................... 7<br />
3.3.2. Fields Identifying the Issuer ........................................................................................................... 8<br />
3.3.3. Other Supported Fields................................................................................................................... 9<br />
3.4. PROFILES FOR SPECIFIC CERTIFICATE TYPES ......................................................................................11<br />
3.4.1. Device Authentication <strong>Certificate</strong>s ..............................................................................................11<br />
3.4.2. Screen Name Authentication <strong>Certificate</strong>s....................................................................................11<br />
3.4.3. Full Name Authentication <strong>Certificate</strong>s ........................................................................................12<br />
3.4.4. Basic Encryption <strong>Certificate</strong>s.......................................................................................................12<br />
3.4.5. Identification <strong>Certificate</strong>s .............................................................................................................13<br />
3.5. IDENTIFICATION AND CONFIRMATION .................................................................................................13<br />
3.5.1. Identifying Subjects.......................................................................................................................13<br />
3.5.2. Confirmation of the Factual Content of <strong>Certificate</strong>s ..................................................................14<br />
3.6. CONFIDENTIALITY AND INTELLECTUAL PROPERTY ............................................................................16<br />
3.6.1. Confidentiality of <strong>Certificate</strong> Content..........................................................................................16<br />
3.6.2. Intellectual Property Rights in <strong>Certificate</strong> Content ....................................................................16<br />
4. CERTIFICATE AND KEY PAIR LIFECYCLES...............................................................................17<br />
4.1. A CERTIFICATE AND KEY PAIR AS SEEN BY A PARTICIPATING MEMBER ..........................................17<br />
4.2. PROCESSES ............................................................................................................................................18<br />
4.2.1. Setup and Replacement of <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Capabilities.........................................18<br />
4.2.2. Expiration and Renewal of an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Capability .....................................21<br />
4.2.3. Revocation of an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Capability...........................................................22<br />
4.2.4. Timing of Verification and <strong>Certificate</strong> Invalidation ...................................................................24<br />
4.2.5. Archiving and Record Retention of <strong>Certificate</strong>s .........................................................................25<br />
4.3. KEY MANAGEMENT, DISTRIBUTION, AND RECOVERY .......................................................................25<br />
4.3.1. Public Keys and their <strong>Certificate</strong>s ...............................................................................................25<br />
4.3.2. Private Authentication Keys.........................................................................................................25<br />
4.3.3. Private Encryption Keys and their Recovery ..............................................................................26<br />
4.3.4. Private Identification Keys ...........................................................................................................26<br />
5. CERTIFICATION OPERATIONS ........................................................................................................26<br />
5.1. SECURITY AND SOUNDNESS OF OPERATIONS ......................................................................................26<br />
5.2. TERMINATION OF CA............................................................................................................................27
5.3. AUDITS ..................................................................................................................................................27<br />
6. AMENDMENT AND REVIEW OF THIS CP/CPS ............................................................................29<br />
7. MISCELLANEOUS PROVISIONS .......................................................................................................29<br />
8. GLOSSARY AND REFERENCES.........................................................................................................30<br />
8.1. DEFINITIONS..........................................................................................................................................30<br />
8.2. REFERENCES..........................................................................................................................................32<br />
8.3. LINKS.....................................................................................................................................................32<br />
APPENDIX A NATIONAL ADAPTATIONS ..............................................................................................34<br />
APPENDIX B COMPARISON TO [RFC 3647]............................................................................................. 1
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI <strong>Certificate</strong> <strong>Policy</strong> and<br />
<strong>Certification</strong> Practice Statement<br />
1. Introduction<br />
This document (termed the “CP/CPS”) is the <strong>com</strong>bined certificate policy and certification practice<br />
statement for the public key infrastructure known as <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI. <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI supports a suite of services that can enhance the level of security associated with<br />
<strong>AOL</strong>’s consumer services for <strong>Member</strong>s who choose to participate. For example, these services<br />
may include issuing certificates to <strong>Member</strong>s, certificates that can be used to authenticate access<br />
to the <strong>AOL</strong> system, or to encrypt and digitally sign electronic <strong>com</strong>munications. The <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI also provides the ability for <strong>AOL</strong> to allow participating nonmembers to access and<br />
rely on certificates issued to <strong>Member</strong>s.<br />
<strong>Certificate</strong> policies and certification practice statements are often contained in two separate<br />
documents that set the general policies governing the operation and use of a public key<br />
infrastructure, and the practices that will be utilized to conform to such policy. For simplicity, all<br />
certificate-related policies and practices relevant to <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI have been<br />
<strong>com</strong>bined in this single CP/CPS document.<br />
The <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI is a closed <strong>com</strong>munity PKI. <strong>Certificate</strong>s will only be issued by the<br />
<strong>AOL</strong>CA to participating <strong>Member</strong>s for reliance and use by participants. Because the services<br />
intended to be offered pursuant to this CP/CPS are directed to a closed <strong>com</strong>munity of <strong>AOL</strong>’s<br />
<strong>Member</strong>s and other approved participating nonmembers (section 2.3.3), the rights and<br />
responsibilities of participants using <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services will substantially be<br />
detailed in the user agreements governing access to and use of a particular service.<br />
This CP/CPS document details the general operations and practices for all <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong><br />
PKI services and provides the framework under which all certificates of the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong><br />
PKI will be created, managed and/or used by participants. But this CP/CPS must be read in<br />
conjunction with the <strong>Member</strong> Agreement, <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Addendum, and/or<br />
participating nonmember agreement applicable to a particular <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service<br />
offered by <strong>AOL</strong> in order to fully understand a participant’s rights and responsibilities. <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI services are not intended to be used or relied upon by persons who are not<br />
participants.<br />
Certain internal operational procedures relating to <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI have not been<br />
disclosed in this or other publicly released documents in order not to unnecessarily jeopardize the<br />
security of the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI.<br />
2. Context and Community<br />
2.1. The <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> Public Key Infrastructure<br />
<strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI described in this CP/CPS is an infrastructure that will allow <strong>AOL</strong> to<br />
develop and offer to <strong>Member</strong>s particular security-related products and services that make use of<br />
certificate services.<br />
Currently, certificates governed by this CP/CPS may identify the following subjects:<br />
• a device (Device Authentication <strong>Certificate</strong>);<br />
• an <strong>AOL</strong> organizational entity (<strong>AOL</strong> Identification <strong>Certificate</strong>s);<br />
• an <strong>AOL</strong> Screen Name (Screen Name Authentication <strong>Certificate</strong>);<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
• a full name (Full Name Authentication <strong>Certificate</strong>); and<br />
• encrypted messages or data streams (Basic Encryption <strong>Certificate</strong>).<br />
These certificates will be issued by the <strong>AOL</strong>CA to <strong>Member</strong>s and <strong>AOL</strong> organizations in connection<br />
with specific <strong>AOL</strong> product and/or service offerings that are not yet developed. Nevertheless, some<br />
examples of anticipated product and service offerings include the following:<br />
• Access Control: <strong>Certificate</strong>s may be installed into a small hardware device (i.e. the<br />
<strong>AOL</strong> Token) that can easily be connected to or disconnected from a participating<br />
<strong>Member</strong>’s <strong>com</strong>puter. Its functionality is essentially that of a smart card (also called<br />
a “chip card” or “integrated circuit card”). Each <strong>AOL</strong> Token has a unique identifier,<br />
namely a device serial number (Card Unique Identifier, or “CUID”). Some may also<br />
include a Device Authentication <strong>Certificate</strong>. <strong>AOL</strong> Tokens also have functionality<br />
designed to prevent tampering and permit detection of counterfeiting. An <strong>AOL</strong><br />
Token may be bound to a <strong>Member</strong>’s account or subaccount Screen Name. Once<br />
bound to a participating <strong>Member</strong>’s Screen Name and properly connected to a<br />
<strong>com</strong>puter, the <strong>AOL</strong> Token can provide additional security for a participating <strong>Member</strong><br />
when logging into the <strong>AOL</strong> system to access <strong>AOL</strong> services.<br />
• Secure Communications: <strong>Certificate</strong>s issued by the <strong>AOL</strong>CA, including those<br />
installed into an <strong>AOL</strong> Token, can also be used to encrypt and digitally sign<br />
electronic <strong>com</strong>munications, for instance, to enable a participating <strong>Member</strong> to send<br />
secure e-mail, instant messages, or other information. Encryption helps protect the<br />
confidentiality of the encrypted information, and the digital signature helps assure<br />
the authenticity of the encrypted message by enabling a recipient to detect if the<br />
message has been altered in transmission as well as attribute it to a source<br />
identified in the certificate. However, to a great extent, achieving this improved<br />
level of security depends on whether all parties to an online <strong>com</strong>munication have<br />
and use <strong>com</strong>patible security technology. Among participating <strong>Member</strong>s, that<br />
<strong>com</strong>patibility can be assured through use of the <strong>AOL</strong> system.<br />
For more information on <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI, see https://pki–info.aol.<strong>com</strong>/<strong>AOL</strong>MSPKI.<br />
Specific information about <strong>AOL</strong> security product offerings will also be available from time to time<br />
on www.aol.<strong>com</strong> as such products be<strong>com</strong>e available.<br />
2.2. The <strong>AOL</strong> Community and <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
Participation<br />
2.2.1. <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Participation<br />
<strong>AOL</strong> provides a variety of online services. Some of these services are limited to an online<br />
<strong>com</strong>munity of <strong>Member</strong>s. Such services are offered today under a variety of well-known brand<br />
names, some of which include <strong>AOL</strong> LLC, <strong>AOL</strong> for Broadband, Netscape Internet Service,<br />
CompuServe, <strong>AOL</strong> Instant Messenger, and ICQ. Other <strong>AOL</strong> services are made available to the<br />
general public without any need for user registration, such as <strong>AOL</strong>.<strong>com</strong>, MapQuest.<strong>com</strong>, and<br />
Netscape.<strong>com</strong>.<br />
<strong>AOL</strong> expects to use the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI as described in this CP/CPS for the purpose<br />
of providing security-related services to <strong>Member</strong>s in order to enhance their existing <strong>AOL</strong> services.<br />
Access to and use of such <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services may either be governed by a<br />
<strong>Member</strong>’s existing <strong>Member</strong> Agreement or a supplemental <strong>Member</strong> Agreement, the <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI Addendum, which is applicable to a particular <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service<br />
offering elected by the <strong>Member</strong>.<br />
<strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services are not intended to be stand-alone services, and therefore<br />
are not intended to be directed towards nonmembers. Instead, such persons may be offered the<br />
opportunity for limited participation in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI system in order to accept<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
and rely upon certificates that have been issued to participating <strong>Member</strong>s who choose to interact<br />
with a nonmember, for instance, in order to receive and decrypt a secure email sent from a<br />
participating <strong>Member</strong>. Such nonmembers will need to enter an agreement with <strong>AOL</strong> and/or the<br />
<strong>AOL</strong>CA in order to be authorized to rely on any certificate issued by, or information secured by,<br />
an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service. Section 2.3.3 explains that agreement process. <strong>AOL</strong><br />
and/or the <strong>AOL</strong>CA may charge additional fees for the use of <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services.<br />
These fees (if any) are subject to change. Any such fees will be published with the respective<br />
product documentation and/or enrollment process.<br />
In the event of any inconsistency between the terms of this CP/CPS and the terms of a <strong>Member</strong><br />
Agreement or participating nonmember agreement applicable to a particular <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI service, the terms of the <strong>Member</strong> Agreement or participating nonmember agreement<br />
(as applicable) shall apply (See https://pki-info.aol.<strong>com</strong>/<strong>AOL</strong>MSPKI). Persons who are not<br />
participants but who rely on <strong>AOL</strong> <strong>Member</strong> PKI certificates, or information associated with such<br />
certificates, do so at their own risk; see section 2.3.3.<br />
2.2.2. PKI Roles<br />
• A public key infrastructure conventionally consists of at least the following<br />
roles:Certifier: An entity issuing and revoking certificates, also known as a certification<br />
authority or CA. Certifiers in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are <strong>AOL</strong>CAs, and are either<br />
<strong>AOL</strong> or a service provider operating the CA certification system on <strong>AOL</strong>’s behalf.<br />
• Subject: An entity listed in the subject field of a certificate. A subject is not necessarily<br />
a person; in the case of a device authentication certificate, the entity listed as subject is<br />
an <strong>AOL</strong> Token.<br />
• Relying party: A person or system who relies on a certificate, i.e. accepts the<br />
certificate as being accurate in circumstances that may cause a detriment to the person<br />
if the certificate is not as represented in this CP/CPS.<br />
The <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI provides functionality and support to enable participating<br />
<strong>Member</strong>s to act as subjects and relying parties as described in this CP/CPS. Participating<br />
nonmembers can also act as relying parties with limited service from <strong>AOL</strong> for that purpose; see<br />
section 2.3.1. <strong>AOL</strong> and <strong>AOL</strong>CAs do not provide certificates or other services to participating<br />
nonmembers.<br />
2.2.3. <strong>AOL</strong> <strong>Certification</strong> Authorities<br />
The <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI consists of a PKI consisting of at least two levels of CAs:<br />
• The <strong>AOL</strong> Root Certifier; and<br />
• Certifiers, referred to as “<strong>AOL</strong>CAs”, which issue certificates directly to subjects. <strong>AOL</strong>CAs<br />
are certifiers whose certificates can be verified using a certificate issued by the <strong>AOL</strong> root<br />
certifier.<br />
Refer to https://pki-info.aol.<strong>com</strong>/<strong>AOL</strong> for more information on the <strong>AOL</strong> Root Certifier.<br />
2.2.4. Applicability and Use of <strong>Certificate</strong>s<br />
<strong>Certificate</strong>s are suitable and enabled for use with particular <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services<br />
only, and must not be used or accepted for any other use. In many cases, the use of a certificate<br />
within a particular product or service will be controlled by software and/or devices that make up<br />
the infrastructure for such product or service offering.<br />
<strong>Certificate</strong>s are authorized for use only with the particular <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service or<br />
product for which a user is a valid participant and has been properly authenticated, and for no<br />
other purpose.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
RELYING PARTIES ARE SOLELY RESPONSIBLE FOR DETERMINING THE SUITABILITY OF<br />
A CERTIFICATE FOR A PARTICULAR PURPOSE.<br />
2.3. LIMITATIONS<br />
2.3.1. Services Are For Participants Only<br />
An <strong>AOL</strong>CA does not issue certificates to anyone who is not a participating <strong>Member</strong> subject to the<br />
terms of an applicable <strong>Member</strong> Agreement (except for <strong>AOL</strong> itself and its affiliates and suppliers).<br />
Further, an <strong>AOL</strong>CA does not permit anyone to be<strong>com</strong>e a relying party unless such person is<br />
either a participating <strong>Member</strong> or a participating nonmember subject to the terms of an applicable<br />
agreement with <strong>AOL</strong> or the <strong>AOL</strong>CA. Nonparticipants are, therefore, expected to be nonexistent<br />
in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI.<br />
2.3.2. Disclaimer of Warranties and Limitation of Liability<br />
Except as expressly provided otherwise in a <strong>Member</strong> Agreement, participating nonmember<br />
agreement, or <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Addendum, any reliance on a certificate listing this<br />
CP/CPS is at the relying party’s own risk. This CP/CPS describes certain aspects of the public<br />
key infrastructure known as <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI, but that description is not relevant or<br />
applicable to non-participants except as promotional literature to persuade them to sign up and<br />
participate in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI products or services. Similarly, any information in<br />
certificates is only promotional in relation to non-participants.<br />
<strong>AOL</strong> AND ITS SUPPLIERS DISCLAIMS ANY AND ALL WARRANTIES, BOTH EXPRESS AND<br />
IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF<br />
MERCHANTABILITY, ANY WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE AND<br />
ANY WARRANTY OF ACCURACY OF INFORMATION PROVIDED WITH RESPECT TO <strong>AOL</strong><br />
MEMBER SECURITY, INCLUDING USE OF KEY PAIRS, CERTIFICATES, OR ANY OTHER<br />
GOODS OR SERVICES PROVIDED BY AN <strong>AOL</strong>CA TO ANY PERSON. <strong>AOL</strong> AND ITS<br />
SUPPLIERS FURTHER DISCLAIM ANY AND ALL WARRANTIES, BOTH EXPRESS AND<br />
IMPLIED, THAT PARTICIPATION IN THE <strong>AOL</strong> MEMBER SECURITY PKI WILL AFFECT IN<br />
ANY MANNER THE LEGAL RECOGNITION OR ENFORCEABILITY OF A DIGITAL<br />
SIGNATURE.<br />
IN NO EVENT SHALL <strong>AOL</strong>, AN <strong>AOL</strong>CA OR THEIR SUPPLIERS BE LIABLE FOR INDIRECT,<br />
SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING, WITHOUT<br />
LIMITATION, ANY LOSS OF PROFITS, LOSS OF DATA, COST OF PROCUREMENT OF<br />
SUBSTITUTE SERVICES, OR ANY OTHER INDIRECT, SPECIAL, INCIDENTAL OR<br />
CONSEQUENTIAL DAMAGES, HOWSOEVER CAUSED, AND ON ANY THEORY OF<br />
LIABILITY, WHETHER FOR BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE AND<br />
STRICT LIABILITY), OR OTHERWISE. THESE LIMITATIONS WILL APPLY WHETHER OR<br />
NOT <strong>AOL</strong>, AN <strong>AOL</strong>CA OR THEIR SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY<br />
OF SUCH DAMAGES, WHETHER OR NOT SUCH DAMAGES COULD HAVE BEEN<br />
FORESEEN AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY<br />
LIMITED REMEDY. SUBJECT TO THE FOREGOING, <strong>AOL</strong>’S, <strong>AOL</strong>CAS’, AND THEIR<br />
SUPPLIERS’ LIABILITY FOR DIRECT DAMAGES OF ANY KIND OR NATURE IN<br />
CONNECTION WITH THIS AGREEMENT AND <strong>AOL</strong> MEMBER SECURITY PKI SERVICES<br />
SHALL IN NO EVENT EXCEED US$50.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
2.3.3. Enrollment Process for Non-Participants<br />
A non-participant who wishes to be<strong>com</strong>e a relying party in connection with <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong><br />
PKI services may do so by agreeing to participate in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI as a<br />
nonmember under the terms of a participating nonmember agreement. See https://pkiinfo.aol.<strong>com</strong>/<strong>AOL</strong>MSPKI.<br />
<strong>AOL</strong> and/or the <strong>AOL</strong>CA may charge additional fees for the use of <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI services. These fees (if any) are subject to change. Any such fees will be<br />
published at https://pki–info.aol.<strong>com</strong>/<strong>AOL</strong>MSPKI. Under such agreement participating<br />
nonmembers will have access to revocation information and can install the <strong>AOL</strong> root certificate<br />
into their operating system.<br />
2.3.4. Relying Party Obligations<br />
Without limiting the foregoing provisions, any relying party’s reliance on a certificate issued by the<br />
<strong>AOL</strong>CA must be reasonable and exercise ordinary business prudence under the circumstances<br />
and must conform to the following obligations:<br />
• Ensure that use of a certificate is appropriate and reasonable in light of this CP/CPS, as<br />
well as any applicable <strong>Member</strong> Agreement, <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Addendum, or<br />
participating nonmember agreement;<br />
• Validate the certificate (i.e., confirm that it has not expired or been revoked or<br />
suspended), by checking the published revocation list;<br />
• Trust and make use of the certificate only if a valid certificate chain is established<br />
between the relying party and the subject. A valid chain means that the digital signatures<br />
on certificates have been verified back to the <strong>AOL</strong> root certifier and the relevant<br />
certificate revocation lists have been checked to determine the current validity of each<br />
certificate as of the time of reliance (see also section 3.1);<br />
• Verify the digital signature in question using the appropriate algorithm as specified in the<br />
certificate, and<br />
• Act in good faith, in light of all the circumstances that were known or should have been<br />
known at the time of reliance.<br />
A relying party assumes all risks and liability arising from any decision to rely on a certificate in a<br />
manner inconsistent with these obligations.<br />
3. <strong>Certificate</strong> Content and Confirmation<br />
3.1. Identifying and Authenticating <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
<strong>Certificate</strong>s<br />
This CP/CPS relates only to certificates issued by an <strong>AOL</strong>CA and that reference this CP/CPS.<br />
This CP/CPS does not restrict participants from using other certificates, or relate to those<br />
certificates in any way.<br />
A certificate for use in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI has two identifying characteristics:<br />
(1) It lists this CP/CPS as described below, and<br />
(2) It is issued and signed by an <strong>AOL</strong>CA.<br />
A certificate used in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI references this CP/CPS in two ways:<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
(1) By listing the object identifier of a certificate profile listed in this CP/CPS in the<br />
certificatePolicies field, as defined in section 4.2.1.5 of [RFC 3280];<br />
(2) By listing the URL of this CP/CPS in the certificate’s cpsURI subfield of its<br />
certificatePolicies field, as defined in section 4.2.1.5 of [RFC 3280].<br />
In addition to <strong>AOL</strong>’s copyright in this document, <strong>AOL</strong> holds a copyright in each of the object<br />
identifiers listed in this document and assigned by <strong>AOL</strong>. Only <strong>AOL</strong>CAs have licenses permitting<br />
use of those copyrighted object identifiers.<br />
The authenticity of an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificate can be evaluated by verifying the<br />
<strong>AOL</strong>CA’s digital signature on it. The certificate used for that verification is issued by the <strong>AOL</strong> root<br />
certifier, described online at https://pki-info.aol.<strong>com</strong>/<strong>AOL</strong>. The <strong>AOL</strong> root certifier issues<br />
certificates only to <strong>AOL</strong>CAs so as to enable participants to verify the authenticity of other<br />
participants’ certificates in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI. It does not issue certificates to<br />
participants or promulgate rules for the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI; the relevant rules found in the<br />
<strong>Member</strong> Agreement and the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Addendum.<br />
<strong>AOL</strong> root certificates are distributed in some operating systems, and can be downloaded from<br />
https://pki-info.aol.<strong>com</strong>/<strong>AOL</strong>. The authenticity of a root certificate can also be resolved by<br />
<strong>com</strong>paring a freshly downloaded one against the one a participant already has.<br />
3.2. Form and Content of <strong>Certificate</strong>s Generally<br />
<strong>Certificate</strong>s issued by an <strong>AOL</strong>CA and listing this CP/CPS:<br />
• Conform to the specifications of [ITU X.509] and [IETF 3280] except where this<br />
CP/CPS requires otherwise;<br />
• Contain no extensions not expressly specified in this CP/CPS;<br />
• Contain no identifiers for the subject not listed in this CP/CPS; and<br />
• Contain information current as of the date of issuance, which is the date listed in the<br />
validity:notBefore field of the certificate. Subsequent events or changes affecting<br />
the accuracy or reliability of that information will not be reflected in the certificate<br />
once it has been issued.<br />
Data in certificates has the significance given it in [ITU X.509] and [RFC 3280] except where this<br />
CP/CPS specifies otherwise, and except that those standards must not be applied so as to<br />
impose any legal obligations or liabilities on <strong>AOL</strong>, an <strong>AOL</strong>CA, or any participant unless that<br />
obligation is expressly prescribed in a <strong>Member</strong> Agreement or the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
Addendum, a participating nonmember agreement, or this CP/CPS.<br />
The rules in [ITU X.520] section 3 specify which characters in the data content of a certificate are<br />
significant and match other data.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
3.3. Fields Supported for Use in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
3.3.1. Fields Identifying the Subject<br />
An <strong>AOL</strong>CA indicates the certificate’s subject in the subject field of the certificate by including at<br />
least one identifier of a type specified in the table below:<br />
Identifier type: 1 With data content of: Indicates:<br />
UserID (UID) 2<br />
CommonName (CN), either: 4<br />
A sequence of alphanumeric<br />
characters such as<br />
“fred23miami”<br />
The words “<strong>AOL</strong> Key - ” followed<br />
by a hexadecimal numeral.<br />
The words “<strong>AOL</strong> <strong>Member</strong> - ”<br />
followed by a sequence of<br />
alphanumeric characters such<br />
as “fred23miami”.<br />
One of the subject’s Screen<br />
Names 3<br />
The number is the card unique<br />
identifier recorded in the<br />
non-volatile memory of the<br />
subject’s <strong>AOL</strong> Token. The words<br />
“<strong>AOL</strong> Key” indicate that the <strong>AOL</strong><br />
Token identified by the number<br />
was issued a Device<br />
Authentication certificate by an<br />
<strong>AOL</strong>CA.<br />
The words “<strong>AOL</strong> <strong>Member</strong>” indicate<br />
that the subject is a member of<br />
<strong>AOL</strong> and the alphanumeric<br />
characters are one of the<br />
<strong>Member</strong>’s Screen Names identified<br />
by the Screen Name associated<br />
with a <strong>Member</strong>’s account when the<br />
certificate was issued.<br />
Alphanumeric text other than<br />
“<strong>AOL</strong> <strong>Member</strong>”.<br />
A name by which the subject is<br />
<strong>com</strong>monly known, additional<br />
information is provided in the OU<br />
field.<br />
Organizational Unit (OU) Alphanumeric text Indicates the <strong>com</strong>monly known<br />
name for the entity providing the<br />
security service or product.<br />
OrganizationName (O)<br />
The words “America Online<br />
Inc.” 5<br />
The subject is a <strong>Member</strong> of <strong>AOL</strong>.<br />
1 This column lists the technical names of the identifiers for the subject. The format of certificates is binary<br />
and specified using Abstract Syntax Notation 1 (ASN.1). That binary format is not easy to read, so a<br />
certificate is often decoded into alphanumeric text, which is human-readable as well as processable using<br />
text-based scripts. The identifiers first listed are those defined in ASN.1 in [ITU-T X.509], and those in<br />
parentheses are the corresponding alphanumeric representations, which conform to [RFC 2253].<br />
2 UIDs are not present in all end entity certificates, only as re<strong>com</strong>mended to confirm to [RFC 3280].<br />
3 The subject may have only one Screen Name, or may have more. If the subject has multiple Screen<br />
Names, only one can be listed in a certificate, but the subject may enable any or all of their Screen Names<br />
to use <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI authentication capabilities. In that case, separate authentication<br />
certificates are necessary, one for each Screen Name, together with separate private keys. The separate<br />
certificates and private keys may be stored in one or more <strong>AOL</strong> Tokens.<br />
Although a Screen Name may appear in more than one certificate, the <strong>AOL</strong> system prevents creation of<br />
duplicate Screen Names.<br />
4 The subject field never contains more than one CommonName (CN) identifier for the subject; so the<br />
CommonName identifiers listed above are alternatives. The certificate profiles listed in section 3.4 make<br />
clear which form of CommonName appears in each certificate type.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Identifier type: 1 With data content of: Indicates:<br />
CountryName (C)<br />
Alphanumeric text other than<br />
“America Online Inc.”<br />
A standard two-letter<br />
abbreviation listed in [ISO 3166]<br />
for a country, such as “US” for<br />
the United States.<br />
The legally registered name of the<br />
<strong>com</strong>pany representing the subject.<br />
The country from which the subject<br />
obtains <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
services or in which the subject’s<br />
organization is legally registered. 6<br />
In some certificates, an <strong>AOL</strong>CA also indicates the certificate’s subject in the subjectAltName field<br />
of the certificate by including one or more identifiers of a type specified in the table below<br />
applicable to the certificate.<br />
Identifier type: 7 With data content of: Indicates:<br />
otherName with<br />
subfield type-id of<br />
2.16.840.1.113730.7.2<br />
otherName with<br />
subfield type-id of<br />
1.3.6.1.4.1.1066.4.1<br />
rfc822Name<br />
Alphanumeric characters<br />
such as “fred23miami”.<br />
A hexadecimal numeral.<br />
Alphanumeric text <strong>com</strong>pliant<br />
with [RFC 822].<br />
One of the subject’s Screen Names. 8<br />
The number is the card unique identifier (CUID)<br />
recorded in the non-volatile memory of the<br />
subject’s <strong>AOL</strong> Token.<br />
The subject’s e-mail address.<br />
Section 3.5 of this CP/CPS explains how the <strong>AOL</strong>CA confirms the accuracy of the identifiers for<br />
the subject listed in this section.<br />
3.3.2. Fields Identifying the Issuer<br />
<strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificates identify the <strong>AOL</strong>CA that issued the certificate in the issuer<br />
field of the certificate by including the following:<br />
5 America Online, Inc. formally changed its name to <strong>AOL</strong> LLC on April 3, 2006. References to America<br />
Online, Inc. are imbedded in certificates issued by the <strong>AOL</strong> root certifier. It is important to note that America<br />
Online, Inc. and <strong>AOL</strong> LLC refer to the same organization.<br />
6 <strong>AOL</strong> and its suppliers, for example, are located in many countries worldwide, and <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong><br />
PKI services may be available in several or all of those countries. The country name in the subject field of<br />
the certificate indicates the country in which the subject is legally registered from which <strong>AOL</strong>, ts supplier<br />
provides <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services to the subject.<br />
7 See footnote 1.<br />
8 See footnote 2.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Identifier type: 9 With data content of: Indicates:<br />
OrganizationName (O) Alphanumeric text The full 10 <strong>com</strong>pany name of the <strong>AOL</strong>CA that<br />
issued the certificate.<br />
LocalityName (L) Alphanumeric text The city or town in which the issuing <strong>AOL</strong>CA’s<br />
principal place of business is located.<br />
StateOrProvinceName<br />
(ST)<br />
CountryName (C)<br />
Alphanumeric text<br />
A standard two-letter<br />
abbreviation listed [ISO 3166]<br />
for a country, such as “US”<br />
for the United States.<br />
The state or province in which the issuing<br />
<strong>AOL</strong>CA’s principal place of business is located.<br />
The country in which the issuing <strong>AOL</strong>CA’s<br />
principal place of business is located.<br />
CommonName (CN) Alphanumeric text Used within <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI to list<br />
which system was used to create the certificate.<br />
Validity<br />
The subfields notBefore and<br />
notAfter contain dates in the<br />
form specified for UTC in<br />
[RFC 3280].<br />
NotBefore indicates the date on which the CA<br />
signing certificate begins to be valid and notAfter<br />
indicates when it ceases to be valid,<br />
approximately 25 years.<br />
To be certain that the issuer is an <strong>AOL</strong>CA, verification of the digital signature on the certificate is<br />
necessary. See section 3.1.<br />
3.3.3. Other Supported Fields<br />
<strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificates also contain the following:<br />
Field Name<br />
Critical?<br />
11<br />
Data Content<br />
Significance<br />
version n/a v3 only (indicated by the<br />
integer “2”)<br />
serialNumber n/a An integer unique to the<br />
certificate among all serial<br />
numbers in certificates issued<br />
by the same certifier<br />
signature n/a The subfield<br />
algorithmIdentifier: algorithm<br />
contains the object identifier<br />
(specified in [RFC 3280]) for<br />
SHA-1 with RSA encryption.<br />
validity n/a The subfields notBefore and<br />
notAfter contain dates in the<br />
form specified for UTC in [RFC<br />
3280].<br />
subject n/a Contain at least one identifier<br />
specified in section 3.3.1.<br />
Indicates the version of [ITU-T<br />
X.509] to which the certificate<br />
conforms.<br />
<strong>Certificate</strong> serial number. The<br />
<strong>com</strong>bination of issuer and serial<br />
number <strong>com</strong>prises a unique<br />
identifier for the certificate<br />
Indicates the algorithm used by<br />
the issuer to sign the certificate,<br />
which is SHA-1 with RSA.<br />
NotBefore indicates the date on<br />
which the subject’s certificate<br />
begins to be valid and notAfter<br />
indicates when it ceases to be<br />
valid. Unless otherwise<br />
specified, the period between the<br />
two dates is approximately 5<br />
years.<br />
As specified in section 3.3.1.<br />
9 See footnote 1.<br />
10 Abbreviations indicating incorporation that are <strong>com</strong>mon in the jurisdiction of incorporation may be used.<br />
For example, “Inc.” in the US, “Ltd” in the UK, and “GmbH” in Germany.<br />
11 “Critical” indicates for an extension whether an application is required to be able to process the content of<br />
the field. It is not applicable (“n/a”) for fields that are not extensions; see [ITU-T X.509] and [RFC 3280].<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Field Name<br />
Critical?<br />
11<br />
Data Content<br />
Significance<br />
authorityKeyIdentifier No The subfield keyIdentifier<br />
contains the SHA-1 hash of<br />
the public key by which the<br />
issuer’s signature on the<br />
certificate can be verified.<br />
subjectKeyIdentifier No The subfield keyIdentifier<br />
contains the SHA-1 hash of<br />
the public key listed in<br />
subjectPublic-<br />
KeyInfo:subjectPublicKey.<br />
The other subfields of<br />
subjectKeyIdentifier are not<br />
used.<br />
keyUsage Yes For a certificate used for<br />
encryption, Bit 3 of the<br />
bitstring is set to true; all<br />
others are set to false.<br />
For a certificate used for<br />
authentication, Bit 0 of the<br />
bitstring is set to true; all<br />
others are set to false, except<br />
that Bit 1 of the bitstring may<br />
also be set to true. 12<br />
extendedKeyUsage No Publicly and privately<br />
registered Object Identifiers<br />
(OIDs).<br />
certificatePolicies No As stated in sections 3.4.1-<br />
3.4.53.4.4.<br />
Indicates which public key to use<br />
in verifying the authenticity of the<br />
certificate.<br />
The subfield keyIdentifier labels<br />
the public key of this certificate<br />
for convenient reference and to<br />
prevent confusion with other key<br />
pairs the same subject may<br />
have.<br />
Indicates to software applications<br />
what the key is to be used for<br />
(see [ITU X.509] and [IETF<br />
3280]). In the <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI, this field does not<br />
imply a legal obligation but rather<br />
is to signal to applications how to<br />
use the certificate and the<br />
corresponding private key.<br />
Indicates specific intended<br />
usages for the public key<br />
contained in the certificate or the<br />
private key associated with<br />
same. Refer to sections 3.4.1-<br />
3.4.5. (This extension is not<br />
present in all <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI certificates.)<br />
As stated in sections 3.4.1-<br />
3.4.53.4.4.<br />
subjectAltName No As stated in section 3.3.1. As stated in section 3.3.1.<br />
basicConstraints No The subfield CA is set to false.<br />
The pathLenConstraint is<br />
inapplicable.<br />
CRLDistributionPoints No The subfield<br />
DistributionPointName<br />
contains a URL. The<br />
reasonFlags subfield is<br />
unused (i.e. bit 0 is true).<br />
authorityInformationAcc<br />
ess<br />
No<br />
The subfields method and<br />
location contains a URI<br />
indicating the URL where<br />
OCSP information about this<br />
certificate is available.<br />
Indicates that applications are<br />
not to use the certificate in<br />
verifying the digital signature on<br />
another certificate.<br />
Points to a URL where more<br />
information about the postissuance<br />
validity or reliability of a<br />
certificate may be available.<br />
Points to a URL where more<br />
information about the postissuance<br />
validity or reliability of a<br />
certificate may be available.<br />
(This extension is not present in<br />
12 A value of true for Bit 1 indicates that the certificate may be used for a “nonrepudiation service”, which is<br />
defined in [RFC 3280] section 4.2.1.3 as “protect[ing] against the signing entity falsely denying some action”,<br />
such as a digital signature verifiable by reference to the certificate. Whether this technical “nonrepudiation”<br />
legally prevents a digital signer from denying a signature depends on more than simply setting this bit to<br />
“true”. This bit is a signal to digital verification software on how to use the certificate rather than a basis for<br />
legal inferences, which would have to be grounded in additional facts and circumstances as well as in the<br />
applicable law.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Field Name<br />
Critical?<br />
11<br />
Data Content<br />
Significance<br />
all <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
certificates.)<br />
3.4. Profiles for Specific <strong>Certificate</strong> Types<br />
3.4.1. Device Authentication <strong>Certificate</strong>s<br />
A device authentication certificate is used to authenticate an <strong>AOL</strong> Token and establish a secure<br />
channel between the <strong>AOL</strong> Token and the <strong>AOL</strong> system for login and other purposes.<br />
Device authentication certificates thus identify and authenticate an <strong>AOL</strong> Token rather than a<br />
person. Relying parties must possess other facts, apart from the information contained in a<br />
device authentication certificate, to link this certificate to anyone. A device authentication<br />
certificate is issued when an <strong>AOL</strong> Token is activated and then later associated with a participating<br />
<strong>Member</strong>’s account. It is possible to infer from a device authentication certificate that those events<br />
took place. However, the associated account or <strong>Member</strong> is not listed in the device authentication<br />
certificate, and disclosure of that information by <strong>AOL</strong> or an <strong>AOL</strong>CA is subject to the <strong>AOL</strong> privacy<br />
policy; see section 3.6.1.<br />
Device authentication certificates are identified by the policy OID suffix of 1. In other words, a<br />
conforming certificate lists this CP/CPS in the certificatePolicies:policyIdentifier field with a final<br />
OID segment consisting of “1”, for a <strong>com</strong>plete OID of:<br />
1.3.6.1.4.1.1066.1.1000.1.0.1.1<br />
A device authentication certificate contains all of the fields specified in section 3.3 above, with the<br />
following additional specifications:<br />
Field<br />
Additional Content Specifications (if any)<br />
subject Contains the following as described in the table in section 3.3.1:<br />
- CommonName (CN) identifier containing “<strong>AOL</strong> Key –“ and the card unique<br />
identifier of the subject’s <strong>AOL</strong> Token<br />
- OrganizationName (O)<br />
- CountryName (C)<br />
keyUsage<br />
subjectAltName<br />
The UID identifier is not used in a device authentication certificate.<br />
Bit 0 of the bitstring is set to true; all others are set to false.<br />
Contains the CUID of the <strong>AOL</strong> Token.<br />
3.4.2. Screen Name Authentication <strong>Certificate</strong>s<br />
A Screen Name authentication certificate is for use in verifying its subject’s digital signature on a<br />
message or other data.<br />
A Screen Name may or may not reflect the <strong>Member</strong>’s real name. The <strong>Member</strong> selects their<br />
Screen Name(s) 13 in setting up and administering their account or sub-account. The <strong>Member</strong><br />
Agreement gives <strong>AOL</strong> some discretion to police against problematic (e.g. duplicate, vulgar, etc.)<br />
Screen Names, but <strong>AOL</strong> does not otherwise determine the content of a Screen Name. <strong>AOL</strong> and<br />
an <strong>AOL</strong>CA also disclose information further identifying the <strong>Member</strong> bearing a Screen Name only<br />
in accordance with the <strong>AOL</strong> privacy policy. Consequently, Screen Name authentication<br />
certificates provide only limited identification of an actual person.<br />
13 A <strong>Member</strong> may have multiple Screen Names but can list only one in a Screen Name authentication<br />
certificate. See footnote 2.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Screen Name authentication certificates in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are identified by the<br />
policy OID suffix of 2. In other words, a conforming certificate lists this CP/CPS in the<br />
certificatePolicies:policyIdentifier field with a final OID segment consisting of “2”, for a <strong>com</strong>plete<br />
OID of:<br />
1.3.6.1.4.1.1066.1.1000.1.0.1.2<br />
A Screen Name authentication certificate contains all of the fields specified in section 3.3above,<br />
with the following additional specifications:<br />
Field<br />
Additional Content Specifications (if any)<br />
subject Contains the following as described in the table in section 3.3.1:<br />
- CommonName (CN) identifier containing “<strong>AOL</strong> <strong>Member</strong> –“ and the<br />
subject’s <strong>AOL</strong> Screen Name.<br />
- UserID (UID) containing the subject’s <strong>AOL</strong> Screen Name<br />
- OrganizationName (O)<br />
- CountryName (C)<br />
keyUsage<br />
subjectAltName<br />
Bit 0 of the bitstring is set to true; Bit 1 may be set to either true or false (see<br />
note 10). All other bits are set to false.<br />
Contains the subject’s Screen Name in the otherName subfield and the<br />
subject’s rfc822Name (e-mail address).<br />
3.4.3. Full Name Authentication <strong>Certificate</strong>s<br />
A full name authentication certificate is for use in verifying its subject’s digital signature on a<br />
message or other data.<br />
A participating member’s full names is verified against an authoritative database for this<br />
information. Such sources may include an <strong>AOL</strong> employee database or <strong>AOL</strong> <strong>Member</strong> billing<br />
record.<br />
Full name authentication certificates in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are identified by the policy<br />
OID suffix of 3. In other words, a conforming certificate lists this CP/CPS in the<br />
certificatePolicies:policyIdentifier field with a final OID segment consisting of “3”, for a <strong>com</strong>plete<br />
OID of:<br />
1.3.6.1.4.1.1066.1.1000.1.0.1.3<br />
A full name authentication certificate contains all of the fields specified in section 3.3above, with<br />
the following additional specifications:<br />
Field<br />
Additional Content Specifications (if any)<br />
subject Contains the following as described in the table in section 3.3.1:<br />
- CommonName (CN) identifier containing the name by which the subject’s<br />
is <strong>com</strong>monly known.<br />
- UserID (UID) containing the subject’s <strong>AOL</strong> Screen Name<br />
- OrganizationName (O)<br />
- CountryName (C)<br />
keyUsage<br />
subjectAltName<br />
Bit 0 of the bitstring is set to true; Bit 1 may be set to either true or false (see<br />
note 10). All other bits are set to false.<br />
Contains the subject’s Screen Name in the otherName subfield and the<br />
subject’s rfc822Name (e-mail address).<br />
3.4.4. Basic Encryption <strong>Certificate</strong>s<br />
A basic encryption certificate is for use in encrypting messages or data streams to be sent to the<br />
subject. Its purpose is not to facilitate verification of a digital signature but rather to enable a<br />
sender to encrypt the session key that the sender has used to encrypt information, and thereby to<br />
keep the information confidential from everyone but the subject of the certificate.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Basic encryption certificates in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are identified by the policy OID<br />
suffix of 5. In other words, a conforming certificate lists this CP/CPS in the<br />
certificatePolicies:policyIdentifier field with a final OID segment consisting of “5”, for a <strong>com</strong>plete<br />
OID of:<br />
1.3.6.1.4.1.1066.1.1000.1.0.1.5<br />
A basic encryption certificate contains the same fields as a Screen Name or Full Name<br />
authentication certificate (depending on which type of authentication certificate the subject<br />
enrolled for) except that in the keyUsage field, Bit 3 of the bitstring is set to true, and all others are<br />
set to false.<br />
3.4.5. Identification <strong>Certificate</strong>s<br />
An identification certificate identifies a data stream, host, or object which participating <strong>Member</strong>s<br />
access or download. Its purpose is to provide an additional level of confidence that the data<br />
stream, host, or object is administered by <strong>AOL</strong> or one of its authorized agents.<br />
Conforming identification certificates in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are identified by listing this<br />
CP/CPS in the certificatePolicies:policyIdentifier field:<br />
1.3.6.1.4.1.1066.1.1000.1.0.2.1 (data objects), or<br />
1.3.6.1.4.1.1066.1.1000.1.0.2.2 (hosts)<br />
An Identification certificate contains all of the fields specified in section 3.3above, with the<br />
following additional specifications:<br />
Field<br />
OrganizationalUnit (OU)<br />
Additional Content Specifications (if any)<br />
The business unit or product division of the <strong>AOL</strong> organization responsible for<br />
the service utilizing <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI.<br />
3.5. Identification and Confirmation<br />
This section examines how the issuing <strong>AOL</strong>CA, in cooperation with <strong>AOL</strong>, confirms the identity of<br />
the <strong>Member</strong> who is to be the subject of a certificate, as well as confirms the accuracy of the other<br />
facts represented by the <strong>AOL</strong>CA issuing the certificate.<br />
3.5.1. Identifying Subjects<br />
An <strong>AOL</strong> <strong>Member</strong> is the source of some of the information in a certificate referencing this CP/CPS.<br />
<strong>AOL</strong> obtains that information from the <strong>Member</strong> at various times over the life of the account,<br />
including when the account is first opened. <strong>Member</strong> verification methods may change from time<br />
to time to reflect improvements in security techniques.<br />
To confirm that the <strong>Member</strong> (rather than someone else) is the source of that information, <strong>AOL</strong><br />
identifies the provider of the information as the <strong>Member</strong> through at least one of the following<br />
procedures:<br />
• Over the telephone: In response to questions from <strong>AOL</strong> <strong>Member</strong> Services staff,<br />
the person provides staff with accurate answers to one or more <strong>AOL</strong> security<br />
questions. Such questions inquire after facts that the <strong>Member</strong> ordinarily knows but<br />
which are not generally known by others. <strong>AOL</strong> corroborates the identification<br />
achieved through such a question by asking for additional information listed in <strong>AOL</strong><br />
<strong>Member</strong> records. <strong>AOL</strong> staff never asks the <strong>Member</strong> to disclose a password.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
• Login: The person has logged in using the <strong>Member</strong>’s primary Screen Name (or<br />
equivalent Screen Name authorized as such by the primary Screen Name) and that<br />
Screen Name’s password.<br />
• Account opening: By providing information in response to account opening<br />
questionnaires followed by confirmatory experience. If possible, <strong>AOL</strong> opens the<br />
account and gathers the initial <strong>Member</strong> information over a secure channel after<br />
activating the new <strong>Member</strong>’s <strong>AOL</strong> Token; however, if no <strong>AOL</strong> Token is available,<br />
the new <strong>Member</strong> provides the information using other secure conduits such as<br />
SSL/TLS. The information may include a payment method, in which case <strong>AOL</strong><br />
discovers whether that payment method is operative at registration time. If the<br />
payment method proves inoperative at a later time, <strong>AOL</strong> requests a correction and<br />
eventually terminates the account if accurate information is not provided. Some<br />
<strong>AOL</strong> accounts may be gifts or paid for by another person; <strong>AOL</strong> does not require any<br />
similarity between any name associated with the payment method and the name<br />
provided as the <strong>Member</strong>’s name.<br />
• By manual methods: Subject information for identification certificates is gathered<br />
and verified manually by authorized AMSPKI staff members during the enrollment<br />
process.<br />
The identification of prospective <strong>AOL</strong> employees, including <strong>Member</strong> Services, involved in the<br />
above-listed procedures, is confirmed with a background check and check of employment history<br />
and immigration status 14 before they are employed and issued their identification cards. Access<br />
to <strong>AOL</strong> facilities is controlled by those cards.<br />
These identification methods do not rule out all avenues of circumvention, perhaps the most<br />
<strong>com</strong>mon of which consists of the <strong>Member</strong> sharing the authenticating information (e.g. the<br />
answers to <strong>AOL</strong> security questions, private key files, or the <strong>AOL</strong> Token and login information)<br />
with another person. <strong>AOL</strong> apprises <strong>Member</strong>s of the possible consequences of so doing.<br />
Whether a <strong>Member</strong>’s enabling of another person to use the <strong>Member</strong>’s account is an implicit<br />
authorization to act for the <strong>Member</strong> or is obtained by fraud depends on the circumstances and<br />
applicable law.<br />
3.5.2. Confirmation of the Factual Content of <strong>Certificate</strong>s<br />
Before an <strong>AOL</strong>CA issues a certificate, the <strong>AOL</strong>CA confirms 15 the accuracy of the factual<br />
representations to be made in the certificate. For <strong>Member</strong> certificates confirmation is ordinarily<br />
not performed on a per-certificate basis but rather for each account and subaccount (i.e. each<br />
Screen Name created within the account). The current information recorded in the <strong>Member</strong><br />
records of the account is used to supply part of the content of a certificate shortly before it is<br />
issued as described in section 4.2.1. Organizational entity certificates are always manually<br />
verified by authorized AMSPKI staff members.<br />
The factual content of a certificate to be issued is confirmed if the <strong>AOL</strong>CA has done the following<br />
for the identifier(s) of the subject to be included in the certificate:<br />
14 The main text reflects the practice for US employees. In other countries, local law and business practices<br />
may vary. In those countries, <strong>AOL</strong>’s hiring practices are in line with those of other employers in the<br />
information technology and e-<strong>com</strong>merce industries.<br />
15 In a PKI, a Registration Authority (RA) often performs these functions. In the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI,<br />
this function may or may not be performed by a dedicated RA function. RAs, if used, enroll with an <strong>AOL</strong>CA<br />
by providing identification credentials that are <strong>com</strong>pared with the appropriate sources before being enabled<br />
for this role. The CA authorizes external RAs, if used, upon successful identification and authentication, and<br />
approval of the external RA enrollment and certificate application forms. External RAs are responsible for<br />
identification and authorization of subscribers and must secure their private signing keys used for signing<br />
applications, securely forward certificate requests to the CA, and securely store any subscriber information<br />
collected (if necessary). <strong>AOL</strong>CAs verify the authenticity of a subject’s certificate requests received by an RA<br />
by validating the RA’s digital signature on the submission.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Type of information<br />
(from third column of the tables in section 3.3.1)<br />
The unique identifier embedded in firmware of<br />
the <strong>AOL</strong> Token (listed in a device authentication<br />
certificate)<br />
The subject’s Screen Name<br />
That the subject is a <strong>Member</strong> of <strong>AOL</strong><br />
A name by which the subject is <strong>com</strong>monly known<br />
The country from which the subject obtains <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI services<br />
Issuer identifiers<br />
Confirmed in this manner<br />
The <strong>AOL</strong> system queries the <strong>AOL</strong> Token over a<br />
secure channel established between the <strong>AOL</strong> Token<br />
and the <strong>AOL</strong> system. The <strong>AOL</strong> system thereby<br />
ascertains whether the <strong>AOL</strong> Token is authentic and, if<br />
so, retrieves its identifying number (CUID), and passes<br />
that information to the <strong>AOL</strong>CA.<br />
After logging in the subject via a secure channel, the<br />
<strong>AOL</strong> system checks that the Screen Name under<br />
which the subject is logged in as is active in the <strong>AOL</strong><br />
account records for the subject.<br />
After logging in the subject via a secure channel, the<br />
<strong>AOL</strong> system checks that the Screen Name under<br />
which the subject is logged in as is active in the <strong>AOL</strong><br />
account records for the subject.<br />
By <strong>com</strong>paring the identifier to be included in the<br />
certificate against a source which:<br />
(1) is normally relied on in the country listed in the<br />
CountryName (C) field as a documentation for<br />
confirming a person’s name, and<br />
(2) is not known to the <strong>AOL</strong>CA to have identification<br />
practices which create an unreasonable risk of false or<br />
erroneous identification.<br />
For <strong>AOL</strong> staff certificates, this information is generally<br />
checked against an authoritative employee database.<br />
Reference to <strong>AOL</strong> records to ascertain the country<br />
location of the affiliate or partner (including in some<br />
cases a franchisee) of <strong>AOL</strong> LLC that provides <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI services to the <strong>Member</strong>. <strong>AOL</strong><br />
and its affiliates generally impose surcharges for<br />
access to <strong>AOL</strong> services from outside that country, so<br />
the subject has an economic motivation to obtain <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI services from the country where<br />
the subject resides. However, apart from the<br />
inference drawn from that fact, <strong>AOL</strong> does not confirm<br />
the subject’s ordinary geographical location.<br />
Reference to the <strong>com</strong>pany records of the <strong>AOL</strong>CA that<br />
issued the certificate. 16<br />
The <strong>Member</strong> can update or correct the information about the subject on file in the <strong>AOL</strong> <strong>Member</strong><br />
records in any of the following ways:<br />
• Informing <strong>AOL</strong> <strong>Member</strong> Services. <strong>AOL</strong> provides extensive help desk support to<br />
<strong>Member</strong>s via telephone or online <strong>com</strong>munications. <strong>Member</strong> Services staff can<br />
update a <strong>Member</strong>’s details in <strong>AOL</strong> records after identifying the <strong>Member</strong> as<br />
described in section 3.5.1. The <strong>Member</strong> must also establish that the <strong>Member</strong><br />
controls the primary Screen Name of the account. After confirming the identity of<br />
the caller in that manner, <strong>AOL</strong> <strong>Member</strong> Services will respond to a request by the<br />
caller to change the caller’s <strong>Member</strong> information in <strong>AOL</strong> records.<br />
• Updating <strong>AOL</strong> records online via a secure connection. The <strong>AOL</strong> system<br />
includes online functionality enabling the primary Screen Name to manage its<br />
account using transport-layer security after securely logging in. Each Screen Name<br />
16 Whether the <strong>AOL</strong>CA actually issued the certificate is ascertainable by checking the certificate’s<br />
authenticity, which is done by verifying the digital signature on the certificate. <strong>Certificate</strong>s in the <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI are ultimately verifiable by reference to a certificate issued by the <strong>AOL</strong> Root CA; see<br />
section 3.1.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
can also manage its sub-account to the extent that the primary Screen Name<br />
permits.<br />
<strong>AOL</strong> and an <strong>AOL</strong>CA generally do not update <strong>Member</strong> information on file in <strong>AOL</strong> records unless<br />
the <strong>Member</strong> initiates that update. It is possible that <strong>Member</strong> information on file be<strong>com</strong>es out of<br />
date, or that <strong>Member</strong> information reflected in the content of a certificate be<strong>com</strong>es out of date after<br />
the certificate is issued. When a certificate is renewed or replaced, the <strong>AOL</strong>CA that issued the<br />
certificate will use the then-current information on file in the certificate.<br />
Before issuing a certificate, the <strong>AOL</strong>CA also confirms that the prospective subject holds the<br />
private key that corresponds to the public key to be certified through the key generation and<br />
issuance process described in section 4.2.1. A secure channel is used to <strong>com</strong>municate between<br />
the subject’s <strong>AOL</strong> Token and the <strong>AOL</strong> system to ensure accurate transmission of the keys.<br />
Except for the subject identifiers and the subject’s public key, the <strong>AOL</strong>CA does not confirm<br />
information in the certificate, and that information is to be understood not as a factual assertion<br />
but rather as, for example, specifying a parameter for the operation of authentication or<br />
encryption software.<br />
<strong>AOL</strong> retains documentation supporting confirmation as long as a certificate having the confirmed<br />
content is valid, and it may in its discretion retain it longer.<br />
3.6. Confidentiality and Intellectual Property<br />
3.6.1. Confidentiality of <strong>Certificate</strong> Content<br />
<strong>Certificate</strong>s are designed to circulate widely in technological systems, and restricting their<br />
dissemination is impractical. In accordance with standards, most applications include a copy of<br />
the relevant certificate with each digital signature or block of encrypted data. Consequently,<br />
information in a certificate is not treated as confidential as a practical matter. In addition,<br />
expiration and revocation status of a certificate must, by design, be published and is therefore not<br />
treated as confidential.<br />
The <strong>AOL</strong> system does not forward confidential <strong>Member</strong> information to an <strong>AOL</strong>CA for inclusion in<br />
a certificate. What information is confidential is determined in accordance with the applicable<br />
<strong>Member</strong> Agreement, the <strong>AOL</strong> privacy policy, and applicable law.<br />
<strong>AOL</strong> and the <strong>AOL</strong>CA may disclose confidential <strong>Member</strong> information to law enforcement officials<br />
or private litigants in order to <strong>com</strong>ply with valid legal process such as a search warrant, subpoena<br />
or court order, to protect the <strong>com</strong>pany's rights and property, or during emergencies when we<br />
believe physical safety is at risk.<br />
3.6.2. Intellectual Property Rights in <strong>Certificate</strong> Content<br />
<strong>Member</strong>s agree and acknowledge that <strong>AOL</strong> and its suppliers own and shall retain all respective<br />
rights, title and interest in and to, and all intellectual property rights embodied in or associated<br />
with any <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI product or service. Such right, title and interest shall extend<br />
without limitation to any content, software, graphics, design materials, technology, methods,<br />
architecture, publications, business plans and other tangible or intangible intellectual propertybased<br />
assets of any kind in machine readable, printed or other form and all revisions,<br />
enhancements, improvements, technical know-how, patents, copyrights, moral rights and trade<br />
secrets associated with any <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI product or service. Except as expressly<br />
stated in this CP/CPS or an applicable <strong>Member</strong> Agreement, participants and relying parties will<br />
have no rights of any kind in or to any certificate, <strong>AOL</strong> Token, key pairs, trademarks or other<br />
intellectual property, PKI documents or the <strong>AOL</strong> system. There are no implied licenses under this<br />
Agreement, and any rights not expressly granted under this Agreement are reserved by <strong>AOL</strong>.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
4. <strong>Certificate</strong> and Key Pair Lifecycles<br />
The lifecycle of a certificate is essentially the lifecycle of a participant’s digital authentication or<br />
encryption capability. To a great extent, the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI presents a participant<br />
with features and lets the participant manage them simply as capabilities, rather than involving<br />
the participant in the intricacies of certificate processes and key management. This section<br />
explains how what the participating <strong>Member</strong> sees in their user interface maps to what happens<br />
behind the scenes.<br />
4.1. A <strong>Certificate</strong> and Key Pair as Seen by a Participating <strong>Member</strong><br />
A <strong>Member</strong> begins participating in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI by obtaining an and <strong>AOL</strong><br />
<strong>Certificate</strong> or <strong>AOL</strong> Token and agreeing to an applicable <strong>Member</strong> Agreement. Those actions are<br />
outside the scope of this CP/CPS, which assumes that they have occurred.<br />
For <strong>AOL</strong> Tokens, once an <strong>AOL</strong> Token has been obtained and activated for a given account or<br />
subaccount, the primary Screen Name of the participating <strong>Member</strong>’s account or (for Device<br />
Authentication certificates only) the Screen Name of a subaccount can:<br />
• Start a new digital authentication or encryption capability for the account or<br />
subaccount. When this happens, the <strong>AOL</strong> Token generates a new key pair and an<br />
<strong>AOL</strong>CA issues a certificate containing the public key of the new key pair. The <strong>AOL</strong><br />
system sends the certificate to the participating <strong>Member</strong> by inserting it into the<br />
<strong>Member</strong>’s <strong>AOL</strong> Token.<br />
• Stop as soon as possible an authentication or encryption capability. This notifies<br />
the <strong>AOL</strong>CA that issued the relevant certificate to revoke it; see section 4.2.3.<br />
• Gracefully shutdown an authentication or encryption capability. This stops the<br />
automatic renewal or replacement of the certificate as it expires but leaves it valid<br />
until it expires. The certificate can still be relied on for authentication or used for<br />
encryption until it expires. This normal shutdown effects a gradual and “natural”<br />
termination of the signing or encrypting capability in contrast to the more abrupt stop<br />
caused by revocation.<br />
• (Device Authentication <strong>Certificate</strong>s only) Suspend all digital signing and/or<br />
encrypting capabilities. This is done by temporarily unbinding the private key(s)<br />
stored on the <strong>AOL</strong> Token from the participating <strong>Member</strong>’s account. The <strong>AOL</strong> Token<br />
remains listed in the account so that the <strong>Member</strong> can easily resume using it, but<br />
usage of the listed <strong>AOL</strong> Token is blocked as a functional matter. While the <strong>AOL</strong><br />
Token is not unbound from the account, the only <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI function<br />
available to the <strong>Member</strong> is resuming the suspended capabilities i.e. re-binding the<br />
<strong>AOL</strong> Token to the account.<br />
• Resume suspended digital signing and/or encrypting capabilities. This re-binds the<br />
<strong>AOL</strong> Token to the participating <strong>Member</strong>’s account.<br />
These concepts in the user interface essentially present security functions and related<br />
certification processes to the participant without technical jargon. The following sections explain<br />
how these basic functions trigger certification processes.<br />
<strong>AOL</strong> organizational entities participate in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI by requesting and<br />
receiving a certificate bound by this CP/CPS. They are bound by the processes and restrictions<br />
of this document until they destroy the certificate or the certificate is revoked. Once issued, the<br />
organizational entity can immediately begin using the certificate for its intended purpose.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
4.2. Processes<br />
The significant events occurring in the lifecycle of an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI authentication,<br />
encryption, or identification capability include:<br />
• Setting up a new capability, which consists of generating a new key pair and having<br />
a certificate issued for it. Replacing an existing capability is the same procedure,<br />
with the new key pair and certificate taking the place of the old one, except as noted<br />
in section 4.2.1.4.<br />
• Expiration of a capability, i.e. the expiration of the related certificate.<br />
• Renewal of an existing capability, in which a new certificate is issued for an existing<br />
key pair without generating new keys.<br />
Revocation of an existing capability, which terminates it as soon as possible. Ordinarily,<br />
a capability that is no longer intended for use can be left to expire, but quicker<br />
termination is possible if a problem arises.<br />
The following subsections describe these processes in detail. The remainder of this section<br />
assumes that all of the following are true at the time when the action described is taken:<br />
• The participating <strong>Member</strong> has in effect a contract for <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
services.<br />
• The participating <strong>Member</strong>’s account is in good standing, i.e. not suspended due to<br />
payment problems or inactivity, or subject to other restrictions according to the<br />
<strong>Member</strong> Agreement and <strong>AOL</strong> policies.<br />
• The requested <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service is available to the participating<br />
<strong>Member</strong>. Availability may vary for regulatory or product phasing or marketing<br />
reasons. Some jurisdictions regulate encryption or other information security<br />
technology, which may restrict the availability of <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services<br />
in those areas. The availability of a particular <strong>AOL</strong>CA’s service may also depend on<br />
local law.<br />
• The person carrying out the action has the power to do so for the <strong>Member</strong>. A single<br />
<strong>Member</strong>’s account can have multiple subaccounts, each with its own Screen Name.<br />
For the account as a whole, one Screen Name, termed the “primary Screen Name”,<br />
has full administrative authority over the account. A Screen Name may have<br />
varying power over its subaccount depending on restrictions imposed by the<br />
primary Screen Name. This control and administration functionality is a feature of<br />
the <strong>AOL</strong> system that has been also applied in relation to <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI.<br />
4.2.1. Setup and Replacement of <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
Capabilities<br />
Setting up a new authentication, encryption, or identification capability involves generating a new<br />
key pair and having a new certificate issued for it. Those processes vary depending on the<br />
function for which the new key pair and certificate are to be employed (also see section 3.4 for<br />
how the certificate content varies according to function).<br />
• An authentication key pair is generated in the <strong>AOL</strong> Token and a certificate is issued<br />
for the new public key when the participating <strong>Member</strong> sets up a new authentication<br />
capability. The certificate may be either a Screen Name authentication certificate or<br />
a full name authentication certificate (sections 3.4.2-3.4.3).<br />
• When the participating <strong>Member</strong> sets up a new encryption capability, an <strong>AOL</strong>CA<br />
generates a new encryption key pair and retains a backup copy of the private key in<br />
case the <strong>Member</strong> loses theirs (section 4.3.3). An encryption certificate is issued for<br />
the new public key, and the certificate and private key are inserted into the<br />
<strong>Member</strong>’s <strong>AOL</strong> Token.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
• An identification key pair is generated in a controlled environment manually. The<br />
certificate signing request is manually verified and approved by two authorized<br />
AMSPKI personnel, and the signed certificate returned to the requester.<br />
In all cases, a new key pair is generated and a certificate issued. For all but identification<br />
certificates, the whole process typically lasts less than a minute depending on the bandwidth of<br />
the participant’s network connection. The following subsections describe each of these<br />
processes in detail.<br />
4.2.1.1. Key Generation and Device <strong>Certification</strong> for <strong>AOL</strong> Tokens<br />
Each <strong>Member</strong> participating in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI has an <strong>AOL</strong> Token, which secures<br />
critical <strong>com</strong>munications between the <strong>Member</strong> and the <strong>AOL</strong> system. A <strong>Member</strong> or prospective<br />
<strong>Member</strong> can receive an <strong>AOL</strong> Token in a variety of ways; the distribution of unactivated <strong>AOL</strong><br />
Tokens is a promotional issue.<br />
Until activated, <strong>AOL</strong> Tokens have only a potential security function in the <strong>AOL</strong> system. Each <strong>AOL</strong><br />
Token must be activated before it can be used. Activation includes a symmetric key exchange,<br />
an initial public/private key generation, and certification for the <strong>AOL</strong> Token. (As distributed, the<br />
manufacturer installs a unique symmetric key to secure the <strong>AOL</strong> Token. In the activation process<br />
a new symmetric key, not known to the manufacturer, is generated by an <strong>AOL</strong>CA to replace the<br />
previous key.)<br />
To activate a new <strong>AOL</strong> Token, the <strong>Member</strong> inserts it into the appropriate port of their <strong>com</strong>puter,<br />
as directed, and connects to the <strong>AOL</strong> system. The following then occur:<br />
(1) The <strong>AOL</strong> system detects the presence of an unactivated <strong>AOL</strong> Token.<br />
(2) The <strong>AOL</strong> Token establishes a secure channel between itself and the <strong>AOL</strong> system. If a<br />
<strong>Member</strong> is already logged into <strong>AOL</strong>, their current <strong>AOL</strong> session information is recorded.<br />
(3) Following an instruction from the <strong>AOL</strong> system, the <strong>AOL</strong> Token generates a public and<br />
private key pair and stores the private key. The <strong>AOL</strong> Token then sends a copy of the<br />
public key to the <strong>AOL</strong> system.<br />
(4) The <strong>AOL</strong> system forwards the public key to an <strong>AOL</strong>CA, which issues a certificate listing<br />
the key. The certificate satisfies the content specifications for a device authentication<br />
certificate (section 3.4.1). To issue the certificate, the <strong>AOL</strong>CA obtains additional data<br />
from the <strong>AOL</strong> Token and the <strong>AOL</strong> system as necessary for the content of the certificate,<br />
creates a certificate in the required form, encodes it as required by [ITU-T X.690], and<br />
digitally signs it using one of the <strong>AOL</strong>CA’s private keys.<br />
(5) The <strong>AOL</strong>CA inserts the certificate into the subject’s <strong>AOL</strong> Token via a secure channel<br />
through the <strong>AOL</strong> system.<br />
(6) If a <strong>Member</strong> is already logged into <strong>AOL</strong>, the <strong>AOL</strong>CA stores a copy of the certificate in<br />
the <strong>AOL</strong> system, which extracts the public key from the certificate and stores it in the<br />
<strong>Member</strong>’s account file along with its expiration date (the date in the certificate’s<br />
validity:notAfter field). The <strong>AOL</strong> system may take further actions to record activation of<br />
the <strong>AOL</strong> Token or the start of <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services (if this <strong>AOL</strong> Token is<br />
the first activated for the account).<br />
(7) The <strong>AOL</strong> system notifies the Subject that the <strong>AOL</strong> Token is activated.<br />
4.2.1.2. Key Generation and <strong>Certification</strong> for Authentication<br />
To set up a new authentication capability (key pair and certificate), a participating <strong>Member</strong> must<br />
be authenticated to the <strong>AOL</strong> system over a secure channel and the <strong>AOL</strong> Token must be<br />
connected to the <strong>Member</strong>’s <strong>com</strong>puter. When the <strong>Member</strong> requests the <strong>AOL</strong> system to set up a<br />
new authentication capability through the account maintenance interface in the <strong>AOL</strong> client<br />
software, the following occurs:<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
(1) If the <strong>AOL</strong> Token was not previously activated, a new symmetric key is installed to<br />
replace the symmetric key shared by the manufacturer.<br />
(2) Following an instruction from the <strong>AOL</strong> system, the <strong>AOL</strong> Token generates a new key<br />
pair. On <strong>com</strong>pletion of that key generation, the <strong>AOL</strong> Token stores the private key<br />
securely without ever exposing it outside the <strong>AOL</strong> Token. The <strong>AOL</strong> Token transmits a<br />
copy of the public key to the <strong>AOL</strong> system via a secure channel.<br />
(3) On receipt of the public key, the <strong>AOL</strong> system forwards it to an <strong>AOL</strong>CA, which issues a<br />
certificate containing the public key. The other content of the certificate is as specified<br />
for either a Screen Name or full name authentication certificate (section 3.4). To issue<br />
the certificate, the <strong>AOL</strong>CA obtains additional data from the <strong>AOL</strong> Token and the <strong>AOL</strong><br />
system as necessary for the content of the certificate, creates a certificate in the<br />
required form, encodes it as required by [ITU-T X.690], and digitally signs it using one of<br />
the <strong>AOL</strong>CA’s private certification keys.<br />
(4) The <strong>AOL</strong>CA inserts the certificate into the subject’s <strong>AOL</strong> Token via a secure channel<br />
through the <strong>AOL</strong> system. This causes the <strong>AOL</strong> Token to activate the private key, which<br />
has not been available for use until now.<br />
(5) The <strong>AOL</strong>CA stores a copy of the certificate in the <strong>AOL</strong> system.<br />
(6) The <strong>AOL</strong> system notifies the <strong>Member</strong> that the new authentication capability is ready for<br />
use, as requested.<br />
(7) The <strong>AOL</strong> system marks the <strong>AOL</strong> Token as “activated” and available for use, if not<br />
previously activated.<br />
4.2.1.3. Key Generation and <strong>Certification</strong> for Encryption<br />
To set up a new encryption capability (key pair and certificate), a participating <strong>Member</strong> must<br />
already have an activated <strong>AOL</strong> Token <strong>com</strong>plete with an authentication certificate and key pair.<br />
The <strong>Member</strong> also must have logged into the <strong>AOL</strong> system via a secure channel. Then, when the<br />
<strong>Member</strong> requests the <strong>AOL</strong> system to set up a new encryption capability through the account<br />
maintenance interface in the <strong>AOL</strong> client software, the following occur:<br />
(1) The <strong>AOL</strong>CA generates a key pair for the participating <strong>Member</strong> using a hardware<br />
security module that conforms to the specifications for level three of [FIPS 140-2]. The<br />
hardware security module encrypts the private key as soon as it is generated.<br />
(2) For the key recovery purposes explained in section 04.3.3 below, the <strong>AOL</strong>CA stores an<br />
encrypted copy of the private key in a secure database reserved for such keys.<br />
(3) The <strong>AOL</strong>CA issues a certificate listing the new public key with the content specified for<br />
an encryption certificate in section 3.4.4. To issue the certificate, the <strong>AOL</strong>CA obtains<br />
the additional data required for the certificate from the <strong>AOL</strong> system, creates a certificate<br />
in the required form, encodes it as required by [ITU-T X.690], and digitally signs the<br />
certificate using one of the <strong>AOL</strong>CA’s private certification keys.<br />
(4) The <strong>AOL</strong>CA inserts the private key and the certificate (including the public key) into the<br />
subject’s <strong>AOL</strong> Token via a secure channel through the <strong>AOL</strong> system.<br />
(5) The <strong>AOL</strong>CA stores a copy of the certificate on the <strong>AOL</strong> system.<br />
(6) The <strong>AOL</strong> system notifies the <strong>Member</strong> that the new encryption capability is ready for<br />
use.<br />
4.2.1.4. Key Generation and <strong>Certification</strong> for Identification<br />
To set up a new identification capability, a participating <strong>Member</strong> must be an active employee for<br />
<strong>AOL</strong> or one of its agents. This process is manual and occurs with the following steps:<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
(1) Following an instruction from the AMSPKI staff, an authorized agent from the<br />
organizational entity generates a public/private key pair in a controlled environment that<br />
meets or exceeds the re<strong>com</strong>mended security stance for <strong>AOL</strong> <strong>com</strong>puting devices.<br />
(2) The public key is submitted in PKCS#10 format to the AMSPKI staff along with<br />
identifying information for the requester and the certificate’s subject name.<br />
(3) An AMSPKI staff member verifies the request via the following methods:<br />
i. The public key is verified with the requester by manually <strong>com</strong>paring MD5, SHA1<br />
or similar “fingerprints”.<br />
ii.<br />
iii.<br />
iv.<br />
The requester’s employment status is confirmed using authoritative employment<br />
databases and other methods.<br />
Business purpose for the certificate is reviewed and evaluated for<br />
appropriateness.<br />
If the request meets these and any other applicable guidelines, the request is<br />
approved and the resulting certificate is returned to the original requester.<br />
4.2.1.5. Replacing a Key Pair and <strong>Certificate</strong><br />
Replacement of an authentication key pair and certificate (as distinct from their renewal described<br />
in section 4.2.2 occurs by means of the same processes for generating new key pairs and issuing<br />
new certificates. The replacement keys and certificate overwrite their older counterparts in the<br />
<strong>AOL</strong> Token and the <strong>AOL</strong> system unless the certificate and key pair are for encryption capabilities<br />
as indicated by the keyUsage field of the certificate.<br />
Private keys used to decrypt data are not automatically overwritten when a new encryption<br />
certificate is issued. Instead, they remain stored and usable in the participating <strong>Member</strong>’s <strong>AOL</strong><br />
Token after the certificate expires so that previously encrypted data can still be decrypted.<br />
However, the number of private decryption keys that can remain on the <strong>AOL</strong> Token is limited by<br />
its storage capacity, which is affected by the requirements placed on the <strong>AOL</strong> Token as a whole.<br />
If an old private decryption key is overwritten, it can be recovered as specified in section 4.3.3.<br />
Replacement of an identification key pair and certificate is initiated by a request from an<br />
authorized agent. The replacement process followed is the issuance process in section 4.2.1.4.<br />
4.2.2. Expiration and Renewal of an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
Capability<br />
Expiration of a digital authentication or encryption capability occurs automatically when the date<br />
arrives that is listed in the certificate’s validity:notAfter field (unless it is revoked previously). Most<br />
applications will not use the key pair after its certificate expires, at least not without returning an<br />
error message (see section 4.2.4 for the effect of expiration on subsequent verifications).<br />
The <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI does not require participants to track the expiration dates of their<br />
certificates and request new ones before their existing certificates expire. Instead, the <strong>AOL</strong><br />
system automatically informs participating <strong>Member</strong>s of an impending expiration of Screen Name<br />
authentication, Full Name authentication, and Basic encryption certificates. In general, these<br />
certificates are not renewed. They are replaced with new certificates and key pairs when<br />
necessary. To permit a smooth transition between certificates, participating <strong>Member</strong>s are<br />
informed ahead of time and instructed on how to “reactivate” their <strong>AOL</strong> Token4.2.1.4.<br />
When a certificate <strong>com</strong>es within 60 days (and 10 days) of its expiration<br />
(1) the <strong>AOL</strong> system sends a message to the participating <strong>Member</strong> (as identified by their<br />
email address or Screen Name in the affected certificate). This message provides<br />
further directions on how to replace the information on their <strong>AOL</strong> Token before it<br />
expires. As a result of that process, the <strong>AOL</strong> system replaces the certificate and key<br />
pair as described in section 4.2.1.5.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
(2) The participating <strong>Member</strong> retains overall control whether to continue the digital<br />
authentication or encryption capability in operation (see section 4.1).<br />
Identification certificates are not renewed. Requesters must follow the issuance process for<br />
replacement identification certificates (see section 4.2.1.4).<br />
4.2.3. Revocation of an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Capability<br />
A participating <strong>Member</strong> can abruptly terminate an <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI capability by having<br />
the <strong>AOL</strong>CA that issued the corresponding certificate revoke it. An <strong>AOL</strong>CA revokes a certificate<br />
that it has issued whenever one of the following events occurs:<br />
• Request to <strong>AOL</strong> <strong>Member</strong> Services or Other Administrative Centers<br />
(Applicable to all <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificate types): A <strong>Member</strong><br />
Services or other appropriately authorized staff member will cause the <strong>AOL</strong>CA to<br />
revoke a participating <strong>Member</strong>’s certificate after identifying the <strong>Member</strong> as<br />
described in section 3.5.1. The <strong>Member</strong> must also establish that he controls the<br />
primary Screen Name of the account or the Screen Name listed in the certificate to<br />
be revoked.<br />
• Updating <strong>AOL</strong> records online via client interface (Applicable to Device<br />
Authentication certificates only): The primary Screen Name can revoke any<br />
certificate in the account, or the Screen Name listed in a certificate can revoke it,<br />
using the account management functionality of the <strong>AOL</strong> system client. Transportlayer<br />
security between the client and the <strong>AOL</strong> system secures the <strong>com</strong>munications<br />
channel between them. 17<br />
The <strong>AOL</strong>CA also revokes the certificate if the participant notifies <strong>AOL</strong> to terminate <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI services, if the participant ceases to be a <strong>Member</strong> of <strong>AOL</strong>, or if <strong>AOL</strong> requests<br />
revocation of a certificate for any reason. Moreover, if the <strong>AOL</strong>CA that issued a certificate has<br />
reason to doubt its reliability, it may revoke the certificate at its discretion, and may notify the<br />
subject before doing so except in an emergency.<br />
Revoking a certificate invalidates the corresponding digital authentication or encryption capability.<br />
However, tracking down and erasing every copy of the certificate, wherever it has circulated, is<br />
infeasible. In principle, revocation renders inoperative the cryptographic keys and algorithms that<br />
are the core of the authentication or encryption capability, although in practice, software<br />
applications can stop using the keys only if they discover the revocation. Because the technical<br />
basis of a digital authentication or encryption capability persists despite revocation of the<br />
underlying certificate, revocation is actually just a declaration by the <strong>AOL</strong>CA that the public key<br />
certificate underlying the capability is no longer reliable. If a prospective relying party is notified of<br />
that declaration, s/he can avoid relying on a capability that has be<strong>com</strong>e unsound. As a practical<br />
matter then, the effectiveness of revocation in preventing misplaced reliance depends on notice<br />
to a relying party that a certificate is revoked. 18<br />
<strong>AOL</strong>CAs notify participants 19 of certificate revocation by including in each certificate a reference<br />
to a certificate revocation list, 20 which is a list of certificates revoked within a time period specified<br />
17 Device authentication certificates for <strong>AOL</strong> Tokens are not revoked. <strong>AOL</strong> Token certificates can be<br />
unbound from a particular <strong>Member</strong> account by <strong>AOL</strong> <strong>Member</strong> Services staff. <strong>Member</strong> Services also keeps a<br />
list of lost or stolen keys, which are not bound to active accounts.<br />
18 Revocation, or the lack of it, is not implicit or to be inferred from actions taken for another purpose. For<br />
example: sending or receiving digitally signed e-mail via <strong>AOL</strong> does not indicate that the relevant certificate is<br />
necessarily valid. The only valid and reliable notice of revocation is the one posted at the point listed in the<br />
CRLdistributionPoints field.<br />
19 RAs, if used, are not typically notified upon revocation of a certificate submitted through an RA.<br />
20 The reference to the <strong>Certificate</strong> Revocation List relevant to a given certificate is found in the<br />
CRLdistributionPoints field of that certificate. That field contains a URL pointing to a site from which a<br />
participant can retrieve the relevant certificate revocation list via HTTP. Retrieval and processing of the<br />
certificate revocation list is handled automatically by most software.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
in the list. The form of the list is standardized in [ITU-T X.509] and [RFC 3280], and lists issued<br />
by <strong>AOL</strong>CAs conform to those standards. The fields in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificate<br />
revocation lists are the following, beginning at the TBSCertList level:<br />
Field Name Critical? Data Content Significance<br />
version n/a V2 only (indicated by the<br />
integer “1”)<br />
Indicates the version of [ITU-T<br />
X.509] to which the certificate<br />
revocation list (CRL) conforms.<br />
signature n/a Same as specified for certificates in section 3.3.3.<br />
issuer n/a The distinguished name of<br />
the issuer of the revoked<br />
certificate specified according<br />
to section 3.3.2<br />
ThisUpdate n/a A date and time specified<br />
according to section 5.1.2.4<br />
of [RFC 3280] (i.e. in<br />
UTCtime)<br />
NextUpdate n/a A date and time specified<br />
according to section 5.1.2.5<br />
of [RFC 3280] (i.e. in<br />
UTCtime). Except for device<br />
authentication certificates, the<br />
time indicated may be from<br />
24 to 72 hours from the time<br />
listed in ThisUpdate<br />
Revoked<strong>Certificate</strong>s n/a If present, this field contains<br />
the following subfields:<br />
user<strong>Certificate</strong> contains a<br />
subfield containing an integer<br />
revocationDate contains a<br />
date and time specified as<br />
UTCtime<br />
authorityKeyIdentifier No The subfield keyIdentifier<br />
contains the SHA-1 hash of<br />
the public key by which the<br />
issuer’s signature on the CRL<br />
can be verified.<br />
CRLnumber No A long integer not exceeding<br />
20 octets in length.<br />
Identifies the <strong>AOL</strong>CA that issued<br />
the CRL (and the revoked<br />
certificate).<br />
The date and time when the<br />
certificate revocation list was<br />
issued.<br />
Except for device authentication<br />
certificates, 21 the latest date and<br />
time when the issuer anticipates<br />
issuing an update to the current<br />
CRL. Updated CRLs may be<br />
issued sooner, however.<br />
If this field is present,<br />
user<strong>Certificate</strong> indicates the<br />
serial number of the unexpired,<br />
revoked certificate and<br />
revocationDate i.e. the time when<br />
the certificate was revoked.<br />
If this field is absent in a<br />
particular certificate revocation<br />
list (CRL), 22 a user can infer that<br />
no certificates have been revoked<br />
as of the issue date of the CRL,<br />
unless the certificate is a device<br />
authentication certificate (see<br />
below in this section).<br />
Indicates which public key to use<br />
in verifying the authenticity of the<br />
certificate.<br />
The serial number of this CRL in<br />
an incrementally increasing<br />
sequence of CRLs.<br />
<strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificate revocation lists do not expressly list this CP/CPS but it<br />
nevertheless applies to every certificate revocation list issued by an <strong>AOL</strong>CA.<br />
21 As explained elsewhere in this section, notice of revocation for device authentication certificates is posted<br />
directly to <strong>AOL</strong> <strong>Member</strong> records. The certificate revocation list for such certificates is therefore empty and<br />
not updated. The NextUpdate field in that list is included in order to conform to [RFC 3280] but is left blank.<br />
22 CRLs are ordinarily issued as a result of batch processes, and <strong>AOL</strong>CAs run the CRL-producing batch<br />
process once every 24 hours (see NextUpdate), but may augment the NextUpdate interval by as much as<br />
72 hours. If no certificates have been revoked, this field will be absent as required in section 5.1.2.6 of<br />
[RFC 3280].<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
All certificate revocation lists in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are cumulative; i.e. they list every<br />
unexpired certificate revoked to date by the <strong>AOL</strong>CA that issued them.<br />
Device authentication certificates are an exception to this section. No certificate revocation list is<br />
published for them; instead notice is given directly to the only party in a position to rely on them,<br />
and that is <strong>AOL</strong>. Device authentication certificates are used only by <strong>AOL</strong> and only to log in a<br />
participant <strong>Member</strong> securely between their <strong>AOL</strong> Token and the <strong>AOL</strong> system. Consequently, the<br />
only persons legitimately 23 involved in the use of device authentication certificates are the<br />
<strong>Member</strong> and <strong>AOL</strong>. Because <strong>AOL</strong> uses the certificate to identify the <strong>Member</strong>’s <strong>AOL</strong> Token, <strong>AOL</strong><br />
is the only party that relies on device authentication certificates. Instead of publishing revocation<br />
of device authentication certificates on a certificate revocation list, <strong>AOL</strong>, as the sole relying party,<br />
uses a more efficient means: It removes the public key listed in the certificate from the<br />
participant’s <strong>Member</strong> records. 24 The <strong>AOL</strong>CA foregoes giving notice to <strong>AOL</strong> because the point of<br />
the notice has already been served by removal of the public key from the account records.<br />
The <strong>com</strong>plete revocation process (from initial request through to publication of notice) may take<br />
up to 24 hours. The certificate remains valid until the <strong>AOL</strong>CA <strong>com</strong>pletes its revocation.<br />
For all <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI certificates on which a participant can rely, notice of revocation<br />
in the form of a certificate revocation list will be publicly available, even to nonparticipants. Where<br />
<strong>AOL</strong> is the only relying party (e.g.as in the case of device authentication certificates or, where use<br />
of a certificate is solely for use in network access control), notification of revocation is handled<br />
internally and publication of a certificate revocation list would serve no useful purpose.<br />
4.2.4. Timing of Verification and <strong>Certificate</strong> Invalidation<br />
Applications verifying digital signatures ordinarily return an error message to the user if the<br />
relevant certificate is invalid (expired or revoked) when verification occurs. When reliance on a<br />
digital signature occurs is a legal question that depends on the facts and circumstances of a<br />
specific case. If a certificate was valid when a person relied on it, its subsequent invalidation may<br />
be immaterial under applicable law. Legal advice may be informative should such questions<br />
arise.<br />
However, regardless of when reliance occurs or occurred, digital authentication applications vary<br />
in whether they can verify or re-verify a digital signature retrospectively, i.e. as of a time other<br />
than the current time according to the system clock at the moment when the verification function<br />
is run. Most client applications, including <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI, do not currently provide<br />
functionality enabling retrospective verification without changing the system clock to that earlier<br />
time.<br />
Ordinarily (absent a revocation), <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI minimizes this problem by renewing<br />
or replacing a certificate at least 60 days before it expires, which means it remains valid but<br />
unused for the remaining days. During that period, verification by reference to a valid certificate<br />
is still possible.<br />
To prevent inconvenience to relying parties, it is advisable in normal circumstances to let a<br />
certificate expire rather than revoke it when discontinuing an authentication capability. That<br />
leaves prospective relying parties a grace period during which they can still verify or re-verify a<br />
digital signature. However, in the event of a private key security <strong>com</strong>promise (such as loss of the<br />
<strong>AOL</strong> Token housing those private keys), revocation is advisable despite any inconvenience it may<br />
cause.<br />
23 As always, intruders cannot be fully ruled out. The <strong>AOL</strong> system includes technology to prevent intrusive<br />
access. To help prevent intrusion by impersonating a <strong>Member</strong>, <strong>Member</strong>s are advised to keep login<br />
information confidential and keep their <strong>AOL</strong> Tokens away from persons who could use them in unauthorized<br />
ways.<br />
24 A certificate revocation list is posted for device authentication certificates, but this list should not be relied<br />
upon by Participants. Device authentication certificates may nevertheless be revoked (for example in cases<br />
where the certificate was erroneously issued or if the public key or device is known to be <strong>com</strong>promised), but<br />
currently the only foreseeable relying party (<strong>AOL</strong>) handles this case itself, as explained in the main text.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
These timing issues do not arise in relation to encryption certificates because of differences in<br />
their use and storage; see section 4.2.1.4.<br />
4.2.5. Archiving and Record Retention of <strong>Certificate</strong>s<br />
Section 4.2.1 describes how long a certificate is stored in the <strong>Member</strong> records of the <strong>AOL</strong> system.<br />
In general, a certificate is in those records only so long as it is valid and the corresponding private<br />
key is in use by the <strong>Member</strong>.<br />
Each <strong>AOL</strong>CA archives a copy of the certificate and retains that copy in accordance with the<br />
record retention policies governing <strong>AOL</strong>.<br />
Section 3.5.2 covers the retention of information confirming certificate content.<br />
4.3. Key Management, Distribution, and Recovery<br />
In general, <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI handles cryptographic keys automatically and without<br />
involving the <strong>Member</strong>. This section summarizes the main points of the behind-the-scenes key<br />
processes.<br />
4.3.1. Public Keys and their <strong>Certificate</strong>s<br />
All public keys are encapsulated in a certificate shortly after they are generated. Thereafter, a<br />
public key’s lifecycle is that of its certificate and the two are ordinarily not separated. For Device<br />
authentication certificates, some <strong>AOL</strong> systems may store the associated public key without its<br />
certificate wrapping to expedite reference, but they nevertheless keep it in active use only as long<br />
as its certificate is valid.<br />
<strong>AOL</strong> and <strong>AOL</strong>CAs do not currently offer public directory or repository services or other means of<br />
distributing certificates and public keys to anyone who may be interested, although the <strong>AOL</strong><br />
system provides them to participating <strong>Member</strong>s as needed. For example, a <strong>Member</strong> can obtain<br />
another <strong>Member</strong>’s certificate in order to use the public key in it to encrypt data to be sent to that<br />
<strong>Member</strong> or to verify that <strong>Member</strong>’s digital signature. The <strong>AOL</strong> system and its client software<br />
perform that certificate retrieval automatically for <strong>Member</strong>s using <strong>AOL</strong> software.<br />
4.3.2. Private Authentication Keys<br />
In the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI, all participating <strong>Member</strong>s’ private keys used for authentication<br />
according to the corresponding certificate are stored in the <strong>AOL</strong> Token. The <strong>AOL</strong> Token also<br />
generates all private authentication keys. The <strong>AOL</strong> system or an <strong>AOL</strong>CA does not copy or<br />
expose a private authentication key outside of the <strong>AOL</strong> Token in which it was generated. <strong>AOL</strong><br />
Tokens conform to [GP KMS Requirements] and [GP Card Specification] in the security they<br />
provide for private keys.<br />
The <strong>AOL</strong> system overwrites an old private authentication key in the <strong>AOL</strong> Token with a new one<br />
when the corresponding certificate is replaced as described in section 4.2.1.4, but not when it is<br />
renewed as described in section 4.2.2. In either case, private keys that are to be<strong>com</strong>e disused<br />
are not left to clutter the <strong>AOL</strong> Token and pose a risk of improper use.<br />
The <strong>AOL</strong> system has no means to recover or destroy a <strong>Member</strong>’s lost or stolen private<br />
authentication keys. For that reason, it is advisable to keep the <strong>AOL</strong> Token secure and not to<br />
disclose the information necessary to access and use the private keys stored in it. If it is lost, or if<br />
a private key stored on it is divulged, the certificates of the <strong>com</strong>promised private key(s) can be<br />
revoked so as to minimize any harm that might otherwise arise through reliance on an<br />
authentication capability that has be<strong>com</strong>e unsound.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
4.3.3. Private Encryption Keys and their Recovery<br />
A private key certified for use with encryption decrypts data that has been encrypted using the<br />
corresponding public key. Without that private key, data encrypted using the public key may well<br />
not be recoverable by any practicable or cost-effective means available to the would-be user of<br />
the data.<br />
To prevent data loss through private key errors, 25 each <strong>AOL</strong>CA retains a backup copy of each<br />
private encryption key that it generates (section 4.2.1.3). It stores the backup copy only in<br />
encrypted form. The <strong>AOL</strong>CA does not disclose a private encryption key from its backup database<br />
except:<br />
• Pursuant to a request to restore the key by the participating <strong>Member</strong> listed as the<br />
subject of the corresponding certificate, and then only after the <strong>Member</strong> identifies<br />
him or herself as specified in section 3.5.1. If <strong>AOL</strong> confirms the subject’s<br />
identification (section 3.5.1) and the authenticity of the request, the <strong>AOL</strong>CA restores<br />
the key to the subscribing <strong>Member</strong> via a secure method through the <strong>AOL</strong> system.<br />
• As ordered by a governmental authority (such as a court) which <strong>AOL</strong> reasonably<br />
believes to have jurisdiction, or as otherwise required by applicable law. See<br />
Appendix A for jurisdiction-specific information.<br />
<strong>AOL</strong> and <strong>AOL</strong>CAs perform no backup of private authentication keys generated on <strong>AOL</strong> Tokens.<br />
4.3.4. Private Identification Keys<br />
In the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI, identification private keys are manually generated by the<br />
requester. As such, the control and oversight for these keys is beyond that of the <strong>AOL</strong> system.<br />
The <strong>AOL</strong> system has no means to recover or destroy a lost or stolen private identification key.<br />
For that reason, it is advisable to keep the file system containing the private identification key<br />
secure and access controls established such that it cannot be disclosed inappropriately. The<br />
identification private key must also be protected by a strong passphrase in case it is stolen. If it is<br />
stolen or copied or the passphrase revealed to unauthorized persons, the certificates of the<br />
<strong>com</strong>promised private key(s) must be revoked so as to minimize any harm that might otherwise<br />
arise through reliance on an identification capability that has be<strong>com</strong>e unsound.<br />
5. <strong>Certification</strong> Operations<br />
The quality, availability, and other aspects of the service that <strong>AOL</strong> and an <strong>AOL</strong>CA provide in<br />
relation to <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI are covered in contracts with each participant. To the<br />
extent that <strong>AOL</strong> provides certification services for participants (i.e. acts as their <strong>AOL</strong>CA), those<br />
services may be covered in the <strong>Member</strong> Agreement or participating nonmember agreement.<br />
Participating nonmembers enter into an online contract when they begin participating as relying<br />
parties and install <strong>AOL</strong> root certificate(s) in their operating system.<br />
5.1. <strong>Security</strong> and Soundness of Operations<br />
<strong>AOL</strong> and <strong>AOL</strong>CAs endeavor to operate according to the generally accepted practices and<br />
procedures in the Internet service industry. More specifically, they substantially <strong>com</strong>ply with the<br />
following standards in relation to the security and soundness of their operations:<br />
• [Webtrust ® Criteria];<br />
25 In some jurisdictions, government regulations may require <strong>AOL</strong> to retain a backup copy of a private<br />
encryption key.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
• [GP Card Specification];<br />
• [GP Functional Requirements]; and<br />
• [GP KMS Requirements].<br />
<strong>AOL</strong> and <strong>AOL</strong>CA operations are thoroughly documented for internal purposes, but that<br />
documentation is proprietary and confidential. All critical CA operations take place within a<br />
physically secure facility with at least four layers of security to access sensitive hardware or<br />
software. Such systems are physically separated from the organization’s other systems so that<br />
only authorized employees of the CA can access them. Physical access to the CA systems is<br />
strictly controlled. Only trustworthy individuals with a valid business reason are provided such<br />
access.<br />
All CA systems have industry standard power and air conditioning systems to provide a suitable<br />
operating environment. All CA systems have reasonable precautions taken to minimize the<br />
impact of water exposure. All CA systems have industry standard fire prevention and protection<br />
mechanisms in place.<br />
Off-site backups are stored in a physically secure manner by a bonded third-party storage facility.<br />
Media storage under the control of the CA is subject to the normal media storage requirements of<br />
the <strong>com</strong>pany.<br />
Waste is disposed of in accordance with the organization’s normal waste disposal requirements.<br />
Cryptographic devices are physically destroyed or securely zeroized in accordance with the<br />
manufacturers’ guidance prior to disposal.<br />
As part of the CA’s scheduled system backup procedures, audit trail files are backed up on at<br />
least a daily basis. Audit trail files are archived on a weekly basis.<br />
Disaster Recovery and Business Continuity plans are tested and reviewed at least annually. The<br />
<strong>AOL</strong>CA has a business continuity plan to restore the CA’s business operations in a reasonably<br />
timely manner following interruption to, or failure of, critical business processes. The CA’s<br />
business continuity plan defines 24 hours as an acceptable system outage time in the event of a<br />
natural disaster or CA private key <strong>com</strong>promise. The <strong>AOL</strong>CA maintains a recovery site located<br />
approximately 20 miles from the CA’s primary site. Backups of critical system information and<br />
audit logs are performed daily, and event journals are reviewed at least on a bi-monthly basis.<br />
5.2. Termination of CA<br />
An <strong>AOL</strong>CA may terminate its operations at the direction of the <strong>AOL</strong> <strong>Policy</strong> Management Authority.<br />
(PMA) In the event the CA is terminated, all certificates issued under the CA will be revoked and<br />
the CA will cease to issue certificates. The CA will provide no less than one month’s notice to all<br />
<strong>AOL</strong> business units utilizing the services of the CA. Upon termination the records of the CA will<br />
be archived and transferred to a specified custodian.<br />
5.3. Audits<br />
An <strong>AOL</strong>CA may choose to be certified by independent third parties as conforming to Webtrust ®<br />
for <strong>Certification</strong> Authorities. In these cases, periodic audits ensure the <strong>AOL</strong>CA’s continuing<br />
conformity to the [Webtrust ® Criteria] of the American Institute of certified Public Accountants and<br />
the Canadian Institute of Chartered Accountants. The [Webtrust ® Criteria] specify the frequency<br />
and other requirements for periodic audits. This report is made available to the PMA and the<br />
<strong>AOL</strong>CA’s management. If significant deficiencies are reported in an audit, the PMA will direct the<br />
<strong>AOL</strong>CA management to address these deficiencies within 60 days of notice.<br />
Auditors have access to internal documentation as needed for the audit and subject to<br />
agreements governing their services.<br />
<strong>AOL</strong>CAs not conforming to Webtrust ® for <strong>Certification</strong> Authorities criteria must still substantially<br />
adhere to the WebTrust audit criteria but are not subject to independent audit. These CAs will<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
provide periodic audit reports to the PMA and <strong>AOL</strong>CA management. If significant deficiencies are<br />
reported in an audit, the PMA will direct the <strong>AOL</strong>CA management to address these deficiencies<br />
within 60 days of notice.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
6. Amendment and Review of this CP/CPS<br />
<strong>AOL</strong> has adopted this CP/CPS through its PKI <strong>Policy</strong> Management Authority. It is under<br />
continuous review as <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI develops and is subject to amendment by the<br />
PKI <strong>Policy</strong> Management Authority. For contractual purposes, changes in this CP/CPS are<br />
changes in the specifications of a service provided by <strong>AOL</strong>.<br />
Some changes to this CP/CPS may be deemed by the <strong>AOL</strong> PMA to have minimal or no impact<br />
on participants. Such changes may be made without changing the revision number of this<br />
CP/CPS. Changes to this document deemed by the <strong>AOL</strong> PMA to have significant impact on the<br />
participants of the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI may be made with 45 days notice and a<br />
corresponding change in version number for this CP/CPS. Such changes will be publicly posted<br />
to the <strong>AOL</strong>MSPKI website.<br />
Any notices or correspondence relative to this CP/CPS may be sent to the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong><br />
PKI Administrator by email (pki-info@aol.net) or postal mail:<br />
PKI <strong>Policy</strong> Management Authority<br />
C/O Operations <strong>Security</strong><br />
<strong>AOL</strong> LLC<br />
12100 Sunrise Valley Drive<br />
Reston, VA 20191<br />
7. Miscellaneous Provisions<br />
a. Choice of Law and Forum. The laws of the Commonwealth of Virginia, excluding<br />
its conflicts-of-law rules, govern this CP/CPS. Participants (“you”) expressly agree<br />
that exclusive jurisdiction for any claim or dispute with <strong>AOL</strong> or relating in any way to<br />
this CP/CPS or <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services resides in the courts of Virginia,<br />
and you further agree and expressly consent to the exercise of personal jurisdiction<br />
in the courts of Virginia in connection with any such dispute or claim. The foregoing<br />
provision may not apply to you depending on the laws of your jurisdiction. This<br />
CP/CPS shall not be governed by the United Nations Convention on Contracts for<br />
the International Sale of Goods.<br />
b. Severability. If any term of this CP/CPS is found by a court of <strong>com</strong>petent jurisdiction<br />
to be invalid, illegal or unenforceable, the term shall be construed in a manner<br />
consistent with applicable law to reflect, as nearly as possible, the original meaning of<br />
the provision, and the remainder of the CP/CPS shall be enforced according to its<br />
terms.<br />
c. Survival. Sections 2.3, 3.6, 6, 7, and Appendix A shall survive any expiration or<br />
termination of this CP/CPS.<br />
d. Notices. By affirmatively using any <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service, you consent<br />
to receive all <strong>com</strong>munications, including notices, agreements, legally required<br />
disclosures or other information in connection with any <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
service electronically from <strong>AOL</strong> (collectively, "Notices"). You agree that <strong>AOL</strong><br />
generally can send you electronic Notices by (i) e-mail to your primary email account<br />
(if one has been registered with <strong>AOL</strong>), and/or (ii) by "pop up notice" on an <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI service and/or by (iii) posting the Notices on a main page or<br />
prominent area of the relevant <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI service or this site. Any<br />
notices or correspondence you wish to provide <strong>AOL</strong> relative to this CP/CPS shall be<br />
sent to the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Administrator, as specified in Section 6 above.<br />
e. Entire Agreement. This CP/CPS constitutes the entire and only agreement<br />
regarding your use of <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services, except for any applicable<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
<strong>Member</strong> Agreement or participating nonmember agreement you may choose to enter<br />
with <strong>AOL</strong> which will govern the particular <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services<br />
provided in connection with such <strong>Member</strong> Agreement or participating nonmember<br />
agreement. This CP/CPS supersedes all prior and contemporaneous<br />
representations, agreements and other <strong>com</strong>munications regarding the <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI services. Except as expressly set forth herein, this CP/CPS may not be<br />
amended, modified, or supplemented in any manner, except by a written instrument<br />
signed by an authorized representative of, or otherwise authorized by, <strong>AOL</strong>. No<br />
provision hereof shall be deemed waived (by any act or omission) unless such waiver<br />
is in a writing signed by an authorized representative of <strong>AOL</strong>.<br />
8. Glossary and References<br />
8.1. Definitions<br />
Within this CP/CPS and in any contract, certificate profile, or other document incorporating these<br />
definitions by reference, the following terms have the meanings indicated:<br />
(3) <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI Addendum: The portion of the <strong>Member</strong> Agreement, or<br />
the supplementary agreement with a <strong>Member</strong>, that provides for <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong><br />
PKI services. In the case of a participating nonmember, the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
Addendum is the contract providing for limited reliance services from <strong>AOL</strong>; see section<br />
2.2.1.<br />
(4) <strong>AOL</strong>: See Appendix A.<br />
(5) <strong>AOL</strong>CA: <strong>AOL</strong> in its role as certification service provider for <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI,<br />
as well as any supplier or other entity authorized by <strong>AOL</strong> to perform that role.<br />
(6) <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI: The name for the particular <strong>AOL</strong> system used to enable<br />
certain security-related products and services that rely on the issuance, management<br />
and/or use of digital certificates and other cryptographic capabilities described in this<br />
CP/CPS. See also section 2.1.<br />
(7) <strong>AOL</strong> system: The network and related infrastructure managed and/or operated by or<br />
for <strong>AOL</strong> in order to provide information, entertainment, <strong>com</strong>munications, and<br />
transactional services to <strong>Member</strong>s, including without limitation the <strong>AOL</strong> <strong>Member</strong><br />
<strong>Security</strong> PKI. The <strong>AOL</strong> system also consists of the network and infrastructure used to<br />
extend any such services (or portion thereof) to participating nonmembers, as provided<br />
in section 2.2.1.<br />
(8) <strong>AOL</strong> Token: A device conforming to [GP Card Specification] and manufactured<br />
according to <strong>AOL</strong>’s specifications. Used to generate and store public and private<br />
authentication keys, store certificates, and to establish secure channels. See also<br />
section 2.1.<br />
(9) Bind: In relation to an <strong>AOL</strong> Token and a named <strong>Member</strong> or account, to associate the<br />
<strong>AOL</strong> Token with the <strong>Member</strong> or Account in the <strong>AOL</strong> <strong>Member</strong> records.<br />
(10) <strong>Certificate</strong>: A digital record which:<br />
(a)<br />
(b)<br />
(c)<br />
contains a public key (possibly in a form encoded pursuant to applicable<br />
technical standards),<br />
either lists a subject or refers to a subject listed in other records available to its<br />
issuer, and<br />
is digitally signed by its issuer.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
(11) <strong>Certificate</strong> request: A data record containing information to be included in a<br />
certificate and signed by the subject-to-be of that certificate using the private key<br />
corresponding to the public key to be certified.<br />
(12) <strong>Certificate</strong> Revocation List (CRL): A time-stamped list of revoked certificates that is<br />
digitally signed and published by an <strong>AOL</strong>CA. See section 4.2.3.<br />
(13) Confirm: To substantiate through the exercise of reasonable care the accuracy of a<br />
factual representation to be included in a certificate. See section 3.5.<br />
(14) CP/CPS: This document, which specifies the policies and practices of the public key<br />
infrastructure used in the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI.<br />
(15) Full Name: The legal name by which a participating <strong>Member</strong> may be known. In some<br />
cases this may also be their Common Name.<br />
(16) <strong>Member</strong>: A person or system who has registered to use any service or product<br />
offered through the <strong>AOL</strong> system pursuant to a <strong>Member</strong> Agreement. A “participating<br />
<strong>Member</strong>” is a <strong>Member</strong> in one or more <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services.<br />
(17) <strong>Member</strong> Agreement: A written contract establishing the terms and conditions under<br />
which a user may obtain access to and/or use any product or service offered through<br />
the <strong>AOL</strong> system. Separate <strong>Member</strong> Agreements may apply to separate products and<br />
services.<br />
(18) Participant: Either:<br />
(a)<br />
(b)<br />
A <strong>Member</strong> of an <strong>AOL</strong> <strong>Member</strong> PKI <strong>Security</strong> service, or<br />
A participating nonmember.<br />
(19) Participating nonmember: A person who is authorized to rely on one or more<br />
certificates issued by an <strong>AOL</strong>CA pursuant to a participating nonmember agreement,<br />
but who is not authorized under such agreement to have certificates issued listing that<br />
person as a subject. See section 2.2.1.<br />
(20) Participating nonmember agreement: A written contract establishing the terms and<br />
conditions under which a user is given the limited authorization to rely on one or more<br />
certificates issued by an <strong>AOL</strong>CA to a <strong>Member</strong>, but that does not establish any right to<br />
have certificates issued on such user’s behalf.<br />
(21) Primary Screen Name: The Screen Name that holds full administrative power over a<br />
<strong>Member</strong> account, without that power being subject to termination or suspension by any<br />
other Screen Name. See <strong>AOL</strong> system documentation on <strong>Member</strong> account<br />
management for more information.<br />
(22) PMA: An acryonym for “<strong>Policy</strong> Management Authority”, the body overseeing overall<br />
management and coordination of <strong>AOL</strong>CA policies. The PMA reviews WebTrust audit<br />
reports and approves changes to CP/CPS documents enforced by <strong>AOL</strong>CAs.<br />
(23) Publish: To make information widely available for reference and retrieval, such as by<br />
posting it on the World Wide Web.<br />
(24) Relying party: A person that receives a certificate identifying a subject and that is in a<br />
position to act in reliance upon that certificate and/or information verified using the<br />
certificate.<br />
(25) Revoke a certificate: To include the certificate in a class of certificates that are no<br />
longer valid regardless of when they expire. See section 4.2.3.<br />
(26) Screen Name: An alphanumeric identifier for a <strong>Member</strong>’s master account or subaccount,<br />
within an <strong>AOL</strong>-controlled domain (e.g., Screen Name@aol.<strong>com</strong>).<br />
(27) Secure channel: A line of digital <strong>com</strong>munication between a <strong>Member</strong>’s activated <strong>AOL</strong><br />
Token and the <strong>AOL</strong> system that is opened and encrypted as specified in [GP Card<br />
Specification].<br />
(28) Subject: A person or device that is the subject of a certificate, i.e. listed in the subject<br />
field of the certificate as described in section 3.3.1.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
(29) Valid certificate: A certificate which, at a given time:<br />
(a) has been issued (section 4.2.1);<br />
(b) has not yet expired as indicated by its validity:notAfter field; and<br />
(c) has not been revoked as specified in section 4.2.3.<br />
8.2. References<br />
[<strong>AOL</strong> Root Certifier CP/CPS]: <strong>AOL</strong> Root Certifier: <strong>Certificate</strong> <strong>Policy</strong> and <strong>Certification</strong> Practice<br />
Statement (2005). This document is adopted and published in cooperation with <strong>AOL</strong> Operations<br />
<strong>Security</strong>.<br />
[FIPS 140-2]: National Institute for Standards and Technology, Federal Information Processing<br />
Standard 140-2: <strong>Security</strong> Requirements for Cryptographic Modules -- 01 May 25<br />
(Supersedes FIPS PUB 140-1, 1994 January 11)<br />
[GP Card Specification]: GlobalPlatform Inc., GlobalPlatform Card Specification version 2.1.1<br />
(March 2003).<br />
[GP Functional Requirements]: GlobalPlatform Inc., Multi Application Smart Card Management<br />
Systems: Functional Requirements version 3.4 (May 2001).<br />
[GP KMS Requirements]: GlobalPlatform Inc., GlobalPlatform Key Management System:<br />
Functional Requirements version 1.0 (November 2003).<br />
[ITU-T X.509]: International Tele<strong>com</strong>munication Union, Information technology - Open Systems<br />
Interconnection - The Directory: Public-key and attribute certificate frameworks version 3 (2000).<br />
[ITU-T X.520]: Information technology - Open Systems Interconnection - The directory: Selected<br />
attribute types (1997).<br />
[ITU-T X.690] Information technology - ASN.1 encoding rules: Specification of Basic Encoding<br />
Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) (2002).<br />
[RFC 822]: D. Crocker, Standard for the Format of ARPA Internet Text Messages (1982).<br />
[RFC 2311] S. Dusse, P. Hoffman, B. Ramsdell, L. Lundblade, L. Repka, S/MIME Version 2<br />
Message Specification (1998).<br />
[RFC 3280]: R. Housley, W. Polk, W. Ford, D. Solo, Internet X.509 Public Key Infrastructure:<br />
<strong>Certificate</strong> and <strong>Certificate</strong> Revocation List (CRL) Profile (2002).<br />
[RFC 3647]: S. Chokhani, W. Ford, R. Sabett, C. Merrill, S. Wu, Internet X.509 Public Key<br />
Infrastructure: <strong>Certificate</strong> <strong>Policy</strong> and <strong>Certification</strong> Practices Framework (2003).<br />
[Webtrust ® Criteria]: American Institute of Certified Public Accountants, Inc. and Canadian<br />
Institute of Certified Public Accountants, Suitable Trust Services Criteria and Illustrations for<br />
<strong>Security</strong> Availability, Processing Integrity, Online Privacy, and Confidentiality (Including Webtrust ®<br />
and SysTrust ® ) version 3.0 (2003).<br />
8.3. Links<br />
Some of the references listed in the foregoing bibliography are available online from the following:<br />
• RFCs: http://www.ietf.org/rfc.html<br />
• ISO standards: http://www.iso.ch/iso/en/ISOOnline.frontpage<br />
• ITU standards: http://www.itu.int/publications/online/index.html<br />
• Global Platform specifications: http://www.globalplatform.org<br />
• Federal Information Processing Standards: http://www.itl.nist.gov/fipspubs/bynum.htm<br />
• Webtrust: http://www.webtrust.org<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Promotional and <strong>com</strong>mercial information about the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI is online at<br />
https://pki-info.aol.<strong>com</strong>/<strong>AOL</strong>MSPKI.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Appendix A<br />
National Adaptations<br />
For participants residing in the jurisdictions listed below, the following apply and supersede any<br />
provision to the contrary in the foregoing CP/CPS.<br />
United States<br />
(30) Definition of <strong>AOL</strong>. “<strong>AOL</strong>” means <strong>AOL</strong> LLC Inc., a Delaware corporation, and any<br />
entity in which <strong>AOL</strong> LLC, Inc. controls directly or indirectly at least 50% of the equity or<br />
ownership interest.<br />
(31) Orders for disclosure of backup private key. <strong>AOL</strong> will not disclose any backup<br />
private encryption key stored by <strong>AOL</strong> except to <strong>com</strong>ply with valid legal process such as<br />
a search warrant, subpoena or court order, to protect the <strong>com</strong>pany's rights and<br />
property, or during emergencies when we believe physical safety is at risk. That<br />
disclosure makes possible the decryption of any data encrypted using the<br />
corresponding public key. <strong>AOL</strong> may be forbidden by law to inform an affected <strong>Member</strong><br />
of the disclosure, and in any case, it does not do so absent an inquiry from the affected<br />
<strong>Member</strong>. Legal advice may be informative should a <strong>Member</strong> have a concern in<br />
particular circumstances.<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Appendix B<br />
Comparison to [RFC 3647]<br />
This appendix is for reference only and is not an integral part of the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
CP/CPS.<br />
Although [RFC 3647] re<strong>com</strong>mends that a certificate policy or certification practice statement<br />
follow the outline it prescribes (section 6), the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI CP/CPS does not do so<br />
for several reasons, including:<br />
• The requirements of its audience: Participants in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI will<br />
generally be consumers and not information security experts. Recourse to security<br />
expertise is not likely to be cost-effective or justifiable for the uses foreseen for <strong>AOL</strong><br />
<strong>Member</strong> <strong>Security</strong> PKI. The <strong>com</strong>plex and highly technical subject matter envisioned<br />
in [RFC 3647] is therefore not seen as being most appropriate for the intended user<br />
audience. Instead, this CP/CPS strives to be simpler and more concise than a<br />
conventional certificate policy or certification practice statement.<br />
• The underlying contractual basis for <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI: The legal<br />
basis for the participant-<strong>AOL</strong>/<strong>AOL</strong>CA relationship derives from the <strong>Member</strong><br />
Agreement and participating nonmember agreement, which are separate<br />
documents from the CP/CPS even though they relate to many of the issues in the<br />
[RFC 3647] outline. Because of the existence of this broader legal structure<br />
governing services to be offered in connection with the <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI,<br />
the [RFC 3647] outline is a poor fit for the material to be covered in the CP/CPS,<br />
which is entirely descriptive.<br />
• Differences in purpose: The outline in [RFC 3647] presumes a need for full,<br />
public disclosure of all aspects of the subject PKI because privity is not expected to<br />
exist between the certification service provider and the end users of the PKI. By<br />
contrast, <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services are expected to be provided to<br />
participants who have privity with the <strong>AOL</strong>CA and/or <strong>AOL</strong>. The CP/CPS specifies<br />
<strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI services in sufficient detail to provide the framework to<br />
support the anticipated security and certification services to be offered to<br />
participants. <strong>AOL</strong>’s additional internal and confidential procedures ensure good<br />
order in its operations but are not public information.<br />
• No concrete need for <strong>com</strong>parison: Although <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI follows<br />
industry standards and is designed for interoperability, the infrastructure is designed<br />
for use by a closed <strong>com</strong>munity of participants and any prospective requirements for<br />
interoperability, cross-certification, or bridging to ac<strong>com</strong>modate other PKIs, have not<br />
yet been defined. Consequently, useful <strong>com</strong>parisons cannot be made between the<br />
CP/CPS and similar documentation written to serve different PKI service objectives.<br />
Because the mapping from the CP/CPS outline to [RFC 3647] is inexact, reading the CP/CPS as<br />
structured is advisable. However, the following table may help locate relevant provisions.<br />
Number in<br />
[RFC 3647]<br />
Heading in [RFC 3647]<br />
1.1 Overview 1<br />
1.2 Document name and identification Title page; 3.1<br />
1.3 PKI participants 2.2<br />
Reference in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
1.4 <strong>Certificate</strong> usage <strong>Member</strong> Agreement and participating<br />
nonmember agreement; 3.4<br />
1.5 <strong>Policy</strong> administration 6<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS
Number in<br />
[RFC 3647]<br />
Heading in [RFC 3647]<br />
2.1-2.4 Repositories, publication, access 3.1, 4.2.3<br />
3.1 Naming 3.3.1, 3.3.2<br />
3.2 Initial identity validation 3.5<br />
3.3 Identification and authentication for re-key requests 4.2.1.44.2.1.5<br />
4.1-4.2 <strong>Certificate</strong> application and processing 4.2.1<br />
4.3 <strong>Certificate</strong> issuance 4.2.1-4.2.2<br />
4.4 <strong>Certificate</strong> acceptance 4.2.1<br />
Reference in <strong>AOL</strong> <strong>Member</strong> <strong>Security</strong> PKI<br />
4.5 Key pair and certificate usage No stipulation other than contractual<br />
limits on usage of <strong>AOL</strong> system as a<br />
whole; liability limits may be relevant<br />
4.6 <strong>Certificate</strong> renewal 4.2.2<br />
4.7 <strong>Certificate</strong> re-key 4.2.1.54.2.1.4<br />
4.8 <strong>Certificate</strong> modification 3.5.2 (updating account information)<br />
4.9 <strong>Certificate</strong> revocation and suspension 4.2.3<br />
4.10 <strong>Certificate</strong> status services 4.2.3<br />
4.11 End of subscription 4.2.3 (termination of <strong>Member</strong>ship)<br />
4.12 Key escrow and recovery 4.3.3<br />
5-6 Facility, management, and operational controls<br />
Technical security controls<br />
7.1 <strong>Certificate</strong> profiles 3.4<br />
7.2 CRL profile 4.2.3<br />
7.3 OCSP profile 4.2.3<br />
8 Compliance audit and other assessments 5<br />
9.1 Fees <strong>Member</strong> Agreement; participating<br />
nonmember agreement<br />
9.2 Financial responsibility <strong>Member</strong> Agreement; participating<br />
nonmember agreement<br />
9.3 Confidentiality of business information 3.6.1; <strong>Member</strong> Agreement<br />
9.4 Privacy of personal information 3.6.1; <strong>Member</strong> Agreement<br />
9.5 Intellectual property rights 3.6.2; <strong>Member</strong> Agreement<br />
9.6 Representations and warranties 3.3; <strong>Member</strong> Agreement<br />
9.7 Disclaimers of warranties <strong>Member</strong> Agreement<br />
9.8 Limitations of liability <strong>Member</strong> Agreement<br />
9.9 Indemnities <strong>Member</strong> Agreement<br />
9.10 Term <strong>Member</strong> Agreement<br />
9.11-9.16 Individual notices, dispute resolution, governing<br />
law, other legal boilerplate<br />
5<br />
<strong>Member</strong> Agreement<br />
Version 1.05<br />
<strong>AOL</strong> ® <strong>Member</strong> <strong>Security</strong> PKI<br />
Combined CP/CPS