# Council Directive 1999/37/EC of 29 April 1999 on the registration documents for vehicles, Division III.2: Data storage and protection

Extent: E+W+S+N.I.

Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1:
(A) Data as per Chapters II.4 and II.5
All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card.
(B) Other data as per Chapter II.6
Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent.
(C) Other data as per Chapter II.7
Optionally, further vehicle-related data of general interest may be stored on the card.
The data from the Letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according their requirements.
There are no read restrictions on these files.
Write access to these files shall be restricted to the national competent authorities (and their authorised Agencies) in the Member State issuing the smart card.
Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a Security Module (e.g. a Security Module Card) of the national competent authorities (or their authorised Agencies). Thereby Card Verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The Card Verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field).
The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card.
The specification of the files and commands needed for the authentication process and the writing process is under responsibility of the Member States. The security assurance has to be approved by Common Criteria Evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant.
(D) Verification data for authenticity of registration data
The issuing authority calculates its electronic signature about the complete data of a file containing the data of the Letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data:
electronic signature of registration data related to Letter A,
electronic signature of registration data related to Letter B.
For verification of these electronic signatures the card shall store:
certificates of the issuing authority calculating the signatures about the data of Letters A, B.
Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities.

---
Source: https://www.legislation.gov.uk/eudr/1999/37/annex/II/division/III/division/III.2 (the official version)
Page: https://openlegislation.uk/eu-directive-1999-37/annex-II/division-III/division-III.2
Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives.