hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.2 ITS-S communication messages | NN Requirement References UCs 1.1. A sending ITS-S shall be able to correctly sign CAMs using valid AT certificates ETSI TS 102 941 [3] UC-1-1 UC-1-2 UC-1-3 UC-1-4 UC-1-5 UC-2-4 UC-2-5 1.2. A receiving ITS-S shall be able to verify CAMs signed using valid AT certificates ETSI TS 102 941 [3] UC-1-1 UC-1-2 UC-1-3 UC-1-4 ... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.3 ECTL Handling | NN Requirement References UCs 2.1. Check the existence of the ECTL ETSI TS 102 941 [3] EU Certificate Policy [4] UC-1-4 UC-2-5 UC-2-3 2.2. Check the expiration of the ECTL ETSI TS 102 941 [3] EU Certificate Policy [4] UC-1-4 UC-2-5 UC-2-3 2.3. Check the delta ECTL handling ETSI TS 102 941 [3] EU Certificate Policy [4] ... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.4 RCA CTL Handling | NN Requirement References UCs 3.1. The ITS-S checks the RCA CTL for the Access Point of the EA ETSI TS 102 941 [3] UC-3-1 UC-3-2 UC-3-3 UC-3-4 3.2. Handling CTL signed using any present crypto domain (NIST-P256, Brainpool P256r1, Brainpool P384r1) ETSI TS 102 941 [3] UC-3-1 UC-3-2 UC-3-3 UC-3-4 UC-4-1 UC-4-2 UC-4-3 UC-... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.5 RCA CRL Handling | NN Requirement References UCs 4.1. Check the presence of the CRL from the current root CA ETSI TS 102 941 [3] UC-3-4 UC-4-4 4.2. Check the presence of the CRL from the foreign root CA (different RCA case) ETSI TS 102 941 [3] UC-1-4 UC-3-4 UC-4-4 4.3. Check the presence of the currently used AA certificate in the CRL fr... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.6 PKI communication - Enrolment Management | NN Requirement References UCs 5.1. The EA shall be able to track the ITS-S lifecycle ETSI TS 102 941 [3] 5.2. The EA shall be able to verify the presence of the ITS-S technical key in the local database ETSI TS 102 941 [3] UC-3-1 UC-3-2 5.3. The EA shall be able to handle a correct Enrolment Request (valid enrolment be... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.7 PKI communication - Authorization Management | NN Requirement References UCs 6.1. The AA shall be able to handle the authorization request sent by an ITS-S ETSI TS 102 941 [3] UC-4-1 UC-4-2 UC-4-3 UC-4-5 6.2. The AA shall only accept authorization requests with pop (proof of possession) signature in case of ITS-S with privacy requirements ETSI TS 102 941 [3] UC-4-1... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 5.8 PKI interoperability | NN Requirement References UCs 7.1. AA shall be able to communicate with EAs belonging to different RCAs when their corresponding Root CAs are trusted by ECTL and AA and EA both know the certificates and access points of each other. ETSI TS 102 941 [3] UC-4-3 7.2. If the EA has two Access Points in the CTL, the AA shall... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6 Interoperability test descriptions | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.1 Overview | Interoperability test descriptions consist of three groups: • ITS-S secured communication • PKI communication • CA certificate requests These groups are described in the clauses below. |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2 ITS-S secured communication | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.1 Successful basic communication | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.1.1 Use-case 1-1 - Both ITS-S authorized by the same AA | Interoperability Test Description Identifier TD_ITS_SEC_UC1-1 Objective Secure communication between ITS-S authorized by the same AA Description Two ITS-S, authorized by the same AA, are sending CAMs and both accept these CAMs Configuration The CFG_SEC configuration shall be used with additional requirements: • The ATs... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.1.2 Use-case 1-2 - Different AAs of the same PKI | Interoperability Test Description Identifier TD_ITS_SEC_UC1-2 Objective Secure communication between ITS-S authorized by different but commonly trusted AAs Description Two ITS-S, authorized by different AA (belonging to the same RCA), are sending CAMs and both accept these CAMs Configuration The CFG_SEC configuration s... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.1.3 Use-case 1-3 - Peer-to-peer distribution of AA certificate | Interoperability Test Description Identifier TD_ITS_SEC_UC1-3 Objective Secure communication between ITS-S authorized by different and initially partially unknown AAs Description Two ITS-S, authorized by different AA, are sending CAMs. The AA authorizing the sender is initially unknown from the receiver's perspective. ... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.1.4 Use-case 1-4 - Participating ITS-S are registered in different RCAs | Interoperability Test Description Identifier TD_ITS_SEC_UC1-4 Objective Secure communication between ITS-S authorized by AAs of different RCAs Description Two ITS-S, authorized by AAs belonging to different RCAs, are sending CAMs and both accept these CAMs Configuration The CFG_SEC configuration shall be used with the ... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.1.5 Use-case 1-5 - Pseudonym changing | Interoperability Test Description Identifier TD_ITS_SEC_UC1-5 Objective ITS-S are changing the ATs and related identifiers (pseudonym change) as expected Description Two ITS-S, authorized by the same AA, are sending CAMs and both accept these CAMs. The two ITS-Stations are running the same GNSS simulation. The ITS-S sh... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2 Exceptional behaviour basic communication | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.1 Use-case 2-1 - Invalid certificate region | Interoperability Test Description Identifier TD_ITS_SEC_UC2-1 Objective No communication between ITS-S within unauthorized regions Description The sending ITS-S is triggered to send DENMs. The regional restrictions of the available ATs do not include the place of the UC execution Configuration The CFG_SEC configuration... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.2 Use-case 2-2 - Invalid ValidityPeriod of ATs | Interoperability Test Description Identifier TD_ITS_SEC_UC2-2 Objective Rejected sending of CAMs if no AT with a valid ValidityPeriod is available Description The sending ITS-S is triggered to send CAMs. The ValidityPeriod of all available ATs does not include the time of the UC execution ( all ATs are either expired ... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.3 Use-case 2-3 - PSID exceptional behaviour | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.3.1 Use-case 2-3a - CAM PSID missing in ATs - rejected sending | Interoperability Test Description Identifier TD_ITS_SEC_UC2-3a Objective Rejected sending of CAMs if ATs are missing the CAM PSID Description The sending ITS-S is triggered to send CAMs. Its available ATs do not include the PSID for CAMs (36) Configuration The CFG_SEC configuration shall be used with the following addi... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.3.2 Use-case 2-3b - DENM PSID missing in ATs - rejected sending | Interoperability Test Description Identifier TD_ITS_SEC_UC2-3b Objective Rejected sending of DENMs if ATs are missing the DENM PSID Description The sending ITS-S is triggered to send DENMs. Its available ATs do not include the PSID for DENMs (37) Configuration The CFG_SEC configuration shall be used with the following ... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.4 Use-case 2-4 - Using of AT issued by AA included in the CRL | Interoperability Test Description Identifier TD_ITS_SEC_UC2-4 Objective Rejection of CAMs authorized with ATs that are issued by a revoked AA Description The receiving ITS-S does not know the AA that authorized the ATs of the sender. The signer identifier of the received AT refers to a revoked AA. Therefore the receive... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.2.2.5 Use-case 2-5 - Unknown RCA | Interoperability Test Description Identifier TD_ITS_SEC_UC2-5 Objective Rejection of messages of ITS-S belonging to an untrusted RCA Description The receiving ITS-S does not know the RCA of the sender. The untrusted RCA is not part of the ECTL. The sender AA is not known, too, and needs to be requested Configuration Th... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3 PKI communication | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.0 Overview | Interoperability tests for PKI communication can be accomplished through a sequence of the UCs below. Comprehensive scenarios (see clause 6.4) including a sequence of use cases shall describe the ITS-S and PKI communications as a whole, starting with enrolment, authorization by the same or different AA, and finally sen... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.1 Enrolment behaviour | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.1.1 Use-case 3-1 - Valid enrolment behaviour | Interoperability Test Description Identifier TD_ITS_SEC_UC3-1 Objective Valid enrolment behaviour. Description ITS-S stations "senders" are registered to their PKI. Check that the EC certificate is received when the enrolment process is triggered on the ITS-S "sender". It is recommended for the PKI to issue the CTL con... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.1.2 Use-case 3-2 - Enrolment behaviour with already enrolled station | Interoperability Test Description Identifier TD_ITS_SEC_UC3-2 Objective Valid re-enrolment behaviour. Description ITS-S stations "senders" are registered to their PKI and was already enrolled. Check that the new EC certificate is received when the enrolment process is triggered on the ITS-S. Configuration The CFG_PKI_E... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.1.3 Use-case 3-3 - Enrolment behaviour when ITS-S is not registered on the EA | Interoperability Test Description Identifier TD_ITS_SEC_UC3-3 Objective Enrolment behaviour when ITS-S is not registered on the EA. Description ITS-S stations are not registered into their PKI. Check that the new EC certificate is not received when the enrolment process is triggered on the ITS-S. Configuration The CFG_... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.1.4 Use-case 3-4 - Enrolment behaviour when EA is on the CRL | Interoperability Test Description Identifier TD_ITS_SEC_UC3-4 Objective Enrolment behaviour when EA is on the CRL. Description ITS-S stations are registered to their PKI and the corresponding EA was included into the CRL. Check that the ITS-S does not send the enrolment request when triggered or does not consider recei... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.2 Authorization behaviour | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.2.1 Use-case 4-1 - Valid authorization behaviour | Interoperability Test Description Identifier TD_ITS_SEC_UC4-1 Objective Valid authorization behaviour. Description ITS-S stations are enrolled to their PKI. Check that the AT certificate is received when the authorization process is triggered on the ITS-S and ITS-S sends AT request with encrypted EC signature. It is re... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.2.2 Use-case 4-2 - Authorization behaviour with optional privacy requirements | Interoperability Test Description Identifier TD_ITS_SEC_UC4-2 Objective Authorization behaviour with optional privacy requirements. Description ITS-S stations are registered at the PKI with optional privacy requirement. Check that the AT certificate is received when the authorization process is triggered on the ITS-S a... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.2.4 Use-case 4-4 - Authorization behaviour when AA is on the CRL | Interoperability Test Description Identifier TD_ITS_SEC_UC4-4 Objective Authorization behaviour when AA is on the CRL. Description ITS-S stations are registered to their PKI and the corresponding AA was included into the CRL. Check that the ITS-S does not send the authorization request to this AA when triggered or does... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.2.5 Use-case 4-5 - Check renewal of expired AT certificates | Interoperability Test Description Identifier TD_ITS_SEC_UC4-5 Objective Check renewal of expired AT certificates. Description Check that ITS-S requests for new AT when all ATs in the pool are expired or about to be expired. See note. Configuration The CFG_PKI_AUTHORIZATION configuration shall be used with additional re... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.3 CA certificate request and distribution | |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.3.1 Use-case 5-1 - Initial CA certificate request | Interoperability Test Description Identifier TD_ITS_SEC_UC5-1 Objective Initial CA certificate request. Description CA generates the valid CaCertificateRequestMessage and provides it to RCA. RCA generates a new CA certificate, provides it to the CA, updates and publishes the CTL accordingly. See note. Configuration The... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.3.3.2 Use-case 5-2 - Re-keying of CA certificate | Interoperability Test Description Identifier TD_ITS_SEC_UC5-2 Objective Re-keying of CA certificate. Description CA generates the valid CaCertificateRekeyingMessage and provides it to RCA. RCA generates a new CA certificate, provides it to the CA, updates and publishes the CTL accordingly. See note. Configuration The C... |
edc47863997555e38dbe7042d128ab8e | 103 600 | 6.4 Comprehensive scenarios | Comprehensive scenarios may include a group of ITS-S and their PKI, a group of ITS-S and different PKIs or only PKI certification authorities. When an ITS-S is involved, the test scenario shall start by the enrolment, then the authorization and finish with broadcasting a message (CAM, DENM) to the neighbouring using th... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 1 Scope | The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the Message Queuing Telemetry Transport (MQTT) protocol. It will be a reference base for both client side test campaigns and server side test campaigns addressing the performance issues. |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 2 References | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 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... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 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... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 3 Definition of terms, symbols and abbreviations | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 3.1 Terms | For the purposes of the present document, the following terms apply: active server: connected server with at least 1 registered topic active subscriber: connected client with at least 1 topic subscription application messages: data carried by the MQTT protocol across the network for the application as defined in the OA... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 3.2 Symbols | Void. |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CoAP Constrained Application Protocol CPU Central Processing Unit DOC Design Objective Capacity GTW Gateway IoT Internet of Things IUT Implementation Under Test KPI Key Performance Indicator LAN Local Area Network MQTT Message Queuing Telemetr... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4 Performance metrics | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.0 Introduction | The performance metrics specified herein pertain to the specifics of a MQTT IUT. As such, the objective is to use these metrics in order to determine how well the MQTT component (be it client or server) is performing its functions. As MQTT is a transport protocol, the metrics will be focused on how fast, reliable and e... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.1 Concepts | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.1.1 Test Equipment Considerations | For measuring performance of a given Test System (TS), a comprehensive description of the test environment is required. This includes but it is not limited to: • TS hardware infrastructure: resource specification, type, capacity and distribution. • test environment type and resources (virtualization technology, allocat... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.1.2 Measurement Preliminary Considerations | In order for the collected measurement data to be useful, special consideration needs to be given to the TS setup. Given that the performance evaluation is targeting one or several IUTs same TS setup characteristics are required in order for the evaluation results to allow valid comparisons between them. Some of the ch... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2 Measurement Methodology | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2.0 Introduction | This clause presents the test methodology for MQTT performance evaluation. From the performance perspective, all measurable metrics related to the protocol should be considered. Although not exhaustive, these metrics can be categorized as follows. Powerfulness metrics, as defined in ETSI TR 101 577 [i.2] include 3 sub ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2.1 Metric Post-processing | The collection of metric values from a SUT is performed by multiple agents and/or directly by the IUT. Often a better insight into the IUT performance is gained by post-processing these values in order to get more meaningful results. To this scope, the data samples can be aggregates over time intervals in the experimen... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2.2 Message Types | Table 1 contains the set control packet messages specified by the MQTT [1] standard. ETSI ETSI TS 103 597-3 V1.1.1 (2021-01) 10 Table 1: Message Types Control Packet Name Description Client-> Server Server-> Client Payload CONNECT client requests a connection to the server Required CONNACK acknowledge connection requ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2.3 Test parameters | The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in table 2. Table 2 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2.4 Operation Message Flows | The IUT will be evaluated based on the metric values obtain as a result of the service operations using the messages described in clause 4.1.1. The set of messages exchanged triggered by the initial client message are further referred as operations. For the tests, the metrics use operations rather than specific message... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.2.5 Test Campaign Parameters | For test-campaign evaluations, a sequence of control packet exchanges are specified. This allows for defining multiple types of test benchmarks based on client-server interactions. This may address but not be limited to the following: • duration; • control packet sending order; • number of control packets sent per sess... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.3 Powerfulness metrics | The powerfulness category of performance characteristics contains indicators of speed and quantity of service production. The following metrics are derived from ETSI TR 101 577 [i.2]: • Capacity: ability to accept incoming service requests per time unit. For this metric set, the type of messages considered for evaluati... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.4 Reliability metrics | The reliability category of performance characteristics contains indicators of how predictable a system's service production is. The performance category has subcategories for Quality-of-Service, Stability, Availability, Robustness, Recovery and Correctness: • Stability: Stability characteristics are indicators of a sy... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 4.5 Efficiency metrics | The following metrics are derived from ETSI TR 101577 [i.2]. The performance category efficiency contains different types of indicators of resource usage and resource utilization. These metrics can be recorded additional to the Powerfulness metrics during the specified tests. The scope of these are to determine system ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 5 Configurations | The performance test configurations are derived from the SUT access points and functional test configurations. ETSI ETSI TS 103 597-3 V1.1.1 (2021-01) 16 Figure 6: MQTT Server-Client test configurations Furthermore, there are consideration following possible performance specific load and measurement tools. Figure 7: MQ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6 Benchmarking | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.1 Generic adjustments | This clause specifies the MQTT protocol performance metrics. As a protocol evaluation rationale, the metrics presented herein are directly addressed to IUTs: systems and associated components implementing the protocol, namely clients and servers. No requirements will be expressed regarding specifics of such IUTs in ter... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.2 Benchmarking Methodology | This clause aims to describe a viable methodology for benchmarking the performance of an IUT. In the case of MQTT, an IUT may consist of one or several Brokers or one or several Clients. The approach is inspired from the examples in IETF RFC 2544 [i.1] from the point of view of measurement preconditions, approach and s... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.3 Metric examples | This clause presents a series of benchmark metric examples: • Connection-release delay: the time delay between DISCONNECT message and TCP connection closing. Value expressed in milliseconds (ms). • Setup-delay: the time interval starts when a CONNECT message is sent and ends when the corresponding CONNACK message has b... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.4 Benchmark Examples | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.4.0 Introduction | For evaluating the metrics described in clause 4, the benchmark tests can be grouped in 3 main categories: 1) Load Tests: These tests are used for determining or validating the IUT workload range. The workload consists of one or multiple message exchanges between the IUT and the Test System. The aim is to observe the P... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.4.1 KPI Determination | The KPI determination benchmark is an exploratory performance evaluation that aims to determine the operational performance of an IUT. The KPIs are specified as an input. The scope of this evaluation is to establish a reliable indication of how the SUT is expected to perform in production. The KPIs are determined accor... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 6.4.2 KPI Validation | The KPI validation benchmark is performance evaluation that aims to validate whether the IUT performs according to requirement specifications. The KPIs and their thresholds are specified as an input. The scope of this evaluation is to establish a reliable indication of how the SUT is expected to perform in production. ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 7 Examples of Tests | |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 7.0 Introduction | A test should be presentable as a document, with accompanying data files, that provides a full description of an execution of a performance test on a test system. Description of the test case and objective of the test case, e.g. the definition of the targeted metrics should be contained therein. The following sections ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 7.1 Test Objectives | In this clause example 2 formalized test objective examples are presented. A set of test purposes are presented in Annex A. EXAMPLE 1: Broker Publish Load Test: Determine if the IUT (broker) can handle the given publish message load for a determined period of time without exceeding the delay threshold within a given ... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 7.2 Test Purpose | In this clause a formalized test purpose example is provided. A set of test purposes are presented in Annex A. Precondition: • The IUT is running and configured to accept client connections. • Client(s) send CONNECT messages. • Client(s) start sending PUBLISH messages at a specified rate (messages per second) totalling... |
7c42d60174b604a02661bba1af94b34a | 103 597-3 | 7.3 Test Report | The test report will include the test execution time, test parameters (e.g. number of messages, rate) and measurement/aggregated measurement results (e.g. the average PUBLISH/PUBACK message sequence latency was 3 ms end-to-end). Table 4: Performance load test report for PUB/ACK example Test Number T-01 Test Category Pe... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 1 Scope | The present document provides general security considerations and guidelines about the Message Queuing Telemetry Transport (MQTT) protocol. The collective ideas presented in the present document are enriched with example Test Purposes (TPs) to outline possible implementations. |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 2 References | |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 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... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 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... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 3 Definition of terms, symbols and abbreviations | |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: black-box testing: testing activity conducted without knowledge of the internal structure of the system under test grey-box testing: testing activity conducted with a partial knowledge of the internal structure of a system under test system under test... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 3.2 Symbols | Void. |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CVE Common Vulnerabilities and Exposures DoS Denial of Service IUT Implementation Under Test JSON JavaScript Object Notation MITM Man-in-the-Middle MQTT MQ Telemetry Transport SQL Structured Query Language SUT System Under Test TDL Test Descri... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 4 Security Test Objectives | When talking about security test objectives mean assets that are worth protecting. This clause does not focus on how to protect those assets but raising awareness when it comes to implementing the protocol, especially within an IoT environment. Of course, the following list does not claim to be complete. Prior to this,... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.1 Fuzz Testing | |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.1.1 General Description | Fuzzing is an effective negative black box testing method of finding unknown vulnerabilities in software. A System Under Test (SUT) is exposed via its interfaces to unexpected data. The idea is to send partially invalid data to get the system into an unexpected state. Inputs are generated randomly or systematically by ... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.1.2 Example Approach | Figure 1: Fuzzing configuration One possible application of the fuzzing approach can be found in the Eclipse IoT-Testware project [i.1] that implement a fuzzing proxy. The Fuzzing Proxy is a MITM (Man-in-the-middle) Fuzzer which is capable of proxying the network traffic between two systems and altering this traffic on... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.1.3 MQTT-specific Considerations | Regarding MQTT, different message fields can be considered for the fuzzing approach. The fixed-size 2-byte header can be started with. Exhausting non-defined or reserved values within the possible range opens various possibilities to expose potential vulnerabilities. The following fields are defined optional containing... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.2 Penetration Testing | A penetration test is a special kind of test where an attack on a system or network is simulated by an attacker or attacker team. The attacker attempts to break into the system and take control. In contrast to testing during development, no parts or artifacts of the system to be tested are checked and there are no func... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.3 Testing for vulnerabilities | Testing for vulnerabilities is an approach, where already known vulnerabilities from other systems are used to check the SUT. These vulnerabilities can be found in databases and bug reports in the internet, e.g. in CVE databases. There is always a good chance, that common mistakes can be found in different implementati... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 5.4 Further approaches | The security testing methods and techniques continuously grow and evolve following new attack strategies and pattern. Basic security techniques as presented above are well-known from ETSI TR 101 583 [i.8] as new security testing approaches (e.g. address spoofing and amplification attacks). Security testers always need ... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 6 Test Configurations | The security test configurations are derived from the SUT access points and functional test configurations. For all test configurations presented in this clause, a sniffing tool like Wireshark is recommended, but not shown in figure 3. Figure 3: MQTT test configurations |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 7 MQTT Security Test Purposes | |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 7.1 Introduction | Several TPs can be derived from the security test objectives and testing techniques mentioned in clauses 4 and 5. Some important aspects for MQTT security testing include: • Robustness (coverage criteria, test suite execution time, number of test cases to be executed, number of test data): - Data level: malformed packe... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 7.2 Authentication/authorization | The following TP has been derived from TP_CR_1_1_Identification_authentication_1 in ETSI TS 103 646 [i.3]. TP Id TP_ MQTT_BROKER_SEC_AUT_001 Test Objective Ensure the IUT identifies and authenticates users. Case invalid account identifier/invalid authenticator Reference MQTT 3.2.2.3 PICS Selection Initial Conditions wi... |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 7.3 Encryptions | As mentioned in clause 5.4.5 of the protocol definition [1] encryption may be provided using e.g. TLS or VPN. |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 7.4 Specific protocol security considerations | MQTT specific security considerations have been provided and discussed in clause 5.4.11 of the protocol definition [1]. |
f911331b668860f19e5c33c52247ab56 | 103 597-2 | 8 Vulnerability Test Samples | Testing for Vulnerabilities can be done using vulnerability data bases as inspiration for test cases, such as using associated weaknesses from CVE. Sample TPs from CVEs [i.5], [i.6] and [i.7] that were found in existing MQTT implementations are the following: TP Id TP_MQTT_BROKER_SEC_CVE_001 Test Objective Verify that ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.