NIST PIV and digital identity SP 800-63A-4
All1 The CSP SHALL monitor the entire identity proofing session through a high-2 The CSP SHALL have a live proofing agent participate remotely with the applicant3 The CSP SHALL require all actions taken by the applicant during the evidence4 The CSP SHALL require that all digital validation and verification of evidence5 Subscriber Accounts6 Threats and Security Considerations7 Privacy Considerations8 Customer Experience Considerations
| Ref | Title | Text | |
|---|---|---|---|
| 1 | The CSP SHALL monitor the entire identity proofing session through a high- | resolution video transmission with the applicant. | changed here |
| 2 | The CSP SHALL have a live proofing agent participate remotely with the applicant | for the evidence collection, evidence validation, and verification steps of the identity proofing process. Data entry of attributes for resolution and enrollment MAY be done without the presence of a live proofing agent. | changed here |
| 3 | The CSP SHALL require all actions taken by the applicant during the evidence | collection, evidence validation, and verification steps to be clearly visible to the remote proofing agent. | changed here |
| 4 | The CSP SHALL require that all digital validation and verification of evidence | (e.g., via chip or wireless technologies) be performed by integrated scanners and sensors (e.g., embedded fingerprint reader). 5. All devices used to support interaction between the proofing agent and the applicant SHALL be safeguarded fro | changed here |
| 5 | Subscriber Accounts | This section is normative. | changed here |
| 5.1 in 5 |
Subscriber Accounts | The CSP SHALL establish and maintain a unique subscriber account for each active subscriber in its identity system from the time of enrollment to the time of account closure. The CSP establishes a subscriber account to record each subscribe | changed here |
| 5.2 in 5 |
Subscriber Account Access | The CSP SHALL provide the capability for subscribers to authenticate and access information in their subscriber account. For subscriber accounts that contain personal information, this capability SHALL be accomplished through AAL2 or AAL3 | changed here |
| 5.3 in 5 |
Subscriber Account Maintenance and Updates | The CSP SHALL provide the capability for a subscriber to request that information be updated in their subscriber account. The CSP MAY provide a mechanism for subscribers to directly update non-core attributes. With the exception of physica | changed here |
| 5.4 in 5 |
Subscriber Account Suspension or Termination | The CSP SHALL promptly suspend or terminate the subscriber account when one of the following occurs: • The subscriber elects to terminate their subscriber account with the CSP. • The CSP determines that the subscriber account has been com | changed here |
| 5.5 in 5 |
Data Breach Notification | In the event of a data breach of CSP records, the CSP SHALL provide notification to subscribers whose personal information may have been exposed to unauthorized access. Such notification SHALL include information about the breach and action | changed here |
| 5.6 in 5 |
Multiple Subscriber Account Scenarios | Some CSPs need to support a single user’s ability to interact with the CSP while fulfilling different roles or personas. For example, a subscriber may interact as themselves and also as a representative of a business across different servic | changed here |
| 6 | Threats and Security Considerations | This section is informative. Effectively protecting identity proofing processes requires layering security controls and processes throughout a transaction with a given applicant. To achieve this, it is necessary to understand where and how | changed here |
| 6.1 in 6 |
Threat Mitigation Strategies | Threats to the enrollment and identity proofing process are summarized in Table 2. Related mechanisms that assist in mitigating these threats are summarized in Table 3. These mitigations should not be considered comprehensive but rather a s | changed here |
| 6.2 in 6 |
Collaboration With Adjacent Programs | A close coordination of identity proofing and CSP functions with cybersecurity, privacy, threat intelligence, and program integrity teams can enable a more complete protection of business capabilities while constantly improving identity pro | changed here |
| 7 | Privacy Considerations | This section is informative. These privacy considerations provide additional information for implementing the requirements set forth in Sec. 3.3 and are intended to guide CSPs and RPs in designing identity systems that prioritize protectin | changed here |
| 7.1 in 7 |
Collection and Data Minimization | These guidelines permit the collection and processing of only the personal information necessary to validate the claimed identity, associate the claimed identity to the applicant, mitigate fraud, and provide RPs with the attributes they may | changed here |
| 7.1.1 in 7.1 |
Social Security Numbers | These guidelines permit the CSP to collect SSNs as an attribute for use in identity resolution. However, overreliance on the SSN can contribute to misuse and place the applicant at risk of harm, such as through identity theft. Nonetheless, | changed here |
| 7.2 in 7 |
Notice and Consent | These guidelines require the CSP to provide explicit notice to the applicant at the time of collection regarding the purpose for collecting and maintaining a record of the attributes necessary for identity proofing, including whether such a | changed here |
| 7.3 in 7 |
Use Limitation | These guidelines require CSPs to employ measures that maintain predictability (i.e., enabling reliable assumptions by individuals, owners, and operators about the processing of personal information by an information system) and manageabilit | changed here |
| 7.4 in 7 |
Redress | These guidelines require the CSP to provide effective and secure mechanisms for redressing applicant complaints or problems that arise from identity proofing and make the mechanisms easy for applicants to find and access. The Privacy Act r | changed here |
| 7.5 in 7 |
Privacy Risk Assessment | These guidelines require the CSP to conduct a privacy risk assessment. In conducting a privacy risk assessment, CSPs should consider: | changed here |
| 7.6 in 7 |
Agency-Specific Privacy Compliance | These guidelines cover specific compliance obligations for federal CSPs. It is critical to involve an agency’s SAOP in the earliest stages of identity service development to assess and mitigate privacy risks and advise the agency on complia | changed here |
| 8 | Customer Experience Considerations | This section is informative. To align with the standard terminology of user-centered design, customer experience, and usability, the term “user” is used throughout this section to refer to the human party. In most cases, the user in questi | changed here |
| 8.1 in 8 |
Usability | [ISO/IEC9241-11] focuses on the users, goals, and context of use as the necessary elements for achieving effectiveness, efficiency, and satisfaction. A holistic approach that considers these key elements is necessary to achieve usability. | changed here |
| 8.1.1 in 8.1 |
General User Considerations During Identity Proofing and Enrollment | The following usability considerations are applicable across all steps of the enrollment process. Additional information about these principles can be found in Sec. 8.1.2, Sec. 8.1.3, and Sec. 8.1.4. • To avoid user frustration, streamline | changed here |
| 8.1.2 in 8.1 |
Preparation | Ensuring that users are as prepared as possible for the identity proofing and enrollment process is critical to the overall success and usability of identity proofing and enrollment. Such preparation is only possible if users receive the n | changed here |
| 8.1.3 in 8.1 |
Identity Proofing and Enrollment | The following usability considerations are specific to identity proofing and enrollment: • At the start of an identity proofing session, remind users of the procedure. Do not expect them to remember the process that was described during th | changed here |
| 8.1.4 in 8.1 |
Post-Enrollment | Post-enrollment refers to the step immediately following enrollment but prior to the first use of an authenticator. As previously described, users will have already been informed at the end of their enrollment session regarding the expected | changed here |
| 8.2 in 8 |
Customer Success Considerations | A primary aspect of customer experience is anticipating the needs of the user population and offering solutions that are suitable for that population. This becomes considerably more difficult within the context of identity proofing as the p | changed here |
| 8.2.1 in 8.2 |
Support Multiple Types of Identity Proofing | Whether deployed by a single CSP, multiple CSPs, or through an arrangement with RP customer service representatives, the use of multiple identity proofing types as defined in Sec. 2.1.3 provides more opportunities for users to achieve posit | changed here |
| 8.2.2 in 8.2 |
Partner With Multiple Credible and Authoritative Sources | Credible and authoritative sources provide a means to confirm the accuracy of identity data that an applicant claims during the proofing process. It is an essential step in preventing synthetic identity attacks and enabling accurate informa | changed here |
31 of 31.