Contents
Article 4Authority Access Points#
1.The AAP components shall enable the access of the competent authorities’ officers to the eFTI exchange environment and shall constitute an officer’s sole point of access to that environment.
2.An AAP shall perform the following functionalities:
(a)authenticate the identity of the competent authority officers, or ensure the authentication of the identity of the competent authority officers;
(b)authorise the request for access to eFTI data of the competent authority officers, based on their respective access rights stored in the authorisation registry, or reject the request if the competent authority officer has no active access rights registered;
(c)register the authorised requests for access to eFTI data by issuing a unique identification number for each such request, and record at least the following information for each request:
(i)identification references of the officer responsible for lodging the request;
(ii)the UIL of the eFTI data to which access is requested, or the identifier or identifiers provided by the officer when lodging the request;
(iii)the references to the access rights of the competent authority officer responsible for lodging the request, as recorded in the authorisation registry;
(iv)the date and time at which the request was lodged;
(d)transmit the authorised requests for access to eFTI data to the eFTI Gate for processing, by providing the following information:
(i)the unique identification number of the request;
(ii)the UIL of the eFTI data for which access is requested, or the identifier or identifiers provided by the officer when lodging the request;
(iii)the references to the processing rights of the competent authority officer responsible for lodging the request, as recorded in the authorisation registry;
(e)receive the responses to requests transmitted by the eFTI Gate and make these responses available to the competent authority officer responsible for that request via the user application;
(f)keep an audit trail of the responses received for each request by logging at least the following information:
(i)the unique identification number of the request for which the response was received;
(ii)the date and time at which the response was received by the AAP;
(iii)the date and time at which the response was forwarded by the AAP to the officer responsible for the respective request;
(g)keep an archive of the requests for access to eFTI data and of the log of the received responses for a period of 2 years or, where national applicable provisions on the availability of evidence for the enforcement of the provisions for which access to eFTI data is required provide for a longer period of time, for that period of time;
(h)when a follow-up communication in accordance with Article 3(4) is lodged, register the follow-up communication by issuing a unique identification number for the follow-up communication and record at least the following information for that follow-up communication:
(i)identification references of the officer responsible for lodging the follow-up communication;
(ii)the UIL of the eFTI data and the unique identification number of the request for access to that data for which the follow-up communication was lodged;
(iii)the date and time at which the follow-up communication was lodged;
(iv)the content of the follow-up communication;
(i)transmit the follow-up communications to the eFTI Gate for processing, by providing the following information:
(i)the UIL of the eFTI data and the unique identification number of the request for access to that data for which the follow-up communication was lodged;
(ii)the content of the follow-up communication.
3.To provide the functionalities set out in paragraph 2, an AAP shall:
(a)use appropriate electronic identification means that allow for reliable identification and authentication of the officers of the competent authorities, or that allow for verifying that the identification and authentication of those officers is ensured by another appropriate ICT component;
(b)use an authorisation registry;
(c)establish and maintain a secure connection to an eFTI Gate;
(d)support a secure connection to the user application.
Source: EUR-Lex, © European Union, 1998-2026. Reuse authorised under Decision 2011/833/EU.