hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.11 EAA renewal service | EAA-8.2.11-01: An X.509-AC EAA shall not incorporate any component implementing the semantics specified in clause 4.2.12 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.2.12 EAA short-lived | EAA-8.2.12-01: The etsi-eaaShortLived extension shall implement the semantics specified in clause 4.2.13 of the present document. EAA-8.2.12-02: An X.509-AC EAA may incorporate the etsi-eaaShortLived extension. EAA-8.2.12-03: The eaashortLived extension shall be as defined below. -- shortLived EAA attestation extension... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.3 Attested attributes | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.3.1 General requirements | EAA-8.3.1-01: An X.509-AC EAA shall incorporate each individual Attested Attribute as an instance of the Attribute type specified in clause 4.2.7 of IETF RFC 5755 [6]. EAA-8.3.1-02: An X.509-AC EAA shall place the individual Attested Attributes in the attributes field. The present document specifies two implementations... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.3.2 Attested attributes for X.509 AC/JSON implementation | EAA-8.3.2-01: An X.509-AC EAA conformant to the X.509 AC/JSON implementation, shall place the attributes within one instance of JSONEncodedAttribute type. EAA-8.3.2-02: JSONEncodedAttribute shall be as defined below. -- JSON encoded attestation extension id-etsi-eaa-x509AC-ext-jsonattr OBJECT IDENTIFIER ::= { id-etsi-e... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.3.3 Attested attributes for X.509 AC/ASN.1 implementation | EAA-8.3.3-01: Within an X.509-AC EAA conformant to the X.509 AC/ASN.1, each attribute shall be a DER-encoded instance of a specific ASN.1 type, and shall be placed within the attributes sequence as specified in IETF RFC 5755 [6], clause 4.2.7. EAA-8.3.3-02: For associating a set of attributes to one entity different th... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.4 Attested attributes metadata | 8.4.1 Implementation of support to selective disclosure of Attested Attributes An X.509-AC EAA can achieve selective disclosure through atomic EAAs, i.e. X.509 Attribute Certificates attesting only one attribute. EAA-8.4.1-01: EAAs Issuer issuing X.509-AC EAA should support the selective disclosure with the issuance of... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.5 EAA data for key binding | In an X.509-AC EAA the key binding is natively implemented, because the requirement EAA-8.2.5.1-03 states that "the holder field shall include the objectDigestInfo field, which in turn, shall have the publickeycert value as specified in IETF RFC 5755 [6], clause 7.3". |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.6 EAA digital signature | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 8.6.1 Requirements for EU Qualified EAA (QEAA) | QEAA-8.6.1-01: The requirements specified in clause 4.6.2 shall apply 8.6.2 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-8.6.2-01: The requirements specified in clause 4.6.3 shall apply. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 63 Annex A (informat... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 1 Scope | The present document provides the interworking specification between the oneM2M service layer and the OGC SensorThings API to enable seamless integration of IoT data and services, particularly in smart city environments. |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 2 References | |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 3 Definition of terms, symbols and abbreviations | |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 3.1 Terms | Void. |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 3.2 Symbols | Void. |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 3.3 Abbreviations | Void. ETSI ETSI TS 118 141 V5.4.1 (2025-11) 6 oneM2M TS-0041 version 5.4.1 Release 5 |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 4 Conventions | The keywords "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 5 Introduction to OGC SensorThings API | The SensorThings API (STA) is a standard of the Open Geospatial Consortium (OGC). It provides a framework for communication and exchanging data between sensors and applications. The standard is divided in two parts. SensorThings API Part 1 [1] is dedicated to sensing and was published in 2016 and updated in 2021. A STA... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.0 Overview | Figure 6.0-1 shows an architecture approach for an Interworking Proxy Entity (IPE) between oneM2M and the OGC SensorThings API. The IPE is located between a oneM2M CSE and an OGC/SensorThings API (STA) server. The basic interworking enables applications that are connected to a oneM2M-based system to get data from senso... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.1 OGC/STA-to-oneM2M data model mapping | According to oneM2M TS-0033 [2], a representation of a non-oneM2M Proximal IoT function/device in a oneM2M-specified resource instance is to be synchronized with the entity that it represents. Thus, the OGC Sensing Entities data model has to be represented in the hosting CSE. The Sensing Entities data model is comprehe... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.2 Communication flow | Figure 6.2-1 shows the oneM2M-to-OGC/STA direction of the communication flow. In order to transfer data from a oneM2M sensor to the OGC/STA server the IPE creates a <subscription> resource to the <container> resource in the CSE containing the desired data. Triggered by a sensor event a new <contentInstance> resource is... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3 Configuration aspects | |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.0 Introduction | To enable interworking, preparation is required for both the oneM2M CSE and the OGC/STA server (see figure 6.3.0-1). As described in clause 6.0, the IPE maps data from an OGC/STA Observation entity to a oneM2M <contentInstance> resource and vice versa. The present document defines a 1-to-1 relationship in each directio... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.1 Configuration of OGC/STA server side | |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.1.0 Overview | Both directions of the data flow between the OGC/STA server and the IPE require their own configuration steps. |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.1.1 Communication direction OGC/STA server towards IPE | In figure 6.3.1.1-1, an OGC/STA client is connected to an OGC/STA server, and its data is forwarded to the IPE. The OGC/STA client publishes data to the OGC/STA server via an HTTP POST message. An Observation entity according to the Sensing Entities data model [1] belongs to a Datastream entity (see figure 5-2). The IP... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.1.2 Communication direction IPE towards OGC/STA server | The IPE requires a destination Datastream entity to send an Observation entity containing data from the oneM2M side. If no associated Datastream entity exists on the OGC/STA server, it shall be created. This can be done beforehand or at the IPE's start-up, depending on the implementation. When a Datastream entity is cr... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.2 Configuration of the oneM2M CSE | |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.2.0 General configuration aspects | The IPE needs to perform configuration steps on the hosting CSE. The IPE shall register itself as an Application Entity (AE) that is represented as an <AE> resource in a oneM2M resource tree. The CSE uses notifications to communicate new events to the IPE (AE). Therefore, the <AE> resource shall have the requestReachab... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.2.1 Communication direction oneM2M CSE towards IPE | Two <container> resources are required in the CSE for the operation of the IPE, one for outgoing data and one for incoming data. The <container> resource that is appointed to hold the data to be forwarded to the OGC/STA side (outgoing data) has to be created, if not already existing. The message flow for the creation o... |
7efb944d94d19e29c48c44c584f47180 | 118 141 | 6.3.2.2 Communication direction IPE towards oneM2M CSE | The <container> resource that is appointed to hold the data from the OGC/STA side (incoming data) has to be created, if not already existing. The message flow for the creation of a <container> resource is shown in figure 6.3.2.1-1. The CSE is now prepared to receive data from OGC/STA via the IPE. The IPE sends data as ... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 1 Scope | The present document specifies a framework for use within ETSI TC DATA to coordinate and promote public demonstrations of Proof of Concept (PoC) validating key technical components developed in TC DATA. The objective for the PoCs is to build commercial awareness and confidence and encourage development of an open ecosy... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 2 References | |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 3 Definition of terms, symbols and abbreviations | |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 3.1 Terms | For the purposes of the present document, the following terms apply: DATA PoC proposal: initial description of a PoC Project, submitted as a contribution for review and acceptance by the TC DATA before the PoC Project starts NOTE: See annex A. DATA PoC report: detailed description of the results and findings of a PoC p... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 3.2 Symbols | Void. |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence API Application Programming Interface CTI Centre for Testing and Interoperability EU European Union F2F Face to Face ICT Information Computing Technology IoT Internet of Things LD Low Delay NGSI Next Generation Servi... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4 TC DATA PoC Framework | |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.1 Rationale | The distributed solutions considered by TC DATA include data infrastructures, data products, data access services, and Application Interfaces (APIs) in the ICT domain, to be used by machines and human beings, and their virtual representations. These solutions address the three dimensions of distributed data processing,... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.2 Call for PoCs | The ETSI TC DATA calls for PoC proposals during the life of the TC. Details will be made publicly available on the ETSI TC DATA portal. ETSI ETSI TS 104 200 V1.1.1 (2025-11) 8 |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.3 TC DATA PoC Proposal Submission | PoC Team formation is beyond the scope of the TC DATA. The PoC Team shall prepare a TC DATA PoC Proposal according to the TC DATA PoC Proposal template in clause A.1, and the TC DATA PoC Review Team may be consulted in support of this effort. The PoC Proposal shall be submitted to the TC DATA as a contribution uploaded... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.4 TC DATA PoC Proposal Review | |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.4.1 General | The TC DATA solutions PoC Review Team is responsible for administering this TC DATA PoC process. The TC DATA solutions PoC Review Team shall collect and distribute the TC DATA PoC Proposals and announce the accepted TC DATA PoC Proposal based on the review against the TC DATA PoC acceptance criteria of clause 4.5. The ... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.4.2 Accepted TC DATA PoC Proposals | The DATA solutions PoC Review Team will send an email to the PoC Team to confirm the acceptance of the TC DATA PoC Proposal. The DATA solutions PoC Review Team will send an email to the 'DATA@LIST.ETSI.ORG' list to announce each accepted TC DATA PoC Proposal to the TC DATA community. Keep a "List of Accepted Proposals"... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.4.3 Rejected TC DATA PoC Proposals | The DATA solutions PoC Review Team will send an email to the PoC Team to notify them that the TC DATA PoC Proposal has been rejected with the reason based on the criteria of clause 4.5. No further action will be taken by the TC DATA on rejected proposals. PoC Teams may submit revised TC DATA PoC Proposals for future co... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.5 TC DATA PoC Proposal Acceptance Criteria | The criteria for acceptance of TC DATA PoC Proposals are: 1) The TC DATA PoC Proposal shall contain the information requested in the format of the TC DATA PoC Proposal Template of clause A.1, referred to as the PoC Team. This will be checked by ETSI CTI and the PoC Review Team. 2) The organizations participating in a P... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 4.6 TC DATA PoC Report | Once an TC DATA PoC Team project is concluded, a TC DATA PoC Report with the PoC results is expected to be provided to TC DATA as a contribution to a plenary of TC DATA physical meeting or be announced on the 'DATA@list.etsi.org' mailing list. A PoC Wiki section of the ETSI portal via a link on the TC DATA home page wi... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 5 Overall Roles and Activities within PoCs | |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 5.1 General | TC DATA participants activities when forming PoC Teams and executing PoC Projects are outside the scope of the TC DATA. The TC DATA shall not manage individual PoC Projects nor get involved in forming PoC Teams or executing TC DATA PoC Proposals. |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 5.2 ETSI CTI Role | The ETSI Centre for Testing and Interoperability (CTI) has experience in supporting the organization of technology evaluations and interoperability events (in many ways similar to PoCs). This experience may be useful in assisting the PoC Teams with administration and project management support including: • Formation of... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 5.3 Other roles and responsibilities | TC DATA: The TC DATA is interested in the outcome of the PoC projects. In the context of the PoC framework, it is in charge of: • Identifying PoC topics. • Identifying expected contributions and timelines for PoC topics. • Processing the contributions made by the PoC teams on those topics. PoC Review Team: Entity in ch... |
91caf3fd1a84827e4401fd4afd8a0efb | 104 200 | 5.4 PoC activity process | Figure 1 provides a description of the PoC activity process. Figure 1: PoC Activity Process New PoC topic New PoC topic identification Comments Comments Yes Yes PoC proposal No PoC Report No PoC proposal review PoC Project Lifetime PoC report review PoC proposal preparation Accepted? PoC team PoC Review Team / Experts ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 1 Scope | The present document provides guidance for implementing the Critical Security Controls to mitigate the most common form of attacks against Industrial Control Systems (ICS) commonly found in critical infrastructure. |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 2 References | |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 3 Definition of terms, symbols and abbreviations | |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 3.1 Terms | For the purposes of the present document, the following terms apply: 3-2-1 backup policy: popular rule of thumb for protecting data by making multiple copies access control: process of granting or denying specific requests for obtaining and using information and related information processing services; and to enter spe... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 3.2 Symbols | Void. ETSI ETSI TS 104 100 V1.1.1 (2025-11) 18 |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authentication, Authorization, and Accounting ACL Access Control List AD Active Directory API Application Programming Interface ARP Address Resolution Protocol BYOD Bring Your Own Device CD Compact Disc CERT Computer Emergency Response Tea... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.1 Introduction, Methodology and Use | A consistent approach is needed for analysing the Controls in the context of ICS. For each of Control, the following information is provided: • ICS Applicability: This assesses the degree to which a Control and Safeguard functions or pertains to ICS. ETSI ETSI TS 104 100 V1.1.1 (2025-11) 20 • ICS Challenges: These are ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2 Applying the Critical Security Controls and Safeguards | |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.1 CONTROL 01 Inventory and Control of Enterprise Assets | ICS Applicability The first Control is the most important because it is necessary to first identify the systems and devices that need to be secured. Control 1 is about taking inventory. Understanding and solving the asset inventory and device visibility problem is critical in managing an enterprise security program. Th... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.2 CONTROL 02 Inventory and Control of Software Assets | ICS Applicability This Control offers steps needed to identify, track, and account for software and firmware used in the OT environment. Actively managing software can be a challenge in ICS. Much of the software is provided by vendors and is tied to specific hardware platforms. This software often has commercially avai... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.3 CONTROL 03 Data Protection | ICS Applicability This Control's focus is on data protection and the relevance greatly varies based on ICS environment. These environments often do not contain much if any sensitive data in the traditional sense (PII, credit cards, etc.) In many ICS networks, control data consists of physical measurements such as flow,... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.5 CONTROL 05 Account Management | ICS Applicability Internet of Things (IoT) devices can play a large role in the ICS environment. ICS IoT devices will have a series of accounts already created and in use when the device is purchased and shipped. Account management is applicable to the mobile applications, devices, and cloud platforms all used for IoT.... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.6 CONTROL 06 Access Management Control | ICS Applicability OT devices may require access management but are often not integrated into traditional directory services for user management. This is due to the fact that software is often used to access a device interface, or there is no user account needed to interact with the device. Access Control Management is ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.7 CONTROL 07 Continuous Vulnerability Management | ICS Applicability This Control addresses the need for continuous vulnerability management, which can be a significant task in most enterprises. Understanding and managing vulnerabilities is just as challenging to an ICS environment as it is to traditional IT systems. One advantage the ICS has in this arena is that thes... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.8 CONTROL 08 Audit Log Management | ICS Applicability This Control offers guidance for the maintenance and monitoring of audit logs [i.42]. Logging of security events in ICS environments can be a challenge due to the nature of many of the embedded or legacy devices present. Many devices do not support native logging of security events. Those that do ofte... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.9 CONTROL 09 Email and Web Browser Protections | ICS Applicability This Control focuses on the security of web browsers and email clients, which are very vulnerable to attack vectors. Most ICS environments do not require internet access, and email clients are not needed because they are often isolated from business networks. Email is utilized in ICS environments but ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.10 CONTROL 10 Malware Defences | ICS Applicability This Control addresses the steps needed to ensure a strong defence against malware intrusions. Malicious code is a very real threat to ICS. It has been crafted to target the devices or processes unique to these industries. While proper network segmentation and defence-in-depth strategies help to mitig... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.11 CONTROL 11 Data Recovery | ICS Applicability This Control references the need for performing system backups for data recovery capability. It requires different approaches within individual ICS environments. Different components support various backup methods. While some support full system backups, the majority offer only configuration exports. ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.12 CONTROL 12 Network Infrastructure Management | ICS Applicability This Control addresses the need to manage the configuration of all network devices using a change control process. The network infrastructure of an ICS network typically carries additional requirements when compared to traditional IT systems. Usually, these networks focus on availability and are archi... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.13 CONTROL 13 Network Monitoring and Defence | ICS Applicability The network infrastructure of an ICS network typically carries additional requirements when compared to traditional IT systems. Usually, these networks focus on availability and are architected with real-time performance and redundancy requirements. Network defences cannot be relied upon to be perfect... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.14 CONTROL 14 Security Awareness and Skills Training | ICS Applicability This Control focuses on educating and training based on job-role in a range of security practices that span basic to advanced skills, and to security awareness and vigilance. Human error, oversights, and negligence are leading causes of security weakness, and the consequences of untrained or inadequat... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.15 CONTROL 15 Service Provider Management | ICS Applicability In our modern, connected world, enterprises rely on service providers to help manage their data or rely on third-party infrastructure for core applications or functions. This Control covers actions that should be taken to ensure that third-party service providers are properly securing their customers'... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.16 CONTROL 16 Application Software Security | ICS Applicability This Control focuses on application security in the OT environment, where countless off-the-shelf, web-based, and proprietary applications can be running on a network. This can be a big task for system administrators. It is not uncommon for ICS environments to contain some custom-engineered, in-house ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.17 CONTROL 17 Incident Response Management | ICS Applicability This Control addresses the processes and steps required to prepare for an incident. Well-defined and implemented incident response plans can allow an enterprise to identify, contain, reduce impacts, and more quickly recover from a cyber incident. This is especially important for enterprises where ICS ... |
7f56ede492f66a79f91abae4bbde094b | 104 100 | 4.2.18 CONTROL 18 Penetration Testing | ICS Applicability This Control is focused on designing and conducting controlled penetration testing in an operational technology environment, including connected devices and systems that may not be normally viewed as a constituent component, service, or system for an ICS. The goal is to test both employee responsivene... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 1 Scope | The present document provides the specification of the Services Announcement (SA) service, including its protocol functions, based on ISO 16460 [1]. The definition of the interface between Service Provider and Service Announcer ITS stations (ITS-S) as well as of the communication steps following the service announcemen... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 2 References | |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 3 Definition of terms, symbols and abbreviations | |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 902 [i.2] and the following apply: Services Announcement (SA): provision, via an ITS communication functionality, of information about an ITS-S service NOTE: Such information can include the ITS-S service identity, availability and communication d... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: changeCount Component of samBody channelIndex Component of ServiceInfo pointer to ChannelInfo ChannelInfo Datatype of channelInfos list entry channelInfos Component of samBody chOptions Component of ServiceInfo contentCount Component of changeCount ... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 103 902 [i.2] and the following apply: NOTE: Where an abbreviation defined in ETSI TR 103 902 [i.2] has multiple definitions, the definition appropriate to the context of the present document applies. SU Service User |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 4 SA service introduction | The SA service is an ITS application support functionality operating at the facilities layer of an ITS station. It provides information about available ITS applications and ITS-S services to other ITS stations. It also reports services announced by SA services inside other ITS stations to the ITS applications. The SA s... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5 SA service functional specification | |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.1 SA service in the ITS-S reference architecture | The Services Announcement (SA) service is located at the facilities layer of the ITS-S reference architecture and is divided into a management plane entity and a data plane entity. It interfaces with ITS applications to receive the application registration and to provide the received SAEM content to the ITS application... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.2 SA service functional architecture | The SA management entity is responsible for the registration/update/deregistration of applications and the notifications to applications. It shall offer the following functions: • Register SP: this function enables a Service Provider ITS application to register/update/deregister its offered ITS-S service, or • Register... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.3 Interfaces of the SA service | |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.3.1 Interface to ITS applications | A Service Provider ITS application may register/update/deregister its offered ITS-S service at the SA management using the IF_Registration and the parameters specified in table 1. A Service User ITS application may register/update/deregister potential services of interest at the SA management using the IF_Registration ... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.3.2 Interface between SA message processing and SA management | The SA service entities allocated in the data plane and in the management plane exchange information among each other for the purpose of the service announcement. The SA management uses the communication requirements (see clause 6.2.1) to select a suitable ITS-S communication protocol stack, also referred to as "ITS-S ... |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.3.3 Interface to security plane entities | In case ETSI ITS security [6] at the facilities layer is used, the SA service shall exchange information directly with the entity(ies) in the security plane via the interface IF.Security. |
e9d681ecdb54b17c0af73e2470bc7f9d | 104 091 | 5.3.4 Interface to management plane entities | The SA service may exchange information with the entity(ies) in the ITS management plane via the interface IF.Control. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.