Structure of the document Clause Samples

Structure of the document. After completing the introduction in this section, we continue by explaining the role of the cyber risk modelling in the WISER framework in Section 2. Having thus provided the context, in Section 3 we explain our rationale for selecting the three WISER risk modelling languages, which are CORAS for human-readable risk models, DEXi for qualitative risk assessment algorithms, and R for quantitative risk algorithms. In Section 4, we give a short overview of each of these languages, in order to provide some background for the rest of the document aimed at readers not familiar with the languages, as well as references for further information. We then move on to the actual guidelines. In Section 5, we present the overall method for risk cyber risk modelling in WISER. This overall method is the same whether one chooses to use qualitative or quantitative assessment. Section 6 provides specific guidelines for creating CORAS models, which is the first step of the overall method and is performed independently of whether qualitative or quantitative assessment will be used. In Section 7, we give guidelines for defining qualitative assessment algorithms based on a CORAS diagram using DEXi, while Section 8 offer similar guidelines for quantitative algorithms using R. Although simple support for impact assessment is included in Section 7 and Section 8, these sections are primarily dedicated to likelihood assessment. In Section 9, we present a more in-depth approach to economic impact assessment, while societal impact assessment is addressed in Section 10. We then conclude in Section 11. This document also contains five appendices. Appendix I defines what it means for a function on intervals to be monotonically increasing, as this concept plays a role in the guidelines offered in Section 8. Appendix II presents the naming conventions we use in order to ensure clear links between the elements of a CORAS diagram and a corresponding DEXi model or R script. The next three appendices illustrate results of applying the guidelines from Section 7 and Section 8 on a CORAS diagram. First, we present the CORAS diagram in Appendix III. Then we show a corresponding DEXi model in Appendix IV, and finally a corresponding R script in Appendix V.

Structure of the document. The document follows the structure explained below: • Section 1 introduces the document and its context as well as the relationship of this deliverable to other project outcomes. Finally, the methodology adopted to produce this deliverable is presented.

Structure of the document. The document is structured as follows: • The introduction defines risk assessment and socio-economic impacts, looks at the main drivers for SME risk management, and provides a sample of sources consulted. • Section2 defines selected cyber threats and then presents a set of case studies illustrating different types of socio-economic impacts resulting from successful cyber-attacks while also showing new trends in the cyber threat landscape. It concludes with key takeaways for WISER based on key points emerging from the case studies.

Structure of the document. After this introductory chapter, the document outlines the main architectural design choices, processes and guidelines that define the ACDC TDF and is structured as follows:  Chapter 3 presents the ACDC TDF and describes it from different perspectives: development, deployment and operational.  Chapters 4 and 5 focus on the main processes associated to the TDF operation: management, development & integration, providing guidelines and tools to support them.  Chapter 6 provides an index and summary of the SotA Catalogue that is expanded in Annex 8.  Finally, Chapter 7 concludes the document and outlines the future work. This document includes multiple annexes that complement the information provided in sections 2 to 6:  Annex 8 compiles descriptions of the state of the art catalogue of tools (aka SotA Catalogue) that the different partners of ACDC bring into the project. These tools will be integrated to build the ACDC solution that will used in the WP3 experiments. The SotA Catalogue’s main objective is to keep an up to date database of tools offered by the different partners of the ACDC consortium, classified according a taxonomy defined in the TDF. The catalogue shall support the inclusion of tools from outside consortium (i.e. the Community Portal members), thus it is a dynamic instrument that requires of the support of a tool that allows easy modifications and efficient searching capabilities. For this reason, the SotA Catalogue in the annex of this document will be migrated to the Community Portal where the owners of the different tools published in the catalogue can maintain the descriptions and documentations provided in a more convenient manner. This approach also has the advantage that can be permanent linked from other sources of ACDC information, such as the official project website, the support centres or the CERTs.  Annex 9 contains a description of the CybOX format, referenced in section 3.2.5.  Annex 10 is the Minimal Dataset Schema in JSON format, referenced in section 3.2.2.  Annex 11 lists the template used for describing tools in deliverable D2.4, referenced in section 5.  Annex 12 contains the template table used for describing each individual tool in the SotA Catalogue.  Annex 13 lists the aspects evaluated for each individual tool in the Handover to WP3 spreadsheet.  Annex 14 is the checklist created by Task 1.2.1 and used by WP2 Task forces for assessing how the ACDC tools deal with the legal aspects considered in ACDC.

Structure of the document. The remainder of this document is structured as follows: In the main part of the document, In part A (User manual), the user learns how to set up, start and perform a training session with CIPRTrainer, how to use ‘what if’ analysis, and how to modify the system settings. In part B (documentation), we provide a “Quick Start” guide for users of CIPRTrainer and an overview of the structure of CIPRTrainer’s modular user interface. We conclude by summarising the main properties of the single-trainee version of CIPRTrainer in the following figure. Figure 1: Simplified scheme of CIPRTrainer’s main components. The design engine is represented by the rounded rectangle labelled “SyMo” and the scenario developer’s icon. All other shown components belong to CIPRTrainer’s training engine. The most important element for users of CIPRTrainer is the CIPR- Trainer Graphical User Interface (GUI), through which both trainer and trainee operate CIPRTrainer. As written in deliverables D6.3 [CIPRNetD63] and D6.4 [CIPRNetD64], two of the modelling activities for setting up the scenarios take place in the Federated Simulation part (Critical Infrastructure models) and in the Database part (definition of events, rules, and dependencies). PART A: USER MANUAL

Structure of the document. This deliverable aims to describe the ICT-Emissions Project corporate identity, more specifically, Chapter 2 introduces the ICT-Emissions logotype, the Word and Power Point templates. The ICT-Emissions Project should have a strong identity using the project logo; an overall corporate identity (document and slideshow templates) has been developed for the project to give it a common image towards the outside world and to communicate in a consistent way and with a clear and recognisable brand. A colour scheme of 3 shades of Green wording on the logo will make the ICT-Emissions project easily identifiable are important for dissemination, raising awareness around the achievements of the whole project. The ICT-Emissions logo should be used in the front page of all project reports, in the top left corner of each page (as in the present document). The logo is illustrated below as Figure 9. Different types and qualities for the logo can be found in the Downloads section of the ICT-Emissions website (▇▇▇.▇▇▇-▇▇▇▇▇▇▇▇▇.▇▇).

Structure of the document. The document is structured as follows. Section 1 gives a brief overview of the purpose of the document by introducing the first idea of a requirements intelligence unit. Then, in Section 2 we explain the state of the art related to the mining, classification, clustering of requirements and user feedback, and their visualization. Based on the results of the state of the art, we show the first version of the conceptual model in Section 3. We present an overview of the architecture related to the goal of this document and describe the components that are part of the proposed architecture. Within the components, we explain their goal, methods, the techniques we might use, and their challenges. In Section 4, we present two papers which are the result of research in OpenReq that are related to this deliverable. Section 5 summarizes the document.

Structure of the document. ‌ The remainder of this document is organized as follows: •

Structure of the document. ‌ The document first addresses the existing IoT architectures (Section 4). Instead of developing a new architecture, we adopted an approach of building on top of the existing IoT architectures and aligning it with the ongoing related developments in several projects and standardization bodies. Section 5 provides a description of the updated IoT6 architecture. A description of a concrete system based on the IoT6 architecture is provided in Section 6. In Section 7 the definition of the IoT scenario and its elements in the IoT Architecture Reference Model is given and IoT6 selected Use Cases are presented according to the IoT Architecture Reference Model. Section 8 addresses the reviewers’ comments regarding the IoT non-functional architecture properties. Section 9 concludes the document with a summary of our conclusions and some suggestions where further work is required.