EN ISO/IEC 24760-1:2022

IT Security and Privacy - A framework for identity management - Part 1: Terminology and concepts (ISO/IEC 24760-1:2019)

This document defines terms for identity management, and specifies core concepts of identity and identity management and their relationships.
It is applicable to any information system that processes identity information.

IT-Sicherheit und Datenschutz - Rahmenwerk für Identitätsmanagement - Teil 1: Terminologie und Konzept (ISO/IEC 24760-1:2019)

Sécurité IT et confidentialité - Cadre pour la gestion de l'identité - Partie 1: Terminologie et concepts (ISO/IEC 24760-1:2019)

Le présent document définit les termes relatifs à la gestion de l'identité, et spécifie les concepts fondamentaux de l'identité et de la gestion de l'identité ainsi que leurs relations.
Il s'applique à tout système d'information qui traite des informations d'identité.

Varnost in zasebnost IT - Okvir za upravljanje identitete - 1. del: Terminologija in koncepti (ISO/IEC 24760-1:2019)

Standard ISO/IEC 24760-1:2019 opredeljuje izraze za upravljanje identitete in navaja temeljne koncepte identitete in upravljanja identitete ter razmerij med njima.
Uporablja se za vse informacijske sisteme, ki obdelujejo podatke o identiteti.
Na voljo je literatura z dokumenti, ki opisujejo različne vidike upravljanja informacij o identiteti.

General Information

• Status: Published
• Publication Date: 28-Jun-2022
• Withdrawal Date: 30-Jan-2023
• ICS: 35.030 - IT Security
• Technical Committee: CEN/CLC/TC 13 - Cybersecurity and Data Protection
• Drafting Committee: CEN/CLC/JTC 13/WG 5 - Data Protection, Privacy and Identity Management
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 29-Jun-2022
• Due Date: 24-Nov-2023
• Completion Date: 29-Jun-2022
• Ref Project: SIST EN ISO/IEC 24760-1:2022 - IT Security and Privacy - A framework for identity management - Part 1: Terminology and concepts (ISO/IEC 24760-1:2019)

Overview

EN ISO/IEC 24760-1:2022 - "IT Security and Privacy - A framework for identity management - Part 1: Terminology and concepts" defines a common vocabulary and the core concepts for identity and identity management. Applicable to any information system that processes identity information, this standard establishes the relationships between identity, identity information, identifiers, credentials, attributes and management processes. It is the first part of the ISO/IEC 24760 series and was prepared under ISO/IEC JTC 1 SC 27.

Key topics

The standard focuses on terminology and conceptual structure rather than prescriptive technical implementations. Key topics include:

• Definitions and terms for identity management, ensuring a shared vocabulary across organizations and vendors.
• Identity and identity information: how entities (people, devices, software) are represented.
• Identifiers and credentials: concepts of identifiers, credentials and credential management.
• Attributes: attribute types, domains of origin and attribute semantics.
• Identity lifecycle: enrolment, registration, identity proofing, verification, authentication, maintenance and revocation.
• Authentication and verification: conceptual models for proving and authenticating identity information.
• Federation: conceptual relationships where identities and attributes cross administrative domains.
• Privacy protection: privacy concepts related to identity data handling and minimization.
• Implementation aspects and operational structures that support identity management processes.

Practical applications

EN ISO/IEC 24760-1:2022 is useful when you need a standardized conceptual foundation for identity and access management (IAM) initiatives:

• Design and architecture: create IAM architectures that align with standardized concepts for identifiers, credentials and attribute management.
• Procurement and interoperability: specify requirements that vendors can interpret consistently, reducing ambiguity in contracts and integrations.
• Governance and policy: develop identity lifecycle policies (enrolment, proofing, authentication, maintenance) using a common terminology.
• Compliance and audit: document identity-management practices against recognized terminology and concepts.
• Privacy-by-design: map identity flows and apply privacy concepts such as data minimization and domain of origin. Typical users: IAM architects, security engineers, CIOs, privacy officers, compliance teams, system integrators and standardization bodies.

Related standards

• Part of the ISO/IEC 24760 series and prepared under ISO/IEC JTC 1 SC 27.
• Use this document as the conceptual basis before applying implementation-focused or domain-specific identity standards and technical specifications.

Keywords: identity management, identity information, identity lifecycle, authentication, identifiers, credentials, privacy, IAM standard, EN ISO/IEC 24760-1.

Standards Content (Sample)

SLOVENSKI STANDARD
01-september-2022
Varnost in zasebnost IT - Okvir za upravljanje identitete - 1. del: Terminologija in
koncepti (ISO/IEC 24760-1:2019)
IT Security and Privacy - A framework for identity management - Part 1: Terminology and
concepts (ISO/IEC 24760-1:2019)
Informationstechnik - Sicherheitsverfahren - Rahmenwerk für Identitätsmanagement -
Teil 1: Terminologie und Konzept (ISO/IEC 24760-1:2019)
Sécurité IT et confidentialité - Cadre pour la gestion de l'identité - Partie 1: Terminologie
et concepts (ISO/IEC 24760-1:2019)
Ta slovenski standard je istoveten z: EN ISO/IEC 24760-1:2022
ICS:
35.030 Informacijska varnost IT Security
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN ISO/IEC 24760-1

NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2022
ICS 35.030
English version
IT Security and Privacy - A framework for identity
management - Part 1: Terminology and concepts (ISO/IEC
24760-1:2019)
Sécurité IT et confidentialité - Cadre pour la gestion de Informationstechnik - Sicherheitsverfahren -
l'identité - Partie 1: Terminologie et concepts (ISO/IEC Rahmenwerk für Identitätsmanagement - Teil 1:
24760-1:2019) Terminologie und Konzept (ISO/IEC 24760-1:2019)
This European Standard was approved by CEN on 6 June 2022.

CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for
giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical
references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to
any CEN and CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.

CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.

CEN-CENELEC Management Centre:
Rue de la Science 23, B-1040 Brussels
© 2022 CEN/CENELEC All rights of exploitation in any form and by any means
Ref. No. EN ISO/IEC 24760-1:2022 E
reserved worldwide for CEN national Members and for
CENELEC Members.
Contents Page
European foreword . 3

European foreword
The text of ISO/IEC 24760-1:2019 has been prepared by Technical Committee ISO/IEC JTC 1
"Information technology” of the International Organization for Standardization (ISO) and has been
taken over as EN ISO/IEC 24760-1:2022 by Technical Committee CEN-CENELEC/ JTC 13 “Cybersecurity
and Data Protection” the secretariat of which is held by DIN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN-CENELEC shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN and CENELEC websites.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
Endorsement notice
The text of ISO/IEC 24760-1:2019 has been approved by CEN-CENELEC as EN ISO/IEC 24760-1:2022
without any modification.
INTERNATIONAL ISO/IEC
STANDARD 24760-1
Second edition
2019-05
IT Security and Privacy —
A framework for identity
management —
Part 1:
Terminology and concepts
Sécurité IT et confidentialité — Cadre pour la gestion de l'identité —
Partie 1: Terminologie et concepts
Reference number
ISO/IEC 24760-1:2019(E)
©
ISO/IEC 2019
ISO/IEC 24760-1:2019(E)
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Fax: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

ISO/IEC 24760-1:2019(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 General terms . 1
3.2 Identification . 3
3.3 Authenticating identity information . 3
3.4 Management of identity . 5
3.5 Federation . 7
3.6 Privacy protection . 7
4 Symbols and abbreviated terms . 8
5 Identity . 8
5.1 General . 8
5.2 Identity information . 9
5.3 Identifier .10
5.4 Credential .10
5.4.1 General.10
5.4.2 Credential management .11
6 Attributes .11
6.1 General .11
6.2 Types of attribute .12
6.3 Domain of origin .13
7 Managing identity information .13
7.1 General .13
7.2 Identity lifecycle .14
8 Identification .15
8.1 General .15
8.2 Verification .16
8.3 Enrolment .17
8.4 Registration .17
8.5 Identity proofing .17
8.5.1 General.17
8.5.2 Identity evidence .18
9 Authentication .18
10 Maintenance .19
11 Implementation aspects .19
12 Privacy .19
Bibliography .21
Index of terms .23
© ISO/IEC 2019 – All rights reserved iii

ISO/IEC 24760-1:2019(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that
are members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www. iso. org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www. iso.o rg/patents) or the IEC
list of patent declarations received (see http:/ /patents.i ec. ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www. iso
.org/iso/foreword. html.
This document was prepared by Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 27, IT Security Techniques.
This second edition cancels and replaces the first edition (ISO/IEC 24760-1:2011) which has been
technically revised. The main changes compared to the previous edition are as follows:
— new terms have been added to Clause 3;
— some definitions have been simplified and corrected;
— some terms have been deleted and some replaced;
— the introductory paragraphs of Subclause 5.1 have been reworded;
— new subclauses 5.4 and 8.5 has been created;
A list of all parts in the ISO/IEC 24760 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www. iso. org/members. html.
iv © ISO/IEC 2019 – All rights reserved

ISO/IEC 24760-1:2019(E)
Introduction
Data processing systems commonly gather a range of information on their users, be it a person, piece
of equipment, or piece of software connected to them, and make decisions based on the gathered
information. Such identity-based decisions can concern access to applications or other resources.
To address the need to efficiently and effectively implement systems that make identity-based decisions,
the ISO/IEC 24760 series specifies a framework for the issuance, administration, and use of data that
serves to characterize individuals, organizations or information technology components which operate
on behalf of individuals or organizations.
For many organizations the proper management of identity information is crucial to maintain security
of the organizational processes. For individuals, correct identity management is important to protect
privacy.
The ISO/IEC 24760 series specifies fundamental concepts and operational structures of identity
management with the purpose to realize information system management so that information systems
can meet business, contractual, regulatory and legal obligations.
The goal of this document is to specify the terminology and concepts for identity management, in order
to promote a common understanding in the field of identity management.
© ISO/IEC 2019 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 24760-1:2019(E)
IT Security and Privacy — A framework for identity
management —
Part 1:
Terminology and concepts
1 Scope
This document defines terms for identity management, and specifies core concepts of identity and
identity management and their relationships.
It is applicable to any information system that processes identity information.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 24760-2:2015, Information technology — Security techniques — A framework for identity
management — Part 2: Reference architecture and requirements
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
3.1 General terms
3.1.1
entity
item relevant for the purpose of operation of a domain (3.2.3) that has recognizably distinct existence
Note 1 to entry: An entity can have a physical or a logical embodiment.
EXAMPLE A person, an organization, a device, a group of such items, a human subscriber to a telecom
service, a SIM card, a passport, a network interface card, a software application, a service or a website.
3.1.2
identity
partial identity
set of attributes (3.1.3) related to an entity (3.1.1)
Note 1 to entry: An entity can have more than one identity.
Note 2 to entry: Several entities can have the same identity.
[13]
Note 3 to entry: ITU-T X1252 specifies the distinguishing use of an identity. In this document, the term
identifier implies this aspect.
© ISO/IEC 2019 – All rights reserved 1

ISO/IEC 24760-1:2019(E)
3.1.3
attribute
characteristic or property of an entity (3.1.1)
EXAMPLE An entity type, address information, telephone number, a privilege, a MAC address, a domain
name are possible attributes.
3.1.4
identifier
attribute or set of attributes (3.1.3) that uniquely characterizes an identity (3.1.2) in a domain (3.2.3)
Note 1 to entry: An identifier can be a specifically created attribute with a value assigned to be unique within
the domain.
EXAMPLE A name of a club with a club-membership number, a health insurance card number together with
a name of the insurance company, an email address, or a Universal Unique Identifier (UUID) can all be used as
identifiers. In a voter’s register, the combination of attributes name, address and date of birth is sufficient to
unambiguously distinguish a voter.
3.1.5
domain of origin
domain (3.2.3) where an attribute (3.1.3) value was created or its value has been (re)assigned
Note 1 to entry: The domain of origin can be provided as meta data for an attribute.
Note 2 to entry: The domain of origin typically specifies the meaning and format of the attribute value. Such
specification can be based on international standards.
Note 3 to entry: An attribute can contain an explicit value that references the domain of origin, e.g. an ISO
country code for a passport number as reference to the issuing country that is the domain of origin of identity
information in the passport.
Note 4 to entry: Operationally, a domain of origin can be available as an authoritative source for an attribute
(sometimes known as the Attribute Authority). An authoritative source can be operated outside the actual
domain of origin. Multiple authoritative sources can exist for the same domain of origin.
EXAMPLE The domain of origin of a club-membership number is the specific club that assigned the number.
3.1.6
reference identifier
RI
identifier (3.1.4) in a domain (3.2.3) that is intended to remain the same for the duration an entity (3.1.1)
is known in the domain and is not associated with another entity for a period specified in a policy after
the entity ceases to be known in that domain
Note 1 to entry: A reference identifier persists at least for the existence of the entity in a domain and can exist
longer than the entity, e.g. for archival purposes.
Note 2 to entry: A reference identifier for an entity can change during the lifetime of an entity, at which point the
old reference identifier is no longer applicable for that entity.
EXAMPLE A driver license number that stays the same for an individual driver’s driving life is a persistent
identifier, which references additional identity information and that is a reference identifier. An IP address is not
a reference identifier as it can be assigned to other entities.
3.1.7
principal
subject
entity (3.1.1) of which identity information is stored and managed by an identity management
system (3.4.8)
Note 1 to entry: Typically, in a context of privacy protection or where a principal is seen as having agency a
principal refers to a person.
2 © ISO/IEC 2019 – All rights reserved

ISO/IEC 24760-1:2019(E)
[SOURCE: ISO/IEC 24760-2:2015, 3.4, modified —The word "pertains" has been clarified and Note 1 to
entry has been reworded.]
3.2 Identification
3.2.1
identification
process of recognizing an entity (3.1.1) in a particular domain (3.2.3) as distinct from other entities
Note 1 to entry: The process of identification applies verification to claimed or observed attributes.
Note 2 to entry: Identification typically is part of the interactions between an entity and the services in a domain
and to access resources. Identification can occur multiple times while the entity is known in the domain.
3.2.2
verification
process of establishing that identity information (3.2.4) associated with a particular entity (3.1.1) is correct
Note 1 to entry: Verification typically involves determining which attributes are needed to recognize an entity in
a domain, checking that these required attributes are present, that they have the correct syntax, and exist within
a defined validity period and pertain to the entity.
3.2.3
domain
domain of applicability
context
environment where an entity (3.1.1) can use a set of attributes (3.1.3) for identification (3.2.1) and other
purposes
Note 1 to entry: In general, the domain of an identity is well defined in relation to the particular set of attributes.
[13]
Note 2 to entry: ITU-T X1252 uses the term context; this document prefers the term domain.
EXAMPLE An IT system deployed by an organization that allows users to login is the domain for the user’s
login name.
3.2.4
identity information
set of values of attributes (3.1.3) optionally with any associated metadata in an identity (3.1.2)
Note 1 to entry: In an information and communication technology system an identity is present as identity
information.
3.3 Authenticating identity information
3.3.1
authentication
formalized process of verification (3.2.2) that, if successful, results in an authenticated identity (3.3.2)
for an entity (3.1.1)
Note 1 to entry: The authentication process involves tests by a verifier of one or more identity attributes provided
by an entity to determine, with the required level of assurance, their correctness.
Note 2 to entry: Authentication typically involves the use of a policy to specify a required level of assurance for
the result of a successful completion.
3.3.2
authenticated identity
identity information (3.2.4) for an entity (3.1.1) created to record the result of authentication (3.3.1)
Note 1 to entry: An authenticated identity typically contains information obtained in the authentication process,
e.g. the level of assurance attained.
© ISO/IEC 2019 – All rights reserved 3

ISO/IEC 24760-1:2019(E)
Note 2 to entry: The existence of an authenticated identity in a particular domain denotes that an entity has been
recognized in that domain.
Note 3 to entry: An authenticated identity typically has a lifespan restricted by an authentication policy.
3.3.3
identity information authority
IIA
entity (3.1.1) related to a particular domain (3.2.3) that can make provable statements on the validity
and/or correctness of one or more attribute values in an identity (3.1.2)
Note 1 to entry: An identity information authority is typically associated with the domain, for instance the
domain of origin, in which the attributes, which the IIA can make assertions on, have a particular significance.
Note 2 to entry: The activity of an identity information authority can be subject to a policy on privacy protection.
Note 3 to entry: An entity can combine the functions of identity information provider and identity information
authority.
3.3.4
identity information provider
identity provider
IIP
entity (3.1.1) that makes available identity information (3.2.4)
Note 1 to entry: Typical operations performed by an identity information provider are to create and maintain
identity information for entities known in a particular domain. An identity information provider and an identity
information authority can be the same entity.
3.3.5
credential
representation of an identity (3.1.2) for use in authentication (3.3.1)
Note 1 to entry: As described in 5.4, customary embodiments of a credential are very diverse. To accommodate
this wide range, the definition adopted in this document is very generic.
Note 2 to entry: A credential is typically made to facilitate data authentication of the identity information
pertaining to the identity it represents. Data authentication is typically used in authorization.
Note 3 to entry: The identity information represented by a credential can, for example, be printed on human-
readable media, or stored within a physical token. Typically, such information can be presented in a manner
designed to reinforce its perceived validity.
Note 4 to entry: A credential can be a username, username with a password, a PIN, a smartcard, a token, a
fingerprint, a passport, etc.
3.3.6
verifier
entity (3.1.1) that performs verification (3.2.2)
Note 1 to entry: A verifier can be the same as, or act on behalf of, the entity that controls identification of entities
for a particular domain.
3.3.7
relying party
RP
entity (3.1.1) that relies on the verification (3.2.2) of identity information (3.2.4) for a particular entity
Note 1 to entry: A relying party is exposed to risk caused by incorrect identity information. Typically, it has a
trust relationship with one or more identity information authorities.
4 © ISO/IEC 2019 – All rights reserved

ISO/IEC 24760-1:2019(E)
3.3.8
identity assertion
statement by an identity information authority (3.3.3) used by a relying party (3.3.7) for
authentication (3.3.1)
Note 1 to entry: An identity assertion can be the cryptographic proof of a successful authentication, created with
algorithms and keys agreed between parties, e.g. in an identity federation.
3.4 Management of identity
3.4.1
identity management
IDM
processes and policies involved in managing the lifecycle and value, type and optional metadata of
attributes (3.1.3) in identities (3.1.2) known in a particular domain (3.2.3)
Note 1 to entry: In general identity management is involved in interactions between parties where identity
information (3.2.4) is processed.
Note 2 to entry: Processes and policies in identity management support the functions of an identity information
authority (3.3.3)where applicable, in particular to handle the interaction between an entity for which an identity
is managed and the identity information authority.
3.4.2
identity proofing
initial entity authentication
verification (3.2.2) based on identity evidence (3.4.4) aimed at achieving a specific level of assurance
Note 1 to entry: Identity proofing is typically performed as part of enrolment. Identity evidence can also be
needed during maintenance of registered identity information, e.g. recovery of a user account.
Note 2 to entry: Typically identity proofing involves a verification of provided identity information and can
include uniqueness checks, possibly based on biometric techniques.
Note 3 to entry: Verification for identity proofing is usually based on an enrolment policy that includes
specification of the verification criteria of the identity evidence to be provided by the entity.
Note 4 to entry: The verified identity information (3.2.4) obtained when performing identity proofing can be
included in the registration and can serve to facilitate future identification of the entity.
3.4.3
enrolment
process to make an entity (3.1.1) known within a particular domain (3.2.3)
Note 1 to entry: Enrolment typically comprises the collection and validation of identity information for
identification of an entity and the collection of the identity information required for identity registration (3.4.6),
followed by identity registration itself.
3.4.4
identity evidence
evidence of identity
information that can support validating identity information (3.2.4)
Note 1 to entry: Identity evidence is the presented and gathered information related to an entity that provides
the attributes needed for a successful identification or authentication at a specific (high) level of assurance.
3.4.5
identity register
IMS register
repository of identities (3.1.2)
Note 1 to entry: A typical identity register is indexed by a reference identifier.
© ISO/IEC 2019 – All rights reserved 5

ISO/IEC 24760-1:2019(E)
Note 2 to entry: The identity information authority in a particular domain typically uses its own identity register.
However, an identity register can be shared between related domains, e.g. within the same commercial entity.
Note 3 to entry: The reliability of the identity information in an identity register is determined by the identity
proofing policies used during enrolment.
3.4.6
identity registration
registration
process of recording an entity’s (3.1.1) identity information (3.2.4) in an identity register (3.4.5)
3.4.7
reference-identifier generator
tool used during enrolment (3.4.3) to provide a fresh unique value for a reference identifier (3.1.6)
EXAMPLE A database management system can be the reference identifier generator when it assigns a unique
record number to a new record being added to a table and the record number is used as reference identifier.
3.4.8
identity management system
mechanism comprising of policies, procedures, technology and other resources for maintaining identity
information (3.2.4) including associated metadata
Note 1 to entry: An identity management system is typically used for identification (3.2.1) or authentication
(3.3.1) of entities. It can be deployed to support other automated decisions based on identity information for an
entity recognized in the domain for the identity management system.
[SOURCE: ISO/IEC 24760-2:2015, 3.3, modified — “of application” has been deleted after “domain” in
Note 1 to entry.]
3.4.9
registration authority
RA
entity (3.1.1) related to a particular domain (3.2.3) responsible for enrolment (3.4.3), identity proofing
(3.4.2) and identity registration (3.4.6)
3.4.10
credential issuer
entity (3.1.1) responsible for provisioning of a credential (3.3.5) to a principal (3.1.7) in a specific
domain (3.2.3)
Note 1 to entry: A credential (3.3.5) provisioned by a credential issuer can have a physical form, e.g. a membership
(smart) card.
Note 2 to entry: The issuance of a credential (3.3.5) for a principal (3.1.7) can be recorded as an attribute (3.1.3)
for the principal, e.g. by recording the unique number of the token issued.
Note 3 to entry: A credential (3.3.5) provisioned by an issuer can be a username and password. A credential in the
form of a smart card or similar security device, can be configured to validate a password off-line.
3.4.11
credential service provider
CSP
trusted entity (3.1.1) related to a particular domain (3.2.3) responsible for management of credentials
(3.3.5) issued in that domain
Note 1 to entry: It is possible that a CSP acts as credential issuer (3.4.10).
6 © ISO/IEC 2019 – All rights reserved

ISO/IEC 24760-1:2019(E)
3.5 Federation
3.5.1
federated identity
identity (3.1.2) for use in multiple domains (3.2.3)
Note 1 to entry: Some or all of the domains where a federated identity can be used can be formally joined as an
identity federation. Identity information providers of domains in the federation can jointly manage a federated
identity.
Note 2 to entry: The federated identity can be persistent or be a temporary one.
3.5.2
identity federation
agreement between two or more domains (3.2.3) specifying how identity information (3.2.4) will be
exchanged and managed for cross-domain identification (3.2.1) purposes
Note 1 to entry: Establishing an identity federation typically includes an agreement on the use of common
protocols and procedures for privacy control, data protection and auditing. The federation agreement can specify
the use of standardized data formats and cryptographic techniques.
Note 2 to entry: The federation agreement can be the basis for identity authorities in each of the domains of
applicability to mutually recognize credentials for authorization.
3.6 Privacy protection
In jurisdictions where certain types of legal entities are granted the right of privacy protection, the
term ‘person’ in the following definitions should be interpreted to include such entities, otherwise the
term ‘person’ is used in relation to a single human individual.
3.6.1
selective disclosure
principle of identity management (3.4.1) that gives a person a measure of control over the identity
information (3.2.4) that can be transferred to a third party, e.g. during authentication (3.3.1)
3.6.2
minimal disclosure
principle of identity management (3.4.1) to restrict the request or transfer of identity information (3.2.4)
to a third party to the minimum information strictly required for a particular purpose
Note 1 to entry: The principle of proportionality is related to minimal disclosure in so far as the effort of control
intervention is reasonable in relation to the activity.
3.6.3
pseudonym
identifier (3.1.4) that contains the minimal identity information (3.2.4) sufficient to allow a verifier
(3.3.6) to establish it as a link to a known identity (3.1.2)
Note 1 to entry: A pseudonym can be used to reduce privacy risks that are associated with the use of identifiers
with fixed or known values.
Note 2 to entry: A pseudonym can be an identifier with a value chosen by the person or assigned randomly.
3.6.4
ephemeral identifier
identifier (3.1.4) with a restricted validity period
Note 1 to entry: Typically, an ephemeral identifier is provided to a subject as a cryptographic credential to
represent an authenticated identity (3.3.2).
Note 2 to entry: Typically, an ephemeral identifier can only be verified in the domain (3.2.3) that created it,
possibly also in domains federated with this domain.
© ISO/IEC 2019 – All rights reserved 7

ISO/IEC 24760-1:2019(E)
3.6.5
blinded affirmation
principle of identity management (3.4.1) of not providing identity information (3.2.4) for an entity (3.1.1)
to a third party except a statement that the entity is known in a domain (3.2.3)
Note 1 to entry: Blinded affirmation provides a strong level of protection for the privacy of a principal (3.1.7).
Note 2 to entry: Blinded affirmation can be realized with an ephemeral identifier (3.6.4) or pseudonym.
4 Symbols and abbreviated terms
ICT Information and Communication Technology
IDM Identity Management
IIP Identity Information Provider
IIA Identity Information Authority
RI Reference Identifier
RP Relying Party
SSO Single Sign On
URI Uniform Resource Identifier
UUID Universal Unique Identifier
5 Identity
5.1 General
An identity represents an entity in an ICT system as data to be stored or processed. The (business)
purposes of a particular domain of application served by an ICT system determine which of the
attributes pertaining to an entity are to be used in its identity. A persistently stored identity is the basis
for identification of a principal. If a persistent identity is not an identifier, identification can require
additional information from the principal.
An identity can, in part or fully, be represented by a credential issued to the principal. If an identity
is represented by such a credential, an identifier for the credential can be included in the registered
identity.
This document considers any set of attributes that describe a particular entity as an identity for the
entity. In some domains, the persistently stored identity information for different entities can be the
same. In this case, additional information is used in identification to recognize an entity as distinct,
[13]
where needed. In other standards, e.g. ITU-T X1252 , the explicit purpose of an identity is the
capability of the identity information to distinguish entities from each other to the extent relevant for
applications in a domain (“in context”).
An entity can have multiple identities, each identity relating to at least one domain. An entity can
have multiple identities relating to the same domain. Some identities of an entity cannot be unique in
any domain.
NOTE 1 The term entity is taken in a broad sense. It represents a physical person, a moral or legal person
(institution, company), an object (information, a system, a device), or a group of these individual entities.
NOTE 2 A human is an entity in this document and has a single, whole existence. It can be described by many
different attributes. Different sets of these attributes form different identities for the same human entity.
8 © ISO/IEC 2019 – All rights reserved

ISO/IEC 24760-1:2019(E)
If an identity is not unique in a particular domain, it can serve to distinguish a group of entities in that
domain that share one or more characteristics from other entities that do not have such a characteristic.
The identity of an entity serves to make known relevant information of the entity in its interactions
with the services and access of resources provided by a domain. A domain specifies the type and range
of permissible values of attributes to be used for identification or other purposes.
NOTE 3 In some cases the term "partial identity" can be used to refer to a particular set of attributes taken
from a larger set of attributes, which in contrast can be referred to as the full identity — all available attributes
— of an entity in a domain. The preferred term in this document is identity.
A domain should deploy an identity management system conforming to the ISO/IEC 24760 series to
manage the identity information of the entities it intends to recognize.
5.2 Identity information
Information pertaining to a particular entity in a domain is called identity information.
If given identity information sufficiently distinguishes an entity from others in the context of a given
use case, then this identity information is a distinguishing identity.
If the combination of values contained in identity information is unique in the domain, then this identity
information is an identifier of the entity.
When a new identity is created for an entity in a domain, an identity information provider for the
domain can create values for required attributes of the new identity. The new attributes can consist of:
— Any information required to facilitate the interaction between the domain and the entity for which
the identity is created;
— Any information required for future identification of the entity, including description of aspects of
the physical existence of the entity;
— Any information required for future authentication of the entity’s identity; or
— One or more reference identifiers.
The new identity information can be derived from identity information for the entity created in
the current or another domain. Deriving information can involve copying, collating, or creating a
pseudonym.
The domain shall ascertain that the created identity information accurately pertains to the entity.
Identity information can be associated with metadata specifying, for instance, its origin, scope of use,
and period of validity. Identity information metadata can itself be identity information and can be
included in the identity it relates to.
Identity information and its associated metadata can be changed. Procedures and conditions for
changing, updating, and creating identity information shall be specified in appropriate policies. These
policies can include keeping records for auditing. These policies can distinguish between a number of
tasks and activities relating to the identity lifecycle (see 7.2), including:
— requesting and receiving information from external sources;
— verifying and validating;
— qualifying and categorizing;
— recording;
— provisioning;
— archiving; and
© ISO/IEC 2019 – All righ
...