dokumendiregister.ee
OtsingAsutusedMCP
Otsing›Majandus- ja Kommunikatsiooniministeerium
Sissetulev kiriAvalik

Kiri

Majandus- ja Kommunikatsiooniministeerium · 23. september 2021
Viit
24.1-6/2021/5582-1
Registreeritud
23. september 2021
Dokumendi liik
Sissetulev kiri
Adressaat
EULISA MANAGEMENT BOARD SECRETARIAT
Saabumis/saatmisviis
e-post
Funktsioon
24.1 EL ja rahvusvahelise koostöö korraldamine
Sari
24.1-6/S Rahvusvahelise koostöö korraldamisega seotud kirjavahetus (Arhiiviväärtuslik)
Toimik
24.1-6/2021
Vastutaja
Silver Tammik (Majandus- ja Kommunikatsiooniministeerium, Kantsleri valdkond, EL ja rahvusvahelise koostöö osakond)

Failid

  • 📎Carriers Registration Process_Introductory Letter-Final.docx1653 KB
  • 📎E-kiri.eml2422 KB
  • 📎F01-Carrier Registration Form_v.2.3.docx100 KB

Sisu (failidest)

left 5448300 INTRODUCTORY LETTER 0 0 INTRODUCTORY LETTER 0 3600450 Carriers Registration Process 0 0 Carriers Registration Process This letter describes the Manual Onboarding support for Carriers into the EES / ETIAS Web Service , enabling Carrier conducted security checks of TCN s , prior to TCN arrival to the EU . The Manual Onboarding covers the following interactions: Registration of Carrier legal entities and their single point of contact ( Carrier SPOC)), as well as Carrier Service Provider contacts; Exchange of the Non-Disclosure Agreement (NDA) and the Encryption Key; Registration of Channel preferences for automated communication System-to-System (Sys2Sys); Support for the Sys2Sys Interface compliance tests; Answers to questions related legislation aspects, project setup, organisational changes, technical aspects, EES / ETIAS Web Service evolution roadmap. Important notice: All documents sent by eu-LISA, which are not for public domain, are encrypted using an encryption / decryption key that is shared with you; The Manual Onboarding lifecycle coverage is focussing on Carriers that need early involvement due to System-to-System (Sys2Sys) testing. Limitations: Onboarding is limited to support prior to the Carrier Entry Into Operations (EIO). Sys2Sys support is covering activities up to Carrier compliance test. Carrier Production support is not included; Carrier activities related to transition to operations, Carrier pilots, Carrier end-user related activities such as training or end-user connection testing are not supported; Support for the registration of individual Carrier staff for web and mobile use by Manual Onboarding is limited to the registration of the Carrier contact that would register such users (in cases where this is not the Carrier SPOC). For support outside of these limitations the Self-Service Onboarding and Support shall be made available at a later stage. Manual Onboarding Overview During the Manual Onboarding process steps, the following information is exchanged: Table 4 – Overview of information exchanged # Information to Carrier Cipher How When From 01 Introductory Letter, including Carrier Registration form Carrier Contact Registration form NDA form Plain-text Download Anytime Working-Group-for-Carriers 02 Encryption Keys Plain-text SMS Registered and NDA signed SMS Gateway (no reply) 03 Welcome Pack, including Introductory letter with forms, as listed under point 1 Registration form for Carrier System and Service Provider contacts Form for Request to be connected Form to report Test Incident En-crypted email Encryption keys shared [email protected] 04 Carrier Technical Guidance En-crypted email Carrier System registered [email protected] 05 Carrier Compliance Test Plan En-crypted email Carrier System registered [email protected] 06 Test Detail Descriptions En-crypted email Carrier System registered [email protected] As seen from a Carrier, the Manual Onboarding Process starts with the following Steps: Preconditions: The Carrier SPOC has visited the public web page at https://www.eulisa.europa.eu/About-Us/Organisation/working-group-for-carriers and picked up this “Introductory Letter” which provides information about how to onboard via the Manual Onboarding service. Process steps The Carrier SPOC registers the Carrier Enterprise by sending an e-mail titled: “Carrier Registration Request”, to dedicated e-mail: [email protected] . This includes registration of the Carrier SPOC as first contact; If applicable, the Carrier SPOC registers other Carrier contacts; If applicable, the Carrier SPOC registers a System Contact for System-to-System access; In case eu-LISA requires clarification during one of these steps, eu-LISA service desk operators will contact the sender via email; All registered contacts submit a completed Non-Disclosure Agreement (NDA). This also applies to the Carrier SPOC; Contacts that have delivered a NDA will receive a text message with encryption keys; These encryption keys are used to encrypt email attachments during the Manual Onboarding email interactions. Notice: Exchange of all emails is done through [email protected] . Carrier Registration The form to be used for Carrier Registration is attached REF _Ref82522699 \h Table 11 – Registration Forms . Carrier Registration steps are depicted below: Figure SEQ Figure \* ARABIC 5 – Carrier Registration The data position to establish registration is defined in the EU implementation act referenced in section REF _Ref74077929 \r \h 13.1 . The registration form will prompt the Carrier SPOC to submit the following data: Table 5 – Carrier Registration Data # Data How Mandatory or Optional 01 Electronic copy of the Carrier’s instruments of constitution, including statutes Attachment M 02 Either: an extract of the Carrier official company registration from either at least one Member State, where applicable, or from a third country , stated in one of the official European Union or one of the Schengen Associated Countries languages Or: an authorisation to operate in one or more Member States, such as an Air Operator Certificate Attachment M 03 Carrier declaration regarding which of the 2 documents in point 2 is submitted, and which language both documents are written in Form Field M 04 the Member State or third country that issued the official company registration (including the registration number, where available) Form Field M 05 The company registration number, where available Form Field O 06 When the carrier registration is with a third country, the Member States in which the carrier operates or intends to operate within the next 6 months . Form Field O 07 Legal name of the Carrier as well as its contact details (email address, telephone number and postal address) Form Field M 08 The contact details of the legal representative of the company requesting the registration with contact details: name surname phone(s) functional or individual email address postal address The Carrier SMS number via which to receive the password to be used for decrypting email attachments. Time zone Form Field M 09 NDA. This is optional because it can also be submitted separately Attachment O 10 Similar details for Carrier SPOC back-up points of contact or other contacts, with a clarification about the role of the other contacts. This is optional because they can also be declared separately at a later stage Form Field O The service desk will validate the submitted data for completeness, formatting, consistency and duplication. If this validation fails, the service desk will contact the originator to resolve issues. When the validation succeeds, the service desk will record the Carrier data and assign to Carrier a Submission ID, and notify Carrier about successful registration and Submission ID. The service desk will next validate the submitted data for restrictive measures, blacklists, sanctions and if this leads to findings, eu-LISA may contact the Carrier or Member States for follow-up. Carrier Contact Registration A Carrier Contact is a person that will be interacting with the Service Desk. This may involve exchange of information under NDA, which is why such contacts are registered. A Carrier Contact is not necessarily a person that is an employee of the same company as the Carrier SPOC. The Carrier may have contracted responsibility to another company, e.g. a Service Provider. Contact Registration steps are depicted below: Figure SEQ Figure \* ARABIC 6 –Contact Registration The contact registration form will prompt the Carrier SPOC to submit the following data: Table 6 – Contact Registration Data # Data How Mandatory or Optional 01 The contact details: name surname phone(s) functional or individual email address postal address The contact SMS number via which to receive the password to be used for decrypting email attachments. Time zone Form Field M 02 In case the Contact is an employee of the registered Carrier: Carrier Submission ID Else: Name of the company Form Field M 03 Contact role Form Field M 04 In case the other company is a service provider: the name of the system that he/ she is the contact for Form Field O The service desk will validate the submitted data for completeness, formatting, consistency, duplication. If this validation fails, the service desk will contact the originator to resolve issues. When the validation succeeds, the service desk will record the Carrier Contact data. In case the contact is belonging to a Carrier Service provider, a Submission ID for the Service Provider is identified or assigned and Carrier SPOC and Carrier Contact are notified about successful registration and Submission ID. The service desk will next validate the submitted data for blacklisting and if this leads to findings, may contact the Carrier Contact or Carrier SPOC for follow-up. NDA Each Carrier Contact needs to complete a NDA in order to receive a decryption key for encrypting or decrypting documents being shared via e-mail during the Manual Onboarding. The picture below shows the key steps: Figure SEQ Figure \* ARABIC 7 – Non-Disclosure Agreement The NDA template will prompt the Carrier Contact to submit the following data: Table 7 – NDA Data # Data How Mandatory or Optional 01 Identification details: Submission ID Name Form Field M 02 Signature confirming agreement to terms specified in the NDA Form Field M The service desk will validate the submitted data for completeness, consistency, duplication. If this validation fails, the service desk will contact the originator to resolve issues. When the validation succeeds, the service desk will record the NDA andnotify the contact about its acceptance. The security team will next submit the encryption key information to the Carrier Contact via text message. Carrier System and System Contact Registration This only applies to Carriers that want to register a System, with a contact that manages their system for Sys2Sys interfacing. This may be a Service Provider contact for Carriers that have outsourced the relevant system, or a Carrier contact for Carriers that operate an in-house system. The picture below shows the key steps: Figure SEQ Figure \* ARABIC 8 – Carrier System Registration The form used, data submitted and follow up actions are the same as for Carrier Contact Registration (see section REF _Ref78539620 \r \h 9.3.3 ), except that the name of the system is now mandatory data to be provided, and the preferences for system (REST/JSON or EDIFACT, and in case of EDIFACT, which version is currently supported) are asked. When the validation succeeds, the service desk will follow up with sharing Carrier Technical Guidance and Test documentation. Carriers that need to register multiple systems should submit a System Registration Form for each system. E-mail convention All messages should be sent to: [email protected] . Registered Carrier SPOCs are requested to use the following mail convention for initial registration requests: Table 8 – Overview of Information Exchanged # Interaction Type Mail convention 01 Carrier registration Use mail Title: CARRIER REGISTRATION – Carrier name 02 Contact registration Use mail Title: Cnnnn – CONTACT REGISTRATION – Contact Name Or Snnn – CONTACT REGISTRATION – Contact Name 03 NDA Use mail Title: Cnnnn – NDA – Contact name 05 System registration Use mail Title: Cnnnn – SYSTEM REGISTRATION – System name 06 Deregistration Use mail Title: Cnnnn – D – Question Summary Or Snnn – D – Question Summary Where Cnnnn or Snnn is the Carrier or Service Provider ID number obtained during registration (i.e.: C1234, S123). Registered Carrier SPOCs are allowed to send e-mails with other questions, problems or complains. Different topics might be addressed using following Request Types: Table 10 – Overview of Information Exchanged – continued # Data How Mandatory or Optional 01 Question A question about the elements in scope of manual onboarding support, i.e. information about: procedures and templates used for Carriers Manual Onboarding and Sys2Sys interfaces legislation aspects project setup technical aspects EES/ETIAS-WS evolution roadmap Use mail Title: Cnnnn – Q – Question Summary Or Snnnn – Q – Question Summary 02 Connection Request to address topics related to interfacing tools for Automatic Sys2Sys communication, technical documentation Use connection request form and mail title: Cnnnn – S – System Connection Summary Or Snnnn – S –System Connection Summary 03 Incident to address incidents or suspected defects that arose during the Sys2Sys interfaces tests Use test incident report form and mail title: Cnnnn – I – Incident Reference Or Snnnn – I – Incident Reference 0 4 Complaint to escalate issues related to received support Use mail Title: Cnnnn – C – Complaint Subject Or Snnnn – C – Complaint Subject Where Cnnnn or Snnn is the Carrier or Service Provider ID number obtained during registration (i.e.: C1234, S123) Manual Onboarding forms Forms to be used by Carrier SPOC for registering Carriers and Carrier Contacts are attached here: Table 11 – Registration Forms # Form MS Word File F 01 Carrier Registration form \s F 02 Carrier Contact Registration form \s F 0 3 Registration form for Carrier System and Service Provider contacts Can be found in the Welcome Pack, which Carrier will receive after the Carrier SPOC has signed the NDA F 0 4 Form for Request to be connected Can be found in the Welcome Pack, which Carrier will receive after the Carrier SPOC has signed the NDA F 0 5 Form to report Test Incident Can be found in the Welcome Pack, which Carrier will receive after the Carrier SPOC has signed the NDA F 0 6 Form to Ask Question Can be found in the Welcome Pack, which Carrier will receive after the Carrier SPOC has signed the NDA F 0 7 NDA Form Carrier Registration F orm Please use this form to transmit the information needed to register in order to gain access to the carrier interface (in accordance with Article 10 of Commission Implementing Regulation (EU) 2021/1224 of 27 July 2021 and Commission Implementing Regulation (EU) 2021/1217 of 26 July 2021 ) . The Carrier Single Point of Contact (Carrier ’ s SPOC) should send this form to the following mailbox: [email protected] . Please add “ Carrier Registration ” in the subject field of the e-mail. Carrier Legal Name Mandatory Carrier e- mail Address (can be a functional or personal address) Mandatory Carrier Telephone Number (e.g. +31 (0) 123456789 ) Mandatory Carrier Postal Address Mandatory Carrier Commercial Name Optional Country Mandatory ( One Member State or a third country where Carrier is registered) Industry Optional (Tick only one) ☐ Air ☐ Sea ☐ Road (Coaches) Industry Tag Optional Official Carrier Entity Optional Declarations Mandatory The carrier identified in this form declares that: ☐ It operates and transport passengers into the territory of the Member States or intend to do so within the next six months (see list of European Union Member States and Schengen associated countries applying ETIAS or operating the EES below) ; ☐ It w ill access and make use of the carrier interface in accordance with the minimum security requirements set out in this registration form ; ☐ Only duly authorised staff will have access to the carrier interface . Legal Representative Contact Details (of the company requesting the registration) Mandatory ( Legal Representative’s data ) Name Surname Position Postal address e -mail (can be a functional or personal address) Phone (e.g. +31 (0) 123456789 ) Mobile phone (e.g. +31 (0) 123456789) Time zone (e.g. UTC +2) Functional e-mail address Optional C ontact point details Mandatory (Single Point of Contact data ) Name Surname Position Postal address e- mail (can be a functional or personal address) Phone (e.g. +31 (0) 123456789) Mobile phone (e.g. +31 (0) 123456789) Time zone (e.g. UTC +2) Backup contact point details Mandatory (Single Point of Contact backup ’s data ) Name Surname Position Postal address e -mail (can be a functional or personal address) Phone (e.g. +31 (0) 123456789) Mobile phone (e.g. +31 (0) 123456789 ) Time zone (e.g. UTC +2) Instruments of company constitution including statutes Mandatory ( The Filen ame(s) and the language used in files attached to the Registration Request). Attached d ocuments should be i n, or officially translated into, one of the official Union or one of the Schengen Associated Countries languages . File Name Document language Registration document Only one is Mandatory – Tick the proper one. ( The Filename(s) and the language used in files attached to the Registration Request). Attached documents should be in, or officially translated into, one of the official Union or one of the Schengen Associated Countries languages . ☐ Company Business Registration from either at least one Member State, where applicable, or from a third country File Name Document language Member State or third country that issued the official company registration Registration number If applicable ☐ Authori s ation to Operate in one or more Member States, such as for example an Air Operator Certificate File Name Document language European Union Member States and Schengen associated countries applying ETIAS or operating the EES where Carrier intends to operate Mandatory when presenting a registration in a 3 rd country ☐ Austria ☐ Belgium ☐ Bulgaria ☐ Croatia ☐ Republic of Cyprus ☐ Czech Republic ☐ Denmark ☐ Estonia ☐ Finland ☐ France ☐ Germany ☐ Greece ☐ Hungary ☐ Iceland ☐ Italy ☐ Latvia ☐ Lichtenstein ☐ Lithuania ☐ Luxembourg ☐ Malta ☐ Netherlands ☐ Norway ☐ Poland ☐ Portugal ☐ Romania ☐ Slovakia ☐ Slovenia ☐ Spain ☐ Sweden ☐ Switzerland Carrier Choice for Data exchange Channels At least one is Mandatory (Tick channels to be planned for use and give further preferences) ☐ Web browser: ☐ Chrome, ☐ Edge, ☐ Fire f ox, ☐ Safari , ☐ Other If other, please specify: ……………….. ☐ Mobile Application: ☐ Android, ☐ iOS, ☐ Other If other, please specify: ………………….. ☐ System-To-System integration Comments Optional MINIMUM SECURITY REQUIREMENTS In order to perform the remote connection, the Carrier must comply with the rules defined below. Failure to comply with those rules may result in Carrier disconnection and/or Carrier deregistration from the Carrier Interface. Obligations of Carriers Carriers shall ensure that only duly authorised staff have access to the carrier interface. The carriers shall put in place at least the following mechanisms: (a) physical and logical access control mechanisms to prevent unauthorised access to the infrastructure or the systems used by the carriers; (b) authentication; (c) logging to ensure access traceability. Carriers shall provide means to ensure compliance with the following security objectives: identifying and managing security risks related to the connection to the carrier interface; protecting the ICT environments and the devices connected to the carrier interface; detecting, analysing, responding to and recovering from cyber security incidents. Authentication Scheme When carriers access the carrier interface using the Application Programming Interface, the authentication scheme shall be implemented by means of mutual authentication in accordance with Art 45 paragraph 3 of the ETIAS Regulation 2018/1240. Authorised Staff The Carrier shall ensure that the tasks entrusted to them are carried out only by authorised staff. The Carrier must keep a register of the members of the authorised staff. The Carrier shall instruct the Authorised staff to comply with the security rules set out in the current text. Authentication / Identification of the Authorised Staff Each member of the Authorised staff using technical equipment connected to the Carrier Interface must be clearly identified and authenticated. The Carrier is responsible for the internal management and assignment of the Authentication / Identification mechanism(s) for its staff. The Carrier is legally, jointly and severely liable for the consequences of the misuse or loss of the Authentication / Identification mechanism(s) allowing the use of the Carrier Interface by persons not belonging to the Authorised staff. Carrier specific duties The Carrier undertakes: To use the information provided by eu-LISA for no other purpose than to execute the tasks based on the EES 2017/2226 and ETIAS Regulation 2018/1240 and shall not reproduce, publish or otherwise disclose such information to any third party; To destroy all data, transferred to premises of the Carrier in order to perform the tasks required once they are no longer needed; To remedy as soon as possible and on best effort basis any fault, problem or weakness that could appear and for which the Carrier is responsible; To comply with new security rules at the request of eu-LISA, for example if eu-LISA implements new Authentication and Access control mechanisms for the connection to the Carrier Interface. Conduct a risk assessment and implement a security plan for ensuring the security of the Carrier connection to the Carrier interface Members of the authorised staff duties: The members of the authorised staff shall be informed by the Carrier’s Single Point of Contact (SPOC) on the following rules: To comply with the security rules and policies of the Carriers related to the connection to the Carrier Interface; Not to disclose information held by the Carrier on behalf of eu-LISA to third parties, except on a need-to know basis where authorised; To make reasonable use of all available means of controlling access provided by the Carrier and in balance with the sensitivity of the information concerned to prevent unauthorised persons from using the resources at their disposal, in particular by ensuring that computer terminals are not accessible during absences; Not to disclose authentication procedures or share them with third parties unless required to do so by the needs of the service and after obtaining the Carrier approval; To be responsible for action taken in their name; Not to install or use on computers (work stations, local or central servers, etc.) any equipment or programmes, from portable storage media (diskettes, optical disks, etc.) or downloaded from electronic bulletin boards, e mail systems or telecommunications networks belonging to third parties, unless explicitly authorised by the Carrier; Not to install or have installed connections with networks without explicit authorisation from the Carrier; Not to set up electronic bulletin boards, e mail systems, modem connections or any other type of information communication system that could enable unauthorised persons to gain access to the eu-LISA systems without explicit authorisation from the Carrier; Not to use equipment or software that is their private property when connected to the Carrier's and / or eu-LISA's network without prior explicit authorisation from the Carrier; To notify their superior in the Carrier as soon as they suspect any failure or incident affecting the security of their own environment or of other systems; To take all possible steps in respect of availability, confidentiality and integrity to safeguard the security of their working environment, particularly as regards working methods they have introduced or developed themselves. Prohibited uses Any party is prohibited from using the interface or its content: For any unlawful purpose; To solicit others to perform or participate in any unlawful acts; To violate any international, federal, provincial or state regulations, rules, laws, or local ordinances; To infringe upon or violate eu-LISA intellectual property rights or the intellectual property rights of others; To harass, abuse, insult, harm, defame, slander, disparage, intimidate, or discriminate based on gender, sexual orientation, religion, ethnicity, race, age, national origin, or disability; To submit false or misleading information; To upload or transmit viruses or any other type of malicious code that will or may be used in any way that will affect the functionality or operation of the Service or of any related website, other websites, or the Internet; To collect or track the personal information of others; To spam, phish, pharm, pretext, spider, crawl, or scrape; For any obscene or immoral purpose; To interfere with or circumvent the security features of the Service or any related website, other websites, or the Internet. eu-LISA reserve the right to terminate use of the service or any related website for violating any of the prohibited uses. NOTIFICATION The carrier shall inform eu-LISA of any changes regarding the information provided via this form or in case of technical changes affecting the ‛system to system’ connection to the carrier interface that may require additional testing in accordance with Article 12 through a new submission of the present form. The carrier will be automatically deregistered from the authentication scheme if the logs show that the carrier has not used the carrier interface during a period of one year. The carrier may be deregistered from the authentication scheme in case of a breach of the provisions of t he applicable regulation, the security requirements referred above or the technical guidelines, including in case of abuse of the carrier interface. The carrier is obliged to inform eu-LISA of any personal data breach that may occur and regularly review the access rights of the dedicated staff . Saatja: "EULISA MANAGEMENT BOARD SECRETARIAT" <[email protected]> Saaja: "EULISA MANAGEMENT BOARD SECRETARIAT" <[email protected]>, "EULISA CARRIERS" <[email protected]> Teema: Carriers: Registration and Manual Onboarding Kuupäev: 2021-09-22 15:12 Dear Colleagues, We are pleased to inform you that the Carrier Registration for EES and ETIAS is starting! To support the Manual Onboarding process please first consult the attached Carrier Registration Process Introductory letter that contains information on the following important aspects: - Manual Onboarding overview - Registration steps and the data to be submitted - Carrier Contact Registration - NDA for Carrier Contacts - Carrier System and System Contact Registration - Email Convention and Request Types - Manual Onboarding forms To start the registration procedure, please fill in the attached Registration Form and send it to the mailbox EULISA Carriers Onboarding <mailto:[email protected]> [email protected] (detailed instructions in the Introductory letter). Furthermore, a special Registration Section has been created on the <https://www.eulisa.europa.eu/About-Us/Organisation/working-group-for-carr iers> Carriers website; there you will find step-by-step instructions, requirements, registration options, as well as all public documents and specific forms. In case of questions please do not hesitate to contact us by <mailto:[email protected]> [email protected] (kindly please also CC <mailto:[email protected]> [email protected]). Kind regards, On behalf of the Carriers Team Britta Lainevool Stakeholders Management and Support Sector Executive Support and Stakeholders Relation Unit Corporate Governance Department eu-LISA Phone: + 372 605 2207 Mobile: +372 5601 0191 <mailto:[email protected]> [email protected] <mailto:[email protected]> [email protected]
Allikas: Majandus- ja Kommunikatsiooniministeerium dokumendiregister →
dokumendiregister.eeAsutusedEesti avalike dokumendiregistrite otsing · nimistu.ee andmetel