text: Final | 1.0 | Restricted | December 2019

text: Link to be provided upon final publication of the Regulation 5

text: https://eur-lex.europa.eu/eli/reg/2019/881/oj 3 https://ec.europa.eu/growth/content/2018-rolling-plan-ict-standardisation-released_en 4 https://www.enisa.europa.eu/publications/baseline-security-recommendations-for-iot 5 https://www.enisa.europa.eu/publications/iot-security-standards-gap-analysis 7

text: https://www.enisa.europa.eu/publications/iot-security-standards-gap-analysis 13

text: Entity IT Role Use Cases Use Case Notation

text: Use case name: ID: Priority:

text: Access to Communication UC01 High Platform

text: Mgmt_Board_User EC_User

text: ESO_User ECCG_User

text: Complain_User SCCG_User

text: AHWG_User Com_Admin Submitter_User

text: Use case name: ID: Priority:

text: Publish Union rolling work programme UC02 High

text: Use case name: ID: Priority:

text: Request certification scheme UC03 High

text: Use case name: ID: Priority:

text: Access to propose cybersecurity certification UC04 High schemes

text: ENISA_User EC_User

text: Use case name: ID: Priority:

text: Formal approval of cybersecurity certification UC05 High schemes

text: Use case name: ID: Priority:

text: Administration of roles and accounts assigned to specific UC06 High roles

text: Use case name: ID: Priority:

text: Administration and publication UC07 High of cybersecurity certification schemes

text: Use case name: ID: Priority:

text: Administration of EU cybersecurity certificates and UC08 High EU statements of conformity

text: Use case name: ID: Priority:

text: Administration of UC09 High communication platform and official publications

text: Use case name: ID: Priority:

text: Administration of the drafting section UC10 High

text: Use case name: ID: Priority:

text: Prepare a candidate scheme UC11 High

text: Use case name: ID: Priority:

text: Review a candidate scheme UC12 High

text: Use case name: ID: Priority:

text: Access to DMS drafting section UC13 High

text: Use case name: ID: Priority:

text: Access to Meeting Management section UC014 High

text: ECCG_User AHWG_User

text: Use case name: ID: Priority:

text: Approve requests to prepare a UC15 High candidate scheme

text: Use case name: ID: Priority:

text: Provide voting for draft candidate certification scheme UC16 High

text: Use case name: ID: Priority:

text: Transmit draft of proposed candidate scheme to EC UC17 High

text: ENISA_User UC17

text: Use case name: ID: Priority:

text: Submits an EU statement of conformity UC18 High

text: Use case name: ID: Priority:

text: Provides feedback UC19 High

text: Use case name: ID: Priority:

text: Access to publicly available information on Publication UC20 High Platform

text: Download docs

text: <<include>> NO_ROLE UC20 <<include>> Preview docs

text: Use case name: ID: Priority:

text: Access to the Collaboration platform UC021 High

text: ECCG_User AHWG_User

text: SCCG_User Com_Admin

text: Com_Admin ESO_User

text: Use case name: ID: Priority:

text: Upload annual report UC22 High

text: Use case name: ID: Priority:

text: Request revision of schemes UC23 High

text: Use case name: ID: Priority:

text: Provide feedback for schemes UC24 High

text: Use case name: ID: Priority:

text: Formal peer review UC25 High

text: NCCA_User UC31

text: <<extend>> Certs_Statements_Admin ENISA_User

text: Use case name: ID: Priority:

text: Prepare reports UC26 High

text: Use case name: ID: Priority:

text: Reject request for candidate scheme UC27 High

text: Use case name: ID: Priority:

text: Search UC28 High

text: Use case name: ID: Priority:

text: User login UC29 High

text: Enter username

text: <<include>> NO_ROLE

text: Enter password

text: Create username

text: Create password

text: Use case name: ID: Priority:

text: User register UC30 High

text: Enter username

text: <<include>> User

text: Enter password

text: Create username

text: Create password

text: Use case name: ID: Priority:

text: User logout UC31 High

text: Download docs

text: <<include>> User UC20 <<include>> Preview docs

text: Use case name: ID: Priority:

text: Interaction between EC and UC32 Normal third counties for mutual agreements

text: EU Login https://webgate.ec.europa.eu/cas/ 74

text: Dublin Core Metadata Element Set http://www.dublincore.org/specifications/dublin-core/dces/ 75

text: https://ec.europa.eu/ipg/about/rules/ 81

text: Indicator Typical Guaranteed Unit

text: Availability 99.3% 99.0% Uptime/month

text: Response time 1 sec (first byte) Seconds

text: Network time (taken <= 3 sec Seconds by the server to answer to the request of a browser)

text: Dublin Core Metadata Element Set http://www.dublincore.org/specifications/dublin-core/dces/ 87

text: Name of property Type Mandatory Purpose

text: Article 58

text: - National cybersecurity certification authorities https://eur-lex.europa.eu/legalcontent/EN/TXT/HTML/?uri=CELEX:32019R0881&from=EN#d1e3956-15-1 93

text: Entity IT Role Use Cases

text: European Commission EC_User Access to communication platform Publish Union rolling work programme Request certification scheme Access to propose cybersecurity certification schemes Formal approval of cybersecurity certification schemes Request revision of schemes Provide feedback for schemes Request for mutual agreement Formal peer review Access Meeting management Roles_Admin Administration of roles and assignation of accounts to specific roles ENISA CSS_Admin Administration and publication of cybersecurity certification schemes Certs_Statements_Admin Administration of EU cybersecurity certificates and EU statements of conformity Com_Admin Administration of communication platform and official publications

text: Entity IT Role Use Cases

text: DraftSection_Admin Administration of the drafting section ADWG_Secretary Prepare a candidate scheme Review a candidate scheme Access to Content management system (CMS) drafting section Prepare reports Access Meeting management ENISA_User Access to collaboration platform Access to CMS drafting section Access to communication platform Mutual recognition Management Board of Mgmt_Board_User Approve requests to prepare a candidate scheme ENISA Transmit draft of proposed candidate scheme to EC Reject request for candidate scheme European Cybersecurity ECCG_User Request certification scheme Certification Group Access to DMS drafting section Access to Communication Platform Provide feedback for schemes Approval of cybersecurity certification schemes Access Meeting management Stakeholder Cybersecurity SCCG_User Access to Communication Platform Certification Group Access Meeting management Manufacturers & Providers Submitter_User Submit an EU statement of conformity Interested Parties Complains_User Provide feedback The Public NO_ROLE Access to publicly available information on publication platform Search European Standardisation ESO_User Access to communication platform Organisations (ESO) Access to collaboration platform Ad hoc Working Group ADWG_User Provide feedback for schemes Provide voting for draft candidate certification scheme Access to collaboration platform

text: Entity IT Role Use Cases

text: Access to communication platform

text: Access Meeting management

text: National Cybersecurity NCCA_user Upload annual report Certification Authority

text: All Entities All Roles Login

text: All Entities All Roles Register

text: All Entities All Roles Logout

text: Plone Collective Ploneboard https://github.com/collective/collective.ploneboard 13 Plone Discussion https://github.com/plone/plone.app.discussion 14 Drupal Forum module https://www.drupal.org/docs/7/core/modules/forum/overview 15 Drupal Advanced forum https://www.drupal.org/project/advanced_forum 97

text: Wikipedia - Comparison of anti-plagiarism software https://en.wikipedia.org/wiki/Comparison_of_anti-plagiarism_software 100

text: Final | 1.0 | Restricted | December 2019 102

identifier: ENISA it system for certification

title: ENISA it system for certification

text: ABOUT ENISA

text: The European Union Agency for Cybersecurity (ENISA) has been working to make Europe cyber secure since 2004. ENISA works with the EU, its member states, the private sector and Europe’s citizens to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of crossborder communities committed to improving network and information security throughout the EU. Since 2019, it has been drawing up cybersecurity certification schemes. More information about ENISA and its work can be found at www.enisa.europa.eu.

text: CONTACT

text: For contacting the authors please use isdp@enisa.europa.eu For media enquiries about this paper, please use press@enisa.europa.eu

text: EDITORS

text: ENISA

text: CONTRIBUTORS

text: Scott Cadzow Ralph Eckmaier Matthias Pocs Miruna Bădescu, Eau de Web Daniela Moșneagu, Eau de Web

text: LEGAL NOTICE

text: Notice must be taken that this publication represents the views and interpretations of ENISA, unless stated otherwise. This publication should not be construed to be a legal action of ENISA or the ENISA bodies unless adopted pursuant to the

text: Regulation (EU) No 2019/881

text: . This publication does not necessarily represent state-of the-art and ENISA may update it from time to time. Third-party sources are quoted as appropriate. ENISA is not responsible for the content of the external sources including external websites referenced in this publication.

text: This publication is intended for information purposes only. It must be accessible free of charge. Neither ENISA nor any person acting on its behalf is responsible for the use that might be made of the information contained in this publication.

text: COPYRIGHT NOTICE

text: © European Union Agency for Cybersecurity (ENISA), 2019 Reproduction is authorised provided the source is acknowledged.

text: For any use or reproduction of photos or other material that is not under the ENISA copyright, permission must be sought directly from the copyright holders.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: TABLE OF CONTENTS

text: 1. IDENTIFICATION OF BUSINESS AND TECHNICAL PROCESSES 7

text: 1.1 GENERAL INFORMATION 7

text: 1.1.1 Objectives of the review 7 1.1.2 Scope of the review 7 1.1.3 Related documents 7 1.1.4 Applied methodology 7

text: 1.2 GOVERNANCE OF THE FRAMEWORK 8

text: 1.2.1 Introduction and rationale for the EU cybersecurity certification framework 8 1.2.2 Overview of the framework 8 1.2.3 Development, design and publication of the URWP 9 1.2.4 The cybersecurity certification scheme 9 1.2.5 Recognition of an accepted CCS in a Commission Implementing Decision 10 1.2.6 Fines / complaint / courts, guidelines & regular re-assessment 11 1.2.7 Implementation of cybersecurity certification scheme 11

text: 1.3 PROCESSES 12

text: 1.3.1 Registration of self-asserted certificates 12 1.3.2 The certification process 13

text: 1.4 RESOURCES, AND ROLES AND RESPONSIBILITIES 17

text: 1.4.1 Notification of CABs 17 1.4.2 Role identification 18

text: 1.5 CSA REVIEW AND RELEVANT RECITALS AND ARTICLES 20

text: 1.5.1 CSA analysis by recital and

text: article 20

text: 1.6 OTHER CONSIDERATIONS 22

text: 1.6.1 Role of ECCG 22 1.6.2 Role and construction of SCCG 23 1.6.3 Peer review process 23 1.6.4 Issuing EU certificates and the role of ENISA's website 23 1.6.5 Functions and sub-functions of the IT-system 24

text: 1.7 BUSINESS PROCESSES 29

text: 1.7.1 Design and Publication of URWP 29 1.7.2 Preparation of the Candidate Cybersecurity Certification Scheme 29 1.7.3 Inclusion of an accepted candidate certification scheme in a Commission Implementation Decision 30 1.7.4 Implementation of Cybersecurity Certification Scheme 31 1.7.5 Request deriving from the implementation of the scheme 31 1.7.6 Registration of self-asserted certificate 32 1.7.7 Assessment and subsequently seek the revision 32 1.7.8 Peer review and mutual recognition 33

text: ENISA IT SYSTEM FOR CERTIFICATION 2. FUNCTIONAL REQUIREMENTS 34

text: 2.1 IT SYSTEM ARCHITECTURE AND FUNCTIONAL COMPONENTS 34

text: 2.1.1 Logical architecture 34 2.1.2 Major Functional Components 34

text: 2.2 USE CASES 35

text: 2.2.1 Use cases overview 35 2.2.2 Use Cases and Diagrams 37

text: 2.3 STAKEHOLDERS MAP 71

text: 2.4 FUNCTIONAL REQUIREMENTS 73

text: 2.4.1 Authentication and authorization 74

text: 2.5 DOCUMENT AND CONTENT MANAGEMENT 74

text: 2.5.1 Libraries (data store) 75 2.5.2 Reporting, data mining and auditing 75 2.5.3 Communicating over a platform 76 2.5.4 Collaboration on documents 77 2.5.5 Functional public website (CERMIT Portal) 77

text: 2.6 NON-FUNCTIONAL REQUIREMENTS 78

text: 2.6.1 Availability 78 2.6.2 Usability and accesibility 78 2.6.3 Reliability 78 2.6.4 Performance 79 2.6.5 Security 79 2.6.6 Maintainability 79 2.6.7 Scalability 79 2.6.8 Brand integrity and enhancement 79

text: 2.7 ASSUMPTIONS AND CONSTRAINTS 79

text: 3. TECHNICAL REQUIREMENTS 81

text: 3.1 SYSTEM ARCHITECTURE 81

text: 3.1.1 Generic considerations 81 3.1.2 System overview 81 3.1.3 System architecture 83 3.1.4 Technology 84 3.1.5 Infrastructure services 84

text: 3.2 DETAILED DESIGN 86

text: 3.2.1 Content management system 86 3.2.2 Cybersecurity certification schemes 87 3.2.3 Request for certification scheme 91 3.2.4 European cybersecurity certificates and EU statements of conformity 92 3.2.5 National certification schemes 92

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 3.2.6 Conformity self-assessment 93 3.2.7 Conformity Assessment Bodies (CABs) 93 3.2.8 User groups (roles) 94 3.2.9 Lists of terms 96 3.2.10 Formal messages – Message board 96 3.2.11 Discussion forum 97 3.2.12 Meeting management 97 3.2.13 Data mining 99

text: 3.3 TIMELINE FOR IMPLEMENTATION 100

text: ENISA IT SYSTEM FOR CERTIFICATION

text: EXECUTIVE SUMMARY

text: The purpose of this study is to support ENISA in the development of an IT System that will enable all the involved stakeholders to collaborate, exchange and share information towards the preparation, adoption and review of cybersecurity certification schemes – the obligation stemming from the EU Cybersecurity Act . It is divided into three distinct parts, identifying the concrete business needs, processes, and functional and technical requirements for such a system.

text: The first part provides an overview of the envisioned interactions between ENISA, the European Commission (EC) and other relevant stakeholders within the scope of the EU Cybersecurity Certification Framework, as described in the recently legislated EU Cybersecurity Act. In particular, it describes the requirements stemming from the Cybersecurity Act (CSA) in terms of business needs, processes, IT functions and IT use cases. It identifies business activities and provides a semi-formal description of the business logic of the IT System use cases.

text: The structure of the first part follows from the identification of processes and procedures described (explicitly and implicitly) under Title III of the Cybersecurity Act and categorised into the following domains:

text:  governance of the certification process,  processes,  requests,  priorities,  resources, and  roles and responsibilities.

text: For each domain listed above, the document describes interactions between ENISA, the EC and other relevant stakeholders that derive explicitly from the content of Cybersecurity Act or are implicitly required to support key functionalities described in the Act. The aim is to provide the foundations for a holistic understanding on how ENISA and the European Commission will cooperate to effectively design and implement the EU’s cybersecurity certification framework.

text: The goals of the second and third parts are:

text:  To provide the user requirements, use cases, functional and technical specifications of the IT System that will enable all the involved stakeholders to collaborate, exchange and share information towards the preparation, adoption and review of cybersecurity certification schemes. The IT System should take into account all the involved stakeholders: ENISA, Commission, ECCG, SCCG, National cybersecurity certification authorities, National accreditation bodies, Conformity assessment bodies, Standards Developing Organizations.  To provide all the functional and technical specifications of the IT System that will enable all the involved stakeholders to collaborate, exchange and share information towards the preparation, adoption and review of EU cybersecurity certification schemes. An indicative description is given below: o Management of the Union rolling work programme for European Cybersecurity Certification: this includes the initial setup, the processing

text: ENISA IT SYSTEM FOR CERTIFICATION

text: through the interaction with the related stakeholders and the final publication of the programme. o Preparation, adoption and review of a European cybersecurity certification scheme which indicatively includes: request, possible refusal of the request, preparation, consultation with all related stakeholders, establishment of adhoc working groups, ECCG opinion and close collaboration, transmission of the scheme to the Commission, evaluation of the scheme every 5 years, request from the Commission or ECCG group to revise an existing scheme.  To provide all the non-functional requirements of the IT system that will ensure the proper operation of the system, including issues like Security, Data Privacy, Logging, Storage, Configuration, Performance, Cost, Interoperability, Flexibility, Disaster recovery and Accessibility.  To provide the technical and functional specifications for the upcoming development of the Website on European cybersecurity certification schemes. Based on the provisions of the CSA: o The Agency shall maintain a dedicated website providing information on, and publicity of European cybersecurity certification schemes, certificates and EU statements of conformity, including with regard to withdrawn and expired cybersecurity certification schemes and certificates and the repository of links to cybersecurity information provided online by manufacturers and providers in accordance to corresponding article of the CSA o Where applicable, the website shall also indicate the national certifications schemes that have been replaced by a European cybersecurity certification scheme.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 1. IDENTIFICATION OF BUSINESS AND TECHNICAL PROCESSES

text: 1.1 GENERAL INFORMATION 1.1.1 Objectives of the review

text: The objective of this part of the study is to analyse the requirements stemming from the Cybersecurity Act (CSA) in terms of business needs and processes. It should identify business activities and provide a formal description of the business logic of the IT System use cases. Results of the review will be used by ENISA as input to the next step, which will consist in functional and technical specifications of the IT System that will enable all the involved stakeholders to collaborate, exchange and share information towards the preparation, adoption and review of cybersecurity certification schemes. It produces the input to the subsequent step, consisting in describing functional and technical requirements for such an IT system.

text: 1.1.2 Scope of the review

text: This chapter examines the Cybersecurity Act (CSA) to identify particular actions, in the form of both business and technical processes that will enable ENISA to meet its objectives under the CSA. This therefore examines the recitals and articles of the CSA to identify such processes.

text: In particular we consider those EU needs related to emerging cybersecurity certification schemes, which will operate under the European cybersecurity certification framework.

text: 1.1.3 Related documents

text: The study is based on the following documents:

text: Regulation (EU) 2019/881

text: – the Cybersecurity Act  Rolling Plan for ICT Standardisation 2018  Baseline Security Recommendations for IoT, November 2017  IoT Security Standards Gap Analysis: Mapping of existing standards against requirements on security and privacy in the area of IoT, December 2018

text: 1.1.4 Applied methodology

text: No particular formal method has been applied. For the present document a more conventional text based analysis has been undertaken and used to present the results.

text: ENISA IT SYSTEM FOR CERTIFICATION 1.2 GOVERNANCE OF THE FRAMEWORK 1.2.1 Introduction and rationale for the EU cybersecurity certification framework (EU CSCF)

text: The rationale for the EU cybersecurity certification framework is derived from the recitals of the CSA, in particular from Recital 75, which outlines the broad requirement for certification but explicitly relieves the regulation of any obligation to define the certification process itself. Rather it is indicated that ENISA and the other EU stakeholders build the required processes. With the remit of the EU cybersecurity certification framework covering ICT products, services and processes, which conceivably addresses many thousands of entities it should be clear that the EU cybersecurity certification framework should be strongly governed. As the EU expert body for matters relating to Cybersecurity it is reasonable to expect ENISA to be at the heart of this governance process but it is recognised that many other stakeholders will have roles to play in enforcing and implementing any EU cybersecurity certification programme.

text: 1.2.2 Overview of the framework

text: The EU cybersecurity certification framework entails four main phases:

text: 1. the creation and publication of the Union Rolling Working Programme (URWP); 2. the preparation of a candidate cybersecurity certification scheme; 3. the enforcement by legislation of the accepted candidate scheme; and,

text: 4. the implementation of the scheme.

text: Candidate Union Rolling Work Cybersecurity Legislative Implementation Programme (URWP) Certification procedure Scheme (CCCS)

text: Figure 1: Sequence of events in development of EU CSCF

text: Throughout these phases, multiple stakeholders are involved, with EC, ENISA, the European Cybersecurity Certification Group (ECCG) and the Stakeholder Cybersecurity Certification Group (SCCG) being the main entities responsible for the governance of the framework. The phases run in strict sequence with oversight through the stakeholder groups (ECCG and SCCG) operating continuously.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 2: Sequence of events in development of EU CSCF identifying stakeholders for each phase

text: The stakeholders involved in each stage of the timeline are identified in Figures 1 and 2.

text: Details of the roles and responsibilities of each of the ECCG and SCCG are addressed in greater detail later in the present document.

text: 1.2.3 Development, design and publication of the URWP

text: As a pre-requisite for the publication of the URWP (related to cybersecurity) a number of steps are required:

text:  The forming of the SCCG o EC prepares the Terms of Reference (ToR) document and the Call for expression of interest o EC and ENISA publish the Call for expression of interest o ENISA provides a list of candidate members to EC – this may be derived from the existing list of domain experts maintained by ENISA o EC selects based on gender and geographical balance criteria  EC requests advice from SCCG and ECCG  Transparent and broad consultation among all stakeholders based on specific criteria  Publication of a legal non-binding document by EC (at least every three years)  Identification of strategic priorities for future EU cybersecurity certification schemes  Listing of ICT products, services and processes or categories that will benefit from being covered by a scheme  Multiyear overview of requests for candidate schemes taking into account the URWP

text: 1.2.4 The cybersecurity certification scheme

text: There is no requirement to have a single unified cybersecurity certification scheme, thus the CSA discusses the need for ENISA to prepare candidate European cybersecurity certification schemes described in RWP, or for a scheme separately requested by EC or ECCG in urgent

text: ENISA IT SYSTEM FOR CERTIFICATION

text: cases, although in the latter scenario ENISA reserves the right to reject the request. Thus if the URWP identifies n schemes required ENISA shall prepare proposals for those n schemes (where n is at least 1).

text: Every candidate scheme should adhere to a number of common principles and in each case ENISA is expected to create an ad-hoc working group to assist in the preparation of the scheme. Thus ENISA, the ad hoc working group (consisting of contracted experts, including from the Member States’ competent authorities), and the ECCG (who may advice and express an opinion for the final candidate scheme), are all involved in the scheme's development. The normal operating model should be to seek consensus amongst these stakeholders although ENISA has the final say. ENISA is further tasked to provide information about all schemes, both candidates and adopted, to its website as well as indicate the national schemes replaced by European schemes. Finally, ENISA should evaluate periodically (every five years) all adopted European schemes and upon EC’s or ECCG’s request to commence the process for a revised candidate scheme.

text: NOTE: There is a risk of a disruption of business if unscrupulous suppliers propose many schemes as candidates knowing that even if they are not adopted that they have to be referred to. The existence of a scheme in a formally maintained EU/ENISA database however gives credence to the scheme even if it is marked as not-adopted. A minor change should be that only credible schemes are forwarded for consideration and invalid or non-credible schemes are filtered away from official recognition.

text: The content of ENISA's public facing website will be considered as authoritative and thus the data held and presented has to be verified for its overall integrity.

text: 1.2.5 Recognition of an accepted scheme in a Commission Implementing Decision

text: Once a candidate cybersecurity certification scheme is communicated by ENISA to EC, the EC is empowered to adopt it through implementing acts. The process steps involved are:

text:  ENISA transmits the candidate scheme to EC o Comprehensive set of documents as defined in the Cybersecurity Act  Rules  Technical requirements  Standards  Procedures o Specified a minimum set of elements  Subject matter  Scope and object of the cybersecurity certification including ICT products, services and processes covered  Detailed specification of cybersecurity requirements with reference to standards or technical specifications  Evaluation criteria and methods  Levels of assurance and their respective evaluation levels  Specify conditions under which software or hardware updates may require recertification of an ICT product or service or the scope of this certificate being reduced  This set of elements could be provided to ENISA complementing the RWP  EC is empowered to adopt the proposed candidate schemes by means of an implementing act. o EC to prepare an implementing Act

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  EC to be notified by national certification authorities regarding the conformity assessment bodies accredited o Authorisation to issue certificates at specified assurance levels  EC to publish a list of notified conformity assessment bodies in the Official journal (one year after the entry into force) o Amend the list based on notifications after the expiry date o Handle requests to remove conformity assessment bodies

text: 1.2.6 Fines / complaint / courts, guidelines & regular re-assessment

text: Whilst governance of the European cybersecurity certification scheme requires that EU Member States lay down the rules on penalties applicable to infringements and measures necessary for compliance there is no direct role for ENISA over and above those noted here:

text:  Elaboration of guidelines: ENISA shall compile and publish guidelines and develop good practices, concerning the cybersecurity requirements of ICT products, ICT services and ICT processes, in cooperation with national cybersecurity certification authorities and industry in a formal, structured and transparent way. ENISA shall contribute to capacity-building related to evaluation and certification processes by compiling and issuing guidelines as well as by providing support to Member States at their request.  Regular re-assessment of schemes: The Commission acting alongside ENISA shall regularly assess the efficiency and use of the adopted European cybersecurity certification schemes and whether a specific European cybersecurity certification scheme is to be made mandatory through relevant Union law  Promotion: ENISA shall promote the use of European cybersecurity certification, with a view to avoiding the fragmentation of the internal market.

text: 1.2.7 Implementation of cybersecurity certification schemes

text: A number of stakeholders are involved in the implementation of any particular certification scheme with different roles and responsibilities. It is worth noting that ENISA is not explicitly involved in this stage apart from receiving feedback regarding the schemes. More specifically, the processes are:

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  EC and national authorities to exchange information, experiences and good practice with the assistance of ECCG  Share information on possible non-compliance

text: A critical element of the cybersecurity certification framework is to assess and subsequently seek the revision, where necessary, of adopted schemes. The processes are:

text:  EC to assess regularly and at least biannually the efficiency and utilisation of the adopted certification schemes  EC to assess if certain schemes should be rendered mandatory through relevant Union legislation o Identify ICT, products, services and processes for mandatory schemes o Prioritise sectors listed in Annex II of 2016/1148 Directive o Selection of mandatory schemes based on the criteria described in cybersecurity Act

text: To ensure a uniform implementation, peer reviews for relevant certification authorities are mandatory. The processes for the peer reviews are:

text:  EC to organise with at least two MS peer reviews for authorities o ENISA may participate in the peer review  Implementing acts may be adopted to establish plans for peer reviews o Peer reviews to cover a period of at least five years o Specific criteria for peer review teams and methodology used  ECCG will draw up summaries of these reviews o Issue guidelines and recommendations on actions or measures for the relevant authorities

text: There are specific excerpts in the cybersecurity Act denoting how EC can engage in discussions with third countries to create mutual recognition agreements for cybersecurity certifications. The processes are:

text:  Mutual recognition agreements o ENISA and ECCG to advise EC on which negotiations to initiate with third countries o Mutual recognition agreements can be stated in the candidate cybersecurity certification scheme

text: 1.3 PROCESSES 1.3.1 Registration of self-asserted certificates

text: A consequence of

text: Article 53.3

text: is that ENISA has to be able to implement a process for receipt, cataloguing and storage/recovery of self-asserted conformity claims and the resultant "EU statement of conformity". The participants in this process are:

text:  ENISA; o Registrar o Claimant review authority  The claimant;  The evaluation authority of the claimant;  The authority for the specification that the claimant asserts conformity.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Recital 75 and associated sub-recitals provide greater detail of the expectations for assessment.

text: The manufacturer shall make the EU statement of conformity, technical documentation, and all other relevant information relating to the conformity with the scheme available to the NCCA for the period provided for in the corresponding European cybersecurity certification scheme.

text: A copy of the EU statement of conformity shall be submitted to the national cybersecurity certification authority and to ENISA.

text: 1.3.2 The certification process

text: 1.3.2.1 Introduction and CSA considerations

text: A key element throughout the CSA is an expectation that the certification process is available and can be readily adopted by developers and hence by the market as a whole. The practical position is that as of this writing there is no citable process of certification.

text: Certificates issued according to the ISO/IEC 15408 (the Common Criteria) are recognised internationally within the Common Criteria Recognition Agreement (CCRA) and by the SOG-IS Mutual Recognition Agreement (MRA). The wider intent is that the relatively restricted set of member states who are involved in either CCRA or MRA needs to be extended (Recitals 68 and 69 apply).

text: Article 54 of the CSA elaborates on the content of the certificate and the scheme that underpins it. There is a "chicken and egg" situation here that has to be carefully managed in order to ensure that content of the certificate does not define the scheme used to fill in the content.

text: The issuing of an EU statement of conformity is voluntary, unless otherwise specified in Union law or Member State law.

text: 1.3.2.2 Developer and SDO obligations for certification

text: Much of the remainder of this chapter extends from that given in the ENISA publication "IoT Security Standards Gap Analysis" to identify specific actions and processes that have to be addressed by each stakeholder (primarily the SDOs, the assessment agencies/authorities, and the affected industry sectors).

text: Very specifically

text: Article 54.1

text: c states that the certification scheme must make references to the international, European or national standards applied in the evaluation that leads to the granting of the certificate. The challenge to SDOs is therefore to make standards available that meet the necessary technical rigour for evaluation.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 3: Sequence of events in development of EU CSCF identifying stakeholders for each phase

text: For self-assertion of a product or service it is the end point of the SDO role from the above picture that is the starting point for the process that ought to lead to certification. In other words, standards have to have some means of proving that the product or service conforms to them. Conventionally this is achieved using formal test cases and a statement of conformance (the Implementation Conformance Statement).

text: There is an issue with such testing – it tends to be positive in outlook, it doesn't really look under the covers. It is also clear that the number of standards that allow for conformance testing of security features is small in relation to the number of standards. In part, this may be that if a specific operation in the security domain, e.g. the generation of a digital signature is relatively commodity like, in that either the code works or it doesn't. It is in the purpose of a digital signature that the security lies and not necessarily in the specific operation.

text: 1.3.2.3 What form of standards fit to use in certification?

text: There are several domains in which standards are specifically cited as part of the regulatory framework to allow market access. The obvious domains are in each of safety and in radio regulation. In each case, there are a set of Harmonised Standards cited at some point in the Official Journal and which are called out in a Declaration of Conformity (DoC) in a product. Examples of such DoCs for 2 models of smartphone are given below (see also the content of ETSI TS 103 346 regarding electronic versions of such DoC).

text: Whilst the purpose of certificates in the scope of the CSA are not the same as a Declaration of Conformity used in the safety and radio domains the value to the end user may be considered as equivalent.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 4: Screenshot of DoC for the Apple iPhone 7

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 5: Screenshot of DoC for the Samsung Galaxy S7 (model G930F)

text: The Common Criteria approach in the form of a cPP or even in the form proposed for the "Direct Rationale" is somewhat different from the forms used in the SDOs cited in the CSA. This leads directly to a requirement for ENISA to work with the SDOs to define the format for an acceptable process of standards that will allow certification to be granted (i.e. if conformance to the standard is shown then some form of "safe harbour" is effectively granted by self-assertion).

text: 1.3.2.4 Definition of European Security Norm standard format

text: The assurance role of security standards needs to be reinforced as opposed to the purely functional role that many standards seek to define.

text: I.e. most standards, when normative, specify in detail the stimulus-response behaviour expected of a device. Thus, for an action such as digital signature verification, the stimulus will be sending the signature and supporting data to a black box function, with an expected

text: ENISA IT SYSTEM FOR CERTIFICATION

text: response of "True" if the signature is verified, and "False" otherwise. The rationale for the function is often not explicit, but to give assurance it is the rationale that is (arguably) more critical. Some SDOs do perform a risk analysis prior to the development of specific standards, where the risk analysis will provide the rationale for the provision of the security function.

text: Process partners: SDOs, ENISA, SDO participants, Evaluation authorities

text: As stated in [4] the overall purpose of standards from the perspective of the market is twofold in defining what a standard is intended to achieve: (1) interoperability, and (2) confidence. The role of standards in achieving interoperability is well defined by the SDOs themselves and has been extensively written about in [4] and elsewhere. The certification opportunity lies in addressing the role of standards in the domain of confidence. It is somewhat obvious to state that a failure to achieve interoperability will negatively impact confidence, however in the security domain the counter assertion, that interoperability will positively impact confidence with respect to security, is much less likely to be true.

text: Standards as technical specifications apply in a specific context: Generally, a standard will apply to a single product type, or even a single function within a product or service. Security standards are similarly contextual and this has to be recognised when evaluating the security offered and the resultant certificate request. A general concept for the role of standards in the evaluation process is presented in the figure below.

text: Figure 6: Role of standards in certification process

text: 1.4 RESOURCES, AND ROLES AND RESPONSIBILITIES 1.4.1 Notification of CABs

text: Notification of CABs: For each European cybersecurity certification scheme, the NCCAs shall notify the Commission of the CABs that have been accredited and of any subsequent changes. A NCCA may submit to the Commission a request to remove a CAB notified by that authority from the list.

text: Accreditation of CABs: The CABs shall be accredited by national accreditation bodies appointed pursuant to

text: Regulation (EC) No 765/2008

text: . Where a European cybersecurity certificate is issued by a NCCA, the certification body of the NCCA shall be accredited as a CAB. Where European cybersecurity certification schemes set out specific or additional requirements, only CABs that meet those requirements shall be authorised by the NCCA. The accreditation shall be issued to the CABs for a maximum of five years. National accreditation bodies shall take all appropriate measures within a reasonable timeframe to restrict, suspend or revoke the accreditation of a CAB. 17

text: ENISA IT SYSTEM FOR CERTIFICATION

text: One year after the entry into force of a European cybersecurity certification scheme, the Commission shall publish a list of the CABs notified under that scheme in the Official Journal of the European Union. If the Commission receives a notification after the expiry of the period referred to in paragraph 2, it shall publish the amendments to the list of notified conformity assessment bodies in the OJEU within two months of the date of receipt of that notification. The Commission may adopt implementing acts to establish the circumstances, formats and procedures for notifications.

text: On notification by the NCCA, the Commission shall publish the corresponding amendments to that list in the OJEU within one month of the date of receipt of the national cybersecurity certification authority’s request.

text: 1.4.2 Role identification

text: The CSA identifies a number of roles that can be grouped against organisational type. This is shown pictorially in Figure 3.

text: In Figure 7 the entities highlighted in parallelograms are roles that should be assigned in the access control framework of the ICT facilities to be provided by ENISA for the management of the Certification Process.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 7: CSA mapping of roles against organisational type

text: ENISA IT SYSTEM FOR CERTIFICATION 1.5 CSA REVIEW AND RELEVANT RECITALS AND ARTICLES 1.5.1 CSA analysis by recital and article

text: The analysis in the table below considers the CSA with specific attempt to identify process requirements (business or technical) by reference to specific Articles and Recitals of the CSA.

text: RECITAL/ Text Underlying process requirement Business/ ARTICLE Technical

text: Article 49.7

text: The Commission, based on the candidate Requires interaction with the B scheme prepared by ENISA, may adopt Commission implementing acts providing for a European cybersecurity certification scheme for ICT products, ICT services and ICT processes which meets the requirements set out in Articles

text: and

text: . Those implementing acts shall be adopted in accordance with the examination procedure referred to in

text: Article 66(2)

text: Article 51

text: Security objectives of European cybersecurity No specific process requirement – this B certification schemes article states the overall objectives of the certification programme.

text: Article 52

text: Assurance levels of European cybersecurity No specific process requirement. B certification schemes However, the agreed assurance levels have to be cross referenced from the cataloguing process (see below) Modified in The manufacturer or provider of ICT products, ENISA has to be able to implement a T

text: Article 53.3

text: ICT services or ICT processes shall make the process for receipt, cataloguing and EU statement of conformity, technical storage/recovery of self-asserted documentation, and all other relevant conformity claims and the resultant information relating to the conformity of the "EU statement of conformity" ICT products or ICT services with the scheme available to the national cybersecurity certification authority referred to in

text: Article 58

text: for the period provided for in the corresponding European cybersecurity certification scheme. A copy of the EU statement of conformity shall be submitted to the national cybersecurity certification authority and to ENISA.

text: Article … including the type or categories of ICT A clear classification of type/category T 54.1.a products, ICT services and ICT processes of such equipment needs to be covered maintained.

text: RECITALS

text: Recital 75 The purpose of European cybersecurity B certification schemes should be to ensure that ICT products, ICT services and ICT processes certified under such schemes comply with specified requirements that aim to protect the availability, authenticity, integrity and confidentiality of stored, transmitted or processed data or of the related functions of or services offered by, or accessible via those products, services and processes throughout their life cycle. It is not possible to set out in detail the cybersecurity requirements relating to all ICT products, ICT services and ICT processes in this Regulation. ICT products, ICT services and ICT processes and the cybersecurity needs related to those products, services and processes are so diverse that it is very difficult to develop general cybersecurity requirements that are valid in all circumstances. It is therefore necessary to

text: ENISA IT SYSTEM FOR CERTIFICATION

text: adopt a broad and general notion of cybersecurity for the purpose of certification, which should be complemented by a set of specific cybersecurity objectives that are to be taken into account when designing European cybersecurity certification schemes. The arrangements by which such objectives are to be achieved in specific ICT products, ICT services and ICT processes should then be further specified in detail at the level of the individual certification scheme adopted by the Commission, for example by reference to standards or technical specifications if no appropriate standards are available. Recital 76 The technical specifications to be used in Requires that ENISA engage with the B European cybersecurity certification schemes EU-SDOs (CEN, CENELEC, ETSI). should respect the requirements set out in ENISA shall be held responsible for Annex II to

text: Regulation (EU) No 1025/2012

text: of justifying any deviation from adoption the European Parliament and of the Council of EU standards (19). Some deviations from those requirements could, however, be considered to be necessary in duly justified cases where those technical specifications are to be used in a European cybersecurity certification scheme referring to assurance level ‘high’. The reasons for such deviations should be made publicly available Recital 77 A conformity assessment is a procedure for This in part defines the set of T evaluating whether specified requirements conditions that need to be identifiable relating to an ICT product, ICT service or ICT in the resultant certificate. process have been fulfilled. That procedure is carried out by an independent third party that is not the manufacturer or provider of the ICT products, ICT services or ICT processes that are being assessed. A European cybersecurity certificate should be issued following the successful evaluation of an ICT product, ICT service or ICT process. A European cybersecurity certificate should be considered to be a confirmation that the evaluation has been properly carried out. Depending on the assurance level, the European cybersecurity certification scheme should indicate whether the European cybersecurity certificate is to be issued by a private or public body. Conformity assessment and certification cannot guarantee per se that certified ICT products, ICT services and ICT processes are cyber secure. They are instead procedures and technical methodologies for attesting that ICT products, ICT services and ICT processes have been tested and that they comply with certain cybersecurity requirements laid down elsewhere, for example in technical standards. Recital 78 The choice of the appropriate certification and It is suggested that this implies ENISA T associated security requirements by the users or a competent agency reviews the risk of European cybersecurity certificates should analysis associated to the request for be based on an analysis of the risks certification. associated with the use of the ICT products, The mapping from basic – substantial ICT services or ICT processes. Accordingly, – high to existing evaluation processes the assurance level should be commensurate needs to be made. with the level of the risk associated with the intended use of an ICT product, ICT service or ICT process.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: The impact of Articles

text: and

text: is a number of published lists that are to be maintained in the ICT facilities of ENISA. This is shown figuratively in Figure 9.

text: Figure 9: Scope of material to be published by ENISA against CSA article setting the obligation

text: ENISA's website (on the schemes/certificates) shall also indicate the national cybersecurity certification schemes that have been replaced by a European cybersecurity certification scheme.

text: 1.6 OTHER CONSIDERATIONS 1.6.1 Role of the ECCG

text: Members of ECCG are representatives of national cybersecurity certification authorities or representatives of other relevant national authorities. The ECCG is involved in the creation of the URWP and is empowered to propose to ENISA areas for potential schemes that are not included in the URWP. The ECCG provides advice to ENISA during the drafting of candidate EU cybersecurity certification schemes and expresses an opinion when the process is finalised. The ECCG further advises EC on the maintenance and review of existing European schemes. The EECG engages in capacity building activities between national cybersecurity certification authorities and supports the execution of peer assessment procedures. Finally, the ECCG can recommend ENISA to assist international standardisation organisations in order to address gaps in internationally recognised standards.

text: The ECCG shall be composed of representatives of NCCAs or representatives of other relevant national authorities.

text: A Member of the ECCG shall not represent more than two Member States.

text: ENISA shall provide the secretariat of the ECCG.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Consequence of this: ENISA shall be the sole authoritative source for data on all EU cybersecurity certification schemes, European cybersecurity certificates and EU statements of conformity for all cybersecurity certified products on the European market.

text: 1.6.2 Role and construction of the SCCG

text: Members of the SCCG are appointed by EC, selected from a list of experts proposed by ENISA. The Stakeholder Cybersecurity Certification Group shall be composed of members selected from among recognised experts representing the relevant stakeholders. The Commission, following a transparent and open call, shall select, on the basis of a proposal from ENISA, members of the Stakeholder Cybersecurity Certification Group ensuring a balance between the different stakeholder groups as well as an appropriate gender and geographical balance. EC and ENISA co-chair SCCG and the secretariat is provided by the Agency. The SCCG advises EC on strategic decisions regarding the European cybersecurity certification framework and upon request ENISA regarding the agency’s tasks on certification. The SCCG’s main role is to assist EC in the design of the RWP and on urgent situations to facilitate EC and the ECCG to decide for additional certification schemes not included in the RWP.

text: Consequence of this: ENISA shall be the co-chair and secretariat and shall maintain a record of all correspondence relating to the SCCG and a record of all meetings and decisions of the SCCG. ENISA shall also maintain a list of experts as both candidates and secondees (placements) to the SCCG.

text: 1.6.3 Peer review process

text: With a view to achieving equivalent standards throughout the Union in respect of European cybersecurity certificates and EU statements of conformity, NCCAs shall be subject to peer review. Peer review shall be carried out by at least two NCCAs of other Member States and the Commission and shall be carried out at least once every five years.

text: The peer review process shall assess the following:

text: • whether the activities of the NCCAs under review that relate to the issuance of European cybersecurity certificates are strictly separated from their supervisory activities;

text: • the procedures for supervising and enforcing the rules for monitoring the compliance with European cybersecurity certificates;

text: • the procedures used by the NCCSs under review for monitoring, authorising and supervising the activities of the CABs;

text: • whether the staff of authorities or bodies that issue certificates for assurance level 'high' have the appropriate expertise.

text: The Commission may adopt implementing acts establishing a plan for peer review which covers a period of at least five years, laying down the criteria concerning the composition of the peer review team, the methodology to be used in peer review, and the schedule, the frequency and other tasks related to it.

text: ENISA may participate in the peer review.

text: Consequence of this: As indicated further ENISA shall be the sole authoritative source for data on all EU cybersecurity certification schemes, European cybersecurity certificates and EU statements of conformity for all cybersecurity certified products on the European market, it is noted that this shall include an authoritative record of all peer reviews conducted, their target, their participants, and their reports.

text: 1.6.4 Issuing EU certificates and the role of ENISA's website

text: The CABs (and NCCAs) shall issue European cybersecurity certificates referring to assurance level 'basic' or 'substantial' (or 'high') on the basis of criteria included in the European cybersecurity certification scheme. The natural or legal person who submits ICT products, ICT services or ICT processes for certification shall make available to the CAB all information necessary to conduct the certification. The (certificate) holder shall inform the NCCA or CAB of

text: ENISA IT SYSTEM FOR CERTIFICATION

text: any subsequently detected vulnerabilities or irregularities concerning the security that may have an impact on its compliance with the (certification) requirements. ENISA shall maintain a dedicated website providing information on the European cybersecurity certification schemes, European cybersecurity certificates and EU statements of conformity. Such a database should also include:  information on the European cybersecurity certification schemes which are no longer valid  information on withdrawn and expired European cybersecurity certificates and EU statements of conformity  repository of links to cybersecurity information provided in accordance with

text: Article 55

text: Consequence of this: ENISA shall be the sole authoritative source for data on all EU cybersecurity certification schemes, European cybersecurity certificates and EU statements of conformity for all certified products on the European market.

text: 1.6.5 Functions and sub-functions of the IT-system

text: Considering the requirements contained in the CSA, the following functions are necessary for the IT system operated by ENISA:

text: Function Sub-Function Provide a portal for the publication of EU cybersecurity certification schemes Publication Portal (PUB) Provide a portal for the publication of EU cybersecurity certificates Provide a portal for the publication of EU statements of conformity Provide a collaboration platform for preparing a EU cybersecurity Collaboration Platform (COL) certification scheme Communication Platform (COM) Provide secure communication between the different entities Retain information about EU cybersecurity certification candidate schemes Document Management System (DMS) Retain information about EU cybersecurity certificates Retain information about EU statements of conformity

text: An illustration explaining the interaction between these functions can be found in picture 7 (earlier in the present document). The Communication Platform is facilitated for any communication or information exchange between the different stakeholders mentioned in the CSA. The Collaboration Platform is used for preparing the EU cybersecurity certification candidate schemas. In the backend a CMS supports the web server connected with a database, document management system, message board, collaborative work environment and ticketing system. During the preparation of these candidate schemes the Communication Platform is used within the Ad hoc Working Group, the ECCG and the CSSG for communication. Any work progress and others outcome of the Ad hoc Working Group is stored in the Document Management System.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: The Document Management Systems additionally provides document control all provided EU. In the frontend a web server (for example, certification.enisa.europa.eu) offers different content depending on the classes of users.

text: Entity IT role IT use case Access to Communication Platform Publish Union rolling work programme Request certification scheme European EC_User Commission Access to proposes cybersecurity certification schemes Formal approval of cybersecurity certification schemes Administration of roles and account assigned to Roles_Admin specific roles Adminstration and publication of cybersecurity CSS_Admin certification schemes Administration of EU cybersecurity certificates Certs_Statements_Admin and EU statements of conformity Administration of communication platform and Com_Admin ENISA official publications DraftSection_Admin Administration of the drafting section Prepare a candidate scheme ADWG_Secretary Review a candidate scheme Access to DMS drafting section SysAdmin Classical ITC administrator Approve final cybersecurity certificate scheme draft Management Mgmt_Board_User Board of ENISA Transmit draft of proposed candidate scheme to EC Request certfication scheme European Cybersecurity ECCG_User Access to DMS drafting section Certification Group Access to Communication Plattform ENISA IT SYSTEM FOR CERTIFICATION Entity IT role IT use case Stakeholder Cybersecurity SCCG_User Access to Communication Plattform Certification Group manufacturers & Submitter_User Submits a EU statement of conformity providers Interested Parties Complains_User Provides feedback Access to publicly available information on The Public NO_ROLE Publication Platform European Access to Collaboration Platform Standardisation ADWG_User Organisations Access to Communication Platform (ESO) Ad hoc Working ADWG_User Access to Collaboration Platform Group National Cybersecurity NCCA_user Upload annual report Certification Authority

text: For users logged in, the above-mentioned classes of users should be defined. In justified cases additional roles may be foreseen including Conformity Assessment Body, National Accreditation Body and Other stakeholders (as a default value like in online stores). Users have their own accounts, belonging to one of the classes above. Accounts are created by individual users, ENISA activates them (in specific cases, ENISA can also create these accounts).

text: Different web server elements are available to different classes of users. The following web server elements support the functions of the IT system:

text: 1. Requests for schemes 2. Schemes under the EU framework (database of schemes) 3. Conformity Assessment Bodies 4. Documents repository

text: 5. Message board

text: 6. Ad-hoc Expert Groups management

text: 7. Database of national schemes

text: 8. Last events

text: 9. Contact ENISA

text: 1. Requests for certification scheme

text: o Requests can be initiated by European Commission or ECCG o Specific attribute of the user (EC/ECCG) required to launch the request o Online form with the following fields:  Name of scheme  Reference to Rolling Plan  Requestor

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Assurance level  Scope  Requirements  Other information (specific documents can be uploaded later, to the working folder) o Scheme, after being requested, shows on the web server with the following status:  Request received  Pending MB approval  Under elaboration  Transmitted to European Commission  Published (reference to COM decision)  Rejected  + status - Received, Pending MB approval, Under elaboration, Scheme transmitted to COM, Scheme published (number of COM decision), scheme rejected (by whom, on which grounds) o Validation service required:  Requests receives a number and a “service ticket” is issued  ENISA acknowledges reception of request  Management Board allows to launch the preparation of the scheme (art.49.2)  Ticket “solved” when the draft scheme is delivered to the European Commission  All changes communicated to the requestor, EC and ECCG  General observation: the EC, according to CSA, doesn’t intervene in the process of writing schemes

text: 2. Database of schemes

text: o Content  Status of schemes (request / elaboration / published / withdrawn)  Documentation of the scheme (all parts)  Certificates issued under the scheme  National schemes withdrawn  CABs accredited for the scheme  Date of last evaluation of the scheme o Schemes documents - uploaded by ENISA o National schemes affected - uploaded by ENISA o Certificates/statements of conformance and their status will be managed by national bodies and will include:  Name of product/service/process  Assurance level  Status of certificate (valid, withdrawn, expired)  Date of granting  CAB issuing certificate  Date of validity  Link to more information (art.55) o If evaluation date approaches 5 years  Notification has to be issued to ENISA  Option to receive feedback from logged stakeholders should be provided through an online form

text: 3. Database of Conformity Assessment Bodies

text: o In principle, CABs should be notified to the European Commission, not to ENISA. However, for consistency, ENISA should maintain this information as well o National Accreditation Bodies could “notify the European Commission” through ENISA system

text: ENISA IT SYSTEM FOR CERTIFICATION

text: o Alternatively, the information about accredited CABs could be received by ENISA from the Commission – to be discussed with EV o Content of database o Name of the CAB o Name of the accrediting NAB o Scheme for which CAB is accredited (automatic link to the database of schemes) o Link to the information about accreditation o Date of accreditation o Date of expiry of accreditation

text: 4. Documents repository

text: o Suggested format – like used by SDOs o Purpose: exchange of documents between ENISA, EC, ECCG and SCCG o Folders o Meetings / Type (ECCG, SCCG, other) / Year / Meeting number o Projects / Scheme (number of the request) or short name o Proposed file names:  REQ – request,  INE – input ECCG  INS – input SCCG  DRS – draft of a scheme  SOV – summary of votes o Documents can be uploaded either by ENISA, or by the allowed bodies

text: 5. Message board

text: o Main purpose o Exchange of information with ECCG o Exchange of information with SCCG o “Forum” type, structured according to type of communication o Subgroups o Input ECCG o Input SCCG o General discussions o Possibility of commenting in threads and uploading documents o Possibility of weighted voting (for eventual use – user definition should contain the field “number of votes” for specific entity, like “ECCG France = 5”) o Threads started after reception of request (common format needed – to be elaborated)

text: 6. Ad-hoc Expert Groups management

text: o Information about “CEI” for experts for ad-hoc EGs o Upload of experts applications through webpage o Announcements of selection of experts for specific schemes o For logged in experts already contracted o Repository of documents o Collaborative working environment

text: 7. Database of national schemes

text: o Internal database, accessible to ENISA, European Commission, ECCG and SCCG o Responsibility of national bodies (or SCCG members) to provide input when requested, at the beginning of elaboration of schemes o Request to SCCG for information on industrial schemes o Information should contain attributes basing on requirements from Art.54 (elements of the scheme) o ENISA selects the entries with potentially affected schemes o Final draft of schemes includes schemes selected as overlapping

text: 8. Last events

text: ENISA IT SYSTEM FOR CERTIFICATION

text: o Information filtered according to class of user o Content o Announcements (from ENISA) o Information about new documents uploaded o Information about new messages on the board o Public information on progress in preparing candidate schemes (“ENISA shall consult all relevant stakeholders by means of a formal, open, transparent and inclusive consultation process”, Art. 49.3.)

text: 9. Contact ENISA

text: o A “mailbox” supporting various types of communication o Request for scheme o General opinion o Specific opinions (for example: on existing European cybersecurity certification schemes)

text: In principle, the responsibility is on the Commission and/or the ECCG, but ENISA might be involved in peer reviews of National certification bodies and “Bodies that issue certificates” at the high assurance level. ENISA carries out evaluation of schemes every 5 years. IT system functionality other than message board might not be necessary. Templates for requests, comments on schemes, evaluation of schemes, applications for ad-hoc EGs etc. have to be developed. Documents, exchange of information etc should be available and traceable at all times (like all work in SDOs, especially ISO). Security, backups etc. should be the duty of the contractor. The system designed should be portable, in case of change of service provider.

text: 1.7 BUSINESS PROCESSES

text: Based on the above, we describe the main business processes and associated activities, being part of EU Cybersecurity Certification Framework

text: 1.7.1 Design and Publication of URWP

text: EC leads the design and publication of the URWP. The Stakeholders Cybersecurity Certification Group (SCCG) and the the ECCG have an advisory role in this process. Therefore, the processes required for the publication of the URWP are:

text:  The forming of SCCG o EC prepares the Terms of Reference (ToR) document and the Call for expression of interest o EC and ENISA publish the Call for expression of interest o ENISA provides a list of candidate members to EC o EC selects based on gender and geographical balance criteria  EC requests advice from SCCG and ECCG o Transparent and broad consultation among all stakeholders based on specific criteria  Publication of a legal non-binding document by EC (at least every three years) o Identification of strategic priorities for future EU cybersecurity certification schemes o Listing of ICT products, services and processes or categories that will benefit from being covered by a scheme o Multiyear overview of requests for candidate schemes taking into account the URWP

text: 1.7.2 Preparation of the Candidate Cybersecurity Certification Scheme

text: ENISA is responsible to prepare the candidate cybersecurity certification scheme. Other stakeholders involved in this process include the ECCG, EC and an ad-hoc working group.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: More specifically, to provide a final candidate cybersecurity certification scheme the processes and procedures required are:

text:  Publication of the URWP and request from EC to ENISA to prepare the candidate scheme o ENISA must respond and commence the process without undue delay o In urgent cases the ECCG and EC can request a candidate scheme not included in the URWP  ENISA’s Management Board (MB) members are entitled to decline the request from ECCG provided they justify their decision  URWP is updated accordingly by EC  Setting up an ad-hoc working group o Publish Term of Requirement (ToR) document o Create a call for the expression of interest (CEI)  ENISA will select members based on gender and geographical balance criteria  Set the principles for the candidate scheme o Security objectives o Assurance levels o Conformity self-assessment o Elements of European cybersecurity certification schemes  Draft candidate scheme with the advice of ECCG and ad-hoc group o Formal, open, transparent and inclusive consultation o Iterations and qualification of feedback  Opinion of the ECCG for the final candidate scheme o ENISA shall take utmost account of the ECCG’s opinion but the opinion is not binding nor is the absence thereof blocking ENISA to transmit the candidate scheme  ENISA to transmit the finalized candidate scheme to EC o Comprehensive set defined at Union level  Rules  Technical requirements  Standards  Procedures o Specified a minimum set of elements  Subject matter  Scope and object of the cybersecurity certification including ICT products, services and processes covered  Detailed specification of cybersecurity requirements with reference to standards or technical specifications  Evaluation criteria and methods  Levels of assurance and their respective evaluation levels  Specify conditions under which software or hardware updates may require recertification of an ICT product or service or the scope of this certificate being reduced

text: 1.7.3 Inclusion of an accepted candidate certification scheme in a Commission Implementation Decision

text: Once a candidate cybersecurity certification scheme is communicated by ENISA to EC, EC is empowered to adopt it through implementing acts. The processes are:

text:  ENISA transmits the candidate scheme to EC  EC is empowered to adopt the proposed candidate schemes by means of an implementing act.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: o EC to prepare an implementing Act  EC to be notified by national certification authorities regarding the conformity assessment bodies accredited o Authorization to issue certificates at specified assurance levels  EC to publish a list of notified conformity assessment bodies in the Official journal (one year after the entry into force) o Amend the list based on notifications after the expiry date o Handle requests to remove conformity assessment body

text: 1.7.4 Implementation of Cybersecurity Certification Scheme

text: A number of stakeholders are involved in the implementation of the certification scheme with different roles and responsibilities. It is worth noting that ENISA is not explicitly involved in this stage apart from receiving feedback regarding the schemes. More specifically, the processes are:

text:  Manufacturers of ICT products or services submit applications to a conformity assessment body (CAB)  Submissions for certification must provide to the conformity assessment body all necessary information to conduct the certification process  Information should be in electronic format and available at least until the expiry date of the certificate or statement of conformity  Each Member State (MS) to designate one or more national cybersecurity certification authorities responsible to supervise compliance with obligations arising from cybersecurity Act o MS to inform EC of the designated authorities and their tasks o MS can assign tasks to existing authorities o MS can assign authorities in the territory of other MS upon mutual agreement o Activities of national cybersecurity authorities related to activities of certification  Specific tasks and responsibilities  Authorities to provide an annual summary report to EC and ENISA o Monitoring and enforcement o Activities of conformity assessment bodies o Activities of public bodies (accredited as conformity assessment bodies or national cybersecurity certification authorities)  EC and national authorities to exchange information, experiences and good practice with the assistance of the ECCG o Share information on possible non-compliance

text: 1.7.5 Request deriving from the implementation of the scheme

text: There are obligations for ENISA, which occur after the adoption of the scheme and revolve around gathering information during the lifecycle of every scheme. These are:

text:  Receive feedback for the finalized scheme o Identify key stakeholders to provide feedback  EC, ECCG, national authorities, self-certified organizations, manufacturers o Design a system to receive feedback  Establish a template for stakeholders to provide feedback  Receive annual reports from EC and national authorities  EC’s information exchange system for peer review is a potential system that ENISA can utilize o Establish criteria to assess the effectiveness of schemes  Key Performance Indicators

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Make available an up-to-date website o Publish information for adopted schemes  Request EC to notify ENISA when a scheme is adopted  Specify timeframe within which to receive this information  Publish information for candidate schemes  Establish a template o Specify timeframe for publication  Create publicly available reports for the candidate schemes  Establish a template for such a report with withdraw and expiration dates o Specify timeframe for publication o Automatically check internally when schemes are due to expire  Create notifications for expired schemes and commence the revision process  Set the timeframe for the triggering mechanism (how many months before the expiry date)  Elicit certificates and EU statements of conformity from all relevant stakeholders o Establish a system that will allow national authorities, conformity bodies and manufacturers to report when certificates are issued, revoked or altered o Design a template for stakeholders to report such information for every case o Create a repository of links for information provided by manufacturers o Identify and publish which national certification schemes are replaced by European schemes  Respond to invitation from EC to support the peer review process o EC to create ToR

text: 1.7.6 Registration of self-asserted certificate

text: This process is mainly the process for receipt, cataloguing and storage/recovery of self-asserted conformity claims and the resultant "EU statement of conformity".

text: The participants in this process are:

text:  ENISA o Registrar o Claimant review authority  The claimant o The evaluation authority of the claimant; o The authority for the specification that the claimant asserts conformity to

text: 1.7.7 Assessment and subsequently seek the revision

text:  EC to assess regularly and at least biannually the efficiency and utilization of the adopted certification schemes

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  EC to assess if certain schemes should be rendered mandatory through relevant Union legislation o Identify ICT, products, services and processes for mandatory schemes o Priorities sectors listed in Annex II of 2016/1148 Directive o Selection of mandatory schemes based on the criteria described in the Cybersecurity Act

text: 1.7.8 Peer review and mutual recognition

text:  EC to organize with at least two MS peer reviews for authorities o ENISA may participate in the peer review  Implementing acts may be adopted to establish plans for peer reviews o Peer reviews to cover a period of at least five years o Specific criteria for peer review teams and methodology used  The ECCG will draw up summaries of these reviews

text:  Mutual recognition agreements o ENISA and the ECCG to advise EC on which negotiations to initiate with third countries o Mutual recognition agreements can be stated in the candidate cybersecurity certification scheme

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 2. FUNCTIONAL REQUIREMENTS

text: 2.1 IT SYSTEM ARCHITECTURE AND FUNCTIONAL COMPONENTS 2.1.1 Logical architecture

text: Based on the processes identified and the associated activities, the main components of the integrated IT system to support all functionalities are presented in the diagram below. Yellow boxes depict the information available for a general public, while the green ones refer to collaborative tools

text: Figure 10 – IT system logical architecture

text: This section extends the analysis of the processes that are described in the Cybersecurity Act, as presented in Section 2.2 of this document, and identifies the key building blocks for an integrated system that will underpin ENISA’s activities. For every key building block of the system, we detail the functional and technical requirements in the next stages.

text: 2.1.2 Major Functional Components

text: The new IT System will provide the following major components:

text:  Databases for the storage and publication of cybersecurity certification schemes, certificates, statements of conformity, conformity assessment and other bodies 34

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Collaboration platform for the preparation and approval/rejection of the abovementioned types  Communication platform for the secure, traceable communication between the different entities  Content Management System with configurable publishing workflows, versioning and commenting capabilities: o Links to internal and external pages o Regular pages with static content o Files (any type), with extended functionality detailed in section o Videos and images o Events and meetings

text: The main access to all system functionalities will be done through the portal. Users should feel as they are interacting with a single platform, in a coherent sequence across devices. They should also be agnostic of the different technologies used to build the IT System. The main functional components identified for the IT System are detailed in section 2.4. Functional requirements include:

text:  Authentication and authorization  Document and content management  Libraries (data store)  Reporting, data mining and auditing  Collaboration on documents  Functional public website

text: 2.2 USE CASES

text: Based on business needs identified and the main functionalities of the IT System, we have identified the following use cases, which will be detailed in this section.

text: 2.2.1 Use cases overview

text: European Commission EC_User Access to communication UC01 platform Publish Union rolling work UC02 programme Request certification scheme UC03 Access to propose UC04 cybersecurity certification schemes Formal approval of UC05 cybersecurity certification schemes Request revision of schemes UC23 Provide feedback for schemes UC24 Request for mutual agreement UC29 Formal peer review UC25 Access Meeting management UC14

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Roles_Admin Administration of roles and UC06 assignation of accounts to ENISA specific roles CSS_Admin Administration and publication UC07 of cybersecurity certification schemes Certs_Statements_Admin Administration of EU UC08 cybersecurity certificates and EU statements of conformity Com_Admin Administration of UC09 communication platform and official publications DraftSection_Admin Administration of the drafting UC10 section ADWG_Secretary Prepare a candidate scheme UC11 Review a candidate scheme UC12 Access to Content UC13 management system (CMS) drafting section Prepare reports UC26 Access Meeting management UC14 ENISA_User Access to collaboration UC21 platform Access to CMS drafting section UC13 Access to communication UC01 platform Mutual recognition UC32 Management Board of Mgmt_Board_User Approve requests to prepare a UC15 ENISA candidate scheme Transmit draft of proposed UC17 candidate scheme to EC Reject request for candidate UC27 scheme European Cybersecurity ECCG_User Request certification scheme UC03 Certification Group Access to DMS drafting section UC13 Access to Communication UC01 Platform Provide feedback for schemes UC24 Approval of cybersecurity UC05 certification schemes Access Meeting management UC14 Stakeholder SCCG_User Access to Communication UC01 Cybersecurity Platform Certification Group Access Meeting management UC30 Manufacturers & Submitter_User Submit an EU statement of UC18 Providers conformity

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Interested Parties Complains_User Provide feedback UC19 The Public NO_ROLE Access to publicly available UC20 information on publication platform Search UC28 European ESO_User Access to communication UC01 Standardisation platform Organisations (ESO) Access to collaboration UC21 platform Ad hoc Working Group ADWG_User Provide feedback for schemes UC24 Provide voting for draft UC16 candidate certification scheme Access to collaboration UC21 platform Access to communication UC01 platform Access Meeting management UC14 National Cybersecurity NCCA_user Upload annual report UC22 Certification Authority All Entities All Roles Login UC29 All Entities All Roles Register UC30 All Entities All Roles Logout UC31

text: 2.2.2 Use Cases and Diagrams

text: Based on use cases identified, we propose a general use case diagram, which will be detailed in the next phase below.

text: 2.2.2.1 UC01 – Access to the Communication platform

text: Actors: EC_user, SCCG_User, ECCG_User, ADWG_User, Com_Admin, ESO_User, ENISA_User Description: The use case describes the interaction between users and the communication platform of the IT System. This use case covers the main part of the Communication platform – the Message Board. The Meeting Management tool and the email notifications to subscribers are covered in separate use cases. Trigger: Actors are logged in the system and want to access the communication section from the website. Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the platform Normal course: Information for steps:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 1. User accesses the Message Board and reviews the tasks for them and the team(s) 2. User follows up on the specific tasks using the portal functionality 3. User selects a group or specific e-mail address 4. User prepares the message 5. User sends a message to the group members or other entities involved in the process 6. User reviews the discussion threads (s)he is allowed to access 7. User responds to messages 8. System stored the messages posted 9. Notification emails are sent to subscribers Alternative courses: n/a Post conditions: 1. The actors accessed the communication platform, reviewed the messages received, sent messages Exceptions: n/a

text: Figure 11: Access to the Communication Platform Use Case Diagram

text: 2.2.2.2 UC02 – Publish Union rolling work program

text: Actors: EC_user Description: Publishing the URWP document on the website Trigger: Actors are logged in the system and want to publish a finalized URWP document Type: External Preconditions:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Actor is logged in the system and has appropriate authorization to access the platform Normal course: Information for steps: 1. User browses the specific folders 2. User selects the finalized version of the document 3. User prepares the publishing conditions and location 4. User previews document in final draft 5. User reviews that document is published in a correct format and in the correct location 6. User pushes the ‘Publish’ button Alternative courses: n/a

text: Post conditions: 1. The actors accessed the specific document and document was published on the website Exceptions: n/a

text: Figure 12: Publish Union rolling work program Use Case Diagram

text: 2.2.2.3 UC03 – Request certification scheme

text: Actors: EC_user, ECCG_User Description: The use case describes the interaction between users and the communication platform of the IT System in order to request a certification scheme Trigger: Actors are logged in the system and want to access the communication section from the website. Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the communication platform Normal course: Information for steps: 2. User accesses the corresponding section of the portal and adds a new request 3. User fills in the corresponding fields of the factsheet 39

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 4. User selects one or more roles to send the message to 5. User prepares the request message 6. User sends a message to the group members of ENISA 7. System stores the request 8. System updates the progress bar Alternative courses: n/a Post conditions: 1. The actors accessed the communication part of the corresponding section of portal and sent the request to the group members of ENISA Exceptions: n/a

text: Figure 13: Request certification scheme Use Case Diagram

text: 2.2.2.4 UC04 – Access to proposed cybersecurity certification schemes

text: Actors: EC_user, ECCG_User, ENISA_User Description: The use case describes the interaction between users and the collaboration platform of the IT System, in order to access the proposed cybersecurity certification scheme Trigger: Actors are logged in the system and want to access the proposed cybersecurity certification scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the collaboration platform Normal course: Information for steps: 2. User accesses the corresponding section of the portal 3. User browses the folders and selects the specific location

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 4. User selects the specific factsheet that includes the proposed cybersecurity scheme 5. User assesses that all parameters are included in the proposal 6. User reviews the templates for certification Alternative courses: n/a

text: Post conditions: 1. The user accessed the collaboration platform 2. System sent notification regarding the updated document to the relevant groups Exceptions: n/a

text: Figure 14: Access to proposed cybersecurity certification schemes Use Case Diagram

text: 2.2.2.5 UC05 – Formal approval of cybersecurity certification schemes

text: Actors: EC_user Description: The use case describes the interaction between user and collaboration platform of the IT System in order to access and approve the final cybersecurity certification scheme Trigger: Actors are logged in the system and want to access the final cybersecurity certification scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the collaboration platform Normal course: Information for steps: 1. User access the corresponding section of the portal 2. User browse the folders and select the specific location 3. User select the specific document that includes the final version of cybersecurity scheme 4. User reviews the document 5. User pushes the ‘approve’ button

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 6. System sends an update notification to all group members Alternative courses: n/a

text: Post conditions: 1. Cybersecurity Candidate scheme approved 2. The notification related to final status of document was sent to all relevant actors 3. Status of cybersecurity certification scheme is ‘approved’ 4. Progress bar was updated Exceptions: n/a

text: Figure 15: Formal approval of cybersecurity certification schemes Use Case Diagram

text: 2.2.2.6 UC06 – Administration of roles and accounts assigned to specific roles

text: Actors: Roles_Admin Description: The use case describes the interaction between user and administration platform of the IT System in order to manage the roles and accounts Trigger: Actors are logged in the system and want to access the administration section of IT System Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the administration section of the system Normal course: Information for steps: 1. User accesses the administration section 2. Users directed to the EU Login interface for creating accounts or retrieving passwords 3. User creates roles and assigns different rights for each role (view, change, review) 4. User assigns local roles to individual users to access different areas of the portal (entire portal, schemes’ revision section, collaboration sections, etc.) 5. System stores the information related to user accounts, roles, permissions

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 6. System sends notifications to users related to updating their rights Alternative courses: n/a

text: Post conditions: 1. The roles, rights and permissions were assigned to all participants 2. User accounts, rights and permissions are stored in the system 3. Notifications regarding the updating rights in the portal are sent Exceptions: n/a

text: Figure 16: Administration of roles and account assigned to specific roles Use Case Diagram

text: 2.2.2.7 UC07 – Administration and publication of cybersecurity certification schemes

text: Actors: CSS_Admin Description: The use case describes the interaction between users and the administration platform of the IT System, in order to manage the cybersecurity certification scheme Trigger: Actors are logged in the system and want to access the administration of cybersecurity scheme section of IT System Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the administration section of the system Normal course: Information for steps: 1. User accesses the administration section 2. User creates a certification scheme factsheet 3. User prepares the information to be uploaded into the different fields of the factsheet 4. System stores all information inserted in certification scheme factsheet 5. User maintains the information up to date 6. User assigns permissions to access this data to one or more roles 7. System stores the specific rights and permissions related to user access

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 8. The administrator grants access for commenting and voting on the certification scheme for different user roles 9. User publishes the certification scheme in the desired location in the website

text: 10. System updates the status of the scheme

text: 11. System sends notification to associated recipients regarding the update Alternative courses: n/a Post conditions: 1. Certification scheme database was updated 2. All information of the factsheet was uploaded into the database 3. All participants in the process were assigned a specific role, with rights for accessing the certification scheme 4. System stored the information, along with the associated rights and permissions 5. Cybersecurity certification scheme was published and available to the public 6. System sent notifications to users regarding the update Exceptions: n/a

text: Figure 17: Administration and publication of cybersecurity certification schemes Use Case Diagram

text: 2.2.2.8 UC08 – Administration of EU cybersecurity certificates and EU statements of conformity

text: Actors: Certs_Statements_Admin Description: The use case describes the interaction between users and the administration of the IT System, in order to manage the EU cybersecurity certificates and EU statement of conformity Trigger: Actors are logged in the system and want to access the administration of cybersecurity certificates and statement of conformity of IT System Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the administration section of the system Normal course: Information for steps:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 1. User accesses the section for certificates and statements of conformity 2. User checks the list of new cybersecurity certificates and statements of conformity 3. Updates the data on a certificate or statement of conformity, including their validity periods 4. Uploads the received certificate or statement of conformity in the document management component 5. Uploads the report with certificates issued received from NCCA 6. Prepares the format template for information related to the certificate or statement of conformity, in order to be published 7. System stores all information inserted in issued certificates database 8. User maintains information up to date 9. User assigns access permissions to different roles 10. System stores the specific roles and permissions related to users’ access 11. User accesses the specific location in website to publish the report with certificates and statements of conformity issued

text: 12. User previews each certificate or statement of conformity, properly linked to the corresponding schemes

text: 13. User publishes the list of certificates and statements of conformity with associated validity period and status (valid, expired, etc.)

text: 14. System sends notifications to associated recipients regarding the update

text: Alternative courses: n/a

text: Post conditions:

text: 1. Certificates and statements of conformity metadata were created and stored in the system 2. All specific parameters are up to date 3. All information was uploaded into the database 4. Specific permissions were granted to the appropriate roles for accessing information related to certificates and statements of conformity 5. The information related to certificates and statements of conformity is published with associated status 6. System sent notifications to users regarding the update

text: Exceptions: n/a

text: Figure 18: Administration of EU cybersecurity certificates and EU statements of conformity Use Case Diagram

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 2.2.2.9 UC09 – Administration of the communication platform

text: Actors: Com_Admin Description: The use case describes the interaction between administrators and the communication platform of the IT System, in order to manage the work spaces Trigger: Actors are logged in the system and want to access the administration of communication platform Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the administration section of the system Normal course: Information for steps: 1. User accesses the corresponding administration section 2. User creates and configures the Message Board for communication, to ensure an appropriate workflow for communication 3. User defines the necessary message types 4. User provides access to the user’s roles for each message type 5. User changes the specific rights of each role assigned during the process 6. System stores the information related to roles and permissions for communication spaces Alternative courses: n/a Post conditions: 1. The Message Board was created and configured to ensure appropriate workflow for communication 2. All participants in the process were assigned a specific role, with the necessary permissions for the communication section 3. System stored the information related to roles, rights and permissions for each communication space Exceptions: n/a

text: Figure 19: Administration of communication platform and official publications Use Case Diagram

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 2.2.2.10 UC10 – Administration of the drafting section

text: Actors:

text: Description:

text: The use case describes the interaction between administrators and the document management platform of the IT System, in order to manage the draft documents for each section

text: Trigger: Actors are logged in the system and want to access the document management platform

text: Type: External

text: Preconditions:

text: Actor is logged in the system and has appropriate authorization to access the document management section of the system

text: Normal course: Information for steps:

text: 1. User accesses the document management section 2. User defines the default publishing workflow for documents across the section (all folders) 3. User defines the workflow for specific types of documents in specific locations (folders) 4. User implements the workflow for specific types of documents in specific locations 5. User sets up specific permissions for each folder containing documents 6. System stores the information related to roles and permissions for drafting sections 7. User establishes the list of documents that will be drafted in document management section 8. User creates and configures a draft for each specific type of document (certification scheme, URWP, revision report, assessment report, peer review document, mutual agreement document, minutes of meeting, ToR, etc.) 9. User forwards the status of drafted documents in the publishing workflow 10. System sends notification to users related to documents being updated

text: Alternative courses: n/a

text: Post conditions:

text: 1. The draft documents were created 2. The document publication workflows were defined and implemented 3. The documents drafted were associated a workflow and collaboration spaces 4. The folders and documents were granted access and editing permissions for collaboration section 5. System stored the information related to roles and permissions for each folders and documents 6. System sent notifications to users regarding the updating collaboration spaces

text: Exceptions: n/a

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 20: Administration of the drafting section Use Case Diagram

text: 2.2.2.11 UC11 – Prepare a candidate scheme

text: Actors:

text: ADWG_Secretary, ENISA_User

text: Description:

text: The use case describes the interaction between document management platform of the IT System in order to prepare a candidate schema

text: Trigger: The candidate scheme request is approved and actors are logged in the system and want to access the document management platform Type: External

text: Preconditions:

text: Normal course: Information for steps: 1. User accesses the document management section 2. User establishes the document format for candidate scheme 3. User prepares the content for the candidate scheme 4. User defines the workflow for document 5. User implements the workflow associated to the candidate scheme document 6. User sets up the specific permissions for documents drafted for each user group related to preparation of candidate scheme 7. System stores the information related to roles and permissions 8. User puts the draft document for commenting 9. System sends notifications to users related to updates and comments 10. System updates the progress bar

text: Alternative courses: n/a

text: Post conditions:

text: 1. The draft documents for candidate scheme were created 2. The document workflows were implemented 3. The documents drafted have associated workflows and collaboration spaces 4. The folders and documents were assigned permissions for collaboration 5. System stored the information related to roles and permissions for each folder and document

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 6. The notifications were sent 7. The progress bar was updated Exceptions: n/a

text: Figure 21: Prepare a candidate scheme Use Case Diagram

text: 2.2.2.12 UC12 – Review a candidate scheme

text: Actors: ADWG_Secretary, ENISA_User Description: The use case describes the interaction between users and the collaboration platform of the IT System in order to review a candidate scheme Trigger: Actors are logged in the system and want to access the collaboration platform Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the collaboration section of the system Normal course: Information for steps: 1. User accesses the collaboration section of the content management system 2. User selects the specific location and document 3. User reviews the content of the document 4. User inserts comments in specific areas of the document 5. System stores the document together with the comments 6. System sends notifications to users related to the new comments 7. System updates the progress bar Alternative courses: n/a

text: Post conditions: 1. The candidate scheme was reviewed with embedded comments 2. System stored the information related to the comments and their place in the document 3. The notifications were sent 4. The progress bar was updated Exceptions: n/a

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 22: Review a candidate scheme Use Case Diagram

text: 2.2.2.13 UC13 – Access to CMS drafting section

text: Actors: ADWG_Secretary, ECCG_User, ENISA_User Description: The use case describes the interaction between user and content/document management platform of the IT System Trigger: Actors are logged in the system and want to access the content/document management section Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the document management section of the system Normal course: Information for steps: 1. User accesses the document management section 2. User selects the specific location and documents 3. User reviews the folders and documents 4. User establishes the list of documents that will be drafted in document management section 5. User creates and configures a draft for each specific type of document (certification scheme, URWP, revision report, assessment report, peer review document, mutual agreement document, minutes of meeting, ToR, etc.) 6. User defines the workflows for each type of document 7. User implements the workflows associated to each type of document

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 8. User sets up specific permissions for each folder of documents drafted 9. Reviews the document status on its workflow and decides to forward the status 10. System sends notification to users related to updating the collaboration spaces Alternative courses: n/a

text: Post conditions: 1. The access on document management was permitted 2. System stored modifications on folders and documents 3. The collaboration spaces were updated 4. The notifications were sent Exceptions: n/a

text: Figure 231: Access to DMS drafting section Use Case Diagram

text: 2.2.2.14 UC14 – Access to Meeting management

text: Actors: EC_user, SCCG_User, ECCG_User, ADWG_User, ENISA_User Description: The use case describes the interaction between users and the meetings platform of the IT System Trigger: Actors are logged in the system and want to manage the materials for a meeting Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the section. Normal course: Information for steps: 1. User accesses the Meetings section 2. User reviews the meeting schedule 3. User selects meeting creation form to create a new meeting

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 4. User selects the period (dates and times) and location for the meeting 5. User selects the participants for the meeting or allows users to register 6. User includes the agenda of the meeting 7. User uploads other background documents 8. User publishes the meeting on the website, either publicly available or restricted to a group 9. System stores the meeting, (day, time, agenda and participants) 10. After the meeting, user uploads presentations and meeting minutes 11. System sends notification to participant related to meeting Alternative courses: n/a

text: Post conditions: 1. The meeting was created 2. The notifications to participants were sent 3. The meeting and associated information were stored in the system Exceptions: n/a

text: Figure 24: Access to Meeting Management

text: 2.2.2.15 UC15 – Approve requests to prepare a candidate scheme

text: Actors: Mgmt_Board_User

text: Description: The use case describes the interaction between users and the candidate schemes area of the IT System

text: Trigger: After having received a notification from the EC for the preparation of a candidate scheme, actors are logged in the system and want to approve the request to prepare the candidate scheme Type: External

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Preconditions: Actor is logged in the system and has appropriate authorization to access the communication section of the IT System Normal course: Information for steps: 1. User accesses the candidate schemes area 2. User reviews the candidate scheme 3. User evaluates the request 4. User prepares the response 5. User sends the answer to the request with attached status (approved) 6. System stores the request with its associated status, as well as response sent 7. System updates the status of the request Alternative courses: n/a Post conditions: 1. The request was reviewed and has the status ‘approved’ 2. The answer for the request was transmitted 3. The request, associated status and response were stored in the system 4. The status of the request is updated Exceptions: n/a

text: Figure 25: Approve requests to prepare a candidate scheme Use Case Diagram

text: 2.2.2.16 UC16 – Provide voting for draft candidate certification scheme

text: Actors: ADWG_User Description: The use case describes the interaction between users and the collaboration platform of the IT System Trigger: The candidate scheme is finalized and actor is logged in the system and want to access the section for candidate schemes from the website in order to vote the candidate certification scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the platform

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Normal course: Information for steps: 1. User access the schemes’ section 2. User selects the proposed candidate scheme factsheet 3. User reviews the content of the proposed candidate scheme 4. User selects “Vote” button on the selected candidate scheme 5. System stores the vote on the candidate scheme 6. System updates the progress bar Alternative courses: n/a

text: Post conditions: 1. The candidate scheme was voted 2. The new status of scheme was stored in the system 3. The progress bar was updated Exceptions: n/a

text: Figure 26: Provide voting for draft candidate certification scheme Use Case Diagram

text: 2.2.2.17 UC17 – Transmit draft of proposed candidate scheme to EC

text: Actors: ENISA_User Description: The use case describes the interaction between users and the collaboration section of the system, in order to transmit the proposed schemes to EC Trigger: All feedback and voting are integrated in the final version of proposed candidate scheme and actors are logged in the system and want to transmit draft of proposed candidate scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the communication section of the IT System Normal course: Information for steps: 1. User accesses the candidate schemes section 2. User accesses the proposed candidate scheme (UC04)

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 3. User reviews the draft of proposed candidate scheme 4. User accesses the Message Board 5. User selects the type of message 6. User selects the specific recipients 7. User attaches the draft of proposed candidate scheme 8. User pushes ‘transmit candidate scheme’ to the selected recipients 9. System stores the proposed candidate scheme in the document management platform 10. System updates the collaboration platform with the reviewed draft of the proposed candidate scheme 11. System transmits the draft of proposed candidate scheme to the selected recipients (EC_User) 12. System updates the progress bar

text: Alternative courses: n/a

text: Post conditions: 1. The draft of proposed candidate scheme was reviewed 2. The proposed candidate scheme was transmitted 3. System stored the candidate scheme in collaboration platform and document management platform with associated version 4. The progress bar was updated

text: Exceptions: n/a

text: Figure 27: Transmit draft of proposed candidate scheme to EC Use Case Diagram

text: 2.2.2.18 UC18 – Submits an EU statement of conformity

text: Actors:

text: Description:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: The use case describes the interaction between manufacturers/service-providers and the communication section of the system Trigger: Actors are logged in the system and want to submit an EU statement of conformity Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the communication section of the IT System Normal course: Information for steps: 1. User accesses the Message Board 2. User selects type of message 3. User selects the desired EU statement of conformity 4. User uploads the EU statement of conformity 5. User prepares the data associated to the EU statement of conformity 6. User selects the recipients 7. User pushes ‘submit statement of conformity’ 8. System stores the EU statement of conformity into specific location 9. System transmits the notification to the sender that the EU statement of conformity is loaded successfully Alternative courses: n/a

text: Post conditions: 1. The EU statement of conformity was submitted 2. The system was updated 3. The notification of successful submission was transmitted Exceptions: n/a

text: Figure 28: Submits an EU statement of conformity Use Case Diagram

text: 2.2.2.19 UC19 – Provision of feedback for candidate schemes

text: Actors: Complains_User Description:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: The use case describes the interaction between interested parties and the communication section of the system, in order to post feedback on a candidate scheme Trigger: Actors are logged in the system and want to send feedback for a candidate scheme Type: External Preconditions: Actors are logged in the system and want to send feedback for candidate scheme Normal course: Information for steps: 1. User accesses the specific candidate scheme 2. User prepares the feedback 3. User posts a comment on a new or existing thread 4. User associates the feedback to a particular version of the candidate scheme 5. User sends the feedback 6. System stores the feedback together with the specific version of the candidate scheme 7. System transmits the feedback to the relevant group of recipients Alternative courses: n/a

text: Post conditions: 1. The feedback on the candidate scheme was transmitted 2. The feedback on the candidate scheme was stored in the system Exceptions: n/a

text: Figure 29: Provision of feedback Use Case Diagram

text: 2.2.2.20 UC20 – Access to publicly available information on Publication Platform

text: Actors: NO_ROLE Description: The use case describes the interaction between all users and the portal Trigger: Actors want to access available information and publications Type: External Preconditions: n/a

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Normal course: Information for steps: 1. User accesses the portal interface 2. User browses the existing information 3. User searches for types of certificates from the certification scheme 4. User downloads the specific type of certificate 5. User reviews the events Alternative courses: n/a

text: Post conditions: n/a Exceptions: n/a

text: Figure 30: Access to publicly available information on Publication Platform Use Case Diagram

text: 2.2.2.21 UC21 – Access to the collaboration platform

text: Actors: EC_user, SCCG_User, ECCG_User, ADWG_User, Com_Admin, ESO_User, ENISA_User Description: The use case describes the interaction between users and the collaboration platform of the IT System. The voting part of the collaboration platform is described separately, in UC07 and UC16. The inline commenting part of the collaboration platform is described in UC12. Trigger: Actors are logged in the system and want to access the collaboration section from the website Type: External Preconditions:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Actor is logged in the system and has appropriate authorization to access the platform Normal course: Information for steps: 1. User accesses the collaboration part of the content management system 2. User selects a specific document 3. User reviews the existing comments for each version 4. User provides new comments, either by starting a new thread or by continuing an existing one 5. System stores the comments provided 6. System sends notifications to relevant users involved Alternative courses: n/a

text: Post conditions: 1. The feedback on documents was posted on specific versions 2. The updates were stored in the system 3. Notifications on new comments were sent Exceptions: n/a

text: Figure 31: Access to Collaboration Platform Use Case Diagram

text: 2.2.2.22 UC22 – Upload annual report

text: Actors: NCCA_user Description: The use case describes the interaction between users and content management of the IT System Trigger: Actors are logged in the system and want to submit an annual report of issued certificates

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Type: External

text: Preconditions: Actor is logged in the system and has appropriate authorization to access the content management system Normal course: Information for steps: 1. User accesses the relevant section of the content management system 2. User prepares the file and metadata associated to the annual report 3. User uploads the annual report 4. User pushes ‘submit’ for the annual report 5. System stores the report into the specific location 6. System sends upload notifications to the sender and relevant users Alternative courses: n/a

text: Post conditions: 1. The annual report was submitted 2. The system stored the annual report in specific location 3. Notifications of successfully submission were sent Exceptions: n/a

text: Figure 32: Upload annual report Use Case Diagram

text: 2.2.2.23 UC23 – Request revision of schemes

text: Actors: EC_user Description: The use case describes the interaction between users and the communication platform of the IT System Trigger: Actors are logged in the system and want to access the schemes section of the website Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the communication platform

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Normal course: Information for steps: 1. User accesses the Message Board and reviews the message received 2. User selects appropriate type of message 3. User prepares the revision request message 4. User selects the user groups to notify 5. User sends a message to the group members of ENISA 6. The message is stored in the system 7. System updates the progress bar Alternative courses: n/a Post conditions: 1. The revision request was transmitted 2. The request was stored in the system 3. The progress bar was updated Exceptions: n/a

text: Figure 33: Request revision of schemes Use Case Diagram

text: 2.2.2.24 UC24 – Provide feedback for schemes

text: Actors: ECCG_User, Submitter_user, NCCA_user, EC_User, ENISA_User Description: The use case describes the interaction between user and collaboration and communication parts of the IT System Trigger: Actors are logged in the system and want to review and send feedback for candidate scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the collaboration and communication sections of the IT System Normal course: Information for steps: 1. ENISA_User design the system to receive the feedback retaled to implementation of new scheme 2. ENISA_User establish the criteria to assess the effectiveness of scheme

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 3. The actors provide feedback regarding implementation scheme 4. ENISA_User review the information regarding adopted scheme, the report for candidate scheme 5. ENISA_User publish the information regarding adopted scheme, the report for candidate scheme and scheme expiration 6. System stores the feedback 7. Alternative courses: n/a

text: Post conditions: 1. The feedback on the candidate scheme was transmitted 2. The feedback on the candidate scheme was stored in the system 3. The information regarding implementation scheme are published 4. The expiration schemes are published 5. Exceptions: n/a

text: Figure 34: Provide feedback for schemes Use Case Diagram

text: 2.2.2.25 UC25 – Formal Peer Review

text: Actors: EC_User, ECCG_User, NCCA_User, Certs_Statements_Admin, Com_Admin, ENISA_User Description: The use case describes the interaction between users and collaboration and communication sections of the IT System Trigger: Actors are logged in the system and want to review and send feedback for a scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the collaboration and communication sections of the IT System

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Normal course: Information for steps: 1. EC_User accesses the schemes’ section and establishes the period of peer review for a scheme 2. EC_User accesses the Meeting management and creates a new meeting 3. EC_User prepares the meeting agenda and supporting documents and links 4. EC_User selects the member states involved 5. Com_Admin publishes the meeting 6. System sends notifications for the meeting 7. EC_User accesses the Message Board 8. EC_User selects type of message 9. EC_User prepares request for peer review 10. EC_User selects the specific recipients 11. EC_User sends the request to the selected recipients 12. System sends notifications to the selected recipients 13. EC_User accesses the collaboration section 14. EC_User drafts the criteria for peer review

text: 15. System sends notifications to ECCG_User, NCCA_User and ENISA_User regarding selected criteria

text: 16. ECCG_User accesses the collaboration platform and drafts the summary of the review

text: 17. ECCG_User draws issue guidelines and recommendations on actions and measures for the relevant authorities

text: 18. ECCG_User accesses the Message Board

text: 19. ECCG_User selects the type of message

text: 20. ECCG_User sends notifications to ENISA_User regarding the finalisation of the peer review report and recommendations

text: 21. System stores the peer review report, together with the guidelines and recommendations

text: 22. ENISA_User reviews and publishes the peer review report, guidelines and recommendations

text: 23. System sends notifications on the newly published documents

text: Alternative courses: n/a

text: Post conditions: 1. The peer review was performed 2. The peer review report and recommendations were finalized 3. The peer review report and recommendations were stored in the system 4. The peer review report and recommendations were published 5. Notifications were sent to relevant users

text: Exceptions: n/a

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 35: Formal peer review Use Case Diagram

text: 2.2.2.26 UC26 – Prepare reports

text: Actors: ADWG_Secretary Description: The use case describes the interaction between users and reports section of the IT System Trigger: Actors are logged in the system and want to prepare a report Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access reports section of the system Normal course: Information for steps: 1. User accesses the reports section of the website 2. Selects the specific location 3. User chooses a report template 4. System populates the report with data 5. User sets up the specific permissions for accessing report 6. User publishes the report 7. System stores the report in the chosen location Alternative courses: n/a

text: Post conditions: 1. The report was prepared 2. System stored the new report in the chosen location 3. Report was reviewed 4. Report was published

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Exceptions: n/a

text: Figure 36: Prepare reports Use Case Diagram

text: 2.2.2.27 UC27 – Reject request for candidate scheme

text: Actors: Mgmt_Board_User Description: The use case describes the interaction between users and the candidate schemes area of the IT System Trigger: Actors are logged in the system and want to reject the request to prepare a candidate scheme Type: External Preconditions: Actor is logged in the system and has appropriate authorization to access the candidate schemes area of the IT System Normal course: Information for steps: 1. User accesses the candidate schemes area 2. User reviews the candidate scheme 3. User evaluates the request 4. User prepares the response 5. User sends the answer to the request with attached status (rejected) 6. System stores the request with its associated status, as well as response sent 7. System transmits the status of the request and the reasons for rejection Alternative courses: n/a

text: Post conditions: 1. The request was reviewed and has the status ‘rejected’ 2. The answer for the request was transmitted 3. The request, associated status and response were stored in the system

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Exceptions: n/a

text: Figure 37: Reject request for candidate scheme Use Case Diagram

text: 2.2.2.28 UC28 – Search

text: Actors: NO_ROLE Description: The use case describes the interaction between users and the portal’s search section Trigger: Actors want to access available information and publications using search option Type: External Preconditions: n/a Normal course: 1. User accesses the portal interface 2. User selects the search bar 3. User inserts keyword to find specific information 4. The system displays relevant information 5. User selects the specific information from the list displayed Alternative courses: n/a Post conditions: 1. User retrieved the necessary data or information Exceptions: n/a

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 38: Access to publicly available information on Publication Platform Use Case Diagram (Search)

text: 2.2.2.29 UC29 – User Login

text: Actors: All users Description: Users will be prompted to login with their credentials account information before they can use the system. Trigger: User requests to login Type: External Preconditions: 1. The user has an account 2. User is not logged in 3. The user is trying to log in Normal course: Information for steps: 1. The System directs the user to the EU Login (ECAS) page 2. User follows the instructions and logs in 3. User is redirected to the System as authenticated user 4. The user gains access to the system’s functionalities 5. System registers the new access Alternative courses: If the User entered an invalid username and/or password, the following occurs: 1. EU Login interface describes the reasons why the User failed authentication 2. EU Login interface presents the User with suggestions for changes necessary to allow the User to pass authentication 3. EU Login interface prompts the User to reenter the valid information.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 4. The Basic Flow continues where the User enters new information Post conditions: 1. The user was logged in to the system 2. The user had access to the appropriate functions of the system Exceptions: Incorrect credentials

text: Figure 39: User Login Use Case Diagram

text: 2.2.2.30 UC30 – User Registration

text: Actors: All users Description: A user of the IT System creates an account Trigger: User requests to login Type: External Preconditions: The user doesn’t have an account Normal course: Information for steps: This use case starts when a system user is not logged in to the system and goes to the login page. 1. The System directs the user to the EU Login (ECAS) page 2. User follows the instructions and creates an account 3. User returns to the System and logs in with the newly created account Alternative courses: n/a

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Post conditions: 1. The user entered successful information and is returned to the home page as a Logged in User 2. User was unable to log in for one or more reasons and is returned to the home page Exceptions: n/a

text: Figure 40: User Register Use Case Diagram

text: 2.2.2.31 UC31 – User Logout

text: Actors: All users Description: The user clicks on “Logout” and their session is terminated. Trigger: User is done using the website Type: External Preconditions: 1. User is logged in 2. User no longer wants to be logged in Normal course: Information for steps: 1. User is done using the web application 2. User clicks on the ‘logout’ button 3. The system logs the user out and invalidates the cookie/session 4. The system redirects to the default logout page Alternative courses: n/a Post conditions: 1. The user was logged out

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Exceptions: n/a

text: Figure 412: User Logout Use Case Diagram

text: 2.2.2.32 UC32 – Interactions between EC and third counties for mutual agreements

text: Actors:

text: EC_user, ECCG_User, ENISA_User, NCCA_User

text: Description:

text: ENISA will facilitate interactions between EC and countries outside the EU for mutual recognition.

text: Trigger: EC start the mutual recognition and ENISA receives a request from EC to facilitate interaction between selected third counties

text: Type: External

text: Preconditions:

text: 1. EC start the mutual recognition and select the third countries

text: Normal course: Information for steps: 1. EC_User request to ENISA_User and ECCG_User to provide advice to mutual recognition 2. EC_User access the candidate certification scheme and prepare the draft for mutual recognition 3. ENISA_User and ECCG_User provide advice draft for mutual agreements 4. NCCA_User access the mutual recognition document and provide agreements 5. EC_user review and finalised the mutual recognition document 6. EC_User transmit the request to ENISA to update the candidate certification scheme 7. ENISA_User includes the mutual recognition agreements in candidate certification scheme 8. ENISA_User publish the updated candidate certification scheme 9. System store the mutual recognition agreements

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 10. System store the updated candidate certification scheme Alternative courses: n/a Post conditions: 1. The mutual recognition agreements is finalised 2. The candidate certification scheme is updated 3. The updated candidate certification scheme is published Exceptions: n/a

text: Figure 42: Mutual Recognition Agreements Use Case Diagram

text: 2.3 STAKEHOLDERS MAP

text: In the figure below we present the entities, roles assigned for each entity in the IT System and use cases associated to each role.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 43: Stakeholders Map

text: ENISA IT SYSTEM FOR CERTIFICATION 2.4 FUNCTIONAL REQUIREMENTS

text: The major requirements for the IT System in support for the EU Cybersecurity Certification Framework are:

text:  Website and content management system for presentation of data and information  Storage and workflow for requested candidate cybersecurity certification schemes from the EC and the ECCG  Storage and workflow for requests to update current schemes  Support for the design and development of candidate cybersecurity certification schemes  Communications and collaboration features to support the feedback loop (consultation process) with ECCG and other stakeholders  Management of the content for the preparation and transmission of candidate schemes to EC  Mechanism to receive feedback from EC and national authorities for the adopted cybersecurity certification schemes  Mechanism to receive standards to be considered for the design of schemes  Mechanism to receive information from manufacturers on conformity statements  Notification mechanism and support for peer review processes  Receipt, cataloguing and storage of self-asserted conformity claims and the resultant "EU statement of conformity"  Ontology with (hierarchical) lists of terms for all data and content types  Communication platform to engage ENISA with the EU-SDOs (CEN, CENELEC, ETSI).  Support for the post-adoption lifecycle of the schemes (request feedback, participate in peer review of cybersecurity authorities etc.)  Reporting functionalities (statistics and ad-hoc reports)  Support for the automated identification of similarities between schemes and contributions of the various stakeholders of the promulgation of a scheme. (based on the concept of antiplagiarism software or service)  Search and filtering for all data and information published in the website  Ensure the alignment to storage management standards provided by AHWG, ECCG and ENISA  Management of users, roles and permissions: o Authentication of EU Login users and retrieval of user details (full name, id, email address) o Support the creation, maintenance and deleting of user groups for the types of roles identified in this document (EC_User, Roles_Admin, CSS_Admin, Certs_Statements_Admin, Com_Admin, DraftSection_Admin, ADWG_Secretary, ENISA_User, Mgmt_Board_User, ECCG_User, SCCG_User, Submitter_User, Complains_User, ESO_User, ADWG_User, NCCA_user) o Administration of user groups, which will translate into portal roles, as well as assignment of permissions to them

text: The portal will make available the following information:  EU cybersecurity certification schemes and feedback received in the consultation process, as well as those that are candidate schemes, those that are under revision and those that ENISA rejected to design  Certificates, EU statements of conformity issued under the Cybersecurity Act, along with relevant documentation  Componence of the Conformity Assessment Bodies

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Repository of links to cybersecurity information provided online by manufacturers and providers  Message board (discussion forum), with threaded discussion topics for groups and subgroups  Task list for each user and user group  Inbox for specialised communication in the different collaboration processes  Meeting management  Componence of the Ad-hoc Expert Groups  Calls for construction of calls for construction of Ad-hoc Expert Groups  Various other information published in a hierarchical structure

text: 2.4.1 Authentication and authorization

text: As multiple stakeholders with diverse roles and activities are involved throughout the lifecycle of a cybersecurity certification scheme, the system will enable ENISA to authenticate, register and manage permissions for different users.

text: All users involved in these processes either have accounts in the European Commission’s CAS repository (EU Login , formerly known as ECAS) or can request login credentials, therefore it is suggested to use this service to authenticate users. While the EU Login will maintain the users’ information (credentials and passwords), the upcoming portal will store the list of available roles and the mapping of roles per user.

text: The permissions to execute different operations (e.g. add a document, comment on drafts, review a schema) should be granular enough to allow tailoring roles for each of the foreseen stakeholders.

text: 2.5 DOCUMENT AND CONTENT MANAGEMENT

text: One of ENISA’s key roles is the preparation of the candidate cybersecurity certification scheme, with the assistance of an ad-hoc working group and the ECCG for each candidate scheme. Therefore, a document lifecycle management functionality is essential to coordinate the design of the candidate scheme. Also, the Document Management platform will maintain all documents related to the secretariat for SCCG, ECCG and AHWG.

text: The document management platform will have to:

text:  Retain information about EU cybersecurity certification candidate schemes  Retain information about EU cybersecurity certificates  Retain information about EU statements of conformity  Allow publishing of various other documents/reports, either public or private

text: The structure of the documents published in the portal is essential to fit multiple needs, exceeding the traditional metadata and uploaded file capabilities, for which it is more accurate to refer to a document and content management system. It will offer typical document control functionalities:

text:  Versioning capabilities  Notifications on changes to subscribed users  Customisable publishing workflows, to be tailored by portal administrators (drafting, revision, approval, etc.)  Comments on versions, with the possibility to turn the comments ‘on’ or ‘off’’ on individual documents

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Ability to compare content in files, to ensure transparency in the creation of schemes and consensus  Append-only log of user activities which ensures a transparent traceability of user actions

text: The portal’s user interface, accessible from an ENISA sub-domain (for example certification.enisa.europa.eu) will display content according to the rights of the logged in user. Documents and other content (documentation, certificates, statements of conformity, etc.) will be organised in folder-like sections, either public or restricted to different classes of users. Individual and bulk download capabilities will be available to the users with ‘view’ access to the documents.

text: The contents’ metadata should be based on the Dublin Core set, enriched with properties relevant for this context.

text: 2.5.1 Libraries (data store)

text: To ensure a systematic approach, the system will include different structured data about:

text:  schemes (candidate, revision, approved, rejected)  national schemes  requests from ECCG and EC  feedback from third parties  ESOs and SDOs standards  self-conformity certificates  Conformity Assessment Bodies and their users  various groups of persons, relevant to the system’s processes

text: Such data will be stored in databases and maintained through the system, in a transparent way to users who visualise or administer the data. The interface for filling in data, managing or displaying it should be consistent throughout the entire system. Where applicable, the data should be linked by relations, ensuring data integrity and consistency.

text: Similar to the way the documents are stored and maintained, the data repositories will implement the following capabilities and functionalities:

text:  Versioning  Notifications on changes to subscribed users or relevant user groups  Publishing workflow (customisable, where relevant)  Allow comments, feedback or other input from the stakeholders  Append-only log of user activities which ensures a transparent traceability of user actions  Ability to compare content in files to ensure transparency and consensus

text: The metadata should also be consistent with the metadata set of the documents.

text: 2.5.2 Reporting, data mining and auditing

text: Cybersecurity certification schemes have different levels of conformity and expiry dates. Additionally, ENISA is responsible to gather feedback for the implemented schemes and revise those deemed out of date. The system will include auditing and mining capabilities for defined processes.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Based on the existing data and content, several reports will be built to explore data in meaningful ways, to allow searching and filtering or to prepare statistical reports. The reports will be dynamic pages, which bring together data and content from different areas. For instance, it would be relevant to have a filterable list of the certificates, which are about to expire, grouped by countries and other parameters.

text: The use of data mining is intended to ensure and demonstrate consensus in the design of schemes amongst AHWG and ECCG. A third-party component, built for antiplagiarism, should be used to find similarities between the texts of existing schemes and certificates and signal potential overlaps.

text: The auditing components will be available to all logical levels of the system and should focus on:

text:  Access and authentication: proper approval and authorization of all data and documents o Appropriate logins and passwords to restrict access o Lock records/documents for editing after approval o Retain the “envelope” for electronically signed documents o Don’t put faith in email – email approval is weak audit evidence  Document management: availability and access to complete and accurate records o Make sure records/documents are searchable and retrievable o Consistent data/document retention period, so these are available upon request during an audit o Establish a solid form of version control  Security and integrity of documents: protection of documents from accidental modification or deletion o Reliable active directory management that includes mobile devices o Limit access through use of logins and passwords o Two-factor authentication o Perform regular and timely backups o Perform periodic restore or other tests to ensure document integrity  Retention and destruction o Have a disaster recovery plan in place o Destroy records/documents in an orderly and timely manner, and in accordance with the established policy

text: 2.5.3 Communicating over a platform

text: Ensuring that interactions amongst all stakeholders are timely and efficient is crucial, given the various stages in the lifecycle of the scheme that information needs to be communicated and that key players require to collaborate and synchronise their activities. A platform that will facilitate communications amongst all key stakeholders is a key building block of the system. The communication platform will facilitate all communications or information exchange between the different stakeholders mentioned in the CSA. Communication functionalities are destined for authenticated users and include:

text:  Message board (discussion forum), with threaded discussion topics for groups and subgroups, allowing moderation o Task list for each user and user group o Inbox for specialised communication in the processes for adoption and review of certification schemes  Automatic email notifications to users or groups

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Meeting management tool, with agenda, minutes, presentations and links to relevant documents; this tool will also allow the management of participants and printing of the participants list  Possibility to subscribe to receive email updates on new or updated content

text: The management of the groups and subgroups needs to be done in relation with the user roles, each group having being associated a role. Permissions for viewing or executing various functionalities should be granted for roles, instead of per individual users.

text: 2.5.4 Collaboration on documents

text: In almost all processes the communication is essential to provide and receive feedback and advice from different stakeholders. The collaboration functionalities will be used in creating and publishing the URWP with the assistance of the SCCG and the ECCG, as well as in the preparation of the candidate cybersecurity certification scheme with the assistance of an ad-hoc working group and the ECCG for each candidate scheme. In the process of creating and supporting the SCCG and the AHWG, the communication functionalities are a priority.

text: The collaboration platform is used for preparing the EU candidate cybersecurity certification schemes. In the backend, a CMS will support the web server connected to a database, document management system, message board, collaborative work environment and ticketing system. During the preparation of these candidate schemes the Communication Platform is used within the Ad hoc Working Group, the ECCG and the SCCG for communication. Any work progress and other outcome of the Ad hoc Working Group is stored in the Document Management System.

text: The collaboration functionalities consider authenticated users and include:

text:  Threaded comments on uploaded documents  Possibility of weighted voting (user definition will contain number of votes per user group, e.g. ‘ECCG France = 5’  Online commenting on data (e.g. schemes or certificates of conformity), with threaded comments posted on various parts of the data structures

text: 2.5.5 Functional public website (CERMIT Portal)

text: ENISA is required to publish information on a website regarding the candidate schemes, the implemented schemes and the self-conformed manufacturers. In order to ensure that the website will contain up-to-date accurate information it is important to have a back-end system collecting the required information from various stakeholders, as well as a user-friendly frontend software.

text: The website’s functionalities should be accessible on all targeted devices (regular monitors, tablets, mobile phones). By ‘targeted devices’ we mean that simpler, more commonly used interfaces should be available on all devices, while some administrative features of complex editing should be accessible on larger devices, where the possibility of errors due to lower visibility is eliminated.

text: For authenticated and anonymous users, the portal interface should also follow the concept ‘what you see is what you can do’, entailing that users will not see functionality they are not allowed to execute.

text: The IT System website will make publicly available and accessible information related to candidate and adopted schemes, certificates and statements. The IT System will have to make available to a public website:

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  EU cybersecurity certification schemes  Requests for candidate cybersecurity certification schemes  Feedback received in the consultation processes, to the extent the feedback is relevant and does not have a restricted nature  Certificates and EU statements of conformity issued under the cybersecurity Act  Withdrawn items and expiration dates  Repository of links to cybersecurity information provided online by manufacturers and providers  Information received from ICT manufacturers and national certification authorities  National certification schemes replaced by European certification schemes  Information received from national certification authorities  Other relevant information (events, news, contact information, etc.) and the necessary search and filtering functions  Access to the restricted areas for collaboration and communication

text: On a technical level, this architecture will be sustained by a content management system. It will encapsulate the authentication and authorization, document management, built-in or custombuilt collaboration tools, as well as the integration with external databases for the storage and management of relational data.

text: 2.6 NON-FUNCTIONAL REQUIREMENTS 2.6.1 Availability

text: It is required that the IT System is accessible to anonymous visitors 24 hours a day, 7 days a week, 365 days a year excluding scheduled maintenance or pre‐agreed outage periods. The system performance availability standard will be a minimum of 99.95% (the “Availability Standard”). All services, supporting infrastructure and software code must be robust, resilient, stable, and established and maintained in accordance with the modern industry practices and standards for website development and maintenance.

text: The system shall be prepared to handle around 200 users connected at the same time.

text: 2.6.2 Usability and accesibility

text: The user interface must be simple and comprehensible. Users will not be required to read long manuals for navigation, accessing the different types of information or functionalities. Contextual help should be provided when relevant.

text: The interface of the IT System will be easily accessible, modern, responsive, user‐friendly, informative, well organised, visually attractive, up‐to‐date and reliable, taking into account modern European standards for usability and accessibility. The standards set out by the W3C Web Accessibility Initiative should be followed, together with the WAI-ARIA specification for accessible rich internet applications and best-practices.

text: The search must return relevant results, guiding users in retrieving content relevant for them. When searching, appropriate filters should be selectable, while typing search terms should be autocompleted using the portal’s ontology (lists of terms).

text: The pages should generally load under 3 seconds, with slower to retrieve content (e.g. rendered statistics) being showed progressively, after the rest of the page has loaded swiftly.

text: 2.6.3 Reliability ENISA IT SYSTEM FOR CERTIFICATION

text: The system must work reliably enough so that no data loss can occur in cases of system failure and the disruptions in the service can be rapidly spotted, traced and repaired. This also includes business recovery and disaster recovery scenarios.

text: 2.6.4 Performance

text: The performance of the IT System is not critical, but should have minimal user-feedback delays. In particular, the time it takes to load and refresh database items has the potential to interrupt operator workflow. This should be mitigated by the use of expandable products and item categories.

text: The IT System shall have an uptime of more than 99% of the announced 24/7 availability, measured over any 30 days period.

text: 2.6.5 Security

text: User authentication must be required in order to prevent any malicious or unintended manipulation of the configurable products. All activities which assign credentials to users and define workflows are logged separately for security monitoring activities.

text: The IT System will use secure protocols to ensure that the client - server communication is protected against third party intrusions.

text: Each form that allows data entry by users must contain security checks to ensure the integrity of submitted data and to avoid any kind of injection of potentially malicious bits of code that might affect the data or the overall system integrity.

text: The system should ensure that all activities will be monitories and will be compliant with ENISA’s policies and procedures (privacy statements, security policies etc).

text: 2.6.6 Maintainability

text: The system must be easy to maintain and update after the project team delivers it. Appropriate documentation must be provided, to ensure that ENISA staff is aware how to use and maintain its components. Potential future developers must be able to continue the work without the need to contact the initial development team. The code, products, deployment and monitoring procedures must be documented on a level that permits the system to function and to be subsequently updated.

text: 2.6.7 Scalability

text: The IT System will have a relatively constant number of users over the course of time, so the system will not need to handle significant growth in the foreseeable future. The IT System should be able to handle a constantly growing data storage.

text: 2.6.8 Brand integrity and enhancement

text: The provider will ensure that all development work respects and consistently reflects the current ENISA Brand Guidelines.

text: 2.7 ASSUMPTIONS AND CONSTRAINTS

text: The following assumptions and constraints were identified from the system’s perspective:

text:  The IT System will be developed on top of a security-sound platform, known on the market as being reliable, with a high-quality code base, having an active community of contributors or a reliable organisation to sustain its future development, being well documented and allowing the development of extensions and plugins;  The chosen framework should have or allow the development of components to cover all functionalities described above;

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  The IT System will follow the EU standards on website accessibility, design, programming languages, as well as security principles;  The IT System will verify the user identity from an external user management system (EU Login, formally known as ECAS);  The IT System will provide interoperability functionalities for future integration with other systems;  The databases used will need to ensure data integrity checks and the ability to relate stored data;  The IT Systems should be implemented in phases: the most critical functionalities will be implemented first, in order to sustain the urgent business processes, while less urgent functionalities could be delivered in subsequent iterations;  The IT System will be hosted on ENISA infrastructure and system administration will be done following the same standards with the rest of the ENISA websites;  The system will have complete documentation on all deliverables, potential training to the relevant users, as well as knowledge transfer to relevant ENISA staff;  The project management will be done following a standard Agile methodology.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: 3. TECHNICAL REQUIREMENTS

text: 3.1 SYSTEM ARCHITECTURE 3.1.1 Generic considerations

text: The IT System must be developed on top of a security-sound platform, established in the market as being reliable, with a high-quality code base. The platform should have an active community of contributors or a reliable organisation to sustain its future development, must be well documented and should allow the design and implementation of extensions and plugins.

text: The chosen framework should already possess or allow the development of components to cover all functionalities described Section 2. The IT System will follow the EU standards on website accessibility, design, programming languages, as well as security principles, as laid out in the IPG Rules .

text: The IT System will verify the user identity from an external user management system (preferably EU Login, formally known as ECAS). Also, it must provide interoperability functionalities for current and future integration with other systems, following common standards (e.g. GET/POST calls or Restful APIs).

text: The databases used will need to ensure data integrity checks and the ability to relate stored data.

text: The system will need to have complete documentation on all deliverables, potential training to the relevant users, as well as knowledge transfer of system administration and maintenance activities to relevant ENISA staff. Reuse of the existing ENISA frameworks is not mandatory, but would constitute an advantage, as it would reduce the administration burden for ENISA in the long term.

text: 3.1.2 System overview

text:  Website and content management system for presentation of data and information  Storage and workflow for requested candidate cybersecurity certification schemes from the EC and the ECCG  Storage and workflow for requests to update current schemes  Support for the design and development of candidate cybersecurity certification schemes  Communications and collaboration features to support the feedback loop (consultation process) with ECCG and other stakeholders (i.e, Ad-hoc Working Group)  Management of the content for the preparation and transmission of candidate schemes to EC  Mechanism to receive feedback from EC and national authorities for the adopted cybersecurity certification schemes

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Mechanism to receive standards to be considered for the design of schemes  Mechanism to receive information from manufacturers on conformity statements  Notification mechanism and support for peer review processes  Notification mechanism and support for mutual agreement processes (optional)  Receipt, cataloguing and storage of self-asserted conformity claims and the resultant "EU statement of conformity"  Ontology with (hierarchical) lists of terms for all data and content types  Communication platform to engage ENISA with the EU-SDOs (CEN, CENELEC, ETSI).  Support for the post-adoption lifecycle of the schemes (request feedback, participate in peer review of cybersecurity authorities etc.)  Reporting functionalities (statistics and ad-hoc reports)  Support for the automated identification of similarities between schemes and contributions of the various stakeholders of the promulgation of a scheme. (based on the concept of antiplagiarism software or service)  Search and filtering for all data and information published in the website  Ensure the alignment to storage management standards provided by AHWG, ECCG and ENISA  Management of users, roles and permissions: o Authentication of EU Login users and retrieval of user details (full name, id, email address) o Support the creation and maintenance of user groups for the types of roles identified o Administration of user groups, which will translate into portal roles, as well as assignment of permissions to them

text: The system described here will need to operate in real time and to cater for an estimated 200 maximal concurrent users. This figure might increase in time, due to legislative changes or peaks in the number of requests by EC and the ECCG. The accessibility to anonymous or authenticated visitors will need to be 24 hours a day, 7 days a week, 365 days a year, excluding scheduled maintenance or pre‐agreed outage periods. The system performance availability standard will be a minimum of 99.95%. All services, supporting infrastructure and software engineering must be robust, resilient, stable, and established and maintained in accordance with the modern industry practices and standards for website development and maintenance.

text: It is likely that the system will evolve in time in terms of data structures, functionalities and interoperability with external services. Therefore, it has to be scalable and easily maintainable in the future. The development team should foresee the ability to scale both in terms of additional server power, as well in terms of component instances (CMS, database, other frameworks or services). While building the user interfaces, the target users of the application should be taken under consideration:  EU institutions  Members of ECCG and SCCG  National governments and authorities  Manufacturers and providers of ICT products, ICT processes and ICT services  Beneficiaries of ICT products, ICT processes and ICT services  Global and international agencies and organisations  Wider public and media

text: The quality of the projects’ code needs to be tested and measured using dedicated tools such as CodeClimate, Codacy, or similar. Testing of the newly developed code should be conducted at different levels:

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Unit testing, at least for highly used and critical parts  Functional testing, for the critical and most frequently used functionalities  Integration & system testing, when it comes to the interoperability between platforms or integration of third-party components  Usability and accessibility testing for the user interface  Performance testing  Security testing

text: 3.1.3 System architecture

text: The IT System should rely on a modern content management system for the presentation, document management, collaboration, communication and integration with database structures – used in the storage and management of cybersecurity schemes, certificates, statements of conformity and other resources relevant to these processes.

text: Modern content management systems (CMSs) have built-in, strong document management capabilities and pluggable products for various communication and collaboration features. They also allow complex management of the system, layout, content, distinction of users, and allocation of roles and permissions. When certain functionalities are not available, developers either extend existing open source products for that CMS, or they build new ones from scratch. Therefore, it is expected that the upcoming system will be built on top of a CMS.

text: From a technical point of view, the overall requirements for this IT system are depicted in the figure below.

text: Figure 44: Required features of the IT System, organised by technology

text: An important aspect of the system is that most of the functionalities must be designed and implemented for restricted access to a complex set of roles. Therefore, proper tests should be designed to ensure that the restricted content cannot be accessed by users without the

text: ENISA IT SYSTEM FOR CERTIFICATION

text: necessary set of roles, and that privileged operations cannot be executed by unauthorised users.

text: The architecture proposed will have to provide the flexibility to support ever-changing business (often legislatively driven) requirements. Its key feature should be that it separates out business logic, client access technology and centrally-held data into discrete layers with standard, open interfaces. It must be possible for the data to be exported in common formats, in order to integrate it in future versions of the frameworks used, or just reuse this data for other purposes (e.g. building reports).

text: More details about the different system components can be found in the next section.

text: 3.1.4 Technology

text: ENISA currently uses Plone 4.x and 5.x for building most of its dynamic websites. To streamline future administration of the ENISA websites, it would make sense to have this IT system built on top of Plone 5. The more structured data can be stored in an external, relational database, such as MariaDB or Postgres, or in Json-based structures in Plone’s ZODB. This choice can be assessed at the time of detailed analysis of the development.

text: Plone 5 complies with the overall system requirements and allows building Python products for Plone for the implementation of the less standard structures and logic, such as handling the workflows of cybersecurity schemes.

text: 3.1.5 Infrastructure services

text: 3.1.5.1 Deployment

text: The deployment of the system could be made either on the existing ENISA infrastructure or on other platforms.

text: Aside from the production environment, a similar setup should be made for the development and acceptance server, where new versions of the application will be showcased and tested by the stakeholders, before going live. The project should adopt an iterative and agile approach and implement a continuous improvement process, making use of automated testing tools integrated in the development flow (continuous integration suite).

text: Continuous integration tools should be used for the automated testing of the backend (e.g. Travis, Jenkins), as well as for running the tests for the user interface (e.g. Selenium / PhantomJS).

text: The source code of the ENISA products could reside on private Gitlab repositories. Gitlab should therefore be used as support for release management, each release being accompanied by a change log and full traceability of the features developed.

text: 3.1.5.2 Availability

text: The availability of the website and all its internal services will be measured on monthly basis, excluding maintenance periods agreed with ENISA. The requirements are:

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Code performance should also be taken into account in the implementation phase of each project development. At least 95% of the pages should have a loading time less than or equal to to 7 sec/per page.

text: 3.1.5.3 Data handling, backup and restore

text: The application must allow that all data stored by the system are properly backed up.

text: Data portability must be ensured, meaning that the application shall provide capabilities to export the data, so it can still be used by the customer, e.g. in the event of terminating the contract with the developer or host of the service.

text: All appropriate steps must be taken in order to ensure that data protection principles have been implemented. This can be done by choosing a secure framework for implementing the application, by implementing a secure deployment configuration and by implementing the necessary automated tests to ensure data access can be done only for properly authenticated users. Appropriate security policies should be put in place – handling of Intellectual Property, handling of classified documents, encryption of databases, encryption of data at transit and rest, etc.

text: The platform should provide reliable monitoring and logging mechanisms, in order to investigate data breaches and security incidents.

text: 3.1.5.4 Logging

text: Regular log collection needs to be done for reviewing the user access into the application and for security reasons. In case of security incidents, systematically collected logs enrich the understanding of the nature of the incidents during their lifespan and afterwards, during the investigation.

text: Related to this application, the log events should at minimum include:

text: 1. Application account information a. successful and failed application authentication attempts b. failed attempts to use restricted pages c. application account changes (e.g. roles being assigned to accounts) 2. Application operations a. application start-up and shutdown b. application failures c. major application configuration changes d. URLs requested and the type of response provided by the server e. application relevant transactions, for example: i. email messages recording the sender, recipients, subject name, and attachment names ii. requests from EC/ECCG being registered in the system

text: ENISA IT SYSTEM FOR CERTIFICATION

text: iii. changes in the publication workflow of documents

text: The details logged for each event may vary, but at minimum each event should capture:

text:  timestamp  event, status, and/or error codes  short and long descriptions of the event, as relevant to traceback potential issues  user or system account associated with an event  (when the information is available) device used (e.g. IPs, terminal session ID, web browser, etc.)

text: The conventional process to logs is that all actions relevant for the application need to be traceable by properly authenticated users. This method is called ‘append-only logs’, meaning that it should not be possible for users to tamper with the logs and delete certain interactions, without a trace that certain actions have been reverted.

text: 3.2 DETAILED DESIGN 3.2.1 Content management system

text: The content management system will be the main access point to all system functionalities. End users should feel as they are interacting with a single platform, in a coherent sequence across devices and should remain agnostic to the different technologies used to build the entire IT System.

text: The chosen framework must support the ability to build content types with custom metadata, to revise existing content types and to create new ones along the way. The list of content types to be made available should be, at a minimum, the following:

text:  Links to internal and external pages  Regular pages with static content  Files (documents) of any type  Folders  Videos and images  Events  Meetings

text: The structure of the documents published in the portal is essential to fit multiple needs, exceeding the traditional metadata and simple file-upload capabilities. The CMS will offer typical document control functionalities:

text:  Online editing, with validation rules for fields  Versioning capabilities  Notifications on changes to subscribed users  Customisable publishing workflows, to be tailored by portal administrators (drafting, revision, approval, etc.)  Preview of the information before publishing  Comments on versions, with the possibility to turn the comments ‘on’ or ‘off’’ on individual documents  Moving of documents in folders  Minimalistic undo capabilities (e.g. at a minimum the undo of the last operation for a limited period of time)

text: ENISA IT SYSTEM FOR CERTIFICATION

text: The portal’s user interface, accessible from an ENISA sub-domain (for example certification.enisa.europa.eu) will display content according to the rights of the logged user. The portal should be implemented with best practice security features and hold a Qualified Website Authentication Certificate (QWAC). Documents and other content (documentation, certificates, statements of conformity, etc.) will be organised in folder-like sections, either public or restricted to different classes of users. Individual and bulk download capabilities will be available to the users with ‘view’ access to the documents.

text: The CMS will have to accommodate publishing the required information in a hierarchical structure, but also integrate pages that expose other data, possibly stored in databases:

text:  Requests for candidate cybersecurity certification schemes  EU cybersecurity certification schemes and feedback received in the consultation processes, as well as those that are candidate schemes, those that are under revision and those that ENISA rejected to design  Information on the national certification schemes  Certificates, EU statements of conformity issued under the Cybersecurity Act, along with relevant documentation  Self-conformity certificates  List the Conformity Assessment Bodies  Repository of links to cybersecurity information provided online by manufacturers and providers  Discussion forum, with threaded discussion topics for groups and subgroups  Message board - inbox for specialised communication in the different collaboration processes  Meeting management  Composition of the ad-hoc Expert Groups  Calls for expression of interest for the ad-hoc Expert Groups

text: In addition to publishing the raw data, several dynamic pages need to be built for the custom display of the data and information, searches on different subsets of data, as well of predefined reports based on customisable templates. It must be possible for authorized users to select page types and templates from a list when they are creating pages.

text: 3.2.2 Cybersecurity certification schemes

text: European Cybersecurity Certification Schemes (CSS) will be implemented with a complex structure, which makes it suitable for being stored and maintained in a database environment.

text: The following functionalities should be made available for this object type:

text:  Add form, with multiple steps and the possibility to have interim saved versions  Edit form, with multiple steps and the possibility to have interim saved versions, which blocks the editing for other users  View page, listing all fields in an intuitive manner and linking to related objects (see list below)

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Publishing workflow (draft, in review, in comments from stakeholders, voting, transmitted to EC, approved, in revision)  Consultation, which allows posting comments on specific fields by the ADWG and ENISA. This functionality is part of the collaboration platform  Search and filtering of schemes, which will include national schemes as well, further detailed under the sub-section “Reports” below

text: Schemes can be in one of the following states:

text: 1. Candidate – following the request from EC or ECCG, ENISA creates a candidate scheme for review and comments 2. Adopted – following ENISA’s transmission of a final candidate scheme to EC, the scheme is approved with an implementation act 3. Rejected – following a request outside the Union Rolling Working Programme from EC or ECCG, ENISA’s management board rejects the request 4. In assessment – EC and ENISA regularly assess the efficiency and use of the adopted scheme and whenever European CSS 5. Withdrawn – expired or replaced scheme

text: The processes that govern the lifecycle of certification schemes are described in Section 2 and further summarised in the figure below.

text: Figure 45: Default workflow for EU cybersecurity schemes, from request to adoption.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: The properties of European cybersecurity certification schemes known at this time are listed in the table below, but others may become necessary upon a more in-depth analysis at implementation time:

text: Title String, text only yes abstract String, text only yes The subject matter and scope of the certification scheme types_covered Multiple selection yes The type or categories of ICT from list products, ICT services and ICT processes covered description String, HTML yes Description of the purpose of the elements allowed scheme and description of how the selected standards, evaluation methods and assurance levels correspond to the needs of the intended users of the scheme references Complex property, yes References to the international, list of (type, link, European or national standards title, organisation) applied in the evaluation or, where such standards are not available or appropriate, to technical specifications that meet the requirements set out in Annex II to

text: Regulation (EU) No 1025/2012

text: or, if such specifications are not available, to technical specifications or other cybersecurity requirements defined in the European cybersecurity certification scheme assurance_levels Multiple selection no Values: ‘basic’, ‘substantial’, ‘high’ from predefined list conformity_self_assessment_allowed boolean yes An indication of whether conformity self-assessment is permitted under the scheme cab_specific_requirements String, HTML no Where applicable, specific or elements allowed additional requirements to which conformity assessment bodies are subject in order to guarantee their technical competence to evaluate the cybersecurity requirements evaluation_criteria_methods Complex property, yes The specific evaluation criteria and list of (criteria, methods to be used, including types of method, evaluation, in order to demonstrate evaluatin_type) that the security objectives referred to in

text: Article 51

text: are achieved necessary_information String, HTML no Where applicable, the information elements allowed which is necessary for certification and which is to be supplied or otherwise be made available to the conformity assessment bodies by an applicant conditions_marks_labels String, HTML no Where the scheme provides for marks elements allowed or labels, the conditions under which or such marks or labels may be used List of String fields rules_mechanisms_compliance String, HTML yes Rules for monitoring compliance of elements allowed ICT products, ICT services and ICT processes with the requirements of the European cybersecurity certificates or the EU statements of conformity, including mechanisms to demonstrate continued compliance

text: ENISA IT SYSTEM FOR CERTIFICATION

text: with the specified cybersecurity requirements conditions_upkeep String, HTML no Where applicable, the conditions for elements allowed issuing, maintaining, continuing and or renewing the European cybersecurity List of String fields certificates, as well as the conditions for extending or reducing the scope of certification additional_rules_consequential String, HTML yes Rules concerning the consequences elements allowed for ICT products, ICT services and or ICT processes that have been List of String fields certified or for which an EU statement of conformity has been issued, but which do not comply with the requirements of the scheme rules_upcoming_vulnerabilities String, HTML yes Rules concerning how previously elements allowed undetected cybersecurity or vulnerabilities in ICT products, ICT List of String fields services and ICT processes are to be reported and dealt with rules_rentention_by_cabs String, HTML no Where applicable, rules concerning elements allowed the retention of records by conformity or assessment bodies List of String fields related_schemes Complex property, no The identification of national or list of (scheme, international cybersecurity certification type, schemes covering the same type or categories_covered) categories of ICT products, ICT services and ICT processes, security requirements, evaluation criteria and methods, and assurance levels content_format_certificate File (content, title, yes The content and the format of the size, content-type) European cybersecurity certificates to or be issued String, HTML elements allowed content_format_statement_conformity File (content, title, yes The content and the format of the EU size, content-type) statements of conformity to be issued or String, HTML elements allowed adoption_date Date no The date the scheme was adopted by the EC expiration_date Date no The date the scheme is due to expire period Number, in months yes The period of the availability of the EU statement of conformity, technical documentation, and all other relevant information to be made available by the manufacturer or provider of ICT products, ICT services or ICT processes maximum_validity_certificates Number, in months yes Maximum period of validity of European cybersecurity certificates issued under the scheme discosure_policy String, HTML yes Disclosure policy for European elements allowed cybersecurity certificates issued, or amended or withdrawn under the List of String fields scheme conditions_mutual_recognition String, HTML no Conditions for the mutual recognition elements allowed of certification schemes with third countries rules_peer_assessment String, HTML no Where applicable, rules concerning elements allowed any peer assessment mechanism established by the scheme for the authorities or bodies issuing European

text: ENISA IT SYSTEM FOR CERTIFICATION

text: cybersecurity certificates for assurance level ‘high’ pursuant to

text: Article 56(6)

text: . Such mechanism shall be without prejudice to the peer review provided for in

text: Article 59

text: format_procedures_providers Complex property, yes Format and procedures to be followed list of (format, list of by manufacturers or providers of ICT procedures) products, ICT services or ICT processes in supplying and updating the supplementary cybersecurity information in accordance with

text: Article 55

text: As with other types of objects to be implemented in this system, logs of all actions done on CCSs will be kept in the system in the form of ‘append-only’ logs which will register at a minimum:

text:  User executing the action  Precise date and time  Name of the action  Description of the action (optional)

text: After the definition of the candidate scheme by an ENISA user, a review process by the ECCG and the Ad-hoc Working Group begins, which allows the respective users to add comments on specific fields of the candidate scheme. These comments need to be stored in the system and displayed to authorised users in a manner that makes it easy to go through them and draw conclusions. During this time, authorised ENISA users can edit the scheme and make changes, either by creating a new version of the scheme or just by preserving the existing one.

text: The next optional step is for the users to vote (1-5) on the respective version of the candidate scheme. Final count of the votes will be weighted by country and displayed to reviewers in a report.

text: 3.2.2.1 Related objects

text:  Ad-hoc Working group  Feedback from the ECCG and the Ad-hoc Working Group  Weighted voting on the versions  European cybersecurity certificate  EU statements of conformity  Conformity Assessment Body  Conformity self-assessment certificate  National certification scheme

text: 3.2.2.2 Reports

text:  Search of schemes based on their status (candidate, adopted, rejected, in assessment, withdrawn); unauthenticated users should only be allowed to search for adopted or withdrawn schemes  Display comments and votes for a candidate scheme  Searching and filtering of manufacturers of ICT products or services with certifications on a certain scheme  Conformity self-assessment certificates declared under a certain scheme  National certification schemes replaced by an EU scheme

text: 3.2.3 Request for certification scheme

text: The request for a new candidate cybersecurity certification scheme arrives from the EC or the ECCG and needs to trigger the following processes:

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Setting up an ad-hoc working group o Upload relevant documents:  Publish Term of Requirement (ToR) document  Create a call for the expression of interest (CEI)  Preparation of candidate schemes (described in the previous section)

text: This kind of request will be implemented as a formal message sent by the ECCG or the EC to ENISA via the Message board described in Section 3.10. Since the format for the request is not fixed, it is expected that the description of the upcoming scheme, its rules, technical requirements and other elements will be sent in a document format, as attachment to the message.

text: 3.2.4 European cybersecurity certificates and EU statements of conformity

text: ENISA will be the source for data on all EU candidate cybersecurity certification schemes, European cybersecurity certificates and EU statements of conformity for all certified products on the European market. Therefore, this website will publish and make available through searches the data relevant to all these resources.

text: The content and format for the European cybersecurity certificates and the EU statements of conformity are set in the cybersecurity scheme under which they are issued. Aside from the specific fields, these data types will contain:

text:  text of the certificate or statement of conformity  holder of the certificate or statement of conformity (natural or legal person who submitted the ICT products, ICT services or ICT processes for certification)  assurance level specified in the European cybersecurity certification scheme  date of issuance  period of validity  accreditation body  technical documentation and links to relevant documentation on the holder’s website

text: 3.2.4.1 Related objects

text:  European cybersecurity certification scheme  Conformity Assessment Body

text: 3.2.4.2 Reports

text:  Search and filtering through active, withdrawn and expired European cybersecurity certificates and EU statements of conformity  Report on European cybersecurity certificates and EU statements of conformity issued under a specific scheme  Report on European cybersecurity certificates and EU statements of conformity issued for an entity

text: 3.2.5 National certification schemes

text: This data type will be simplified with respect to the European cybersecurity certification scheme, as the full information resides on the national websites. The structure will consist of standard metadata, status and links to the remote site for the text and procedures.

text: The functionalities for the national schemes will be the following:

text:  Internal library, accessible to ENISA, European Commission, ECCG, SCCG; the information for each country will be also accessible to the National Cybersecurity Certification Authorities

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  National bodies and SCCG members will provide input to the data, usually at the beginning of elaboration of schemes  Information should contain attributes based on requirements from Art.58  ENISA users will select the entries with potentially affected schemes  Final draft of schemes includes schemes selected as overlapping

text: 3.2.6 Conformity self-assessment

text: According to the CSA, a European cybersecurity certification scheme may allow for the conformity self-assessment under the sole responsibility of the manufacturer or provider of ICT products, services or processes. Conformity self-assessment shall be permitted only in relation to products, services and processes that present a low risk corresponding to assurance level ‘basic’. Manufacturers or providers submit copies of the conformity self-assessments to the national cybersecurity certification authority and to ENISA, so it is conceivable that the submission to ENISA can be done directly through the system, with a final publication from an ENISA user.

text: The system should maintain a list of conformity self-assessments, each record containing:

text:  Details about the manufacturer or provider of ICT products, ICT services or ICT processes  Statement of conformity  Relevant technical documentation  Scheme to which the self-assessment is made against  Dates of submission and expiration

text: 3.2.6.1 Related objects

text:  European cybersecurity certification scheme  National certification scheme (if any)

text: 3.2.7 Conformity Assessment Bodies (CABs)

text: In the process of implementation of cybersecurity certification schemes, manufacturers of ICT products or services submit applications to a conformity assessment body (CAB). These CABs are accredited by the national accreditation bodies and each MS can accredit one or more CABs. Their list may vary in time, in which case changes (add, restrict, suspend or revoke the accreditation of a CAB) must be notified to the EC and registered in the currently described IT system. To be noted that the accreditation will be issued to the CABs for a maximum of five years.

text: After the approval of a new scheme, the CABs accredited for that scheme should be added or removed progressively by the maintainers of the scheme.

text: The structure of this data type should contain:

text:  Name of the CAB  Contact details  Name of the accrediting NAB  Scheme for which CAB is accredited (automatic link to the database of schemes)  Link to the information about accreditation  Date of accreditation  Date of expiry of accreditation

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  EU Login Users which are members of the CAB

text: 3.2.8 User groups (roles)

text: The system’s processes require different user groups to act together. Examples of these groups are ECCG, SCCG, SCCG candidates and secondees, Ad-hoc Working Groups, members of a National Accreditation Body, etc. As mentioned before, the user repository for this system will be the EU Login repository, which records several user details such as the name, email address and organisation.

text: The users having the role of the CMS administrator will be able to search for EU Login users and assign them different roles. Roles will be assigned acces either on the entire platform, or just in specific locations; for instance, a user from an Ad-hoc Working Group will have the rights to provide feedback on schemes of a certain type, and therefore have the local role of ‘ADWG_User’ on those schemes. It should be possible to grant and revoke users’ roles from the administration area of the portal.

text: The list of roles and their users must be browsable, through a specific page. It should be possible to see all roles (groups of users) and the users having that role at that point. When searching for a user, this page should present the roles that user has in the system and the location for each of them (entire system or specific section).

text: The table below summarises the user roles, as well as the use cases (described in detail in Section 2) in which each role is involved.

text: ENISA IT SYSTEM FOR CERTIFICATION ENISA IT SYSTEM FOR CERTIFICATION 3.2.9 Lists of terms

text: Vocabularies are lists of terms (name, value) used throughout the system for categorising data and information. Typical uses include selection drop downs in search interfaces or when editing the fields of data records. It is essential for the system to allow the definition and maintenance of vocabularies, both programmatically (e.g. by uploading a Json file) or manually, by allowing properly authenticated users to edit the list through the web. Upon editing or deleting values, the system should perform checks to insure that data integrity is maintained, i.e. items used to tag the data are not deleted before the data corresponding records are deleted.

text: Examples of vocabularies are:

text:  List of countries  Types and categories of ICT products, ICT services and ICT processes  Assurance levels  EU and international SDOs

text: All modern CMSs offer support for the maintenance of vocabularies, but further integration will be needed for their integration with the data structures.

text: 3.2.10 Formal messages – Message board

text: As detailed in use cases from the functional requirements section, there are certain steps in the system’s processes that require formal messages to be recorded and stored. For instance, the requests for new candidate cybersecurity certifications schemes from EC/ECCG or the transmission of candidate cybersecurity certification schemes from ENISA to the EC contain messages that must be formally recorded, as they trigger other actions in the system. Moreover, ENISA will co-chair and be the secretariat of SCCG, therefore is required to maintain a record of all correspondence relating to the SCCG.

text: In this context, the system must implement a mechanism to store and display these messages, as well as an interface to browse them by subject and by other filters. It must be possible to reference individual messages in other parts of the system, such as link a message to a candidate scheme. In some cases, receiving a message (e.g. request for new certification scheme) will trigger an entire process in the system.

text: The solution should be similar to an inbox of an email account; in fact, for the purpose of sending and receiving emails, one or more ENISA email addresses should be created. These addresses can be included in copy of the email correspondence that needs to be recorded, triggering the corresponding messages and their metadata to be stored in the system. In the

text: ENISA IT SYSTEM FOR CERTIFICATION

text: case where such address is omitted from a relevant message, it should be possible to manually record the message in the system by properly authenticated users.

text: A component needs to be built (or adapted), in order to ensure the following functionality:

text: 1. Secure storage and backup of all messages 2. Messages from the same thread must be recorded together 3. New messages can be added by manually filling out a form or by allowing the system to automatically register an email message 4. Possibility to tag messages by type/topic, either by using predefined texts in the subject of the email, or by manually tagging them as they arrive in the inbox 5. User interface for browsing messages by thread and for filtering by various tags 6. Possibility to restrict certain types of messages by default 7. Subscription to receive email notifications upon receiving a message; in some cases, the notifications to one or more user groups should be automatic 8. The addition of messages should create events in the system. Depending on the type of message, the events will be linked to scripts, thus triggering various activities to be executed (e.g. automatically send emails to user groups)

text: 3.2.11 Discussion forum

text: This component is intended to facilitate free discussions between stakeholders, as part of the collaboration platform of this system. It should support defining multiple discussion topics, to which threaded messages can be posted. Topics should be restricted to certain user groups, or should be available to all authenticated users, as needed. A mechanism for moderation of discussions should be also implemented.

text: It should be possible to open topics on specific subjects, like a request for a candidate cybersecurity certification scheme or a specific cybersecurity certificate, in which case the topic should reference a link from the portal to the scheme or to the certificate. The threaded posts should allow simple HTML content with formatting and links, as well as attached files up to a certain size.

text: Strictly for purposes of exemplifying suitable modules from the known CMSs, the list below can be considered:

text:  Plone Collective Ploneboard , built on top of Dexterity  Plone content type Discussion , part of the Plone core package and easily extendable  Drupal Forum module , part of the Drupal core  Drupal Advanced forum builds on and enhances Drupal's core forum module

text: 3.2.12 Meeting management

text: ENISA is required to co-chair and provide secretarial duties, as well as to maintain a record of all correspondence relating to the SCCG and a record of all meetings and decisions of the SCCG. Therefore, the inclusion of a meeting management component is relevant for this IT system.

text: The requirements for this are:

text:  Maintain records of the meetings, with their dates and locations

text: ENISA IT SYSTEM FOR CERTIFICATION

text:  Export of the meeting details in iCal format  Maintain agendas, minutes and decisions taken during the meetings, along with the possibility to download the relevant documents  Maintain a list of other documents and links  Maintain a list of attendees, together with their affiliation. This entails the ability to generate reports with the participants, per role, organisation and country  Offer instructions for participating in the meeting  Ability for meeting administrators (ENISA users) to register participants  Offer means to send mass emails to participants, with instructions and questions before the meeting  Ability to restrict the content of the meeting materials to certain roles

text: In addition, other features would be useful for this component and should be implemented:

text:  Possibility for authenticated users to self-register for a meeting  Possibility for meeting administrators to approve the self-registered attendees  Interactive map with the meeting location  Possibility to set a maximum number of participants

text: The wireframe below depicts the envisaged design for the meeting management tool.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 46: Wireframe for the meeting management main interface

text: 3.2.13 Data mining

text: Several parts of the cybersecurity certifications schemes, cybersecurity certificates or the statements of conformity need to be checked for potential duplication of content before being published or released. Therefore, the system must include a data mining component, intended to ensure and demonstrate consensus in the design of schemes amongst the AHWG and the ECCG.

text: ENISA IT SYSTEM FOR CERTIFICATION

text: For this purpose, a third-party component, built for antiplagiarism, should be used to find similarities between the texts of existing schemes, certificates and their technical documentation and signal potential overlaps.

text: A good list of such components can be found on Wikipedia , but other services might become available in the meantime. The difference in choosing the software should be made by the possibility to install the service locally as opposed to using it as a service (SaaS), the size of the database of texts and its relevance to the currently referred technical data, as well as the price of the service.

text: 3.3 TIMELINE FOR IMPLEMENTATION

text: The IT Systems should be implemented in phases: the most critical functionalities will be implemented first, in order to sustain the urgent business processes, while less urgent functionalities could be delivered in subsequent iterations.

text: The implementation of this IT system is scheduled to take place over a year from the signing of the contract (T0). Four delivery phases are foreseen, with interim and final deliverables as follows:

text: 1. Phase 1 [T0 + 3 months] – system in version 0.5, ready for adding content: a. Content management system in place with web design implemented i. Metadata for all content types ii. Content types for folder, link, article, document (file), event, news, video and image galleries iii. Lists of terms iv. User groups b. Message board (inbox of formal messages) c. Request for cybersecurity certification scheme 2. Phase 2 [T0 + 6 months] – system ready for launch in version 1: a. Cybersecurity certification schemes with collaboration features b. Adjustments to the content management system c. Meeting management d. National certification schemes e. Conformity Assessment Bodies f. Discussion forum g. Reports – first set 3. Phase 3 [T0 + 9 months] – system in third version: a. European cybersecurity certificates and EU statements of conformity b. Conformity self-assessment c. Reports – second set of reports d. Data mining 4. Phase 4 [T0 + 12 months] – final version of the system: a. All functionality completed and feedback from stakeholders implemented

text: ENISA IT SYSTEM FOR CERTIFICATION

text: Figure 47: Proposed phases of the project and associated deliverables

text: ENISA IT SYSTEM FOR CERTIFICATION ABOUT ENIS A

text: The European Union Agency for Cybersecurity (ENISA) has been working to make Europe cyber secure since 2004. ENISA works with the EU, its member states, the private sector and Europe’s citizens to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of cross-border communities committed to improving network and information security throughout the EU. Since 2019, it has been drawing up cybersecurity certification schemes. More information about ENISA and its work can be found at www.enisa.europa.eu.