Standard

This part of ISO/IEC 9798 specifies entity authentication mechanisms using symmetric encipherment algorithms. Four of the mechanisms provide entity authentication between two entities where no trusted third party is involved; two of these are mechanisms to unilaterally authenticate one entity to another, while the other two are mechanisms for mutual authentication of two entities. The remaining mechanisms require a trusted third party for the establishment of a common secret key, and realize mutual or unilateral entity authentication.

Source: https://www.iso.org/obp/ui/#iso:std:iso-iec:9798:-2:ed-3:v1:en

This document specifies entity authentication mechanisms using digital signatures based on asymmetric techniques. A digital signature is used to verify the identity of an entity.
Ten mechanisms are specified in this document. The first five mechanisms do not involve an on-line trusted third party and the last five make use of on-line trusted third parties. In both of these two categories, two mechanisms achieve unilateral authentication and the remaining three achieve mutual authentication.

Source: https://www.iso.org/obp/ui/#iso:std:iso-iec:9798:-3:ed-3:v1:en
 

This part of ISO/IEC 9798 specifies entity authentication mechanisms using a cryptographic check function. Two mechanisms are concerned with the authentication of a single entity (unilateral authentication), while the remaining are mechanisms for mutual authentication of two entities.

The mechanisms specified in this part of ISO/IEC 9798 use time variant parameters such as time stamps, sequence numbers, or random numbers, to prevent valid authentication information from being accepted at a later time or more than once.

Source: https://www.iso.org/obp/ui/#iso:std:iso-iec:9798:-4:ed-2:v1:en
 

This part of ISO/IEC 9798 specifies entity authentication mechanisms using zero-knowledge techniques:

— mechanisms based on identities and providing unilateral authentication;

— mechanisms based on integer factorization and providing unilateral authentication;

— mechanisms based on discrete logarithms with respect to numbers that are either prime or composite, and providing unilateral authentication;

— mechanisms based on asymmetric encryption systems and providing either unilateral authentication, or mutual authentication;

— mechanisms based on discrete logarithms on elliptic curves and providing unilateral authentication.

These mechanisms are constructed using the principles of zero-knowledge techniques, but they are not necessarily zero-knowledge according to the strict definition for every choice of parameters.

Source: https://www.iso.org/obp/ui/#iso:std:iso-iec:9798:-5:ed-3:v1:en

This International Standard is aimed at organizations that provide services to communities in cities, and manage the resulting data, as well as decision-makers and policy developers in cities
This International Standard describes, and gives guidance on, a smart city concept model (SCCM) that can provide the basis of interoperability between component systems of a smart city, by aligning the ontologies in use across different sectors. It includes:

• concepts (e.g. ORGANIZATION, PLACE, COMMUNITY, ITEM, METRIC, SERVICE, RESOURCE).

• relationships between concepts (e.g. ORGANIZATION has RESOURCEs, EVENT at a PLACE).

Source: https://www.iso.org/standard/53302.html

This document defines a comprehensive set of evaluation indicators specially related to information and communication technologies (ICT) adoption and usage in smart cities. Firstly, this document establishes an overall framework for all the indicators. Then, this document specifies the name, description, classification and measure method for each indicator.

Source: https://www.iso.org/obp/ui/#iso:std:iso-iec:30146:dis:ed-2:v1:en

The standard establishes a process model by which engineers and technologists can address ethical consideration throughout the various stages of system initiation, analysis and design. Expected process requirements include management and engineering view of new IT product development, computer ethics and IT system design, value-sensitive design, and, stakeholder involvement in ethical IT system design.

Status :  Under development

ICS : 35.210 Cloud computing

This standard defines requirements for a systems/software engineering process for privacy-oriented considerations regarding products, services, and systems utilizing employee, customer or other external user's personal data. It extends across the life cycle from policy through development, quality assurance, and value realization. It includes a use case and data model (including metadata). It applies to organizations and projects that are developing and deploying products, systems, processes, and applications that involve personal information. By providing specific procedures, diagrams, and checklists, users of this standard will be able to perform a conformity assessment on their specific privacy practices. Privacy impact assessments (PIAs) are described as a tool for both identifying where privacy controls and measures are needed and for confirming they are in place.
You can look here for a preview of the Standard Document

Development Status: Under development

This standard describes specific methodologies to help users certify how they worked to address and eliminate issues of negative bias in the creation of their algorithms, where "negative bias" infers the usage of overly subjective or uniformed data sets or information known to be inconsistent with legislation concerning certain protected characteristics (such as race, gender, sexuality, etc.); or with instances of bias against groups not necessarily protected explicitly by legislation, but otherwise diminishing stakeholder or user well-being and for which there are good reasons to be considered inappropriate. Possible elements include (but are not limited to): benchmarking procedures and criteria for the selection of validation data sets for bias quality control; guidelines on establishing and communicating the application boundaries for which the algorithm has been designed and validated to guard against unintended consequences arising from out-of-bound application of algorithms; suggestions for user expectation management to mitigate bias due to incorrect interpretation of systems outputs by users (e.g. correlation vs. causation)
You can look here for a preview of the Standard Document

Development Status: Under development
 

The standard defines specific methodologies to help users certify how they approach accessing, collecting, storing, utilizing, sharing, and destroying child and student data. The standard provides specific metrics and conformance criteria regarding these types of uses from trusted global partners and how vendors and educational institutions can meet them.
You can look here for a preview of the Standard Document

Development Status: Under development
 

The standard defines specific methodologies to help employers to certify how they approach accessing, collecting, storing, utilizing, sharing, and destroying employee data. The standard provides specific metrics and conformance criteria regarding these types of uses from trusted global partners and how vendors and employers can meet them.
You can look here for a preview of the Standard Document

Development Status: Under development