This document provides a framework and establishes requirements for attribute-based unlinkable entity authentication (ABUEA).
This document provides a user-centric framework for handling personally identifiable information (PII), based on privacy preferences.
This document provides a framework for identifying and mitigating re-identification risks and risks associated with the lifecycle of de-identified data.This document is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations, that are PII controllers or PII processors acting on a controller’s behalf, implementing data de-identification processes for privacy enhancing purposes.
ISO/IEC 29100:2011 provides a privacy framework which- specifies a common privacy terminology;- defines the actors and their roles in processing personally identifiable information (PII);- describes privacy safeguarding considerations; and- provides references to known privacy principles for information technology.ISO/IEC 29100:2011 is applicable to natural persons and organizations involved in specifying, procuring, architecting, designing, developing, testing, maintaining, administering, and operating information and communication technology systems or services where privacy controls are required for the processing of PII.
This document gives guidelines for:- a process on privacy impact assessments, and- a structure and content of a PIA report.It is applicable to all types and sizes of organizations, including public companies, private companies, government entities and not-for-profit organizations. This document is relevant to those involved in designing or implementing projects, including the parties operating data processing systems and services that process PII.
This document specifies controls which 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 document provides privacy engineering guidelines that are intended to help organizations integrate recent advances in privacy engineering into system life cycle processes. It describes:(1) the relationship between privacy engineering and other engineering viewpoints (system engineering, security engineering, risk management); and(2) privacy engineering activities in key engineering processes such as knowledge management, risk management, requirement analysis, and architecture design.The intended audience includes engineers and practitioners who are involved in the development, implementation or operation of systems that need privacy consideration, as well as managers in organizations responsible for privacy, development, product management, marketing, and operations.
The document takes a multiple agency as well as a citizen-centric viewpoint. It provides guidance on:- smart city ecosystem privacy protection;- how standards can be used at a global level and at an organizational level for the benefit of citizens; and- processes for smart city ecosystem privacy protection. This document is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations that provide services in smart city environments.
This document defines the scope and key concepts of mixed and augmented reality, the relevant terms and their definitions and a generalized system architecture that together serve as a reference model for mixed and augmented reality (MAR) applications, components, systems, services and specifications. This architectural reference model establishes the set of required sub-modules and their minimum functions, the associated information content and the information models to be provided and/or supported by a compliant MAR system. The reference model is intended for use by current and future developers of MAR applications, components, systems, services or specifications to describe, compare, contrast and communicate their architectural design and implementation. The MAR reference model is designed to apply to MAR systems independent of specific algorithms, implementation methods, computational platforms, display systems and sensors or devices used. This document does not specify how a particular MAR application, component, system, service or specification is designed, developed or implemented. It does not specify the bindings of those designs and concepts to programming languages or the encoding of MAR information through any coding technique or interchange format. This document contains a list of representative system classes and use cases with respect to the reference model.
The standard specifies how Augmented Reality and Virtual Reality (AR/VR) devices should be set up and used in the enterprise; in a manner that ensures Health and Safety (H&S) is maintained, H&S consequences are understood, and additional risks are not introduced. Within this concept of safe usage, there is particular focus on guidance around safe immersion (time) and safety in the workplace. This ISO/IEC standard:(a) defines the concepts of AR, VR, the virtuality continuum and other associated terms such as Augmented Virtuality and Mixed Reality;(b) provides guidance on setting up AR systems;(c) provides guidance on setting up VR systems;(d) provides guidance on safe usage and immersion in AR systems both in the consumer and enterprise domains; and(e) provides guidance on safe usage and immersion in VR systems both in the consumer and enterprise domains.This standard focuses on visual aspects of AR and VR. Other modes such as haptics and olfactory are not addressed within this standard. The standard covers both the hardware (the physical VR/AR head mounted displays) and areas of visual stimulus (the environments and graphics displayed in those headsets). The standard does not cover all possible visual stimulus scenarios; focus is directed toward those areas that are known to have implications on safe use. This specifically includes the source vection (visual illusion of self-motion in physically stationary VR/AR users) and/or motion (physical movement of VR/AR users) and associated safe use considerations. It should be noted that AR/VR have some shared safety concerns, but many are distinct to AR or VR and a consumer or enterprise environment. As such all of these are in scope, and the standard is structured to account for these differences.
ISO/IEC 21823-3:2021 provides the basic concepts for IoT systems semantic interoperability, as described in the facet model of ISO/IEC 21823-1, including:(1) requirements of the core ontologies for semantic interoperability;(2) best practices and guidance on how to use ontologies and to develop domain-specific applications, including the need to allow for extensibility and connection to external ontologies;(3) cross-domain specification and formalization of ontologies to provide harmonized utilization of existing ontologies;(4) relevant IoT ontologies along with comparative study of the characteristics and approaches in terms of modularity, extensibility, reusability, scalability, interoperability with upper ontologies, and so on; and(5) use cases and service scenarios that exhibit necessities and requirements of semantic interoperability.
This recommendation - International Standard provides accompanying reference software for ISO/IEC 23090-9 as an electronic attachment. The use of this reference software is not required for making an implementation of an encoder or decoder in conformance to ISO/IEC 23090-9. Requirements established in ISO/IEC 23090-9 take precedence over the behavior of the reference software.