ISO 24511:2007, 2.24.Activities relating to drinking water and wastewater services::Guidelines for the management of wastewater utilities and for the assessment of wastewater services
The definitions in this edition of ISO 6107 are based on available standards and aim to harmonise the understanding of terms used within ISO TC147 Water quality to facilitate clear understanding and application of the water quality standards and to reduce variation of interpretation as far as possible. Source information is provided where available. This standard aims to improve and feed the terminology database for ISO TC147 and to serve as a reference document for all water quality characterisation committees and users. Terms and the interpretation thereof may differ in various fields i.e.: chemistry microbiology and ecotoxicology. This is indicated in brackets, if applicable, after the term being defined. ISO 6107 is restricted to definitions for terms which appear in standards of ISO/TC 147, Water quality.
This work item will define guidance to the user in order to build his/her own service composition with the expected and relevant quality of experience (QoE) and to ensure his/her data privacy
Along with the development of the Internet of things (IoT) and smart cities and communities (SC&C), various applications have different kinds of requirements for data management, and there are many challenges, especially in data representing, data processing, data service provisioning, and other aspects in a secure and effective manner. Meanwhile, blockchain as an emerging technology possesses the characteristics of trust, transparency, traceability and accountability. It has the potential capabilities to solve the existing issues in data management. Recommendation ITU-T Y.4561 specifies the requirements, generic reference model, common capabilities, and procedures of blockchain-based data management.
Discovery, authentication, and authorization protocols between hosts and storage devices over multiple transports are defined in this standard.
The functions and features to be provided in intelligent electronic devices (IEDs) to accommodate critical infrastructure protection programs are defined in this standard. Security regarding the access, operation, configuration, firmware revision and data retrieval from an IED are addressed. Communications for the purpose of power system protection (teleprotection) are not addressed in this standard.
The enhanced security management function for the protocol defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol,” is described in this standard. Security requirements, system security architecture definitions, and a standardized description of authentication and authorization, along with security procedures and protocols, are specified. This standard can help avoid unintended data disclosure to the public and unauthorized access to resources, while providing enhanced integrity and confidentiality of transmitted data in the ubiquitous green community control network.
Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.
This guide describes recommended practices for the physical security of electric power substations. It is designed to address a number of threats, including unauthorized access to substation facilities, theft of material, and vandalism. It describes options for positive access control, monitoring of facilities, and delay/deter features which could be employed to mitigate these threats. This guide also establishes options for different levels of physical security for electric power substations. The guide does not establish recommendations based on voltage levels, size or any depiction of criticality of the substation. The user will make these decisions based on threat assessment and criticality assignment by the substation owner. Overt attacks against the substation for the purpose of destroying its capability to operate, such as explosives, projectiles, vehicles, etc. are beyond the scope of this guide.
ISO/TS 17975:2015, 3.1. Health informatics::Principles and data requirements for consent in the Collection, Use or Disclosure of personal health information
ISO/TS 21089:2018 describes trusted end-to-end flow for health information and health data/record management. Health data is originated and retained, typically as discrete record entries within a trusted electronic health record (EHR), personal health record (PHR) or other system/device. Health data can include clinical genomics information.Health record entries have a lifespan (period of time managed by one or more systems) and within that lifespan, various lifecycle events starting with (1) originate/retain. Subsequent record lifecycle events may include (2) update (3) attest (4) disclose (5) transmit (6) receive (7) access/view, and more. A record entry instance is managed over its lifespan by the source system. If record entry content is exchanged, this instance may also be managed intact by one or more downstream systems. Consistent, trusted management of record entry instances is the objective of this document, continuously and consistently whether the instance is at rest or in motion, before/during/after each lifecycle event, across one or more systems.
This document specifies a generic business process framework for a smart city focusing solely on smart city-specific processes. Generic business processes common between smart cities and commercial organizations are be identified but not detailed.