The purpose of this DG is to gather use cases from organizations that perform or require identity assurance.
The DG will create a Report containing the use cases, which will be processed into a format suitable for contribution into the ISO SC 27/WG 5 Study Period to collect and document Use Cases for an Identity Assurance Framework.
The contribution is expected to go via the Kantara Initiative Liaison and may also be contributed to ISO via one or more National Standards Bodies as determined by the DG Participants.
The ISO SC 27/WG 5 Study Period
ISO SC 27/WG 5 “Identity management and privacy technologies” has opened a new Study Period to collect and document Use Cases for an Identity Assurance Framework with a scope of:
To compile a set of business use cases that require identity assurance, which can be analyzed to produce functional requirements for identity assurance. These functional requirements can inform the review of TS 29003 and the contents of a potential Identity assurance framework International Standard, and also inform the evolution of ISO/IEC 29115.
SC 27/WG 5 describes Identity Assurance as:
identity assurance is the term used to describe an assured process where:
An identity is established through verification of a set of identity attributes using acceptable evidence or validated systemically against an authoritative data source; then
This identity is bound to the entity.
The outcome of the process is one or more assured identifiers that can be used as the basis for authentication.
The process and the organization operating the process are assured in accordance with a defined policy that includes:
A governance body or authority;
A policy specification that is systemized in a process;
One or more organizations that operate the process;
The detection of policy violations, anomalies and indicators of compromise, and actions to address them;
One or more organizations that assure and enforce the process and the processing organizations.
NOTE: Identity assurance is related to, but not identical to, “Identity Verification” and “Identity Proofing”. Therefore, the DG will seek out use cases from organizations that perform identity verification or identity proofing, in anticipation of discovery of applicable use cases.
The DG will collect "use cases" which contain sufficient detail to derive requirements for organizations performing identity assurance processes.
A use case is a description of the possible sequences of interactions between the system under discussion and its external actors, related to a particular goal.
The 'system' in our case is the assured process operated by the organization.
(To be discussed in DG): The main stakeholder should be either the 'owner'/operator of the assured process; or, the 'customer' of that assured process.
The main goal should be to establish an identity, bind it to the entity, and to result in one or more assured identifiers (bullets a, b, c above).
The use case is intended to describe the functional behaviour of the system.