Working group

The purpose of the standard is to extend the CORA ontology to represent more specific concepts and axioms that are commonly used in Autonomous Robotics. The extended ontology specifies the domain knowledge needed to build autonomous systems comprised of robots that can operate in all classes of unstructured environments. The standard provides a unified way of representing Autonomous Robotics system architectures across different R&A domains, including, but not limited to, aerial, ground, surface, underwater, and space robots. This allows unambiguous identification of the basic hardware and software components necessary to provide a robot, or a group of robots, with autonomy (i.e. endow robots with the ability to perform desired tasks in unstructured environments without continuous explicit human guidance).

The scope of this standard is a service-oriented medical device architecture and communication protocol specification for distributed system of Point-of-Care (PoC) medical devices and medical IT systems that need to exchange data or safely control networked PoC medical devices. It identifies the functional components, their communication relationships as well as the binding of the components and communication relationships to protocol specifications.

The standard defines methods of out-of-band third-party individual identity attestation and secure conveyance requiring no key storage on the endpoint device.

The standard describes an authentication scheme including the following features: 1) User needs single unique login credentials to logon to multi-Server setup 2) It offers a two-factor authentication scheme comprising of password as one and the soft token/hardware token as the second factor for authentication 3) The scheme does not require a password table to be maintained at the server 4) The scheme resists various known authentication related attacks

The IEEE Standards Association (IEEE SA) pre-standards workstream for Clinical Internet of Things (IoT) data validation and interoperability with blockchain was initiated to determine if a viable standards framework could be established to enable the validation of data generated from a clinical-grade IoT device and shared through the interoperability of blockchain technology. Participants in the workstream were gathered from an IEEE SA workshop held at Johns Hopkins University in Rockville, Maryland in April 2018, and grew to include their network of healthcare and Health-IT ecosystem players, as well as participants in prior IEEE SA efforts in related areas. The workstream commenced in August 2018 and completed in February 2019. Participants in this pre-standards workstream who are the authors of this paper are listed in Appendix A. The pre-standards workstream led to the recommendation of the development of an IEEE SA Standards effort on Clinical IoT data and device interoperability with TIPPSS-Trust, Identity, Privacy, Protection, Safety and Security-in connected healthcare to improve data sharing and healthcare outcomes. The pre-standards workstream team decided that blockchain is not necessary for clinical IoT data and device interoperability and validation, nor does it necessarily meet the robust TIPPSS needs in connected healthcare. The workstream recommendation includes a draft TIPPSS Architectural Framework for Clinical IoT data validation & interoperability, which could include digital ledger technology but does not need to do so. The resulting IEEE Standards Association P2733 working group to develop a standard for Clinical IoT Data and Device Interoperability with TIPPSS kick off meeting is scheduled for July 17, 2019, sponsored by the IEEE SA Engineering in Medicine and Biology Society (EMBS).

Data Protection, Privacy and Identity Management

Cybersecurity services

Security evaluation and assessment

The WG considers national and international standards for adoption in the domain of management system standards including supporting control sets covering information and cyber security. Where not being developed by other SDO's, the WG may develop CEN/CENELEC publications in this domain.

Preparation of a first draft business plan - Review the task list ( N08) provided by the CEN-CLC Cybersecurity Coordination Group (CSCG) and asses how these tasks could be taken up in the upcoming TC 13 work

The CSA Quantum Safe Security Working Group's goal is to address key generation and transmission methods that will aid the industry in understanding quantum-safe methods for protecting their data through quantum key distribution (QKD) -- a physics‐based technology to securely deliver keys-- and post-quantum cryptography (PQC) -- mathematical algorithms that are resistant to quantum computing. The goal of the working group is to support the quantum‐safe cryptography community in development and deployment of a framework to protect data whether in movement or at rest.

‘Vanilla’ cloud environments were typically not made to handle harsh environments like that of High Performance Computing (HPC) Cloud Security. Technical concerns for HPC are further complicated by the complex and ever-evolving threat landscape. As we increasingly see cases of pure HPC bare metal infrastructure interacting with the cloud such as I/O interfaces and processes, it brings along more ‘opportunities’ for malicious attacks. While this should be considered and integrated into security policies and guidelines, performance face the perilof being compromised as precious resources are carved out for security protocols and processes. The crossing of cloud and HPC environments often leads us to questions of how security in an HPC cloud environment can be implemented, enforced and ensured without the need to compromise performance. This Working Group strives to provide recommendations that can answer these questions.