This guide categorizes the autonomous capabilities of an automatic through autonomous-unmanned ground vehicle (A-UGV) based on a list of eleven capability categories.
Smart parking lots (SPLs) integrate parking information to enable the coordination of parking facilities within smart cities. SPLs work with other systems to provide various parking services. This Recommendation specifies the requirements and functional architecture for SPLs. The scope of this Recommendation includes: introduction of SPLs; requirements for SPL; Functional architecture of SPL. For use cases of SPL see Appendix I. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
Cryptographic and data authentication procedures for storage devices that support length expansion, such as tape drives, are specified. Such procedures include the following cryptographic modes of operation for the AES block cipher: CCM, GCM, CBC-HMAC, and XTS-HMAC.
EME2-AES and XCB-AES wide-block encryption with associated data (EAD) modes of the NIST AES block cipher, providing usage guidelines and test vectors, are described. A wide block encryption algorithm behaves as a single block cipher with a large plaintext input and ciphertext output, but uses a narrow block cipher [in this case Advanced Encryption Standard (AES)] internally. These encryption modes are oriented toward random access storage devices that do not provide authentication, but need to reduce the granularity of a potential attack.
Cryptographic transform for protection of data in sector-level storage devices is specified in this standard.
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.