This document examines the lamppost network as an important smart community infrastructure from the perspective of data exchange and sharing, guided by ISO 37156 and ISO 37170.

  • Technical report
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off

This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.
Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples).
This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation.

  • Standard
    164 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    140 pages
    English language
    sale 10% off
    e-Library read for
    1 day

RTS/LI-00242-3

  • Standard
    58 pages
    English language
    sale 15% off
  • Technical specification
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies security means and procedures for AVPS Type 3 as specified in ISO 23374-1. It focuses on operation interfaces and management interfaces as defined in ISO 23374-1.

  • Technical specification
    44 pages
    English language
    sale 15% off
  • Draft
    44 pages
    English language
    sale 15% off
  • Draft
    44 pages
    English language
    sale 15% off

This document describes a basic role and functional model of the intelligent transport systems (ITS) data aggregation role, which is a basic role of ISO/TR 4445. It provides a paradigm describing: a) a framework for the provision of ITS data aggregation for cooperative ITS service application; b) a description of the concept of a role and functional model for such roles; c) a conceptual architecture between actors involved in the provision/receipt of ITS data aggregation; d) references for the key documents on which the architecture is based; e) a taxonomy of the organization of generic procedures.

  • Technical report
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off

This document defines the application of medical waveform format encoding rules (MFER) to describe standard electrocardiography waveforms measured in physiological laboratories, hospital wards, clinics, and primary care medical checkups. It covers electrocardiography such as 12-lead, 15-lead, 18-lead, Cabrera lead, Nehb lead, Frank lead, XYZ lead, and exercise tests that are measured by inspection equipment such as electrocardiographs and patient monitors that are compatible with MFER. Medical waveforms that are not in the scope of this document include Holter ECG, exercise stress ECG, and real-time ECG waveform encoding used for physiological monitors.

  • Standard
    34 pages
    English language
    sale 15% off

This document defines the application of medical waveform format encoding rules (MFER) to describe long-term electrocardiography waveforms measured in physiological laboratories and health care clinics. It covers electrocardiography such as bipolar 2, 3-lead, 12-lead that are measured by medical equipment such as Holter electrocardiograph and patient physiological monitors that are compatible with MFER documents encoding rules (see ISO 22077-1).

  • Standard
    28 pages
    English language
    sale 15% off

This document defines an integrated XML implementation of ISO 19115-1 and ISO 19115-2 by defining the following artefacts:
—     a set of XML schema required to validate metadata instance documents conforming to conceptual model elements defined in ISO 19115-1 and ISO 19115-2; and
—     a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints in the ISO 19115-1 and ISO 19115-2 UML models that are not validated by the XML schema.
This document describes the procedure used to generate XML schemas from ISO geographic information conceptual models related to metadata. The XML schemas are generated directly from the conceptual UML model (8.5).

  • Draft
    64 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This standard establishes a normative definition of communication between personal telehealth insulin
pump devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages work done in other
ISO/IEEE 11073 standards including existing terminology, information profiles, application profile
standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in
telehealth environments, restricting optionality in base frameworks in favor of interoperability. This
standard defines a common core functionality of personal telehealth insulin pump devices.
In the context of personal health devices (PHDs), an insulin pump is a medical device used for the
administration of insulin in the treatment of diabetes mellitus, also known as continuous subcutaneous
insulin infusion (CSII) therapy. This standard provides the data modeling according to ISO/IEEE 11073-20601 and does not specify the measurement method.

  • Draft
    132 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies a general framework for the security evaluation of quantum key distribution (QKD) according to the ISO/IEC 15408 series. Specifically, it specifies a baseline set of common security functional requirements (SFRs) for QKD modules, including SFRs on the conventional network components and the quantum optical components, and the entire implementation of QKD protocols. To facilitate the analysis of SFRs, security problems that QKD modules can face in their operational environment are analysed based on a structural analysis of the security functionality of QKD modules and the classification of QKD protocols. The SFRs on conventional network components of QKD modules are mainly characterized under the framework of the ISO/IEC 15408 series and also refer to the methodology of ISO/IEC 19790 and relevant standards on testing of cryptographic modules and network devices.

  • Standard
    52 pages
    English language
    sale 15% off

This document specifies the process references model (PRM) for human-centred design (HCD) according to ISO 9241-220, as well as the process assessment model (PAM) for assessing these processes, based on ISO/IEC 33020 and in accordance with the requirements of ISO/IEC 33004. This HCD PAM contains a set of indicators to be considered while interpreting the intent of the HCD PRM defined in ISO 9241-220. These indicators can also be applied when implementing a process improvement programme post an assessment. NOTE 1 The PRM in this document focuses on assessing HCD processes rather than system life cycle, for example as in ISO/IEC/IEEE 15288, or software life cycle, as in ISO/IEC/IEEE 12207. NOTE 2 If processes beyond the scope of ISO 9241-220 are required, appropriate processes from other PRMs, such as ISO/IEC/IEEE 12207, ISO/IEC/IEEE 15288 or ISO/TS 18152, can be added based on the business needs of the organization. The intended application of this document is computer-based interactive systems. While the processes apply to interactive systems that deliver services, they do not cover the design of those services. The relevant aspects of the processes can also be applied to simple or non-computer-based interactive systems. NOTE 3 HCD concentrates on the human-centred aspects of design and not on other aspects of design, such as mechanical construction, programming or the basic design of services. The process descriptions in this document provide the basis for a rigorous assessment of an enterprise’s capability to carry out human-centred processes in conformity with the ISO/IEC 33004 and ISO/IEC 33020. This document is intended for use by organizations that want to address and improve their treatment of human-centred design of either their internal systems or the products and services they provide, and the procurement of systems and parts of systems. The processes can be applied by small- and medium-sized enterprises as well as by large organizations. NOTE 4 The scope of application of the PAM is the same as that of the PRM, which is described in ISO 9241-220:2019, Clause 1.

  • Standard
    102 pages
    English language
    sale 15% off

This technical specification identifies and clarifies lighting properties for digital building design and maintenance. This document provides all the needed properties to design and to describe lighting systems. These properties are intended to be used for mapping between data providers and requesters. The mapping of the identifiers enables the exchange of luminaire and sensing device data within different databases. The unambiguous mapping and description of properties improves the data quality, reduces misinterpretations and the processing time in digital environments. Therefore, the properties listed in this document establish the essential description of lighting systems in BIM systems and databases. The listed properties in this document are used to structure the product data sheet which is complemented with real product information.

  • Technical specification
    61 pages
    English language
    sale 15% off
  • Draft
    61 pages
    English language
    sale 15% off
  • Draft
    61 pages
    English language
    sale 15% off

This document defines an integrated XML implementation of ISO 19115-1 and ISO 19115-2 by defining the following artefacts: — a set of XML schema required to validate metadata instance documents conforming to conceptual model elements defined in ISO 19115-1 and ISO 19115-2; and — a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints in the ISO 19115-1 and ISO 19115-2 UML models that are not validated by the XML schema. This document describes the procedure used to generate XML schemas from ISO geographic information conceptual models related to metadata. The XML schemas are generated directly from the conceptual UML model (8.5).

  • Standard
    100 pages
    English language
    sale 15% off
  • Standard
    109 pages
    French language
    sale 15% off
  • Draft
    76 pages
    French language
    sale 15% off

IEC 62351-3:2023 specifies how to provide confidentiality, integrity protection, and message level authentication for protocols that make use of TCP/IP as a message transport layer and utilize Transport Layer Security when cyber-security is required. This may relate to SCADA and telecontrol protocols, but also to additional protocols if they meet the requirements in this document.
IEC 62351-3 specifies how to secure TCP/IP-based protocols through constraints on the specification of the messages, procedures, and algorithms of Transport Layer Security (TLS) (TLSv1.2 defined in RFC 5246, TLSv1.3 defined in RFC 8446). In the specific clauses, there will be subclauses to note the differences and commonalities in the application depending on the target TLS version. The use and specification of intervening external security devices (e.g., "bump-in-the-wire") are considered out-of-scope.
In contrast to previous editions of this document, this edition is self-contained in terms of completely defining a profile of TLS. Hence, it can be applied directly, without the need to specify further TLS parameters, except the port number, over which the communication will be performed. Therefore, this part can be directly utilized from a referencing standard and can be combined with further security measures on other layers. Providing the profiling of TLS without the need for further specifying TLS parameters allows declaring conformity to the described functionality without the need to involve further IEC 62351 documents.
This document is intended to be referenced as a normative part of other IEC standards that have the need for providing security for their TCP/IP-based protocol exchanges under similar boundary conditions. However, it is up to the individual protocol security initiatives to decide if this document is to be referenced.
The document also defines security events for specific conditions, which support error handling, security audit trails, intrusion detection, and conformance testing. Any action of an organization in response to events to an error condition described in this document are beyond the scope of this document and are expected to be defined by the organization’s security policy.
This document reflects the security requirements of the IEC power systems management protocols. Should other standards bring forward new requirements, this document may need to be revised.
This second edition cancels and replaces the first edition published in 2014, Amendment 1:2018 and Amendment 2:2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Inclusion of the TLSv1.2 related parameter required in IEC 62351-3 Ed.1.2 to be specified by the referencing standard. This comprises the following parameter:
• Mandatory TLSv1.2 cipher suites to be supported.
• Specification of session resumption parameters.
• Specification of session renegotiation parameters.
• Revocation handling using CRL and OCSP.
• Handling of security events.
b) Inclusion of a TLSv1.3 profile to be applicable for the power system domain in a similar way as for TLSv1.2 session.

  • Standard
    52 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies:
—     the data elements, structures and relationships between the data elements required for the exchange of information, which uniquely and with certainty identify pharmaceutical dose forms, units of presentation, routes of administration and packaging items (containers, closures and administration devices) related to medicinal products;
—     a mechanism for the association of translations of a single concept into different languages, which is an integral part of the information exchange;
—     a mechanism for the versioning of the concepts in order to track their evolution;
—     rules to help regional authorities to map existing regional terms to the terms created using this document, in a harmonized and meaningful way.

  • Standard
    37 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies CAdES digital signatures. CAdES signatures are built on CMS signatures [7], by
incorporation of signed and unsigned attributes, which fulfil certain common requirements (such as the long term
validity of digital signatures, for instance) in a number of use cases.
The present document specifies the ASN.1 definitions for the aforementioned attributes as well as their usage when
incorporating them to CAdES signatures.
The present document specifies formats for CAdES baseline signatures, which provide the basic features necessary for a
wide range of business and governmental use cases for electronic procedures and communications to be applicable to a
wide range of communities when there is a clear need for interoperability of digital signatures used in electronic
documents.
The present document defines four levels of CAdES baseline signatures addressing incremental requirements to
maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the
requirements addressed at levels that are below it. Each level requires the presence of certain CAdES attributes, suitably
profiled for reducing the optionality as much as possible.
Procedures for creation, augmentation and validation of CAdES digital signatures are out of scope and specified in
ETSI EN 319 102-1 [i.5]. Guidance on creation, augmentation and validation of CAdES digital signatures including the
usage of the different properties defined in the present document is provided in ETSI TR 119 100 [i.4].
The present document aims at supporting digital signatures in different regulatory frameworks.
NOTE: Specifically, but not exclusively, CAdES digital signatures specified in the present document aim at
supporting electronic signatures, advanced electronic signatures, qualified electronic signatures,
electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU)
No 910/2014 [i.13].

  • Standard
    63 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    63 pages
    English language
    sale 15% off
  • Standard
    63 pages
    English language
    sale 15% off
  • Draft
    63 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the function, interfaces (IFs), and operating mechanism of CADP and defines the AP association, cloud AC switchover, cloud AC backup and CADP hot backup methods. This document applies to public wireless local area network (WLAN) networking scenarios.

  • Standard
    10 pages
    English language
    sale 15% off

This document defines an additional data concept that may be transferred as the ‘optional additional data ’ part of an eCall MSD, as defined in EN 15722, that may be transferred from a vehicle to a PSAP in the event of a crash or emergency via an eCall communication session.
The purpose of this document is to provide means to notify the PSAP of any limitations to the sending equipment that are endorsed by other standards, but not (immediately) apparent to the receiver. Lack of knowledge about these limitations can hamper the emergency process. This document describes an additional data concept which facilitates the inclusion of information about such limitations in a consistent and usable matter.
This document can be seen as an addendum to EN 15722; it contains as little redundancy as possible.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines a 3rd Party API for the Home and Building HBES Open Communication System.

  • Standard
    124 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    124 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    16 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    16 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the conditions necessary for the interoperable deployment of visible digital seals (VDSs). It describes the structure, possible forms of representation, production process and verification process applicable to VDSs, for any type of document or object to which they relate. This document does not establish requirements for users that issue and verify documents or for users that implement and deploy VDSs. This document does not apply to detailed response formatting functions (RFFs). These requirements and functions are defined by the trust service operator (TSO) and generally cover functionalities such as the security levels of certificates and governance rules to be applied to document issuers and trust service providers (TSPs) intervening in the VDS ecosystem. This document does not apply to the governance related to the operation of the VDS scheme. It is not intended to replace the specifications from Agence Nationale des Titres Sécurisés (ANTS), Bundesamt für Sicherheit in der Informationstechnik (BSI) and International Civil Aviation Organization (ICAO) documents.

  • Standard
    40 pages
    English language
    sale 15% off
  • Standard
    41 pages
    French language
    sale 15% off

This document specifies a structure for globally and unambiguously identifying organizations, and parts thereof, for the purpose of information interchange. This document also gives recommendations regarding cases where prior agreements can be concluded between interchange partners. This document does not specify file organization techniques, storage media, languages, etc. to be used in its implementation. NOTE The procedure for registration of organization identification schemes is specified in ISO/IEC 6523-2.

  • Standard
    10 pages
    English language
    sale 15% off

This document is part of the ISO/IEC 5087 series, which specifies a common data model for cities. This document specifies the foundation level concepts.

  • Standard
    50 pages
    English language
    sale 15% off
  • Draft
    50 pages
    English language
    sale 15% off

This document specifies the syntax, semantics and decoding processes for MPEG immersive video (MIV), as an extension of ISO/IEC 23090-5. It provides support for playback of a three-dimensional (3D) scene within a limited range of viewing positions and orientations, with 6 Degrees of Freedom (6DoF).

  • Standard
    71 pages
    English language
    sale 15% off

This document establishes terms and definitions that are useful in the specification, characterization and evaluation of presentation attack detection (PAD) methods. This document does not provide the following: — standardization of specific PAD detection methods; — detailed information about countermeasures (i.e. anti-spoofing mechanisms), algorithms or sensors; — overall system-level security or vulnerability assessment. The attacks to be considered in this document are those that take place at the capture device during the presentation and collection of the biometric characteristics. Any other attacks are considered outside the scope of this document.

  • Standard
    11 pages
    English language
    sale 15% off

This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
—     ASN.1 (data) types within the fields of EFC;
—     ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

  • Draft
    55 pages
    English language
    sale 10% off
    e-Library read for
    1 day

In respect of pan-European eCall (operating requirements defined in EN 16072), this document defines the high-level application protocols, procedures and processes required to provide the eCall service using a TS12 emergency call over a circuit-switched mobile communications network.
NOTE 1   The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2   HLAP requirements for third-party services supporting eCall can be found in EN 16102, and have been developed in conjunction with the development of this work item, and is consistent in respect of the interface to the PSAP. This deliverable makes reference to those provisions but does not duplicate them.

  • Draft
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies an interoperable, open and extensible information structure for recording PII principals' consent to PII processing. This document provides requirements and recommendations on the use of consent receipts and consent records associated with a PII principal's PII processing consent, aiming to support the: — provision of a record of the consent to the PII principal; — exchange of consent information between information systems; — management of the life cycle of the recorded consent.

  • Technical specification
    52 pages
    English language
    sale 15% off
  • Draft
    51 pages
    English language
    sale 15% off
  • Draft
    51 pages
    English language
    sale 15% off

This document specifies common encryption formats for use in any file format based on ISO/IEC 14496-12. File, item, track, and track fragment metadata is specified to enable multiple digital rights and key management systems (DRMs) to access the same common encrypted file or stream. This document does not define a DRM system. The AES-128 symmetric block cipher is used to encrypt elementary stream data contained in media samples. Both AES counter mode (CTR) and Cipher Block Chaining (CBC) are specified in separate protection schemes. Partial encryption using a pattern of encrypted and clear blocks is also specified in separate protection schemes. The identification of encryption keys, initialization vector storage and processing is specified for each scheme. Subsample encryption is specified for NAL structured video, such as AVC and HEVC, to enable normal processing and editing of video elementary streams prior to decryption. An XML representation is specified for important common encryption information so that it can be included in XML files as standard elements and attributes to enable interoperable license and key management prior to media file download.

  • Standard
    42 pages
    English language
    sale 15% off
  • Draft
    42 pages
    English language
    sale 15% off
  • Draft
    42 pages
    English language
    sale 15% off

This document provides methodology for the use of formal methods to assess robustness properties of neural networks. The document focuses on how to select, apply and manage formal methods to prove robustness properties.

  • Standard
    23 pages
    English language
    sale 15% off
  • Draft
    22 pages
    English language
    sale 15% off

This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines: — ASN.1 (data) types within the fields of EFC; — ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC. This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

  • Standard
    49 pages
    English language
    sale 15% off

This document specifies a cloud AC based wireless local area network (WLAN) networking architecture, defines the cloud access controller dispatch platform (CADP) operating mechanism and the interaction between the network elements such as CADPs, access points (APs), cloud access controllers (ACs) and the WLAN network management system (NMS), and specifies the main functional requirements of each network element. This document applies to public WLAN networking scenarios.

  • Standard
    10 pages
    English language
    sale 15% off

This document defines the stages and identifies associated actions for data processing throughout the artificial intelligence (AI) system life cycle, including acquisition, creation, development, deployment, maintenance and decommissioning. This document does not define specific services, platforms or tools. This document is applicable to all organizations, regardless of type, size or nature, that use data in the development and use of AI systems.

  • Standard
    10 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off

This document specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. This document also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. The requirements set out in this document are generic and are intended to be applicable to all organizations, regardless of type, size or nature.

  • Draft
    24 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides an overview of the whole ISO/IEC 19763 series. This overview includes the purpose, the underlying concepts, the overall architecture and the requirements for the development of other standards within the 19763 series. Collectively, the other parts of the ISO/IEC 19763 series provide a set of normative metamodels to enable the registration of many different types of model. Each of these metamodels is expressed both as a UML class diagram and, more formally, in text. The metamodels, along with the specification in ISO/IEC 11179-3, define the information about the models that is to be registered. The models themselves can be stored in a model repository or can just exist as paper documents. The ISO/IEC 19763 series does not specify any physical structure of a registry where model information is to be recorded.

  • Standard
    17 pages
    English language
    sale 15% off

This document specifies the metamodel that provides a facility to register administrative information and common semantics of models. This document does not specify the metamodel of models in a specific language, but provides a common core metamodel for the other parts of the ISO/IEC 19763 series, each of which specifies a metamodel for a registry that can register models of a specific type, such as ontologies, process models or information models, in a number of different languages.

  • Standard
    24 pages
    English language
    sale 15% off

This document provides a framework and recommendations for establishing trusted connections between devices and services based on hardware security modules. It includes recommendations for components such as: hardware security module, roots of trust, identity, authentication and key establishment, remote attestation, data integrity and authenticity. This document is applicable to scenarios that establish trusted connections between devices and services based on hardware security modules. This document does not address privacy concerns.

  • Standard
    24 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off

IEC 63474:2023 specifies methods of measurement of electrical power consumption in networked standby and the reporting of the results for edge equipment. Power consumption in standby (other than networked standby) is covered by EN 50564, including the input voltage range. This document also provides a method to test power management and to test whether it is possible to deactivate wireless network connection(s). This document does not apply to the measurement of electrical power consumption in networked standby for interconnecting equipment.

  • Draft
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document gives general guidance for the stages in the life cycle of a system’s biometric and associated elements. This covers the following: — the capture and design of initial requirements, including legal frameworks; — development and deployment; — operations, including enrolment and subsequent usage; — interrelationships with other systems; — related data storage and security of data; — data updates and maintenance; — training and awareness; — system evaluation and audit; — controlled system expiration. The areas addressed are limited to the design and implementation of biometric technologies with respect to the following: — legal and societal constraints on the use of biometric data; — accessibility for the widest population; — health and safety, addressing the concerns of users regarding direct potential hazards as well as the possibility of the misuse of inferred data from biometric information. This document is intended for planners, implementers and system operators of biometric applications. Specification and assessment of government policy are not within the scope of this document. However, this document is intended to be beneficial to public authorities when deploying biometric systems.

  • Standard
    31 pages
    English language
    sale 15% off

This document specifies definitions, terminology and processes for secure multiparty computation and related technology, in order to establish a taxonomy and enable interoperability. In particular, this document defines the processes involved in cryptographic mechanisms which compute a function on data while the data are kept private; the participating parties; and the cryptographic properties. The terminology contained in this document is common to the ISO/IEC 4922 series.

  • Standard
    10 pages
    English language
    sale 15% off

This document presents specific characteristics of industrial internet platforms (IIPs), including related security threats, context-specific security control objectives and security controls. This document covers specific security concerns in the industrial context and thus complements generic security standards and reference models. In particular, this document includes secure data collection and transmission among industrial devices, data security of industrial cloud platforms, and secure collaborations with various industry stakeholders. The users of this document are organizations who develop, operate, or use any components of IIPs, including third parties who provide services to the abovementioned stakeholders. This document provides recommendations for users on how to protect IIPs against IIP-specific threats.

  • Standard
    34 pages
    English language
    sale 15% off
  • Draft
    33 pages
    English language
    sale 15% off

This document defines system engineering and management requirements for the life cycle of websites, including strategy, design, engineering, testing and validation, and management and sustainment for intranet and extranet environments. This document applies to those using web technology to present information and communications technology (ICT) information, such as information for users of systems and services, plans and reports for systems and software engineering projects, and documentation of policies, plans, and procedures for IT service management. This document provides requirements for website owners and website providers, managers responsible for establishing guidelines for website development and operations, website engineers, designers, developers, and operations and maintenance staff, who can be external or internal to the website owner's organization. It applies to websites for public access and for limited access, such as for users, customers, and subscribers seeking information on IT systems, products and services. The requirements and recommendations in this document address the following aspects of usability of informational websites and ease of maintenance of managed website operations: a) locating relevant and timely information; b) applying information security management; c) facilitating accessibility and ease of use; d) providing for consistent and efficient development and maintenance practices. This document is not particularly applicable to websites used primarily for marketing or sales, to deliver instructional material (tutorials), or to provide graphical user interfaces (GUI) for business or consumer transactional application processing. However, this document can provide useful insights for managing such sites. This document does not address vendor and product considerations for website engineering and management. This document does not include specifications for application development tools, programming and scripting languages used for websites, metadata tags, or protocols for network communications. It does not address tools or systems used for management or storage of information content (data, documents) that can be presented on websites. This document does not address the design and architecture of software and systems supporting the Internet.

  • Standard
    57 pages
    English language
    sale 15% off
  • Draft
    57 pages
    English language
    sale 15% off