F1F2ANNEX I BREQUIREMENTS FOR CONSTRUCTION, TESTING, INSTALLATION AND INSPECTION

Annotations:
Appendix 10GENERIC SECURITY TARGETS

TACHOGRAPH CARD GENERIC SECURITY TARGET

4.Security enforcing functions

4.2.User identification and authentication

The card must identify the entity in which it is inserted and know whether it is an authenticated vehicle unit or not. The card may export any user data whatever the entity it is connected to, except the control F4and the company card which may export card holder identification data to authenticated vehicle units only (such that a controller is ensured that the vehicle unit is not a fake one by seeing his name on display or printouts).

4.2.1.User identification

Assignment (FIA_UID.1.1) List of TSF mediated actions: none.

X1Assignment (FIA_ATD.1.1) List of security attributes:

USER_GROUP

VEHICLE_UNIT, NON_VEHICLE_UNIT,

USER_ID

Vehicle Registration Number (VRN) and registering Member State code (USER_ID is known for USER_GROUP = VEHICLE_UNIT only).

4.2.2.User authentication

Assignment (FIA_UAU.1.1) List of TSF mediated actions:

  • Driver and Workshop cards: export user data with security attributes (card data download function),

  • Control card: export user data without security attributes except cardholder identification data.

[UIA_301] Authentication of a vehicle unit shall be performed by means of proving that it possesses security data that only the system could distribute.

Selection (FIA_UAU.3.1 and FIA_UAU.3.2): prevent.

Assignment (FIA_UAU.4.1) Identified authentication mechanism(s): any authentication mechanism.

[UIA_302] The Workshop card shall provide an additional authentication mechanism by checking a PIN code (This mechanism is intended for the vehicle unit to ensure the identity of the card holder, it is not intended to protect workshop card content).

4.2.3.Authentication failures

F3Additionally the following assignments describe the card reaction for each single user authentication failure.

Assignment (FIA_AFL.1.1) Number: 1, list of authentication events: authentication of a card interface device.

Assignment (FIA_AFL.1.2) List of actions:

  • warn the entity connected,

  • assume the user as NON_VEHICLE_UNIT.

Additionally the following assignments describe the card reaction in the case of failure of the additional authentication mechanism required in UIA_302.

Assignment (FIA_AFL.1.1) Number: 5, list of authentication events: PIN checks (workshop card).

Assignment (FIA_AFL.1.2) List of actions:

  • warn the entity connected,

  • block the PIN check procedure such that any subsequent PIN check attempt will fail,

  • be able to indicate to subsequent users the reason of the blocking.