Information service
35 Information technology
New standards
EVS-EN ISO 19123-2:2026
Geographic information - Schema for coverage geometry and functions - Part 2: Coverage implementation schema (ISO 19123-2:2026)
Scope:
This document specifies an implementable, conformance-testable coverage structure based on the abstract schema for coverages defined in the ISO 19123-1 coverage fundamentals. This document defines a concrete data structure that is suitable for encoding in many formats.
Base documents:
ISO 19123-2:2026; EN ISO 19123-2:2026
CLC ISO/IEC/TS 29125:2025/A2:2026
Information technology - Telecommunications cabling requirements for remote powering of terminal equipment
Scope:
Amendment to CLC ISO/IEC/TS 29125:2025
Base documents:
ISO/IEC/TS 29125:2017/AMD2:2024; CLC ISO/IEC/TS 29125:2025/A2:2026
ISO/IEC 27090:2026
Cybersecurity — Artificial intelligence (AI) — Addressing security threats and compromises to AI systems
Scope:
This document addresses security threats and compromises specific to artificial intelligence (AI) systems. This document aims to provide information to organizations to help them better understand the consequences of security threats specific to AI systems, throughout their life cycle, and descriptions of how to detect and mitigate such threats.
This document is applicable to all types and sizes of organizations, including public and private companies, government entities and not-for-profit organizations that develop or use AI systems.
This document is applicable to all types and sizes of organizations, including public and private companies, government entities and not-for-profit organizations that develop or use AI systems.
Base documents:
ISO/IEC 38501-1:2026
Information technology — Governance of IT implementation guidance — Part 1: General approach
Scope:
This document provides guidance on the implementation of effective governance of IT in an organization, in accordance with ISO/IEC 38500.
It identifies the key activities that an organization can undertake and provides guidance on the design and establishment of the supporting and enabling arrangements for the governance of IT, clarifying the roles and responsibilities of key organizational stakeholders.
This document can be used by individuals responsible for governance of IT in an organization, as well as individuals supporting the governance of IT in organizations, and is applicable to organizations of all sizes and types.
It identifies the key activities that an organization can undertake and provides guidance on the design and establishment of the supporting and enabling arrangements for the governance of IT, clarifying the roles and responsibilities of key organizational stakeholders.
This document can be used by individuals responsible for governance of IT in an organization, as well as individuals supporting the governance of IT in organizations, and is applicable to organizations of all sizes and types.
Base documents:
ISO 19237:2026
Intelligent transport systems — Pedestrian detection and collision mitigation systems (PDCMS) — Performance requirements and test procedures
Scope:
This document specifies the concepts of operation, minimum functionality, system requirements, system interfaces and test procedures for pedestrian detection and collision mitigation systems (PDCMS), which can reduce the likelihood of fatality and severity of injury. A PDCMS requires information about range to pedestrians, motion of pedestrians, motion of the subject vehicle (SV), driver commands and driver actions. It specifies the behaviours that are required for PDCMS, and the system test criteria necessary to verify that a given implementation meets the requirements of this document. Implementation choices are left to system designers wherever possible.
Systems that include other countermeasures such as evasive steering are not within the scope of this document.
Responsibility for the safe operation of the vehicle remains with the driver.
This document applies to light duty passenger vehicles. It does not apply to other vehicle categories such as heavy vehicles or motorcycles. PDCMS are not intended for off-road use.
Systems that include other countermeasures such as evasive steering are not within the scope of this document.
Responsibility for the safe operation of the vehicle remains with the driver.
This document applies to light duty passenger vehicles. It does not apply to other vehicle categories such as heavy vehicles or motorcycles. PDCMS are not intended for off-road use.
Base documents:
Replaces:
ISO 19237:2017
ISO/IEC 19763-7:2026
Information technology — Metamodel framework for interoperability (MFI) — Part 7: Metamodel for service model registration
Scope:
The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for interoperability. This document specifies a metamodel for registering administrative and evolution information of models of services, facilitating interoperability through the reuse of services.
This document is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of this document.
This document is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of this document.
Base documents:
Replaces:
ISO/IEC 19763-7:2015
ISO 19123-2:2026
Geographic information — Schema for coverage geometry and functions — Part 2: Coverage implementation schema
Scope:
This document specifies an implementable, conformance-testable coverage structure based on the abstract schema for coverages defined in the ISO 19123-1 coverage fundamentals. This document defines a concrete data structure that is suitable for encoding in many formats.
Base documents:
Replaces:
ISO 19123-2:2018
ISO/IEC/IEEE 24748-8:2026
Systems and software engineering — Life cycle management — Part 8: Technical reviews and audits on defence programs
Scope:
This document establishes the requirements for technical reviews and audits to be performed throughout the acquisition life cycle for the US Department of Defense (DoD) and other defense agencies. This document provides the definition, description, and intent, as well as the entry, exit and success criteria, for each technical review and audit. It is to be used to establish agreement between acquirers and suppliers on the technical reviews and audits that are needed for the project, as well as the focus and expectations of each technical review and audit.
Base documents:
Replaces:
ISO/IEC/IEEE 24748-8:2019
ISO 20271-1:2026
Document management — Reference model for long-term preservation of textual documents — Part 1: Overview
Scope:
This document provides an overview of the ISO 20271 series.
The following are covered in this document:
— the scope and structure of the ISO 20271 series;
— description of textual document files within the scope of the ISO 20271 series;
— a summary of the content of each part in the ISO 20271 series;
— guidelines for the extension of other types of document formats.
The following are covered in this document:
— the scope and structure of the ISO 20271 series;
— description of textual document files within the scope of the ISO 20271 series;
— a summary of the content of each part in the ISO 20271 series;
— guidelines for the extension of other types of document formats.
Base documents:
ISO 21423:2026
Robotics — Industrial mobile robots — Communications and interoperability
Scope:
To facilitate interoperability in a shared industrial environment, this document specifies the requirements for communication between two or more of the following:
— industrial mobile robot (IMR);
— IMR fleet manager (IMRFM);
— other machines, equipment, and applications in the shared industrial environment (e.g. machines tended by the IMRs; enterprise resource planning (ERP) tools; and building infrastructure such as lifts, alarm systems, automated doors).
For the purposes of this document, “industrial environment” describes a workplace where the people are working-age adults and the public is restricted from access or not reasonably expected to be present. Further, “industrial” pertains to the production of goods and related services (e.g. manufacturing, laboratory, pharmaceutical, warehousing, distribution, logistics and other workplaces).
The following applications are excluded from the scope of this document: entertainment, consumer, military, medical and use on public roads.
This document is not safety-related; there are no safety requirements. Navigation requirements are excluded from the scope of this document.
— industrial mobile robot (IMR);
— IMR fleet manager (IMRFM);
— other machines, equipment, and applications in the shared industrial environment (e.g. machines tended by the IMRs; enterprise resource planning (ERP) tools; and building infrastructure such as lifts, alarm systems, automated doors).
For the purposes of this document, “industrial environment” describes a workplace where the people are working-age adults and the public is restricted from access or not reasonably expected to be present. Further, “industrial” pertains to the production of goods and related services (e.g. manufacturing, laboratory, pharmaceutical, warehousing, distribution, logistics and other workplaces).
The following applications are excluded from the scope of this document: entertainment, consumer, military, medical and use on public roads.
This document is not safety-related; there are no safety requirements. Navigation requirements are excluded from the scope of this document.
Base documents:
ISO 20435:2026
Framework for representing physical assets using tokens
Scope:
This document establishes a digital ledger technology (DLT) agnostic, decentralized identifier (DID) framework for representing physical assets using tokens. This includes:
— A DID generation method: An algorithmic data method for generating DIDs from assets with immutable unique identifiers, e.g. serial numbers.
— A cryptographic method to tie asset data objects to the DID: An algorithmic hash tree data method for transferring a set of asset data objects that are cryptographically tied together, agnostic to any specific DLT or blockchain system.
— A DID method scheme: A DID method scheme to enable DID registry interoperability, so the digital representation can be stored, resolved or transferred to any compliant DID registry.
— Real world trust anchor processes: Processes for utilizing off-chain trust anchors to establish proof of real-world human and machine generated events and information that tie a real-world asset to its digital representation.
— A DID generation method: An algorithmic data method for generating DIDs from assets with immutable unique identifiers, e.g. serial numbers.
— A cryptographic method to tie asset data objects to the DID: An algorithmic hash tree data method for transferring a set of asset data objects that are cryptographically tied together, agnostic to any specific DLT or blockchain system.
— A DID method scheme: A DID method scheme to enable DID registry interoperability, so the digital representation can be stored, resolved or transferred to any compliant DID registry.
— Real world trust anchor processes: Processes for utilizing off-chain trust anchors to establish proof of real-world human and machine generated events and information that tie a real-world asset to its digital representation.
Base documents:
ISO/IEC 20009-4:2017/Amd 1:2026
Information technology — Security techniques — Anonymous entity authentication — Part 4: Mechanisms based on weak secrets — Amendment 1
Scope:
Amendment to ISO/IEC 20009-4:2017
Base documents:
ISO/TS 6268-3:2026
Health informatics — Cybersecurity framework for telehealth environments — Part 3: Cybersecurity controls of telehealth
Scope:
This document provides telehealth cybersecurity controls of the overall security framework for systems and services applied to telehealth, specifically addressing cybersecurity controls uniquely applicable to telehealth, while general elements relevant to health delivery organizations (HDOs) can be referenced from ISO 27799.
It also includes Annex A, which, for informative purposes, provides a mapping of the controls in 4.2 to 4.5 of this document to the security controls in ISO 27799:2025.
It also includes Annex A, which, for informative purposes, provides a mapping of the controls in 4.2 to 4.5 of this document to the security controls in ISO 27799:2025.
Base documents:
ISO/IEC 5181:2026
Information security, cybersecurity and privacy protection — Data provenance
Scope:
This document provides guidelines, methodologies and techniques for securely deriving information about data assets from multiple sources, intermediaries or users, which is denoted as provenance metadata.
Base documents:
ISO 23219:2026
Natural gas — Format for data from gas chromatograph analysers for natural gas — XML file format
Scope:
This document specifies a text file format − XML file format − for reporting natural gas analysis results and other data relevant to natural gas, natural gas substitutes and other combustible gaseous fuels. The file name is applicable when it includes the extension of .XML (case insensitive).
The XML file format is useful for output from, for example, ISO 6974-1 for composition, ISO 19739 for sulfur compounds and ISO 6974-2 for uncertainty, as input for ISO 6976 for properties calculation or ISO 10723 for performance evaluation. Typically, these are the gas composition as provided on an analysis certificate. The format can also be used for the results of properties calculation or a performance evaluation that can be read into a spreadsheet editor or data processing.
The XML file format is useful for output from, for example, ISO 6974-1 for composition, ISO 19739 for sulfur compounds and ISO 6974-2 for uncertainty, as input for ISO 6976 for properties calculation or ISO 10723 for performance evaluation. Typically, these are the gas composition as provided on an analysis certificate. The format can also be used for the results of properties calculation or a performance evaluation that can be read into a spreadsheet editor or data processing.
Base documents:
Replaces:
ISO 23219:2022
Replaced standards
ISO/IEC 19763-7:2015
Information technology -- Metamodel framework for interoperability (MFI) -- Part 7: Metamodel for service model registration
Scope:
The primary purpose of the multipart standard ISO/IEC 19763 is to specify a metamodel framework for interoperability. ISO/IEC 19763-7:2015 specifies a metamodel for registering models of services, facilitating interoperability through the reuse of services.
ISO/IEC 19763-7:2015 is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of ISO/IEC 19763-7:2015.
ISO/IEC 19763-7:2015 is only applicable to web services whose capabilities are described by some web service description language (see Annex A for examples of such languages). Figure 1 shows the scope of ISO/IEC 19763-7:2015.
Base documents:
Replaced:
ISO/IEC 19763-7:2026
ISO 19237:2017
Intelligent transport systems -- Pedestrian detection and collision mitigation systems (PDCMS) -- Performance requirements and test procedures
Scope:
ISO 19237:2017 specifies the concept of operation, minimum functionality, system requirements, system interfaces, and test procedures for Pedestrian Detection and Collision Mitigation Systems (PDCMS). It specifies the behaviours that are required for PDCMS, and the system test criteria necessary to verify that a given implementation meets the requirements of this document. Implementation choices are left to system designers wherever possible.
PDCMS reduce the severity of pedestrian collisions that cannot be avoided, and may reduce the likelihood of fatality and severity of injury. PDCMS require information about range to pedestrians, motion of pedestrians, motion of the subject vehicle (SV), driver commands and driver actions. PDCMS detect pedestrians ahead of time, determine if detected pedestrians represent a hazardous condition, and warn the driver if a hazard exists. PDCMS estimate if the driver has an adequate opportunity to respond to the hazard. If there is inadequate time available for the driver to respond, and if appropriate criteria are met, PDCMS determine that a collision is imminent. Based upon this assessment, PDCMS will activate CWs and vehicle brakes to mitigate collision severity. This document, while not a collision avoidance standard, does not preclude a manufacturer from implementing collision avoidance with PDCMS.
Systems that include other countermeasures such as evasive steering are not within the scope of this document.
Responsibility for the safe operation of the vehicle remains with the driver.
ISO 19237:2017 applies to light duty passenger vehicles (see 3.6). It does not apply to other vehicle categories such as heavy vehicles or motorcycles. PDCMS are not intended for off-road use.
PDCMS reduce the severity of pedestrian collisions that cannot be avoided, and may reduce the likelihood of fatality and severity of injury. PDCMS require information about range to pedestrians, motion of pedestrians, motion of the subject vehicle (SV), driver commands and driver actions. PDCMS detect pedestrians ahead of time, determine if detected pedestrians represent a hazardous condition, and warn the driver if a hazard exists. PDCMS estimate if the driver has an adequate opportunity to respond to the hazard. If there is inadequate time available for the driver to respond, and if appropriate criteria are met, PDCMS determine that a collision is imminent. Based upon this assessment, PDCMS will activate CWs and vehicle brakes to mitigate collision severity. This document, while not a collision avoidance standard, does not preclude a manufacturer from implementing collision avoidance with PDCMS.
Systems that include other countermeasures such as evasive steering are not within the scope of this document.
Responsibility for the safe operation of the vehicle remains with the driver.
ISO 19237:2017 applies to light duty passenger vehicles (see 3.6). It does not apply to other vehicle categories such as heavy vehicles or motorcycles. PDCMS are not intended for off-road use.
Base documents:
Replaced:
ISO 19237:2026
ISO 19123-2:2018
Geographic information -- Schema for coverage geometry and functions -- Part 2: Coverage implementation schema
Scope:
This document specifies a concrete[1] implementable, conformance-testable coverage structure based on the abstract schema for coverages defined in the ISO 19123 schema for coverage geometry. This document defines a structure that is suitable for encoding in many encoding formats.
[1] "concrete" is used here as a contrast to "abstract" in the sense described in the Introduction.
[1] "concrete" is used here as a contrast to "abstract" in the sense described in the Introduction.
Base documents:
Replaced:
ISO 19123-2:2026
ISO/IEC/IEEE 24748-8:2019
Systems and software engineering -- Life cycle management -- Part 8: Technical reviews and audits on defense programs
Scope:
This standard establishes the requirements for technical reviews and audits to be performed throughout the acquisition life cycle for the US Department of Defense (DoD) and other defense agencies. This standard provides the definition, description, and intent, as well as the entry, exit and success criteria, for each technical review and audit. It is to be used to establish agreement between acquirers and suppliers on the technical reviews and audits that are needed for the project, as well as the focus and expectations of each technical review and audit.
Base documents:
Replaced:
ISO/IEC/IEEE 24748-8:2026
ISO 23219:2022
Natural gas — Format for data from gas chromatograph analysers for natural gas — XML file format
Scope:
This document specifies a text file format - XML file format - for reporting natural gas analysis results and other data relevant to natural gas. The file name is applicable when it includes the extension of .XML (case insensitive).
The XML file format is useful for output from ISO 6974-1[1] for composition and ISO 6974-2[2] for uncertainty, for input for ISO 6976[3] and for input for ISO 10723[4] for performance evaluation. Typically these would be the gas composition as provided on an analysis certificate, or results from a performance evaluation that would be read into an Excel spreadsheet for data processing.
The XML file format is useful for output from ISO 6974-1[1] for composition and ISO 6974-2[2] for uncertainty, for input for ISO 6976[3] and for input for ISO 10723[4] for performance evaluation. Typically these would be the gas composition as provided on an analysis certificate, or results from a performance evaluation that would be read into an Excel spreadsheet for data processing.
Base documents:
Replaced:
ISO 23219:2026
Drafts
prEN ISO/IEC 2382-37
Information technology - Vocabulary - Part 37: Biometrics (ISO/IEC DIS 2382-37:2026)
Scope:
This document establishes a systematic description of the concepts in the field of biometrics pertaining to recognition of human beings. This document also reconciles variant terms in use in pre-existing International Standards on biometrics against the preferred terms, thereby clarifying the use of terms in this field.
This document does not cover concepts (represented by terms) from information technology, pattern recognition, biology, mathematics, etc. Biometrics uses such fields of knowledge as a basis.
In principle, mode-specific terms are outside of scope of this document.
This document does not cover concepts (represented by terms) from information technology, pattern recognition, biology, mathematics, etc. Biometrics uses such fields of knowledge as a basis.
In principle, mode-specific terms are outside of scope of this document.
Base documents:
ISO/IEC DIS 2382-37; prEN ISO/IEC 2382-37
prEN ISO 13606-5
Health informatics - Electronic health record communication - Part 5: Interface specification (ISO/DIS 13606-5:2026)
Scope:
This document specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This document is not intended to specify the internal architecture or database design of such systems.
The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person's care.
Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people's records, are not the focus of this document but such secondary uses could also find the document useful.
This document defines a set of interfaces to request and provide:
— an EHR_EXTRACT for a given subject of care as defined in ISO 13606-1;
— one or more ARCHETYPE(s) as defined in ISO 13606-2;
— an EHR_AUDIT_LOG_EXTRACT for a given subject of care as defined in ISO 13606-4.
This document defines the set of interactions to request each of these artefacts, and to provide the data to the requesting party or to decline the request. An interface to query an EHR or populations of EHRs, for example for clinical audit or research, are beyond its scope, although provision is made for certain selection criteria to be specified when requesting an EHR_EXTRACT which might also serve for population queries.
This document defines the Computational Viewpoint for each interface, without specifying or restricting particular engineering approaches to implementing these as messages or as service interfaces.
This document effectively defines the payload to be communicated at each interface. It does not specify the particular information that different transport protocols will additionally require, nor the security or authentication procedures that might be agreed between the communicating parties or required by different jurisdictions.
The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person's care.
Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people's records, are not the focus of this document but such secondary uses could also find the document useful.
This document defines a set of interfaces to request and provide:
— an EHR_EXTRACT for a given subject of care as defined in ISO 13606-1;
— one or more ARCHETYPE(s) as defined in ISO 13606-2;
— an EHR_AUDIT_LOG_EXTRACT for a given subject of care as defined in ISO 13606-4.
This document defines the set of interactions to request each of these artefacts, and to provide the data to the requesting party or to decline the request. An interface to query an EHR or populations of EHRs, for example for clinical audit or research, are beyond its scope, although provision is made for certain selection criteria to be specified when requesting an EHR_EXTRACT which might also serve for population queries.
This document defines the Computational Viewpoint for each interface, without specifying or restricting particular engineering approaches to implementing these as messages or as service interfaces.
This document effectively defines the payload to be communicated at each interface. It does not specify the particular information that different transport protocols will additionally require, nor the security or authentication procedures that might be agreed between the communicating parties or required by different jurisdictions.
Base documents:
ISO/DIS 13606-5; prEN ISO 13606-5
prEN 50173-10:2026
Information technology - Generic cabling systems - Part 10: Single pair cabling
Scope:
This document specifies 1-pair cabling and can be used in conjunction with all the space-specific standards of the EN 50173 series but especially EN 50173-3 and EN 50173-6.
NOTE 1-pair cabling for EN 50173-2, EN 50173-4 and EN 50173-5 is for further study.
It delivers 1-pair cabling specifications to extend generic cabling systems according to the EN 50173 series.
This document specifies the:
— structure and minimum configuration for extension of generic cabling by 1-pair cabling;
— interfaces at the service outlet (SO/TO);
— performance requirements for cabling links and channels;
— implementation requirements and options;
— performance requirements for cabling components;
— conformance requirements and verification procedures.
This document takes into account the requirements specified in application standards listed in Annex C.
NOTE 1-pair cabling for EN 50173-2, EN 50173-4 and EN 50173-5 is for further study.
It delivers 1-pair cabling specifications to extend generic cabling systems according to the EN 50173 series.
This document specifies the:
— structure and minimum configuration for extension of generic cabling by 1-pair cabling;
— interfaces at the service outlet (SO/TO);
— performance requirements for cabling links and channels;
— implementation requirements and options;
— performance requirements for cabling components;
— conformance requirements and verification procedures.
This document takes into account the requirements specified in application standards listed in Annex C.
Base documents:
prEN 50173-10:2026
prEN 303 994-1 V1.1.2
Cyber Security (CYBER);
Privileged Access Workstations;
Part 1: Physical Device
Scope:
The present document provides requirements that are specific enough to define the desired security outcomes, but flexible enough that there can be innovation and different ways for how they can be achieved. Whilst it is initially targeted towards the Telecoms Sector, the principles are designed to be industry agnostic.
The present document covers the device only. Additional documents will cover other aspects of PAWs that can work in conjunction with each other to meet the needs of the overall system architecture and achieve the relevant security aims.
The present document covers the device only. Additional documents will cover other aspects of PAWs that can work in conjunction with each other to meet the needs of the overall system architecture and achieve the relevant security aims.
Base documents:
Draft ETSI EN 303 994-1 V1.1.2
prEN 303 994-2 V1.1.2
Cyber Security (CYBER);
Privileged Access Workstations;
Part 2: Connectivity
Scope:
The present document provides requirements that are specific enough to define the desired security outcomes, but flexible enough that there can be innovation and different ways for how they can be achieved. Whilst it is initially targeted towards the Telecoms Sector, the principles are designed to be industry agnostic.
The present document covers the connectivity and follows on from ETSI EN 303 994-1. Additional documents will cover other aspects of PAW that can work in conjunction with each other to meet the needs of the overall system architecture and achieve the relevant security aims.
The present document covers the connectivity and follows on from ETSI EN 303 994-1. Additional documents will cover other aspects of PAW that can work in conjunction with each other to meet the needs of the overall system architecture and achieve the relevant security aims.
Base documents:
ETSI EN 303 994-2 V1.1.2
prEN 303 994-3 V1.1.2
Cyber Security (CYBER);
Privileged Access Workstations;
Part 3: System Integration
Scope:
The present document provides requirements that are specific enough to define the desired security outcomes, but flexible enough that there can be innovation and different ways for how they can be achieved. Whilst it is initially targeted towards the Telecoms Sector, the principles are designed to be industry agnostic.
The present document covers system integration and follows on from ETSI EN 303 994-1 - Devices and ETSI EN 303 994-2 - Connectivity. This multi-part deliverable will cover different aspects of PAWs that can work in conjunction with each other to meet the needs of the overall system architecture and the relevant security aims.
The present document covers system integration and follows on from ETSI EN 303 994-1 - Devices and ETSI EN 303 994-2 - Connectivity. This multi-part deliverable will cover different aspects of PAWs that can work in conjunction with each other to meet the needs of the overall system architecture and the relevant security aims.
Base documents:
ETSI EN 303 994-3 V1.1.2