Methods for Testing and Specification (MTS); Test Specification for CoAP; Part 2: Security Tests

DTS/MTS-TSTCoAP-2

General Information

Status
Not Published
Technical Committee
Current Stage
12 - Completion
Due Date
05-May-2021
Completion Date
17-May-2021
Ref Project

Buy Standard

Standard
ETSI TS 103 596-2 V1.1.1 (2021-05) - Methods for Testing and Specification (MTS); Test Specification for CoAP; Part 2: Security Tests
English language
15 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 103 596-2 V1.1.1 (2021-05)






TECHNICAL SPECIFICATION
Methods for Testing and Specification (MTS);
Test Specification for CoAP;
Part 2: Security Tests



---------------------- Page: 1 ----------------------
2 ETSI TS 103 596-2 V1.1.1 (2021-05)

Reference
DTS/MTS-TSTCoAP-2
Keywords
security, testing

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2021.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 596-2 V1.1.1 (2021-05)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
Introduction . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Security Test Objectives . 7
5 Security testing techniques (preliminary consideration) . 7
5.1 Fuzz Testing . 7
5.1.1 General Description . 7
5.1.2 Example Approach . 7
5.1.3 CoAP-specific Considerations . 8
5.2 Penetration Testing . 9
5.3 Testing for vulnerabilities . 9
5.4 Further approaches . 9
6 Test Configurations . 10
7 CoAP Security Test Purposes . 10
7.0 Introduction . 10
7.1 Authentication/authorization . 11
7.2 Encryptions. 12
7.3 Specific protocol security considerations . 12
8 Vulnerability Test Samples . 12
Annex A (informative): Sample security test catalogue . 14
A.1 Introduction . 14
History . 15


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 596-2 V1.1.1 (2021-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and
Specification (MTS).
The present document is part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1 [4].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
The present document provides an introduction and guide for developers and users investigating in security testing of
the COAP communication protocol. It will be a reference base for both client side test campaigns and server side test
campaigns addressing the security issues. It belongs to a multi-part deliverable addressing the most relevant testing
aspects of COAP: conformance, security and performance testing. While the conformance testing part presents a
complete set of test purposes, the content for security and performance parts is different and focus on evaluating
relevant testing techniques and the provision of samples that are specific for COAP. For this reason, the structure of the
present document consists of four main clauses: the first two clauses address the security test objectives, techniques and
methods to be considered for COAP. Concrete practical hints and samples and configuration notes are provided where
feasible. The latter two clauses focus on the security mechanisms and implementation notes mentioned in the COAP
protocol standard and security vulnerabilities known from relevant vulnerability databases. Concrete test purposes have

been described using the Test Description Language (TDL) standardized by ETSI.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 596-2 V1.1.1 (2021-05)
1 Scope
The present document provides general security considerations and guidelines about the Constrained Application
Protocol (CoAP). The collective ideas presented in the present document are enriched with example Test Purposes
(TPs) to outline possible implementations.
2 References
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 are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] IETF RFC 7252: "The Constrained Application Protocol (CoAP)".
[2] ETSI ES 203 119-4: "Methods for Testing and Specification (MTS); The Test Description
Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[3] IETF RFC 8323: "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
[4] ETSI TS 103 596-1: "Methods for Testing and Specification (MTS); Test Specification for CoAP;
Part 1: Conformance Tests".
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 included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] Eclipse IoT-Testware v.0.1.0.
NOTE: Available at https://projects.eclipse.org/projects/technology.iottestware.
[i.2] ETSI ES 202 951: "Methods for Testing and Specification (MTS); Model-Based Testing (MBT);
Requirements for Modelling Notations".
[i.3] ETSI TS 103 646: "Methods for Testing and Specification (MTS); Test specification for
foundational Security IoT-Profile".
[i.4] IEC 62443-4-2: "Security for industrial automation and control systems. Technical security
requirements for IACS components".
[i.5] CVE-2018-14367.
NOTE: Available at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14367.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 596-2 V1.1.1 (2021-05)
[i.6] CVE-2019-12101.
NOTE: Available at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12101.
[i.7] ETSI TR 101 583: "Methods for Testing and Specification (MTS); Security Testing; Basic
Terminology".
3 Definition of terms, symbols and abbreviations
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 (SUT): real open system in which the implementation under test resides
NOTE: Definition of term from ETSI ES 202 951 [i.2].
white-box testing: testing based on an analysis of the internal structure of the component or
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.