Techniques for assurance of digital material used in legal proceedings

DTS/CYBER-0033

General Information

Status
Published
Publication Date
16-Jan-2020
Technical Committee
Current Stage
12 - Completion
Due Date
05-Feb-2020
Completion Date
17-Jan-2020
Ref Project

Buy Standard

Standard
ETSI TS 103 643 V1.1.1 (2020-01) - Techniques for assurance of digital material used in legal proceedings
English language
27 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 103 643 V1.1.1 (2020-01)






TECHNICAL SPECIFICATION
Techniques for assurance of
digital material used in legal proceedings

---------------------- Page: 1 ----------------------
2 ETSI TS 103 643 V1.1.1 (2020-01)



Reference
DTS/CYBER-0033
Keywords
information assurance
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 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

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
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 2020.
All rights reserved.

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.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 643 V1.1.1 (2020-01)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Basic principles . 7
4.1 Summary . 7
5 Definition of a Basic Digital Evidence Bag . 8
5.1 Reference model . 8
5.2 Inputs of digital data . 8
5.2.1 Nature of inputs . 8
5.2.2 A unique identifier for each input . 8
5.2.2.1 Identifiers for case-specific input material . 8
5.2.2.2 Identifiers for reference input material . 8
5.2.3 Time and location information for input material . 9
5.2.4 Format of input material . 9
5.3 Applying Purely Digital Transformations . 9
5.3.1 Definition of a Purely Digital Transformation . 9
5.3.2 Use of PDT in a Digital Evidence Bag . 9
5.4 Details for creating the output . 10
6 Definition of other Digital Evidence Bags . 10
6.1 Introduction . 10
6.2 Definition of a DEB+H . 10
6.2.1 General . 10
6.2.2 Use of hashing in a DEB+H . 11
6.3 Definition of a DEB+IA . 11
6.4 Definition of a DEB+HIA . 11
Annex A (informative): Context . 12
A.1 Purpose of the present document . 12
A.2 Role of trained staff . 12
A.3 Choosing which type of DEB to use . 12
A.4 Example of how the present document could be used . 12
Annex B (informative): Examples . 14
B.1 Introduction . 14
B.2 Examples of transformations which are not PDT . 14
B.3 Examples regarding accuracy and completeness of input material . 14
B.4 Example of linking to physical evidence. 15
Annex C (informative): Data Integrity, Provenance, Continuity and Validity . 16
C.1 Introduction . 16
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 643 V1.1.1 (2020-01)
C.2 Integrity . 16
C.3 Provenance . 16
C.4 Continuity . 16
C.5 Validity . 16
C.6 Other considerations . 17
Annex D (informative): Examples of functions for performing purely digital transformations . 18
D.1 Introduction . 18
D.2 Finding items in common between two or more lists . 18
D.3 Filtering of a list of items based on a criterion . 18
D.4 Adding additional data from reference material . 18
D.5 Presentation of material . 18
D.6 Change of formatting or codec . 19
Annex E (informative): Considerations when handling certain data types . 20
E.1 Introduction . 20
E.2 Phone numbers . 20
E.3 Names . 20
E.4 Addresses . 20
E.5 Locations . 21
E.6 Dates and times . 21
E.7 Identifiers . 21
E.8 Text in general . 21
Annex F (informative): Testing a DEB. 22
F.1 Introduction . 22
F.2 Conformance statement . 22
F.3 Checking when challenged in legal proceedings . 22
Annex G (normative): Hash assurance function . 23
G.1 Requirements . 23
G.1.1 Functional requirements . 23
G.1.2 Non-functional requirements . 23
G.2 Example of a hash assurance function (informative) . 24
G.2.1 Introduction . 24
G.2.2 Specification of primary functionality . 24
G.2.3 Specification of secondary functionality . 25
G.2.4 Specification of tertiary functionality . 25
G.2.5 Use cases . 25
History . 27


ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 643 V1.1.1 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Cyber Security (CYBER).
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.

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 643 V1.1.1 (2020-01)
1 Scope
The present document defines a process of receiving, transforming and outputting material that can be assured digitally.
The process is called the "Digital Evidence Bag" (DEB). The present document identifies the ways that a DEB can be
used to provide assurance of material used in legal proceedings. Specifically, the assurance of the material is not
dependent on the process having been carried out by a qualified or trained human expert.
The present document is designed to be used in situations where a risk assessment of the handling of digital material has
identified that extra assurance of the integrity, provenance, continuity and validity of the digital data is required.
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 4122: "A Universally Unique IDentifier (UUID) URN Namespace".
[2] ETSI TS 103 307: "CYBER; Security Aspects for LI and RD Interfaces".
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] ISO/IEC 17025: "General requirements for the competence of testing and calibration laboratories".
[i.2] Lives and Opinions of Eminent Philosophers, Diogenes Laërtius (c. 225 CE).
[i.3] Navigation and Nautical Astronomy, James Inman (1835).
[i.4] ISO 8601: "Date and time -- Representations for information interchange".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 643 V1.1.1 (2020-01)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
case-specific input material: input material for a Digital Evidence Bag that is specific to the particular investigation or
case
Digital Evidence Bag (DEB): process of storing digital evidence which can be assured digitally
Purely Digital Transformation (PDT): transformation in which a repeatable, deterministic, pre-specified, fail-safe,
well-defined digital function is performed on entirely digital data
NOTE: See clause 5.3.1 for more information.
reference input material: relevant material (if any) which is used to support the case-specific input material by adding
context or background
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
B-DEB Basic Digital Evidence Bag
DEB Digital Evidence Bag
DEB+H Digital Evidence Bag with Hashing
DEB+HIA Digital Evidence Bag with Hashing and Input Assurance
DEB+IA Digital Evidence Bag with Input Assurance
DIPCV Data Integrity, Provenance, Continuity and Validity
GDPR General Data Protection Regulation
LED Law Enforcement Directive
PDT Purely Digital Transformation
4 Basic principles
4.1 Summary
The present document gives a definition for a "Digital Evidence Bag", which is a process for storing and transforming
digital material. Annex A provides an informative description of when this process is intended to be used.
The present document defines and specifies requirements for the following types of Digital Evidence Bag:
1) A Basic Digital Evidence Bag (B-DEB) (see clause 5).
2) A Digital Evidence Bag with Hashing (DEB+H) (see clause 6).
3) A Digital Evidence Bag with Input Assurance (DEB+IA) (see clause 6).
4) A Digital Evidence Bag with Hashing and Input Assurance (DEB+HIA) (see clause 6).
Annex F provides recommendations for testing a DEB.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 643 V1.1.1 (2020-01)
NOTE: A Digital Evidence Bag with Digital Signature would also meet many of the same goals as the Digital
Evidence Bag with Hashing and Input Assurance and this is being considered for a future version.
5 Definition of a Basic Digital Evidence Bag
5.1 Reference model
The model for a Basic Digital Evidence Bag is as shown in Figure 1.
Apply a set of
Check inputs Purely Digital
Inputs of Create output

(clause 5.2) Transformations
digital data
(clause 5.4)
(clause 5.3)

Figure 1: Model for Basic Digital Evidence Bag
5.2 Inputs of digital data
5.2.1 Nature of inputs
There are two types of input material: case-specific input material and reference input material (as defined in clause 3).
EXAMPLE: Examples of reference input material are maps or publicly available reference data.
Basic DEBs shall follow the specifications for input material as listed in clauses 5.2.2 to 5.2.4.
5.2.2 A unique identifier for each input
5.2.2.1 Identifiers for case-specific input material
For a Basic DEB, each input of case-specific input material (see clause 3) shall have a unique identifier attached to it.
One of the two following approaches shall be used:
1) The identifier shall consist of:
a) an identifier supplied by the originating organization; and
b) a unique identifier for the originating organization. A globally-unique identifier shall be created for the
originating organization, using a combination of a nationally-unique identifier together with a country
code.
2) The identifier shall be a randomly chosen globally unique identifier as defined in IETF RFC 4122 [1].
Each piece of case-specific input material should include where relevant an identifier of a request that prompted the
generation of the input.
5.2.2.2 Identifiers for reference input material
For a Basic DEB, the reference input material (see clause 3) should also have an identifier to make it clear where it
came from, and should also identify the time it was collected if that is significantly different from the time the material
is being submitted to the DEB.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 643 V1.1.1 (2020-01)
5.2.3 Time and location information for input material
The time information in a Basic DEB shall consist of the following:
• All time information as supplied by the originating organisation. The input material material should contain
time and date information, including indication of the time zone, for the point at which the data was generated
or created (or for the period over which the data was generated).
• DEB Entry Time: A timestamp shall be added to indicate the time and date, including indication of the time
zone, the data was received at the Digital Evidence Bag.
In the case that the time of creation is clearly indicated by the originating organization, it shall be checked that the DEB
Entry Time is after the time of creation of the material.
The location of collection of information should be included where the point of collection is not necessarily fixed to one
place and is relevant to the value of the material collected.
EXAMPLE: A contract has been placed with a laboratory to provide information, and the contract includes a
statement of the formats in which the data will be provided.
5.2.4 Format of input material
The format for each input file to a Basic DEB should be known or clear (i.e. known via a communication in advance of
sending the data, or clear from the evidence file itself). Each input file should be checked syntactically for data formats
where there are suitable automated checks.
EXAMPLE: If data is submitted in XML and the XML schema is known and agreed, then each input file is
checked against the schema.
5.3 Applying Purely Digital Transformations
5.3.1 Definition of a Purely Digital Transformation
A Purely Digital Transformation (PDT) is one in which a repeatable, deterministic, pre-specified, fail-safe, well-defined
digital function is performed on entirely digital data.
Specifically:
• It is repeatable in that if the step is performed again by a different computer or operator, in a different
environment, in a different country or at a different time, the outcome is always the same.
• It is deterministic in that the same inputs to the process always give the same outputs, which is not dependent
on the training or skill level of an operator.
• It is pre-specified in that the full details of the process are known to all relevant parties in advance and (ideally
but not essentially) the details are published.
• It is fail-safe in that its failure modes are easily distinguishable from successful outcomes (in particular, that a
failure mode looks very different from a successful output with no records in it).
• It is well-defined in that the version numbering is present and accurate and that the formatting is clear and
specified in all places.
• It is digital in that its input and output are digital.
5.3.2 Use of PDT in a Digital Evidence Bag
Within the Digital Evidence Bag, one or more PDTs (as defined in clause 5.3.1) may be applied.
For each transformation, the DEB shall:
• Check formatting and definition of input files is clear.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 643 V1.1.1 (2020-01)
• Check that any standards referred to have a correct version number and are designed for the purpose in
question.
• Check that the input(s) each has an identifier for the material in question.
• Add time and date that the transformation took place, ensuring time zone is clear.
• Attach a unique identifier to the output, add an identification of the process that took place, the time the
transformation took place and add an identifier to the entity that performed it.
The recommendations in Annex E should be followed when handling the types of data listed in Annex E. Examples of
PDT are given in Annex D.
5.4 Details for creating the output
The Basic DEB output file shall contain the following information:
• List of all input files, including identifiers (as defined in clause 5.2.2) and the DEB entry time (clause 5.2.3).
• For each transformation that was applied, a list of the details for that transformation from clause 5.3.2.
• The software name and version that was used.
NOTE: There can also be requirements for the material in the Digital Evidence Bag to be deleted in a complete
and assured way. These requirements are out of scope of the present document, though it is noted that a
number of the techniques in the present document (e.g. list of all processes that have been applied,
identification of inputs and outputs of each stage) can help to demonstrate a list of material which needs
to be deleted.
6 Definition of other Digital Evidence Bags
6.1 Introduction
Clause 6 specifies the following types of Digital Evidence Bag:
• DEB+H (with hashing).
• DEB+IA (with input assurance).
• DEB+HIA (with hashing and input assurance).
NOTE: A Digital Evidence Bag with Digital Signature would also meet many of the same goals as the Digital
Evidence Bag with Hashing and Input Assurance and this is being considered for a future version.
Each of the definitions builds on the definition of a Basic DEB in clause.
Clause A.3 explains when it can be appropriate to choose each of the different types of DEB.
6.2 Definition of a DEB+H
6.2.1 General
A Digital Evidence Bag with Hashing (DEB+H) shall meet the specification of a Basic DEB (clause 5). In addition, it
shall use hashing as specified in clause 6.2.2.
NOTE: A Digital Evidence Bag with Hashing would typically be used in situations where assurance was required
that material had not been changed from the point at which it was submitted to the DEB (and potentially
earlier than this, depending on when the hash was taken) through to the point it was used in court. See
clause A.3 for more information.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 643 V1.1.1 (2020-01)
6.2.2 Use of hashing in a DEB+H
A DEB+H shall create a single file with all input material.
...

Questions, Comments and Discussion

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