Commission Implementing Regulation (EU) 2016/799 of 18 March 2016 implementing Regulation (EU) No 165/2014 of the European Parliament and of the Council laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components (Text with EEA relevance)

Print Options
PrintThe Whole
Regulation
PrintThe Whole
Annex
PrintThe Whole
Part
PrintThis
Division
only
8.CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS
8.1. Cryptographic Systems
CSM_38Vehicle units and tachograph cards shall use an elliptic curve-based public-key cryptographic system to provide the following security services:
mutual authentication between a vehicle unit and a card,
agreement of AES session keys between a vehicle unit and a card,
ensuring the authenticity, integrity and non-repudiation of data downloaded from vehicle units or tachograph cards to external media.
CSM_39Vehicle units and external GNSS facilities shall use an elliptic curve-based public-key cryptographic system to provide the following security services:
coupling of a vehicle unit and an external GNSS facility,
mutual authentication between a vehicle unit and an external GNSS facility,
agreement of an AES session key between a vehicle unit and an external GNSS facility.
CSM_40Vehicle units and tachograph cards shall use an AES-based symmetric cryptographic system to provide the following security services:
ensuring authenticity and integrity of data exchanged between a vehicle unit and a tachograph card,
where applicable, ensuring confidentiality of data exchanged between a vehicle unit and a tachograph card.
CSM_41Vehicle units and external GNSS facilities shall use an AES-based symmetric cryptographic system to provide the following security services:
CSM_42Vehicle units and motion sensors shall use an AES-based symmetric cryptographic system to provide the following security services:
pairing of a vehicle unit and a motion sensor,
mutual authentication between a vehicle unit and a motion sensor,
ensuring confidentiality of data exchanged between a vehicle unit and a motion sensor.
CSM_43Vehicle units and control cards shall use an AES-based symmetric cryptographic system to provide the following security services on the remote communication interface:
Notes:
—Properly speaking, data is transmitted from a vehicle unit to a remote interrogator under the control of a control officer, using a remote communication facility that may be internal or external to the VU, see Appendix 14. However, the remote interrogator sends the received data to a control card for decryption and validation of authenticity. From a security point of view, the remote communication facility and the remote interrogator are fully transparent.
—A workshop card offers the same security services for the DSRC interface as a control card does. This allows a workshop to validate the proper functioning of the remote communication interface of a VU, including security. Please refer to section 9.2.2 for more information.
8.2. Cryptographic Algorithms
8.2.1 Symmetric Algorithms
CSM_44Vehicle units, tachograph cards, motion sensors and external GNSS facilities shall support the AES algorithm as defined in [AES], with key lengths of 128, 192 and 256 bits.
8.2.2 Asymmetric Algorithms and Standardized Domain Parameters
CSM_45Vehicle units, tachograph cards and external GNSS facilities shall support elliptic curve cryptography with a key size of 256, 384 and 512/521 bits.
CSM_46Vehicle units, tachograph cards and external GNSS facilities shall support the ECDSA signing algorithm, as specified in [DSS].
CSM_47Vehicle units, tachograph cards and external GNSS facilities shall support the ECKA-EG key agreement algorithm, as specified in [TR 03111].
CSM_48Vehicle units, tachograph cards and external GNSS facilities shall support all standardized domain parameters specified in Table 1 below for elliptic curve cryptography.
Table 1 |
Standardized domain parameters |
Name | Size (bits) | Reference | Object identifier |
---|
NIST P-256 | 256 | [DSS], [RFC 5480] | |
BrainpoolP256r1 | 256 | [RFC 5639] | |
NIST P-384 | 384 | [DSS], [RFC 5480] | |
BrainpoolP384r1 | 384 | [RFC 5639] | |
BrainpoolP512r1 | 512 | [RFC 5639] | |
NIST P-521 | 521 | [DSS], [RFC 5480] | |
Note: the object identifiers mentioned in the last column of Table 1 are specified in [RFC 5639] for the Brainpool curves and in [RFC 5480] for the NIST curves.
8.2.3 Hashing algorithms
CSM_49Vehicle units and tachograph cards shall support the SHA-256, SHA-384 and SHA-512 algorithms specified in [SHS].
8.2.4 Cipher Suites
CSM_50In case a symmetric algorithm, an asymmetric algorithm and/or a hashing algorithm are used together to form a security protocol, their respective key lengths and hash sizes shall be of (roughly) equal strength. Table 2 shows the allowed cipher suites:
Table 2 |
Allowed cipher suites |
Cipher suite Id | ECC key size (bits) | AES key length (bits) | Hashing algorithm | MAC length (bytes) |
---|
CS#1 | 256 | 128 | SHA-256 | 8 |
CS#2 | 384 | 192 | SHA-384 | 12 |
CS#3 | 512/521 | 256 | SHA-512 | 16 |
Note: ECC keys sizes of 512 bits and 521 bits are considered to be equal in strength for all purposes within this Appendix.
Back to top