Informationsteknik, kontorsutrustning

ISO/IEC 10373 defines test methods for characteristics of identification cards according to the definition given in ISO/IEC 7810. Each test method is cross-referenced to one or more base standards, which can be ISO/IEC 7810 or one or more of the supplementary standards that define the information storage technologies employed in identification card applications. Criteria for acceptability do not form part of ISO/IEC 10373, but will be found in the International Standards mentioned above. Test methods defined in this part of ISO/IEC 10373 are intended to be performed separately. A given proximity card or object, or proximity coupling device, is not required to pass through all the tests sequentially. This part of ISO/IEC 10373 defines test methods which are specific to proximity cards and objects, and proximity coupling devices and proximity extended devices, defined in ISO/IEC 14443-1, ISO/IEC 14443-2, ISO/IEC 14443-3, and ISO/IEC 14443-4. ISO/IEC 10373-1 defines test methods which are common to one or more integrated circuit card technologies and other parts deal with other technology-specific tests. The conformance test plan defined in Annex O specifies the list of tests applicable for each part of ISO/IEC 14443.

This part of ISO/IEC 14443 describes the following:

— polling for proximity cards or objects (PICCs) entering the field of a proximity coupling device (PCD);

— the byte format, the frames and timing used during the initial phase of communication between

PCDs and PICCs;

— the initial Request and Answer to Request command content;

— methods to detect and communicate with one PICC among several PICCs (anticollision);

— other parameters required to initialize communications between a PICC and PCD;

— optional means to ease and speed up the selection of one PICC among several PICCs based on

application criteria;

— optional capability to allow a device to alternate between the functions of a PICC and a PCD to

communicate with a PCD or a PICC, respectively. A device which implements this capability is

called a PXD.

Protocol and commands used by higher layers and by applications and which are used after the initial

phase are described in ISO/IEC 14443-4.

This part of ISO/IEC 14443 is applicable to PICCs of Type A and of Type B (as described in ISO/IEC 14443-

2) and PCDs (as described in ISO/IEC 14443-2) and to PXDs.

NOTE 1 Part of the timing of data communication is defined in ISO/IEC 14443-2.

NOTE 2 Test methods for this part of ISO/IEC 14443 are defined in ISO/IEC 10373-6.

This document specifies a half-duplex block transmission protocol featuring the special needs of a contactless environment and defines the activation and deactivation sequence of the protocol.

This document is intended to be used in conjunction with other parts of ISO/IEC 14443 and is applicable to proximity cards or objects of Type A and Type B.

This document defines how uncompressed audio is carried in files in the family of standards based on the ISO base media file format. This includes mono, stereo and multi-channel audio in Linear Pulse Code Modulation (LPCM) format with various word lengths and sampling rates, and also floating point format. Such representations also occur in other container formats, such as RIFF WAV or AIFF.

This document specifies the concept of operation, minimum functionality, system requirements, system interfaces, and test procedures for Bicyclist Detection and Collision Mitigation Systems (BDCMS). It also defines 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.

BDCMS is fundamentally intended to provide emergency braking of equipped vehicles in order to mitigate collision severity between the subject vehicle and a bicyclist. BDCMS detect bicyclists forward of the subject vehicle, determine if the detected bicyclists are in a hazardous situation with respect to the subject vehicle, and initiate emergency braking if a hazardous situation exists and a collision is imminent. Systems that include other countermeasures such as evasive steering are outside the scope of this document.

The standard defines two types of BDCMS (based on operation in different ambient illuminance) and two classes of BDCMS (based on operation on different vehicle size classes). The standard does not apply to motorcycles. The operational design domain is public roads. BDCMS is not intended for off-road use.

Table 1 — Types and Classes of BDCMS

Responsibility for the safe operation of the vehicle remains with the driver.

Licensable motor vehicles intended for use on public roads, i.e. motorcycles, cars, light trucks, buses, motor coaches, and other heavy vehicles as hazards are outside the scope of this document and are covered under ISO 22839, Intelligent transportation systems — Forward vehicle collision mitigation systems — Operation, performance, and verification requirements.

Pedestrians are outside the scope of this document and are covered under ISO 19237, Intelligent transportation systems — Pedestrian detection and collision mitigation systems (PDCMS) — Performance requirements and test procedures.

This document specifies the test calibration methods and apparatus used when calibrating test tools for cryptographic modules under ISO/IEC 19790:2012 and ISO/IEC 24759:2017 against the test metrics defined in ISO/IEC 17825:2016 for mitigation of non-invasive attack classes.

This document specifies concepts and principles to establish a methodology for specifying level of information need and information deliveries in a consistent way when using Building Information Modelling (BIM).

This document specifies the characteristics of different levels used for defining the detail and extent of information required to be exchanged and delivered throughout the life cycle of built assets. It gives guidelines for principles required to specify information needs.

The concepts and principles in this document can be applied for a general information exchange and whilst in progress, for a generally agreed way of information exchange between parties in a collaborative work process, as well as for a contractually specified information delivery.

The level of information need provides methods for describing information to be exchanged according to exchange information requirements. The exchange information requirements specify the wanted information exchange. The result of this process is an information delivery.

The concepts and principles contained in this document are applicable to all those involved in the asset life cycle. This includes, but is not limited to, the asset owner/operator, the project client, the asset manager, the design team, the construction supply chain, the equipment manufacturer, the system specialist, the regulator, and the end-user.

This document provides the overview of information security management systems (ISMS). It also provides terms and definitions commonly used in the ISMS family of standards. This document is applicable to all types and sizes of organization (e.g. commercial enterprises, government agencies, not-for-profit organizations).

The terms and definitions provided in this document

— cover commonly used terms and definitions in the ISMS family of standards;

— do not cover all terms and definitions applied within the ISMS family of standards; and

— do not limit the ISMS family of standards in defining new terms for use.

This document specifies the requirements for creating sector-specific standards that extend ISO/IEC 27001:2013, and complement or amend ISO/IEC 27002:2013 to support a specific sector (domain, application area or market).

This document explains how to;

— include requirements in addition to those in ISO/IEC 27001:2013,

— refine or interpret any of the ISO/IEC 27001:2013 requirements,

— include controls in addition to those of ISO/IEC 27001:2013, Annex A and ISO/IEC 27002:2013,

— modify any of the controls of ISO/IEC 27001:2013, Annex A and ISO/IEC 27002:2013,

— add guidance to or modify the guidance of ISO/IEC 27002:2013.

This document specifies that additional or refined requirements do not invalidate the requirements in ISO/IEC 27001:2013.

This document is applicable to those involved in producing sector-specific standards.

This document describes principles for interaction between a user and a system that are formulated in general terms (i.e. independent of situations of use, application, environment or technology). This document provides a framework for applying those interaction principles and the general design recommendations.

While this document is applicable to all types of interactive systems, it does not cover the specifics of every context of use (e.g. safety critical systems, collaborative work).

It is intended for the following audiences:

— analysts of requirements (including market requirements, user requirements, and system requirements);

— designers of user interface development tools and style guides to be used by user interface designers and developers;

— developers (including user interface designers), who will apply the guidance during the design and development process (either directly, based on training, or by using tools and style guides which incorporate the guidance);

— evaluators, who are responsible for ensuring that products meet the general design recommendations contained in this document;

— buyers, who will reference this document in contracts during product procurement.

This document focuses on interaction principles related to the design of interactions between user and interactive system. ISO 9241-112 provides further guidance on the presentation of information.

This document does not consider any other aspect of design such as marketing, aesthetics and corporate identity.

This standard specifies the principles and requirements for security-minded information management at a stage of maturity described as "building information modelling (BIM) according to the ISO 19650- series", as well as the security-minded management of sensitive information that is obtained, created, processed and stored as part of, or in relation to, any other initiative, project, asset, product or service.

It addresses the steps required to create and cultivate an appropriate and proportionate security mindset and culture across organizations with access to that information, including the need to monitor and audit compliance.

The approach outlined is applicable throughout the lifecycle of an initiative, project, asset, product or service, whether planned or existing, where sensitive information is obtained, created, processed and/or stored.

This standard is intended for use by any organization who is involved in the use of digital engineering and related technologies in the creation, design, construction, manufacture, operation, management, modification, improvement, demolition and/or recycling of assets or products, as well as the provision of services, within the built environment. It will also be of interest and relevance to those organizations who wish to protect their commercial information, personal information and intellectual property.

This document specifies the application interface in the context of electronic fee collection (EFC) systems

using the dedicated short-range communication (DSRC).

The EFC application interface is the EFC application process interface to the DSRC application layer, as can

be seen in Figure 1 below. This document comprises specifications of:

 EFC attributes (i.e. EFC application information) that can also be used for other applications and/or

interfaces,

 the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI),

 EFC application functions, i.e. further qualification of actions by definitions of the concerned services,

assignment of associated ActionType values and content and meaning of action parameters,

 the EFC transaction model, which defines the common elements and steps of any EFC transaction,

 the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level.

This document specifies the application interface in the context of electronic fee collection (EFC) systems

using the dedicated short-range communication (DSRC).

The EFC application interface is the EFC application process interface to the DSRC application layer, as can

be seen in Figure 1 below. This document comprises specifications of:

 EFC attributes (i.e. EFC application information) that can also be used for other applications and/or

interfaces,

 the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI),

 EFC application functions, i.e. further qualification of actions by definitions of the concerned services,

assignment of associated ActionType values and content and meaning of action parameters,

 the EFC transaction model, which defines the common elements and steps of any EFC transaction,

 the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level.

This document specifies the application interface in the context of electronic fee collection (EFC) systems

using the dedicated short-range communication (DSRC).

The EFC application interface is the EFC application process interface to the DSRC application layer, as can

be seen in Figure 1 below. This document comprises specifications of:

 EFC attributes (i.e. EFC application information) that can also be used for other applications and/or

interfaces,

 the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI),

 EFC application functions, i.e. further qualification of actions by definitions of the concerned services,

assignment of associated ActionType values and content and meaning of action parameters,

 the EFC transaction model, which defines the common elements and steps of any EFC transaction,

 the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level.

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE)

and on-board equipment (OBE) with regard to the conformance to standards and requirements for type

approval and acceptance testing which is within the realm of EFC application specifically.

The scope of this document is restricted to systems operating within the radio emission, electromagnetic

compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated.

This document identifies a set of suitable parameters and provides test procedures to enable the proof of

a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined

requirements of an application. The defined parameter and tests are assigned to the following groups of

parameters:

— functionality;

— quality;

— referenced pre-tests.

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE)

and on-board equipment (OBE) with regard to the conformance to standards and requirements for type

approval and acceptance testing which is within the realm of EFC application specifically.

The scope of this document is restricted to systems operating within the radio emission, electromagnetic

compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated.

This document identifies a set of suitable parameters and provides test procedures to enable the proof of

a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined

requirements of an application. The defined parameter and tests are assigned to the following groups of

parameters:

— functionality;

— quality;

— referenced pre-tests.

This document specifies controls which will shape the content and the structure of online privacy notices as well as the process of asking for consent to collect and process personally identifiable information (PII) from PII principals.

This document is applicable in any online context where a PII controller or any other entity processing PII informs PII principals of processing.

This specification defines the following:

• the SAND architecture which identifies the SAND network elements and the nature of SAND messages exchanged among them,

• the semantics of SAND messages exchanged between the network elements present in the SAND architecture,

• a recommended encoding scheme for the SAND messages, and

• the minimum to implement SAND message delivery protocol.

For security evaluation of biometric recognition performance and presentation attack detection for biometric verification systems and biometric identification systems, ISO/IEC 19989 (all parts) specifies:

- Extended security functional components to SFR Classes in ISO/IEC 15408-2: 2008,

- Supplementary activities to methodology specified in ISO/IEC 18045:2008 for SAR Classes of ISO/IEC 15408-3: 2008.

This document consists of the introduction of the general framework for the security evaluation of biometric systems, including extended security functional components, and supplementary activities to methodology, which is additional evaluation activities and guidance/recommendations for an evaluator to handle those activities. The supplementary evaluation activities are developed in this document while the detailed recommendations are developed in ISO/IEC 19989-2 (for biometric recognition aspects) and in ISO/IEC 19989-3 (for presentation attack detection aspects). This document is applicable only to TOEs for single biometric characteristic type. However, the selection of a characteristic from multiple characteristics in SFRs is allowed.