text: See https://www.enisa.europa.eu/publications/artificial-intelligence-cybersecurity-challenges 2 See https://www.enisa.europa.eu/publications/securing-machine-learning-algorithms

text: See https://www.enisa.europa.eu/news/cybersecurity-threats-fast-forward-2030 4 See https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52021PC0206 5 See https://www.enisa.europa.eu/publications/securing-machine-learning-algorithms

text: 7 The scenario description is aligned with ENISA’s previous work on AI , and provides the following information: • The purpose and the context • A high-level description of the scenario, highlighting the data encountered • The involved actors and their associated roles • A detailed description of the data • Machine learning algorithms • Other assets (besides data) associated with the described scenario • The overall process of the scenario • Security and privacy requirements

text: See https://www.enisa.europa.eu/publications/securing-machine-learning-algorithms 7 See https://www.enisa.europa.eu/publications/artificial-intelligence-cybersecurity-challenges See Article 5 of GDPR

text: In this analysis, we have assigned to one actor the roles of several actors. In many countries, there are different actors such as: the distributed system operator, market operator, energy producers

text: Usually, these renewable sources are dispatched by the system operator.

text: See https://api.meteo-concept.com/documentation_openapi See https://api.gouv.fr/les-api/api_donnees_locales Elamin, Niematallah et Fukushige, Mototsugu. Modeling and forecasting hourly electricity demand by SARIMAX with interactions. 2018. https://www.sciencedirect.com/science/article/abs/pii/S0360544218319297 Smart meters have an ID, which is related to a name, addressee etc at the concentrator level. See https://api.meteo-concept.com/documentation_openapi

text: As we will see, the output training data comes from personal data sources. However, once the model is in production, it only predicts the overall energy consumption. See https://api.meteo-concept.com/documentation_openapi Neda Tavakoli; Sima Siami-Namini; Akbar Siami Namin. A Comparison of ARIMA and LSTM in Forecasting Time Series https://scholars.ttu.edu/en/publications/a-comparison-of-arima-and-lstm-in-forecasting-time-series-5 B, Prabadevi, et al. Deep Learning for Intelligent Demand Response and Smart Grids: A Comprehensive Survey https://arxiv.org/abs/2101.08013 Abualig, Laith, et al. Wind, Solar, and Photovoltaic Renewable Energy Systems with and without Energy Storage Optimization: A Survey of Advanced Machine Learning and Deep Learning Techniques https://www.mdpi.com/1996- 1073/15/2/578

text: See https://www.cnil.fr/fr/linky-gazpar-quelles-donnees-sont-collectees-et-transmises-par-les-compteurs-communicants 22 See https://ec.europa.eu/eurostat/documents/3859598/5935825/KS-GQ-13-003-EN.PDF/baa96509-3f4b-4c7a-94ddfeb1a31c7291

text: Brownlee, Jason. Data Preparation for Machine Learning, Data Cleaning, Feature Selection, and Data Transforms in Python. 2020 https://books.google.fr/books?id=uAPuDwAAQBAJ&printsec=frontcover&hl=fr&source=gbs_ge_summary_r&cad=0#v=one page&q&f=false 24 Lee, Donghun and Kim, Kwanho. Recurrent Neural Network-Based Hourly Prediction of Photovoltaic Power Output Using Meteorological Information. 2019. https://www.mdpi.com/1996-1073/12/2/215 25 Pavicevic, Milutin and Popovic, Tomo. Forecasting Day-Ahead Electricity Metrics with Artificial Neural Networks. 2022. https://www.mdpi.com/1424-8220/22/3/1051 26 Elamina, Niematallah et Fukushige, Mototsugu. Modeling and forecasting hourly electricity demand by SARIMAX with interactions. 2018. https://ideas.repec.org/a/eee/energy/v165y2018ipbp257-268.html 27 Sim, Sze En, et al. Forecasting Electricity Consumption Using SARIMA Method in IBM SPSS Software. 2019. https://www.hrpub.org/journals/article_info.php?aid=8614

text: Baheti, Pragati. Train, Validation, and Test Sets: How to Split Your Machine Learning Data. v7labs. [En ligne] 22 May 2022. https://www.v7labs.com/blog/train-validation-test-set.

text: See https://ec.europa.eu/justice/article-29/documentation/opinion-recommendation/files/2014/wp216_en.pdf The choice of a legal basis is final, and a treatment cannot involve two legal bases. However, in our case, as explained in the body of the report, two treatments are made: a treatment based on the fact that the data is extracted daily and a treatment based on the fact that the data is extracted every hour or half hour. Depending on which of the two treatments is accepted by the consumers, a corresponding legal basis will be chosen. See https://www.cnil.fr/fr/linky-gazpar-quelles-donnees-sont-collectees-et-transmises-par-les-compteurs-communicants

text: See https://www.cnil.fr/fr/intelligence-artificielle/la-cnil-publie-ressources-grand-public-professionnels See https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulationgdpr/accountability-and-governance/data-protection-impactassessments/#:~:text=DPIAs%20are%20a%20legal%20requirement,trust%20and%20engagement%20with%20indivi duals The condition for a DPIA to occur is that at least two conditions are satisfied.

text: See the severity scales in the Annex

text: Strictly speaking, this vulnerability is outside the scope of our analysis since the company oversees the production and distribution of energy -so there is no external stakeholder which manipulate personal data. However, this is not necessarily the case. We therefore draw the reader's attention to this point. Nevertheless, we will not deal with it in the following section

text: https://www.enisa.europa.eu/news/enisa-news/tips-for-secure-user-authentication 39 See https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63-3.pdf See https://cipherwire.net/wpcontent/uploads/2013/06/802.1X_and_NAC___Best_Practices_for_Effective_Network_Access_Control.pdf

text: Based on « Agence Nationale de la Securité des Systèmes d’Information » (ANSSI). See: https://www.ssi.gouv.fr/uploads/2019/11/anssi-guide-ebios_risk_manager-en-v1.0.pdf 43 Metrics based on the National Commission on Informatics and Liberty (CNIL) -an independent French Administrative regulatory body. See: https://www.cnil.fr/sites/default/files/atoms/files/cnil-pia-3-enknowledgebases.pdf

text: Such as the CNIL. It proposes an analysis grid to enable organizations to assess the maturity of their artificial intelligence systems regarding the GDPR available on https://www.cnil.fr/fr/intelligence-artificielle/guide. 45 see the various CNIL method sheets on this subject, such as this one: https://www.cnil.fr/fr/intelligenceartificielle/guide/developper-et-entrainer-un-algorithme

identifier: Cybersecurity and privacy in AI - Forecasting demand on electricity grids

amnesord: Artificial Intelligence and Next Gen Technologies

title: Cybersecurity and privacy in AI - Forecasting demand on electricity grids

text: CYBERSECURITY AND PRIVACY IN AI – FORECASTING DEMAND ON ELECTRICITY GRIDS JUNE 2023 0

text: CYBERSECURITY AND PRIVACY IN AI – FORECASTING DEMAND ON ELECTRICITY GRIDS

text: June 2023

text: ABOUT ENISA

text: The European Union Agency for Cybersecurity, ENISA, is the Union’s agency dedicated to achieving a high common level of cybersecurity across Europe. Established in 2004 and strengthened by the EU Cybersecurity Act, the European Union Agency for Cybersecurity contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies, and helps Europe prepare for the cyber challenges of tomorrow. Through knowledge sharing, capacity building and awareness raising, the Agency works together with its key stakeholders to strengthen trust in the connected economy, to boost resilience of the Union’s infrastructure, and, ultimately, to keep Europe’s society and citizens digitally secure. More information about ENISA and its work can be found here: www.enisa.europa.eu. CONTACT For contacting the authors, please use info@enisa.europa.eu For media enquiries about this paper, please use press@enisa.europa.eu. EDITORS Monika Adamczyk, Apostolos Malatras, Ioannis Agrafiotis, ENISA LEGAL NOTICE This publication represents the views and interpretations of ENISA, unless stated otherwise. It does not endorse a regulatory obligation of ENISA or of ENISA bodies pursuant to the

text: Regulation (EU) No 2019/881

text: . ENISA has the right to alter, update or remove the publication or any of its contents. It is intended for information purposes only and it must be accessible free of charge. All references to it or its use as a whole or partially must contain ENISA as its source. Third-party sources are quoted as appropriate. ENISA is not responsible or liable for the content of the external sources including external websites referenced in this publication. 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. ENISA maintains its intellectual property rights in relation to this publication. COPYRIGHT NOTICE © European Union Agency for Cybersecurity (ENISA), 2023 This publication is licenced under CC-BY 4.0. Unless otherwise noted, the reuse of this document is authorised under the Creative Commons Attribution 4.0 International (CC-BY 4.0) licence (https://creativecommons.org/licenses/by/4.0/). This means that reuse is allowed, provided that appropriate credit is given and any changes are indicated. 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. ISBN: 978-92-9204-620-0 – DOI: 10.2824/92851 – Catalogue Nr: TP-09-23-010-EN-N

text: June 2023

text: TABLE OF CONTENTS

text: 1. INTRODUCTION 6 1.1 STUDY OBJECTIVES 6 1.2 METHODOLOGY 7 1.2.1 Description of the scenario 7 1.2.2 Identification of cybersecurity and privacy threats and vulnerabilities 7 1.2.3 Identification of cybersecurity and privacy controls 7 1.3 TARGET AUDIENCE 7 1.4 USING THIS DOCUMENT 8 2. SCENARIO DESCRIPTION 9 2.1 PURPOSE AND CONTEXT 10 2.2 HIGH-LEVEL DESCRIPTION 10 2.3 ACTORS AND ROLES 11 2.4 PROCESSED DATA 12 2.5 MACHINE LEARNING ALGORITHMS 14 2.6 ASSETS 14 2.7 OVERALL PROCESS 15 2.8 PRIVACY AND CYBERSECURITY REQUIREMENTS 20 3. SECURITY AND PRIVACY THREATS AND VULNERABILITIES 24 3.1 THREAT CONTEXTUALISATION 24 3.1.1 Compromise of ML application components 25 3.1.2 Poisoning 25 3.1.3 Human error 26 3.1.4 Data disclosure 26 3.1.5 Unlawful Processing 26 3.1.6 Unfair processing 26 3.1.7 Lack of transparency 27 3.1.8 Diversion of purpose 27 3.1.9 No respect of data minimisation 27 3.1.10 No respect of storage limitation 27 3.1.11 Synthesis of possible impacts and associated threats 27 3.2 VULNERABILITIES ASSOCIATED TO THREATS AND AFFECTED ASSETS 28

text: June 2023

text: 4. CYBERSECURITY AND PRIVACY CONTROLS 33 4.1 IMPLEMENT A SECURITY BY DESIGN PROCESS 34 4.2 DOCUMENT THE ELECTRICAL FORECAST SYSTEM 34 4.3 CHECK THE VULNERABILITIES OF THE ML COMPONENTS AND IMPLEMENT PROCESSES TO MAINTAIN THEIR SECURITY LEVELS OVER TIME 35 4.4 CHOOSE AND DEFINE A MORE RESILIENT MODEL DESIGN 35 4.5 INTEGRATE POISONING CONTROL IN THE TRAINING DATASET 36 4.6 ENLARGE THE TRAINING DATASET 36 4.7 SECURE THE TRANSIT OF THE COLLECTED DATA 37 4.8 CONTROL ALL DATA USED BY THE ML MODEL 37 4.9 ENSURE RELIABLE SOURCES ARE USED 38 4.10 IMPLEMENT ACCESS RIGHT MANAGEMENT PROCESS 38 4.11 ENSURE ALL SYSTEMS AND DEVICES COMPLY WITH AUTHENTICATION, AND ACCESS CONTROL POLICIES 39 4.12 REDUCE THE AVAILABLE INFORMATION ABOUT THE MODEL 40 4.13 IDENTIFY A DATA CONTROLLER FOR THE ENERGY CONSUMPTION ANTICIPATION DATA PROCESSING 40 4.14 PROPERLY COLLECT AND MAINTAIN USER CONSENT WHEN NEEDED FOR DETAILED ENERGY CONSUMPTION USAGE 41 4.15 ANONYMIZE DATA COMING FROM THE CONCENTRATOR 41 4.16 GENERATE LOGS AND PERFORM INTERNAL AUDIT 42 4.17 PERFORM A PRIVACY IMPACT ASSESSMENT 42 4.18 DEFINE AND IMPLEMENT A DATA RETENTION POLICY 43 4.19 STUDY ON DATA FIELDS NECESSITY AND JUSTIFICATION IN THE PRIVACY POLICY 43 4.20 FORMALISE A LIA (LEGITIMATE INTEREST ASSESSMENT) 44 4.21 MINIMISE DATA AT EACH STEP OF THE PROCESSING; COLLECT ONLY WHAT IS NEEDED WHEN NEEDED 44 4.22 IMPLEMENT A PRIVACY BY DESIGN PROCESS 45

text: June 2023

text: 4.23 RAISE AWARENESS OF SECURITY AND PRIVACY ISSUES AMONG ALL STAKEHOLDERS 45 4.24 SUMMARY 46 5. CONCLUSION 49 ANNEX I: SECURITY AND PRIVACY SCALES AND REQUIREMENTS 50 A.1 CYBERSECURITY AND PRIVACY SEVERITY SCALES 50 A.2 CYBERSECURITY SCALE OF IMPACT 51 A.3 PRIVACY SCALE OF IMPACT 51 A.4 PRIVACY REQUIREMENTS CRITERIA 52

text: June 2023

text: EXECUTIVE SUMMARY

text: Given the great influence of artificial intelligence (AI) in people's daily lives due to the key role it plays in digital transformation through its automated decision-making capabilities, ENISA aims to raise awareness of cybersecurity and privacy threats related to various scenarios using artificial intelligence. To this end, ENISA, with the support of the Ad-Hoc Working Group on Artificial Intelligence Cybersecurity, has published two reports in the last two years: Cybersecurity Challenges of Artificial Intelligence and Securing Machine Learning Algorithms . ENISA continues its momentum with a new report on cybersecurity and privacy in forecasting demand on electricity grids. An in-depth study of the scenario has been conducted by identifying first the assets, the actors and their roles, relevant processes, the AI algorithms used, as well as the requirements in terms of cybersecurity and privacy needed for it. Building upon previous ENISA work such as the “Securing Machine Learning Algorithms” report cited above, in addition to legislation such as GDPR and literature searches, this report has identified cybersecurity and privacy threats and vulnerabilities that can be exploited in the examined scenario. While focus is on ML-related threats and vulnerabilities, broader AI considerations were also taken into account. Lastly, corresponding cybersecurity and privacy controls that consider the context of the scenario and the impact of the associated threats/vulnerabilities were defined. The specificities within the implementation of these controls are described, including possible tradeoffs between cybersecurity, privacy, and performance. Each control is classified as a cybersecurity control, a privacy control, or a mixture of both, depending on the threats it mitigates and their associated impacts (cybersecurity impacts, privacy impacts, or both). This report allows better assessment of the reality that artificial intelligence brings its own set of threats, which consequently insists on the search for new security measures to counter them. Finally, it should be noted that this guide strongly emphasises privacy issues in the same way as cybersecurity issues, privacy being one of the most important challenges facing society today. Security and privacy are intimately related, but both equally important, and a balance must be made specific to each use. As a result, as seen in this report, efforts to optimise security and privacy can often come at the expense of system performance.

text: June 2023

text: 1. INTRODUCTION

text: Abuse of Artificial Intelligence (AI), which has developed significantly in recent years, has been identified by ENISA as one of the top emerging threats . By providing new opportunities to solve decision-making problems intelligently and automatically, AI is being applied to more and more business cases in a growing number of sectors. The associated benefits are significant. However, the development of AI is also accompanied by new threats which project teams will have to face. In many projects, it is apparent that these new threats are related to aspects of cybersecurity in addition to privacy, particularly when AI is used for innovative projects whereby processing personal data takes place. In this spirit, on 21 April 2021, the Commission published the AI Act proposal , which sets out requirements (including cybersecurity and privacy) for AI systems deemed to be high-risk (e.g., used in biometric identification or critical infrastructure management and operation) in order to mitigate threats to health, safety, and fundamental rights. To go further into these high-risk AI systems, ENISA proposes this new report: "Cybersecurity and Privacy in AI - Forecasting Demand on Electricity Grids", which builds directly on the work already initiated by ENISA since 2020 on the identification of risks associated with AI. This new report analyses cybersecurity and privacy requirements and measures in use of AI in forecasting demand on electricity grids. The report describes the scenario fundamental principles (assets, actors processes etc.), identifies the security and privacy risks it poses, and finally cybersecurity and privacy controls, which counteract the identified risks. 1.1 STUDY OBJECTIVES Findings from the ENISA’s report on securing machine learning algorithms indicate that there is no uniform strategy in applying a specific set of security controls to protect machine learning algorithms and in some cases, deployed security controls may result in trade-offs in security and performance. ENISA therefore recommends that organisations which use AI systems should perform detailed analysis of their own AI systems, and conduct targeted risk assessments to find the appropriate balance between cybersecurity, privacy and performance. The objectives of this publication are as follows: • Provide a detailed description of a Forecasting Demand on Electricity Grids scenario. • Identify AI cybersecurity and privacy measures taking into account requirements, threats and vulnerabilities defined for this scenario and practical guidance on how to implement them. • Provide recommendations on how to balance the trade-offs between cybersecurity, privacy, and performance in this scenario. The following section outlines the methodology followed in producing this report.

text: June 2023

text: 1.2 METHODOLOGY Production of this publication, was undertaken in three stages: • Identify and describe in detail the forecasting demand on electricity grids scenario. • Identify cybersecurity and privacy threats associated with the scenario. • Identify relevant cybersecurity and privacy controls. 1.2.1 Description of the scenario 1.2.2 Identification of cybersecurity and privacy threats and vulnerabilities This section of the report focusses on the threats and vulnerabilities related to use of AI in forecasting demand on electricity grids scenario. Based on previously mentioned ENISA work, legislation such as GDPR, and desk research, this report identified the cybersecurity and privacy threats and vulnerabilities that can be exploited. Given the prevalence of machine learning (ML) and ENISA’s past work on the topic, there is more emphasis placed on threats and vulnerabilities related to ML. Nonetheless, wider considerations of AI have been taking into account when identifying security threats and vulnerabilities as well as dedicated to privacy, for which GDPR data protection principles were used as a starting point of our analysis. 1.2.3 Identification of cybersecurity and privacy controls Following the analysis of forecasting electricity on electricity grids scenario, the identification of threats (and their impact), and associated vulnerabilities, this section of the report presents the corresponding cybersecurity and privacy controls that: • Take into account the context of the scenario • Take into account the security and privacy impact of the threat/vulnerabilities (as described in this report) The specificities of implementation of such controls are described including the possible tradeoffs between cybersecurity, privacy and performance. Each control can be either a cybersecurity control, a privacy control, or a mixture of both, depending on the threats it mitigates and their associated impacts (cybersecurity impacts, privacy impacts, or both). Many of the controls are of technical nature, but when appropriate (e.g., per GDPR requirements), organizational controls have also been identified. 1.3 TARGET AUDIENCE The target audience of this report can be divided into the following categories:

text: June 2023

text: • All actors (private or public): to help them in their risk analysis, in the identification of cybersecurity and privacy threats and in the identification of the appropriate security and privacy controls to mitigate the threats related to this scenario • AI technical community, AI cybersecurity and privacy experts and AI experts (designers, developers, ML experts, data scientists, etc.) with an interest in developing secure solutions and in integrating security and privacy by design in their solutions. • Cybersecurity and privacy community: to help in identifying cybersecurity and privacy threats related to forecasting demand on electricity grids scenario and in identifying the appropriate security and privacy controls to mitigate the threats. 1.4 USING THIS DOCUMENT Although we based the scenario close to reality, some assumptions have been to made for the purposes of its analysis. These assumptions should be reassessed by the reader when doing their own analysis. Please note this list is non-exhaustive: • The algorithms chosen for the scenario are based on desk research, and there may be other algorithms that are better suited for it. • Regarding the privacy aspects, we put ourselves in the shoes of the data controller, but only based on the hypothesis that we have made. It is left to the attention of the audience that the privacy requirements as well as the control measures must always be adapted to a context and a situation. • After identifying potential threats, this report identifies security and privacy controls that could be applied to the scenario. However, as is the case for any application of ML, one must also consider traditional security standards (e.g., ISO 27001/2, NIST) because ML applications are also subject to more global threats. It should also be kept in mind that the elements of this report are valid as of the date of publication, and could evolve over time.

text: June 2023

text: 2. SCENARIO DESCRIPTION

text: The following figure presents an overview of the topics that will be addressed in this chapter. Figure 1: Scenario overview

text: June 2023

text: 2.1 PURPOSE AND CONTEXT Consumption and production balance is the core challenge of any smart electricity grid. This is particularly the case since the rise of intermittent renewable energies that help to rebalance the energy mix and reduce reliance on energy production from fossil fuels. However, the inherent intermittence of renewable energies requires distributors to take into account precise predictions to ensure that production is able to meet consumption, even during peak hours. Moreover, to this day there is no way to store energy on a large scale that could allow the temporary separation of production to meet current consumption. For this reason, a national electricity system electricity supplier has defined the following purposes: • reduce the production of electricity from non-renewable energies (conventional power plants, etc.), • prioritise the consumption of electricity produced from renewable energies (photovoltaic panels, wind turbines, etc.), • Ensure all technical conditions for the supply of electricity, including the need to maintain supply with fluctuating demand. To reach these objectives, the national electricity system electricity supplier seeks to make daily predictions on the amount of non-renewable energy production required to supplement the amount of energy produced by renewable sources so that the total energy produced matches the estimated consumer demand. This is done on a daily basis in three steps: • Predict the production of renewable sources using meteorological data (history and forecast), data from the materials (mechanical / electronical characteristics of the solar panels and the windmills) and historical data concerning the previous power production from power farms. • Forecast consumption of the consumers with demographic data, calendar data (events, holidays), and energy consumption. • Compare predicted renewable production against consumption forecast. This provides an important key performance indicator (KPI) for the national electricity system electricity supplier teams to make a decision as to whether additional power plants may be required to supplement the renewable energy, or if the energy produced by renewable sources may be stored. 2.2 HIGH-LEVEL DESCRIPTION The technical core of the scenario is therefore prediction, with the use of artificial intelligence algorithms. To be more precise, machine learning is used along with the supervised learning paradigm (e.g., multivariate regression or neural networks). To achieve these objectives, a dataset is used, amongst which, material characteristics of solar panels and wind turbines, weather data, energy consumption of consumers, calendar data and demographics (regional information about the average age of the population, employment, number of inhabitants etc.). Most of these data are obtained through public application programming interfaces (APIs), with the remaining data already in possession of the electricity provider. Once collected in a data lake via data engineers and network administrators, the data must be explored and prepared. This is aimed at better understanding the data, evaluating the quality and quantity at disposal and adopt a modelling strategy. The data scientist and engineering teams are responsible for these steps. The electricity supplier’s teams, especially

text: June 2023

text: business experts, may be required to give insights about the data collected and help decide which strategy to choose. Selected data are then used to create two machine learning models. A data scientist team is responsible for this step. One model is built to determine the next day's electricity production from renewable electricity production facilities, while the other is built to determine the next day's electricity consumption. The two models are described in detail in 1.9. These two models produce the following outputs: • a daily prediction of the renewable energy production • a daily energy consumption of facilities (inhabitants, industrials etc.) At the end of the prediction processes, predictions are fed back into a dashboard tool used by the electricity provider teams to adjust their power procurement decisions. The following sections aim to detail such scenario by describing actors and their roles, data processed, the assets that allow the project to exist, the explanation of the scenario lifecycle, and the privacy and cybersecurity requirements applied to it. Figure 2: High-level description 2.3 ACTORS AND ROLES The following actors are involved in the forecasting demand on electricity grids scenario.

text: June 2023

text: Figure 3: Actors, roles, and their description

text: Actor Role Description

text: Electricity System Electricity supplier’s teams oversee controlling the electricity End Users and Data supply so that it is optimal at all times, knowing that energy not consumed is

text: Electricity supplier’s

text: Owner (Data energy wasted. In this scenario, the team interprets the model’s results,

text: teams

text: Controller) provides requirements to data scientists, and has control over the solar and wind infrastructure that provides data inputs into the model.

text: Electricity consumers are indirect participants. Their electricity consumption, Electricity consumers Data Provider whether individual or not, is reported through the network of electricity meters, energy suppliers, etc.

text: Open data providers are an external entity providing open-data, including Open-data providers Data Provider demographics, and weather forecasts of solar irradiance, cloud cover and wind speed, amongst other metrics.

text: Data scientists are the spearhead of the algorithms. They oversee cleaning and preparing of the data, building the models and ensuring the relevance of Data scientists Data scientist the results. They work with the Electricity Distribution Electricity supplier’s teams to build a relevant model.

text: Developers and Data Engineers are responsible for routing data, Developers and Data Developers and transformation, production environments and other technical operations as Engineers Data Engineers required.

text: System and communication network’s administrator are responsible for the

text: System and

text: Network installation and the maintenance of digital systems supporting the machine

text: communication

text: administrators learning application, including network (flows etc.) and hosting of on-premises

text: network administrators

text: servers that make the application work.

text: 2.4 PROCESSED DATA As previously mentioned, there are two models, and each uses separate data. It should also be noted that the output data of one model (predicted data) becomes the input data of the same model the next day. Figure 4: Data needed to build the model and input data that the model will use for the electricity production from renewable energies

text: June 2023

text: Data Data type Source / data provider Data Procurement

text: Model ‘s input data

text: Material characteristics Owners of the renewable of renewable electricity These data can be obtained from the results Structured electricity production means, i.e., production means (e.g., of the regular maintenance of the electricity data the electricity system photovoltaic panels, supplier’s equipment.

text: electricity supplier

text: wind turbines)

text: High resolution weather Official meteorological and Several APIs can provide these data for data (solar irradiance, climatological services, every renewable electricity production Time series cloud cover and wind governments as Open-data means. They can provide historical data and speed over time) provider prediction over the coming hours or days .

text: Model’s output data

text: Owners of the renewable These data are known for every renewable Energy production from electricity production means, electricity production means. The collection Time series renewable energies i.e., the electricity system of this information for every plant will give a electricity supplier global overview of the electricity data.

text: Figure 5: Data needed to build the model and input data that the model will use the consumers' energy demand

text: Model’s input data

text: Several APIs can provide these data for every city and occasionally for each Demographics neighbourhood. For instance, the (statistical data Public APIs from national INSEE provide the number of Structured relating to the size of statistical institutes as Open- inhabitants and their repartition for data the population data provider several geographical scales in France. attending the area) The difficulty is to determine which data are impactful to avoid the model becoming over-parameterised.

text: Calendar (calendar of These data are public and can be found events, holydays... to in open data platforms. The difficulty is to help predict times of determine which data are impactful to Structured the year when Open-data provider avoid the model becoming overdata consumption is high parameterised. This information can be or lower than found and must be expressed in a way average) that the system can understand .

text: Consumers’ (including industrials, municipalities, and The electricity supplier can collect the individuals) smart meters energy data from smart meters installed belonging to the electricity at the consumers’ site. Smart meter data Current daily energy system electricity suppliers. Time series is sent to a concentrator, located at a consumption These smart meters provide secondary substation (medium voltage surname, first name, address, low voltage) where all data from all the meter number, telephone 15 individuals are gathered . number, and electricity consumption.

text: Model’s output data

text: June 2023

text: Consumers’ (including As highlighted, the data that will be used industrials, municipalities, and to train the model are collected in the individuals) smart meters following way: the electricity supplier can belonging to the electricity collect the energy data from smart meters system electricity suppliers. installed at the consumers' site. Smart Energy consumption Time series These smart meters provide meter data is sent to a concentrator, surname, first name, address, located at a secondary substation meter number, telephone (medium voltage - low voltage) where all number, electricity data from all the individuals are 16 17 consumption gathered .

text: 2.5 MACHINE LEARNING ALGORITHMS The following algorithms are used in our scenario. The first algorithm (RNN) is used to forecast the daily production of electricity from renewable energies. The second algorithm (SARIMAX) is used to forecast the daily consumer demand. Figure 6: Machine learning algorithms used

text: Learning paradigm Subtype Algorithm Type of data ingested Description

text: A recurrent neural network (RNN) is a class of artificial neural networks where connections between nodes form a Supervised Learning Regression RNN Time series directed graph along a temporal sequence. This allows it to exhibit 18 19 20 temporal dynamic behaviour .

text: Given a time series, the ARIMA model is a tool to understand and predict the future values of this series. The model is composed of two parts: an Time series Supervised Learning Regression SARIMAX autoregressive part (AR) and a moving Structured Data average part (MA). A SARIMAX algorithm has additional seasonality modelling (S) and exogenous variables 18 19 20 (X) in the model .

text: 2.6 ASSETS In addition to the previously described data, the scenario is supported by the following additional assets.

text: June 2023

text: Figure 7: Asset’s description

text: Type of asset Asset Description

text: RNN, daily renewable The model takes as inputs: history of energy production from renewable energy prediction energies, meteorological data, and material characteristics of renewable forecast electricity production means and the model learns to predict energy production using these data as standalone inputs.

text: Models

text: SARIMAX, daily The model takes as inputs: real-time energy consumption of inhabitants, consumption forecast demographics and calendar data and the model learns to predict energy production using these data as standalone inputs.

text: The data ingestion platforms that enable data engineers to store data and Data lake – on-premises exploit them.

text: Open-data provider The different APIs used by the model to obtain data (weather, APIs demographic, calendar).

text: The smart meter is a meter that measures accurately and in real-time the various energy consumptions (water, electricity, gas). The meter directly Smart meters transmits the various information to a backup system allowing the analysis of the collected data.

text: A termination point where all data collected by the smart meters in the Concentrator same area are recorded. The data are then aggregated at this point to form a global consumption.

text: Model server – on- The model server is used to store the model and process the training and premises retraining phases.

text: Environment tools

text: Dashboard tools – on- Tool monitoring electricity production and consumption. The two models premises are incorporated in this tool.

text: Data collected by smart meters is communicated through the electrical Electricity supplier's grid (Power Line Communications – PLC) before reaching the electrical grid concentrator.

text: Integrated Development Software application that provide comprehensives facilities to computer Environment programmers.

text: Programming Libraries A collection of precompiled codes that can be used in a project to realise (with algorithms for well-defined operations. transformation…)

text: Communication protocol A system of rules allowing a group of entities to communicate with each and communication other to share or ask information. Networks

text: 2.7 OVERALL PROCESS As a reminder, the national electricity system electricity supplier seeks to predict the amount of daily "traditional" energy to produce in addition to that produced by renewable energies to satisfy consumer estimated demand. To carry out this scenario, electricity supplier’s teams, data scientists, data engineers and the system administrator work together to understand the final objectives and define the needs. In the following paragraphs, the scenario is described by incorporating it into the different stages of the machine learning lifecycle:

text: June 2023

text: Data collection The first step is to determine how to obtain the needed data and how to incorporate it in the model. Data engineers/developers and network administrators route the data used in the models. The former to format it, to know where to retrieve it, to validate its quality and the latter to build the necessary flows as these data are routed through various channels (public APIs, individual consumer meters provided by the electric company). Of course, even once in production, the data must be routed to the models to make their predictions. Data are routed to an existing on-premises (belonging to the electricity supplier) data lake, which is a set of servers and resources specifically designed to store and orchestrate the data, and to define a set of data tables. Most of these data (material characteristics, and production history) are owned by the electricity supplier. The electricity supplier can collect this data since it knows the amount of equipment at its disposal, the state of these facilities, and its production history. To carry out its project, the electricity supplier collects the data it needs from the results of the regular maintenance of its equipment and from its production history. As mentioned earlier, weather data has an important part to play in this scenario. It greatly influences the amount of electricity produced by renewable energies. The prediction of these data is the expertise of the meteorological services. The latter make these data accessible through APIs that they provide and maintain. This data is considered as open-data and is therefore nonproprietary and free to use. The electricity supplier collects this data using the APIs made available. An important source of data collected is the electricity consumption of the inhabitants. The consumption data is considered personal data because it includes personal information such as name, surname, address, smart meter number and phone number of account holder in addition to the consumption. The electricity supplier collects their electricity consumption from 21. By default, only the daily smart meters installed locally at the consumers' place consumption data (global consumption of the household over a day) is collected to allow the consumers to consult the history of his consumption free of charge. However, smart meters can collect more detailed consumption information. This detailed consumption information is the hourly or half-hourly consumption data. The collection of this detailed consumption data is not automatic. The electricity supplier does not collect detailed consumption data for all households by default, however these may be collected with the user's consent. This data then passes through the Electricity supplier’s electrical grid - PLC to a concentrator located at a secondary sub-station (medium voltage - low voltage). Once this information arrives at the concentrator, a first processing is done by data engineers. To protect this personal data, in accordance with the General Data Protection Regulation (GDPR), the data engineer must filter the data so that it cannot be used to directly identify individual consumers. This includes: • the name of the person • the address of the person • the meter number of the person • the phone number of the person It is also worth noting that smart meters have geolocation, and such information could be used to track the location of consumers living in low density areas. To circumvent this risk, the electricity supplier collects data in areas with a large number of households . The default or detailed consumption values (if the consumer has agreed to share this information for the purpose of the processing) are kept and then aggregated (i.e., summed with all other consumption data) in a large consumption database maintained by

text: June 2023

text: the electricity supplier. This aggregated data does not allow for the retrieval of consumer data. It is therefore anonymised data. In addition, open data are also used in this prediction stage. This includes statistical data related to the size of the population present in the area (demographics), and the calendar of events and holidays, specific to the residents to help to predict times of the year when consumption is high or below average. Demographics can be provided by several APIs and calendars are public, allowing them to be manually located. Data cleaning and data pre-processing From there, data scientists use various tools ranging from on-premises servers (to perform calculations) to programming interfaces on their workstations which call upon data science libraries. These tools allow the data scientists to work with the data and build models. The collected data is cleaned (i.e., ensuring that the data collected is of high quality and exploitable by the model) by data scientists for pre-processing . The pre-processing phase consists first of filling the not available (NA) values (interpolation, average, median, etc.) before encoding the categorical variables into numerical values. Finally, it is ensured that time scales are appropriate for the problem at hand (if it is desired for predictions to be made for every hour of the day, data must be scaled to the hour). Moreover, for both models’ needs, structured data are converted into time series where possible, keeping in mind the static nature of some variables, such as material characteristics, which are constant over time. Model design and implementation Once the data pre-processing done, the types of models to be built must be selected. The models selected are the following: • A Recurrent Neuronal Network (RNN): to forecast the daily production of electricity from renewable energies. o This model was selected because of the known efficiency of these recurrent networks to make predictions for sequential data such as text, sound, or time 18 19 20 24 25 series. Several papers mention different experiments in which RNN, and in particular Long Short-Term Memory (LSTM), are efficient in forecasting electricity production. • A Seasonal AutoRegressive Integrated Moving Average with eXogenous variables (SARIMAX): to forecast consumers’ demand. o Auto-regressive models are very efficient for modelling a temporal 26 27 phenomenon. Publications expose the benefits of using SARIMAX models to forecast electricity consumption. This approach was chosen because consumer consumption prediction is less complex than meteorological forecasting or production forecasting, and seasonality and impacts of contrasting events such as weekends vs weekdays can be anticipated. This model does not necessarily need a neural network, which can be harder to build and heavier to put in production.

text: June 2023

text: For the prediction of consumer demand, the model's parameters are determined by statistical tests and analysis of the time series for the SARIMAX algorithm. The characteristics of the RNN input layer (e.g., batch size, time step, number of sequences/features) are defined. The output of the RNN consists of a real value corresponding to the consumer’s consumption for the next day. Model training, model testing and optimisation During the training method phase, model training is realised on-premises. The data is prepared to the same scale at which predictions are to be made. For our scenario, predictions will be made at the hourly level. During the training phase, data scientists collaborate with data engineers and the electricity supplier to improve their understanding of the data. The data is then divided in different categories for the needs of machine learning, 70% is used for training, 15% for validation and 15% for testing . Once the data is prepared, the data scientists choose and elaborate the models which will learn from the inputted data. In our case, two models are elaborated: the first to predict renewable energy production of the next day, the other to predict electricity consumption of the next day. The prediction of energy production from renewable energies is highly dependent on the weather and the environment in general. To be prepared for any eventuality, the electricity supplier must also train the model for extreme weather conditions. Model Evaluation To evaluate the model, metrics including Mean Absolute Error (MAE), Mean Squared Error (MSE) and Root Mean Squared Error (RMSE) are considered. Model Deployment Finally, the model deployment is done on-premises and the model can be used to predict the future values using new data. Once the model is ready, the data scientists, data engineers and network teams work together to industrialise the model. It is not only the model that is put to production, but all the pipeline work, from pre-processing the data to model evaluation. Deploying the environments necessary for its proper functioning: a pre-production environment for the model testing phases in real conditions and a production environment for later. Technically, this consists in creating flows: • between the data lake and the servers where the model is hosted with the data displayed earlier, • between the model servers and the existing dashboarding tool with only the prediction results. When the pre-production environment is stable, the model is put into production and it can be used through the dashboarding tool. From there, operation teams can now use the dashboard tool to adjust their power procurement decisions. The dashboard allows for a comparison of the results of the two predictions from the separate models and provides key performance indicators (KPIs) that help operation teams decide for the next day whether certain power plants should be turned on or whether energy generated from renewable sources can be stored. Monitoring and inference

text: June 2023

text: When monitoring, performance is measured every time that new data is acquired, comparing predictions to real data. Data engineers / scientists oversee monitoring of the models in addition to the distribution of the acquired data to infer any potential drift. As the scenario here has an impact on critical infrastructure, there cannot afford to be any underperforming results, even for a short period of time. Considering this, as predictions are made daily, it is reasonable to action weekly re-training of the models. Scheduling of model training processes on a weekly basis is done using a job scheduler. All processing pipeline and model training is automated. Through these automated tests and model evaluation, the model is continuously integrated into the production environment. Figure 8: Synthesis of the ML lifecycle and involved actors

text: Steps Description Actors Assets

text: Data is collected from various Data Engineer/Developers Data lake, Concentrator sources such as individual meters, public weather and demographics Electricity consumers Electricity supplier’s electrical Grid APIs or historical consumption and Electricity System Smart meters production data. They are placed in Electricity supplier's teams Data Collection a data pool on-premises before Open data provider APIs being manipulated. All data System and collected from the individual smart communication network’s Programming Libraries meters are anonymous after the administrator Integrated development concentrator and cannot identify the Open Data provider environment consumer.

text: Data Engineer/Developers Programming Libraries The data is cleaned. Useful data is Data Scientist Data lake, Model servers Data Cleaning recovered. Irrelevant or incorrect data is removed. Electricity System Integrated development Electricity supplier's teams environment

text: NA values from cleaned data are filled and all the categorical Data Engineer/Developers Programming Libraries variables are encoded into numerical values. The Data Scientist Data lake, Model servers

text: Data pre-processing

text: characteristics of the input layer of Electricity System Integrated development the algorithms are defined. Data that Electricity supplier's teams environment could identify the consumer is removed at the concentrator level.

text: Programming Libraries The model’s designs and Model design and parameters are determined by our Data lake, Model servers Data Scientist implementation needs, statistical tests, and analysis Integrated development of the time series. environment

text: Data is prepared to enable hourly predictions. Initial training is done Programming Libraries using 70% of the historical data and Data lake, Model servers Model training processed in regional data centres Data Scientist next to supervision centres. 15% of Integrated development the data is used for evaluation of the environment model.

text: Programming Libraries

text: 15% of the most recent data is used Data lake, Model servers Model testing Data Scientist for testing. Integrated development environment

text: Programming Libraries The hyperparameters of the model Data lake, Model servers are optimised through different Data Scientist Optimization techniques. Integrated development environment

text: June 2023

text: From a Machine Learning perspective, the model is evaluated Programming Libraries on dedicated data with metrics such as Mean Absolute Error or Mean Data lake, Model servers Data Scientist Squared Error. If the model’s Model evaluation Integrated development performance does not meet the environment required outcomes, previous steps must be repeated.

text: Data Engineer/Developers

text: Electricity System Data lake The model is put into production on Electricity supplier's teams dedicated servers and incorporated Model server, Dashboarding tool in a dashboarding tool. These System and Model deployment Integrated development servers are hosted on-premises. communication network’s environment administrator, Cloud provider

text: Data lake, Model server Data scientist The model, once in production, Dashboarding tool provides predictions to electricity Electricity System Concentrator suppliers. These predictions can be Electricity supplier's teams displayed via dashboarding tools or Electricity supplier’s electrical grid Monitoring and System and directly incorporated into existing inference communication network’s Smart meters tools for reuse. administrator Open data provider APIs

text: 2.8 PRIVACY AND CYBERSECURITY REQUIREMENTS Cybersecurity requirements The context information given in the previous section enables evaluation of the application’s cybersecurity and privacy requirements. The following table summarises the cybersecurity requirements. Figure 9: Cybersecurity requirements

text: Level Explanation

text: Predictions made by the model are made every day. An unavailability during half a week would be tolerable as old processes could be

text: Availability Low

text: reused until the application is back in service. Longer unavailability would be too time consuming for the Electricity supplier.

text: Data, whether used for training or made by the model, must be accurate with a high level of quality at all steps of the lifecycle. The alteration of the manipulated data can cause a very large imbalance Integrity Critical between the different means of energy production (non-renewable and renewable). Moreover, a poorly trained model could cause an underproduction or an overproduction of energies with very nonnegligible consequences.

text: Not all data is confidential, as some exists in the public domain. However, consumption information of individuals used in the context of Confidentiality Critical our scenario include personal data (upstream of the concentrator). This data is confidential and could highlight the behaviour of individuals whose information is retrieved.

text: Actions linked to the process must be logged (traced and dated) to enable full traceability of changes made to the algorithm. As personal Traceability High data is used in the process, actions linked must be imputable. i.e. all actions must be traced (even consultation actions) and attributable without possibility of repudiation.

text: June 2023

text: Privacy requirements The energy consumption of individuals, which contains personal data (name, address, phone number, etc.) is collected through smart meters. This data is processed in a concentrator so that only aggregated daily consumption values are routed to the data lake. This means there is no longer any personal data in the data lake because the sum of the data consumption of a concentrator does not permit individual consumption to be recognised. In this step it is crucial that this transformation from personal data to anonymised data is performed recognising the goals identified of the WP29 guidelines on anonymisation techniques (i.e., avoiding singling out, likability and inference) . It is important to note that the billing functions are not considered in our case, this topic being out of scope. Because our scenario handles personal data in the data collection phase, it is subject to the GDPR. The following data protection requirements and recommendations should be satisfied. Figure 10: Data protection principles Requirements Explanation

text: Personal data collected (both in training and in production) in the purpose of the scenario must be processed lawfully. That is, the data processing must be based on one of the legal bases provided by Article 6 of GDPR. In addition, individuals' personal data must be processed only in the way they reasonably expect, and any unexpected but justified processing must be clearly explained. Data processing must also comply with the transparency requirements. Lawfulness: for the specificities of this scenario, and as explained in its description, if the electricity supplier wants to extract the detailed consumption data of the users (consumption per hour or half hour), the electricity

text: Lawfulness, 31

text: supplier must obtain the consent of the consumers . If the user does not consent to the retrieval of this hourly

text: fairness, and

text: or half-hourly consumption data, the electricity supplier may retrieve his daily consumption data for legitimate

text: transparency

text: interest. The electricity supplier has a legitimate interest in at least retrieving consumers' daily consumption data. Without this data, the prediction of the users' energy demand is impossible. Fairness: even if the electricity supplier demonstrates that the data processing has a legal basis, it must only process personal data in line with consumers reasonable expectations, i.e., for the prediction of energy demand, and not use it in a way that has an unjustified negative effect on them. Transparency: the electricity supplier must also be transparent with consumers and clearly inform how and why their personal data are used throughout the machine learning lifecycle (for instance as part of the consumer agreement). Personal data collected (both in training and in production) needs to be processed for specific, explicit, and Purpose legitimate purposes and is not further processed in a manner that is incompatible with those purposes. This limitation means that the energy consumption collected and processed should only be used to predict the energy demand. Personal data collected (both in training and in production) needs to be adequate, relevant, and limited to what Data is necessary in relation to the purpose of predicting energy consumption demand by using Machine Learning. minimisation The electricity supplier should justify the data to be used and should indicate the procedures in place to ensure that only essential data such as electricity consumption is processed for this purpose.

text: June 2023

text: Personal data collected (both in training and in production) must be accurate and kept up to date. The electricity supplier, from the collection phase to the production phase, should put in place all appropriate measures to Accuracy promote data accuracy such as keeping the data up to date and ensuring that they remain correct. For example, putting in place a clear and straightforward process for consumers to update their addresses so that consumption data are always associated with the right locations. Personal data collected (both in training and in production) must be kept in a form which permits identification

text: Storage

text: of data subjects for no longer than is necessary for the purposes for which the personal data are processed.

text: limitation

text: Specifically, in our case, the personal data collected is anonymised before exiting the concentrator. Personal data collected (both in training and in production) must be processed in a manner that ensures Security of appropriate security, in particular integrity and confidentiality of the data. In our case, the risks from data personal data corruption are minimal for consumers (as a reminder, billing data is not in scope of our scenario), and we (Integrity and consider that the data extracted by the smart meter has no other purpose than the prediction of the energy demand). On the other hand, the electricity supplier must put in place adequate security measures to ensure

text: Confidentiality)

text: the confidentiality of the data, as the leakage of the latter can indicate the user's habits.

text: As a complement to the GDPR data protection principles listed above, other key privacy topics related to AI systems need to be addressed (some of which are specifically mentioned by national data protection supervisory authorities) : Figure 11: Data protection supervisory authorities’ recommendations for AI systems Recommendations Explanation

text: During the collection phase, the data passing through the electricity supplier network to the concentrator are personal data. A process aiming at deleting direct identifier and aggregate the consumption between all the consumer is made at the level of the concentrator. However, before this processing, data are stored

text: Database creation

text: in the database of the concentrator. The electricity supplier must ensure that only duly authorised persons have access to this data and prevent data loss. The electricity supplier must also ensure that only the right data (energy consumption) are injected into the concentrator. Compliance of the The electricity supplier must justify that the data it collects, the tools it uses and the training model it has training model chosen to achieve its objectives is relevant and free from bias. The electricity supplier must ensure that (i.e., before before the system is put into production, appropriate steps are taken to prevent discrimination and that a human electricity supplier can verify the quality of the algorithm's outputs.

text: production) Finally, the project requires a data protection impact assessment as it completes at least one criterion in the following table : Figure 12: Is a Data Protection Impact Assessment (DPIA) necessary?

text: Criteria Does it match the criteria? Justification

text: Evaluation or scoring

text: Automated decision making with legal or similar significant effect

text: The processing is not intended to do this. Nevertheless, the data collected may Systematic monitoring X allow to determine whether a person is present at home during certain time periods.

text: June 2023

text: Sensitive data or data of highly personal nature

text: Personal data related to energy Data processed on a large scale X consumption are used on a large scale by the electricity supplier.

text: Matching or combining datasets

text: Data concerning vulnerable data subjects

text: The use of artificial intelligence in this Innovative use or applying new X scenario: predicting energy production technological or organizational solutions capacity and demand is innovative.

text: Preventing data subjects from exercising a right or using a service or contract

text: To assess the risks in terms of privacy, personal data processing must consider the following requirements: Figure 13: Privacy requirements regarding data

text: Level Explanation

text: The data, for the user, does not necessarily have to be available. An

text: Availability Low

text: unavailability of several days is acceptable.

text: The output data of the concentrator is not considered as personal data. Indeed, at the concentrator output, it is the sum of the consumption data Integrity Low (from pseudonymised individual consumption data) that is transmitted to the data scientists. The alteration of this data has no influence on the users, such as a more expensive billing.

text: The personal data processed, in particular the detailed (hourly), is confidential. The leakage of such data (possible upstream of the concentrator) would be detrimental to the consumer since it would leak Confidentiality Critical his address for instance. Moreover, in case of data leakage from smart meters, it is possible to know the life habits of consumers and when they are present (high consumption) and when they are absent (low consumption) from home.

text: At a minimum, the actions related to the process must be recorded (traced and dated) to be able to follow the actors involved during the stages of use of personal data (upstream of the concentrator).

text: Traceability High

text: Particularly in the case of court cases, it is necessary to be able to attribute actions to an individual and to be able to impute them criminally.

text: June 2023

text: 3. SECURITY AND PRIVACY THREATS AND VULNERABILITIES

text: 3.1 THREAT CONTEXTUALISATION This section highlights the threats applicable in the forecasting demand on electricity grids scenario. Examples in the context of this scenario are also provided. Also outlined are the impacts that each threat can have in terms of security and privacy as well as their severity in the table. There are two major feared events to consider for our scenario which are the loss of integrity of the data, and the loss of confidentiality of the detailed electricity consumption of inhabitant data. The loss of integrity of the data could lead to an electrical production disruption. Indeed, the impact would be maximum if too little energy was produced, and there was insufficient energy supplied to meet demand. It should be noted, however, that the impact is lessened because the model only assists and does not make decisions directly. Decision-makers have other indicators with them to make decisions (minimum value of energy to be produced etc.). For the company, the loss of confidentiality of the detailed consumption of inhabitant data could lead to reputation degradation, which can result in loss of trust of the consumer. For the consumers, the loss of confidentiality of the detailed consumption could have 2 impacts. First, stolen personal data (home address, for example) could be used to perform phishing attempts or targeted advertising. Also, if detailed consumption of an inhabitant (either hourly or half hourly) were to leak, people would be able to identify whether the inhabitant is at home or not, and it could lead, depending on the case, to unwanted consequences such as robbery (a burglar might determine the hours at which a person is not a home using his energy consumption data), separation/divorce (much like phone bills or credit card details might contain data that the person would consider private, even from his or her spouse), or job loss (in the case where an employer uses energy consumption data ). Moreover, non-compliance with certain privacy requirements by the electricity supplier can lead to impacts on the user such as the significant feeling of invasion of privacy, feeling out of control of their personal data, or change in energy consumption billing if the data is processed for other purposes, besides the directly related with this case. Considering these feared events and associated impacts, the following threats are associated with our scenario.

text: June 2023

text: Before going into the details of the threats and vulnerabilities to which this scenario is subject, the following figure summarises all the threats that will be explained subsequently:

text: Figure 14: Summary of threats and vulnerabilities

text: 3.1.1 Compromise of ML application components An external attacker can directly compromise smart meters, the concentrator, or the API to retrieve weather or demographic data if they are exposed. If one of these components is compromised, the manipulated data can be modified, leading to an electrical production disruption. Data scientists, developers and the various stakeholders involved could have their workstations compromised by an external attacker (directly by using insecure code libraries, for example) which could compromise the ML components. The attacker would then be able either to modify the manipulated data, leading to an electrical production disruption, or steal confidential data (detailed consumption of inhabitant), leading to reputation degradation for the company, significant feeling of invasion of privacy, phishing attempts, or targeted advertising or even robbery, separation/divorce, or job loss for the consumers. 3.1.2 Poisoning During the data collection phase, an external attacker or a malicious user could compromise one or more smart meters (via a worm for instance) to create outliers which would then

text: June 2023

text: constitute historical consumption data. Once the model used to predict the next day consumption has been trained with such data, it could overestimate electricity consumption, leading to an electrical production disruption. In this idea of data modification and after having collected the data, any attacker with sufficient rights and access to the data lake could modify the training data to make the model operate with undesired characteristics, and could even render the model dysfunctional. This could lead to an electrical production disruption. 3.1.3 Human error A data engineer could route the consumption data from the concentrator to the data lake without aggregating and anonymising it. Such a threat could lead to a potential data disclosure which could entail reputation degradation for the company, a significant feeling of invasion of privacy, phishing attempts, or targeted advertising or even robbery, separation/divorce, or job loss for the consumers. 3.1.4 Data disclosure Throughout the scenario lifecycle, an attacker can try to compromise the concentrator to collect stored personal data relating to energy consumption, even where there is no data retention after sending the aggregated data to the data lake. This can be done by physical tampering with the concentrator, or by exploiting vulnerabilities through access to the electricity supplier's electrical network via its smart meters. Resultingly, an attacker with multiple smart meters connected to the electricity supplier’s electrical grid could directly attack other smart meters on the same network to collect consumption data. For the company, these data leaks can lead to reputation degradation. For the electricity consumers, they can lead to significant feeling of invasion of privacy, phishing attempts, targeted advertising, or even robbery, separation, or divorce and/or job loss. 3.1.5 Unlawful Processing There are two cases where two different legal bases should be applied. First, when the electricity supplier wishes to extract the energy consumption of the inhabitants on an hourly or half-hourly basis, it should ask for the users' consent, and proceed to process only when this consent has been given freely, clearly, specifically and knowingly by the user. Second, in the case of daily extraction, the electricity supplier extracts the consumption data based on legitimate interest. In the case where the electricity supplier was to collect data on an hourly or half-hourly basis without having obtained the user’s prior consent beforehand (or otherwise offering opportunity to withdraw consent), the impact on consumers would be a significant sense of invasion of privacy. Their data extracted without their consent would lead to a total lack of trust in the electricity supplier. In addition, the legitimate interest in the day-to-day processing of consumer data may not be adequately justified by the electricity supplier or worse, no justification may be provided. In this scenario, users may question the purpose of the use of their personal data and feel a significant feeling of invasion of privacy. 3.1.6 Unfair processing Even if the electricity supplier demonstrates that the data processing has a lawful basis (depending on the level of data extraction: daily or hourly), it might not process the personal data in the way consumers expect it to be i.e. for energy demand forecasting only. They could use it in a way that has an unjustified negative effect on them, such as unknowingly changing their billing based on consumption forecasts made by the algorithm.

text: June 2023

text: 3.1.7 Lack of transparency The electricity supplier may also not be transparent with users about how their personal data is used and the goal of the use of their data. The terms governing these aspects may not be included or may be deliberately omitted by the electricity supplier in, for example, the contract with its customers. The impact this could have on consumers could result in a feeling of being not in control of personal data. 3.1.8 Diversion of purpose The user data extracted in our case is intended to predict consumer energy demand. However, the electricity supplier may not respect this principle and use the consumer data for ambiguous and non-explicit purposes unrelated to the prediction of energy demand, such as using their data to offer other services or to resell them. For instance, users might be profiled based on their energy consumption and could receive targeted advertisements. Using this data to learn about users' routines and habits could be considered a serious invasion of users' privacy. In the wrong hands, this data could even be used against the physical security of consumers. An even more extreme diversion from the purpose of this information collection could facilitate the surveillance of users; the person in possession of the model and the data could examine the habits of the users to work out whether or not the consumer is at home. The impact this could have on consumers could lead to robbery, or separation/divorce, or job loss. 3.1.9 No respect of data minimisation This could materialise in the form of collecting more data than necessary at the smart meter level or by using more data than necessary at the hub level. For instance, smart meters could collect much more accurate data such as real-time consumption that can be used to track the consumer. The impact this could have on consumers could lead to a significant feeling of invasion of privacy, separation/divorce, job loss in case of data leakage or to potential phishing attempts, targeted advertising, or even robbery. 3.1.10 No respect of storage limitation Data extracted from smart meters of individual households are routed to the concentrator level and amalgamated. This means that no household specific data should be stored after amalgamation. Without clear rules for storing and removing personal data at the concentrator level, the electricity supplier could decide to store user data in the concentrator database for several months when it is not operationally justified. If this data were to be stolen or leaked, the impact to the user could be separation/divorce, job loss, potential phishing attempts, targeted advertising, or even robbery. 3.1.11 Synthesis of possible impacts and associated threats The following table sums up the severity of each impact and the associated threats. Figure 1: Synthesis of possible impacts and associated threats Impact Severity Type Associated Threats Electrical production High Cybersecurity Compromise of ML application components disruption Poisoning Reputation degradation High Cybersecurity Compromise of ML application components Data disclosure Compromise of ML application components Phishing attempts, Moderate Privacy Unlawful processing targeted advertising Unfair processing

text: June 2023

text: Robbery, Compromise of ML application components Separation/divorce, or High Privacy Unlawful processing job loss Unlawful processing Unfair processing Significant feeling of lack of transparency Moderate Privacy invasion of privacy Diversion of purpose No respect of data minimization No respect of storage limitation Not being in control of Lack of transparency Moderate Privacy personal data Change of consumer High Privacy Unfair processing billing 3.2 VULNERABILITIES ASSOCIATED TO THREATS AND AFFECTED ASSETS This figure cross evaluates each threat to a set of associated vulnerabilities. The actors involved and the assets possibly affected by the vulnerabilities are also highlighted: Figure 2: Mapping vulnerabilities to threats and assets/actors on which they rely

text: Vulnerabilities Threats Actors Assets involved

text: Unlawful processing

text: Unfair processing

text: Lack of transparency Absence of an identified Diversion of purpose Electricity supplier's teams Data

text: data controller

text: No respect of data minimization

text: No respect of storage limitation

text: Absence of mechanisms Smart meters

text: to ensure that processing

text: of consumer electricity Concentrator Unlawful processing Electricity supplier's teams

text: affected by consent

text: Electricity supplier’s electrical

text: cannot be carried out

text: grid

text: without consent

text: Disclosure of sensitive

text: data for ML algorithm Data disclosure Data scientists Model

text: training

text: Model

text: Existing biases in the ML

text: Diversion of purpose Data scientists model or in the data Data

text: No respect of data Electricity supplier's teams Data

text: Lack of anonymisation

text: minimization Data engineers Concentrator

text: Unlawful processing Electricity supplier's teams

text: Unfair processing Data scientist Lack of auditability of Lack of transparency Developers and data processing engineers Diversion of purpose N/A No respect of data System and communication minimization network administrators

text: June 2023

text: No respect of storage limitation

text: Lack of control for

text: Poisoning Data Scientists Model

text: poisoning

text: Lack of control of Data

text: 36 Diversion of purpose Electricity supplier's teams Data

text: processor

text: Lack of controls to ensure Smart meters that data is used only for Diversion of purpose Electricity supplier's teams the purposes defined Concentrator

text: Lack of controls to ensure

text: Smart meters

text: the adequacy of the

text: Diversion of purpose Electricity supplier's teams purpose and its current Concentrator

text: use

text: Lack of data deletion No respect of storage Electricity supplier's teams Data mechanisms limitation

text: Electricity supplier's teams

text: Lack of data for

text: increasing robustness to Poisoning Data engineers and Data poisoning developers

text: Lack of data retention No respect of storage Electricity supplier's teams Data policy limitation

text: Unlawful processing

text: Lack of detail on the

text: purposes and justification Unfair processing Electricity supplier's teams N/A

text: for their legitimacy

text: Lack of transparency

text: Human error

text: Unlawful processing Electricity supplier's teams Unfair processing Data scientists Lack of transparency Lack of documentation Developers and Data N/A Diversion of purpose Engineers

text: No respect of data System and communication minimization network administrators

text: No respect of storage limitation

text: Unlawful processing

text: Lack of justification for

text: the collection of Lack of transparency Electricity supplier's teams Data

text: individual personal data

text: No respect of data

text: collected

text: minimization

text: Lack of legal basis related to users' consent when their detailed consumption data (per hour or half hour) are processed or that

text: Unlawful processing Electricity supplier's teams N/A

text: legitimate interest related to the daily processing of the data is not properly justified or that no justification is provided at all

text: June 2023

text: Lack of measures to

text: No respect of data prevent further data Electricity supplier's teams Data minimization

text: collection

text: Electricity supplier's teams

text: Lack of necessary data No respect of data Data scientist Data selection minimization Developers and data engineers

text: Lack of practical means and justification for obtaining the consents of the electricity consumers

text: concerned (those who have a halfhourly view of their electricity consumption)

text: Compromise of ML application components

text: Poisoning Electricity supplier's teams All assets

text: Lack of security by design

text: Human error

text: Data disclosure

text: Unlawful processing

text: Unfair processing

text: Lack of transparency Lack of privacy by design Diversion of purpose Electricity supplier's teams All assets

text: No respect of data minimization

text: Diversion of purpose

text: Data lake

text: Open-data provider APIs

text: Smart meters

text: Concentrator

text: Lack of security process Model server Compromise of ML

text: to maintain a good

text: application components Dashboard tools security level of the Electricity supplier's teams components of the Data disclosure Electricity supplier’s electrical Electrical forecast system grid

text: Integrated Development Environment

text: Programming Libraries Communication protocol and communication Networks

text: Unlawful processing

text: Unfair processing Smart meters

text: Lack of traceability of

text: Lack of transparency actions and/or Electricity supplier’s electrical Electricity supplier's teams modifications made to the No respect of storage grid assets limitation Concentrator Compromise of ML application components

text: Lack of transparency on

text: the purpose of the Lack of transparency Electricity supplier's teams N/A

text: processing, the exact consumption data that are

text: June 2023

text: extracted, and how they are processed.

text: Lack of verification that the data is adequate,

text: relevant and not No respect of data Electricity supplier's teams Data excessive for the purpose minimization

text: of estimating electricity consumption

text: Electricity supplier's teams

text: Data scientists Model easy to poison Poisoning Model Developers and data engineers

text: Electricity supplier's teams

text: No detection of poisoned

text: Data scientist samples in the training Poisoning Data dataset Developers and data engineers

text: Data lake

text: Open-data provider APIs

text: Smart meters Compromise of ML application components Concentrator Poor access rights Poisoning Model server Electricity supplier's teams

text: management process

text: Data disclosure Dashboard tools

text: Human error Electricity supplier’s electrical grid

text: Integrated Development Environment

text: Poisoning

text: Data disclosure Diversion of purpose Data scientists Poor data management Developers and data Data No respect of data engineers minimization

text: No respect of storage limitation

text: Compromise of ML Electricity supplier's teams

text: Excessive information

text: Model available on the model application components Data scientist

text: Electricity supplier's teams

text: Data scientists Unprotected sensitive Developers and Data Data disclosure Data data on test environments Engineers

text: System and communication network administrators

text: Poisoning

text: No respect of data Electricity consumers Use of uncontrolled data minimization Data engineers Data No respect of storage limitation Open-data providers

text: Use of unsafe data or Electricity consumers, models (e.g., with transfer Poisoning Data learning) Open-data providers

text: June 2023

text: Data lake

text: Open-data provider APIs

text: Smart meters

text: Concentrator Electricity supplier's teams Model server Data scientist

text: Use of vulnerable

text: Compromise of ML Dashboard tools components (Among the Developers and data application components whole supply chain) engineers Electricity supplier’s electrical grid Open-data providers Integrated Development Environment

text: Data lake,

text: Open-data provider APIs

text: Smart meters Compromise of ML

text: Weak access protection

text: application components Concentrator

text: mechanisms for ML

text: model components and Poisoning Model server Electricity supplier's teams

text: for personal data

text: (encryption, access Data disclosure Dashboard tools

text: control mechanism…)

text: Integrated Development Environment

text: June 2023

text: 4. CYBERSECURITY AND PRIVACY CONTROLS

text: Before expanding on the details of the cybersecurity and privacy controls applied to the scenario, the following figure summarizes all the controls that will be described: Figure 17: Summary of cybersecurity and privacy controls

text: June 2023

text: 4.1 IMPLEMENT A SECURITY BY DESIGN PROCESS

text: Type Associated Vulnerabilities Threats it mitigates • Compromise of ML application components Cybersecurity Lack of Security by Design • Poisoning • Human error • Data disclosure

text: By default, Security by Design is a methodology to strengthen the cybersecurity of the organisation by automating its data security controls and developing a robust IT infrastructure. This approach focuses on implementing the security protocols from the basic building blocks of the entire IT infrastructure design. The goal of this control is to ensure that risks are identified as early as possible, mitigated before systems go live, and appropriate security controls are implemented. The lack of Security by Design increases the likelihood of all threats related to our case. Therefore, the electricity supplier must ensure, from the development phase, to put in place adequate controls to limit the cybersecurity risk. This starts with a global risk analysis in which all risks associated with all assets are identified. In our case, the electricity supplier will try to reduce the attack surface (for example by updating the smart meters' operating system continuously), to apply the principle of least privilege (by implementing access rights management), to take care of the confidentiality and integrity of the collected data (by encrypting the users' consumption data for example). Conceiving a project following a Security by Design methodology requires less effort than adding security on top of an existing project. However, there could be an impact on the functionality of the use if the outcome of the Security by Design methodology would lead to some functionality not being implemented due to the security risk it generates (e.g., installation of unsecure smart meters). 4.2 DOCUMENT THE ELECTRICAL FORECAST SYSTEM

text: Type Associated Vulnerabilities Threats it mitigates

text: • Human error • Unlawful processing • Unfair processing Cybersecurity Lack of Electrical forecast system documentation • Lack of transparency & Privacy • Diversion of purpose • No respect of data minimisation • No respect of storage limitation Project and system documentation must be produced to preserve knowledge on decisions made during the project phase, application architecture, configuration, maintenance, ability to maintain effectiveness over time, and assumptions made about the model’s use. The system is complex with multiple assets (Open-Data provider, smart meters, concentrator, etc.) which enhance the fact that an exhaustive documentation is mandatory for all assets. This documentation should also include the changes that will be applied, including to the documentation throughout the system life cycle. Therefore, it is necessary that the Open-Data Provider, Data Scientists, Developers, Data Engineers, and System and communication network administrators work together to create and sustain the documentation.

text: June 2023

text: This control does not impact system performance, cybersecurity, or privacy. 4.3 CHECK THE VULNERABILITIES OF THE ML COMPONENTS AND IMPLEMENT PROCESSES TO MAINTAIN THEIR SECURITY LEVELS OVER TIME

text: Type Associated Vulnerabilities Threats it mitigates • Use of vulnerable components • Compromise of ML application Cybersecurity • Lack of security process to maintain a components & Privacy good security level of the components of • Data disclosure the Electrical forecast system

text: For smart meters and the concentrator, it is necessary for the company to ensure that regular security audits are carried out to ensure there are no vulnerabilities. Regular vulnerability scans and automatic patch management processes should also be implemented to maintain a good security level. Preparation of a remediation plan that can be implemented quickly must be committed to, with the capacity to review this plan over time. One differentiating factor for smart meters is that they can be considered as IoT devices, for which audits need specific expertise. Although these devices are connected to the network as regular devices, they also have an interface with the physical world. In our case, smart meters interface with the consumer’s electrical system, which could be a source of vulnerability. For Open-Data provider APIs, it is necessary to define a process to ensure that the level of Open-Data provider security is sufficient over time to avoid data recovery. This could mean an annual audit of the APIs and the completion of an annual security questionnaire. This control would have an impact on the availability of the system, and thus its performance, as it may be audited or updated. This could lead to periodic unavailability of the system for several hours at a time. However, as the availability need of the system is low, the impact of this control is only moderate. Moreover, updates could cause the system to malfunction, leading to errors in the prediction systems that could have a major impact. 4.4 CHOOSE AND DEFINE A MORE RESILIENT MODEL DESIGN

text: Cybersecurity Model easy to poison Poisoning Poisoning of the model could cause electrical production disruption, which would have a high impact for the company. For this reason, the company needs to ensure that the model is fully resilient against this type of attack. For the electrical forecast system, a methodology to harden the system against poisoning threats could be use of the “Bagging” (bootstrap aggregating) technique . This is a machine learning ensemble meta-algorithm designed to improve the stability and accuracy of machine learning algorithms, which combines several versions of the model (e.g., models trained with

text: June 2023

text: different datasets) to limit the impacts related to the poisoning of one of the models. In this case, the company could generate multiple models from different data sets (weather data and consumption of each different years for example) and use a Bagging algorithm with these models to predict the consumption of electricity. If an attacker were to succeed in poisoning one of the models, the effect on the outputs of the system would be greatly reduced, or even mitigated completely, due to the prediction also relying on the other healthy models. This could have an impact on performance of the model as the most representative data is from the most recent year, and using data from previous years would make the prediction less accurate. 4.5 INTEGRATE POISONING CONTROL IN THE TRAINING DATASET

text: Type Associated Vulnerabilities Threats it mitigates • No detection of poisoned samples in Cybersecurity the training dataset Poisoning • Lack of control for poisoning

text: In addition to the previous control, and to reduce to a minimum the probability of the models being poisoned, the training dataset should be checked for poisoning. The RNN algorithm used in our scenario can be checked for poisoning using the STRIP technique. This principle relies on disturbing the inputs and observing the randomness of the predictions. For example, the company could change 1 week of weather data, replacing summer data with winter data, and observe the variance in predictions versus unperturbed. Without high variance, the model could be considered as poisoned. These tests should be performed before the production phase, during the training phase, ensuring that the models used in production are healthy. This control doesn't have impact on system performance, cybersecurity, or privacy. 4.6 ENLARGE THE TRAINING DATASET

text: Lack of data for increasing robustness to Cybersecurity Poisoning poisoning Large timeframes (multiple years) of weather data can be collected and used to train the algorithm to prevent it being susceptible to poisoning attacks. Modifying small amount of weather data would then have a low impact of the overall prediction. Using large timeframes (multiple years) of inhabitant consumption data could also reduce the probability that poising attacks on this data could impact the prediction. This could still have an impact on the model accuracy, considering that weather systems can shift over long timeframes too, but considering the high impact of disruption to electrical production, this control should still be implemented. Long timeframes of consumption data would not impact consumer privacy as any stored data would be the anonymised after the concentrator.

text: June 2023

text: 4.7 SECURE THE TRANSIT OF THE COLLECTED DATA

text: Cybersecurity Poor data management Poisoning Considering the possible impacts of Poisoning, the transit of the collected data should be fully protected against a loss of integrity. Within the collection phase of weather data or inhabitant consumption data, the electrical company should ensure that protocols used for the transfer of data are encrypted and otherwise state of the art (without any known vulnerabilities), such as TLS 1.3. As such, an attacker would not be able to modify the data during transit, and would not be able to poison the model through that route. Generally, Open-Data suppliers comply with this level of requirement. This control would not impact on privacy or performance of the system. 4.8 CONTROL ALL DATA USED BY THE ML MODEL

text: Cybersecurity Use of uncontrolled data Poisoning Considering the high impacts of Poisoning attacks, several means to control the data must be applied, some specific to data science and others more to business- common-practice. These techniques can be applied at the concentrator level and then in the data lake. At the concentrator level, the incoming data is not yet aggregated, so an initial check can be carried out to avoid inconsistent data. There are two common cases of inconsistent data – inconsistency of data type (e.g., alphanumeric vs number) and inconsistency of data value. To prevent this, checks should be performed for the two different cases. An example of an inconsistent value would be to determine whether a consumption figure is abnormally high in relation to previous data, contract data, data from other consumers. Once abnormal data is detected, it can be readjusted before following the data aggregation procedure to the data lake. At the data lake level, more controls can be carried out: • Non-technical checks such as checking the overall consistency of the data (for example checking variability of the weather data) • Technical checks specific to data science and the data sanitisation process to detect possible anomalies (otherwise known as outlier detection).

text: June 2023

text: This control could add latency to the system in case of many reported anomalies on the data. But our scenario does not have a strong need for availability, and the control is important to reduce the probability of model poisoning. The checks that are applied at the concentrator level could have an impact on privacy, because they would manipulate personal data from consumers. To remediate, the systems (software, scripts, excel sheets, etc.) used to perform these checks should be regularly audited, documented, secured by design, and follow access control rules (authentication to use the system, proper access management, etc.). 4.9 ENSURE RELIABLE SOURCES ARE USED

text: Use of unsafe data or models (e.g., with transfer Cybersecurity Poisoning learning) Considering the possible disruption of electrical production due to poisoning attacks, it is mandatory for the company to ensure the reliability of the sources used to collect the data. For weather and demographic data, which is collected from an Open-Data Provider, this should be of a reliable standard, ideally audited once a year to ensure that it doesn’t have any vulnerability that could lead to a loss of integrity of the data. Moreover, and considering the criticality of the poisoning threat, the data can be crossed between several sources to reduce the impact when one of the sources is compromised. However, crossing data from multiple sources could introduce errors within the data set which could alter the model and its performance. Our scenario does not have a strong need for availability. 4.10 IMPLEMENT ACCESS RIGHT MANAGEMENT PROCESS

text: Type Associated Vulnerabilities Threats it mitigates • Compromise of ML application components Cybersecurity Poor access rights management • Poisoning & Privacy • Data disclosure • Human error

text: Threats related to poor access rights management, such as data disclosure, can have a high impact on the company (electrical production disruption) or on the consumers (robbery, separation/divorce or job loss). This security measure defines and assigns roles to users, respecting the principle of least privilege, and limits the access scenarios for processes and assets only to those for which the users have a justified reason. For all the classical systems of our scenario, such as Concentrator, Data lake, Model server, Dashboard tools, and Integrated Development Environment, it is essential to create roles for each user group with associated access rules. These work alongside a process for providing access only to the actors that need it, and to prevent access to unauthorised persons. Each role must respect the principle of least privilege, in particular the roles that can connect to the concentrator as they allow access to all the consumption data and associated personal data. By default, only administrators and data engineers would have this access. It is also very important

text: June 2023

text: to have a process for modifying or revoking user access in timely manner, as long processes for access management generally result in neglect by an organisation. Considering the high volume of smart meter devices, the administration account would likely need to be generic, with the account password stored within an administration Bastion. Then, only mandated electricity supplier’s teams would have the ability to have access this Bastion and connect to the smart meters. In case of an incident or failure, the complexity of the management of these accesses, particularly for the smart meters, could prevent teams from accessing the system to correct potential problems, which could impact the availability of the system, thus its performance. 4.11 ENSURE ALL SYSTEMS AND DEVICES COMPLY WITH AUTHENTICATION, AND ACCESS CONTROL POLICIES

text: Type Associated Vulnerabilities Threats it mitigates • Weak access protection mechanisms for • Compromise of ML application machine learning model components components Cybersecurity • Weak access protection mechanisms of • Poisoning & Privacy the personal data (encryption, access • Data disclosure control mechanism…) • Human error

text: In this control there must be a distinction made between user access and device access. For user access, the Electrical Company must ensure that proper user authentication and access controls regulate access to Smart meters, the Concentrator, the data lake, the Model server, the Dashboard tools, and the Integrated Development Environment. Such access authentication and access control should be managed centrally, with a dedicated solution (e.g., Active Directory) linked to all these assets, except in the case of smart meters, where authentication should remain local due to the high volume of devices. Moreover, for sensitive assets manipulating personal data, such as the concentrator, the electrical company should implement multi-factor authentication for the data engineers and administrators that are granted access. The multi-factor authentication solution must be linked to the central authentication system. For device access, the electrical company should ensure that all device-to-device requests are properly authenticated. To deal with threats, it is important to use good market practices. For example, use of the OAuth 2.0 protocol for all exposed APIs with control via an API gateway. In addition, the certificates for the authorisation server keys should be managed through the company's own Public Key Infrastructure in order to avoid any identity theft scenario. It is also necessary to respect an authentication policy (based on the current recommendations of bodies 38 39 such as ENISA or NIST ) for the authentication of devices on the authorisation server. To protect the secrets in the smart meters, it is necessary to secure them by ensuring that their OS version is up-to-date, and that non-essential ports are closed, amongst other factors. To protect access to the company electric network via smart meters, it is necessary to carry out Network access control with good practices . However, in case of an incident or a failure, the complexity of the authentication, especially for the smart meters, could slow down the remediation of the problem (for example if administrators had trouble authenticating on the system due to the reinforced authentication) and have an impact on the of availability of the system, thus its performance. Additionally, personally authenticating the employees on the system can have an impact on privacy, because personal data (identifiers, mail addresses, etc) would be recorded in these

text: June 2023

text: authentication systems. These authentication systems must respect the principles of Article 5 of the GDPR (data minimisation etc). 4.12 REDUCE THE AVAILABLE INFORMATION ABOUT THE MODEL

text: Type Associated Vulnerabilities Threats it mitigates Cybersecurity Too much information available on the model Compromise of ML application components & Privacy

text: This control lowers the likelihood of Compromise of ML application components by limiting the knowledge of a malicious user about his target and consequently making it more difficult to launch a cyberattack. It is important to understand that this security control alone is not enough, as security by obscurity does not provide sufficient protection. Therefore, all documentation concerning the model itself should be protected. They should be encrypted and protected by a Data Right Management mechanism, allowing only the Data Scientists to access them from their computers. Specifically, the documentation can be stored in a dedicated file server directory to which access rights are regularly reviewed and linked to the access rights management mechanisms described in 4.10 and 4.11. This server must be encrypted by default and located in a network zone dedicated to the company's sensitive resources. In addition, user workstations accessing this file server must be sufficiently protected. In addition to the rights management mechanisms, it is necessary to provide, at least, encryption of the workstations, a confidentiality filters fitted to the screens of workstations in nomadic situations, and securing (OS version up-to-date, closure of non-essential ports etc) of the workstation to prevent the opening of certain ports and the insertion of USB keys. In addition, to avoid the propagation of documents relating to the model, it is recommended that a data loss protection solution be deployed. This control could have an impact on privacy aspect because it may be considered as a contradiction to the principle of transparency required by the GDPR. Therefore, it is important to define documentation that can be communicated to external users (i.e., customers), explaining that their data is not directly used by the model. Moreover, this control could impact the performance of the system, because in case of an incident or a failure, the complexity of the access management could prevent data scientists to have access to the documentation to correct the problem and have an impact of availability of the system, thus its performance. 4.13 IDENTIFY A DATA CONTROLLER FOR THE ENERGY CONSUMPTION ANTICIPATION DATA PROCESSING

text: • Unlawful processing Privacy Absence of an identified data controller • Unfair processing • Lack of transparency Identifying a data controller is essential to prevent various high impacts for the company and its employees due to unlawful processing, unfair processing, or lack of transparency. Selfidentifying as the data controller means performing accountability actions (documentation, assessments, etc.) and making sure that the energy consumption anticipation data processing is compliant with personal data protection GDPR obligations and does not infringe on privacy rights of data subjects. Self-identifying as the data controller means also taking responsibility in case of non-compliance or adverse privacy effects on data subjects.

text: June 2023

text: Such a measure does not have a negative impact in our case. On the contrary, it improves the privacy of users without impacting the performance of the system or its security. 4.14 PROPERLY COLLECT AND MAINTAIN USER CONSENT WHEN NEEDED FOR DETAILED ENERGY CONSUMPTION USAGE

text: Type Associated Vulnerabilities Threats it mitigates • Absence of mechanisms to ensure that the processing of consumer electricity affected by consent cannot be carried out without consent • Lack of legal basis related to user’s consent when their detailed consumption data (per hour or half hour) are processed or that the Privacy Unlawful processing legitimate interest related to the daily processing of the data is not properly justified or that no justification is provided at all • Lack of practical means and justification for obtaining the consent of the electricity consumers concerned

text: When the electricity supplier wants to extract the energy consumption of the inhabitants on an hourly or half-hourly basis, it should ask first for the users' consent and go on with the processing of the granular data only when this consent has been given. This means that there must be an opt-in function in the user interface (e.g., a checkbox) provided by the energy electricity supplier that the consumers must actively check (opt-in) to agree to provide their detailed energy consumption. Then, the consent of each user would be stored within a dedicated database belonging to the company and used accordingly for the collection (or not) of detailed consumption data. It is as important to ensure that when a subject revokes their consent, their detailed consumption data is no longer processed. However, when this control is properly implemented, it is easier for data subjects to withhold consent for use of their personal data. Therefore, the data collected could be less rich with proper consent management and could be limited to daily energy consumption for a larger number of data subjects. In addition, there is a (relatively small) additional cost to implementing proper consent management. This measure impacts on security, because the company must protect not only the energy consumption data that the user gives with his consent but also the storage of the consent over time in a dedicated and secure space. The collection and storage must have a level of security adapted to the principles of non-repudiation (encryption of the data, traceability of access to the equipment, signatures via daily private keys in the database of the dedicated space, etc.). 4.15 ANONYMIZE DATA COMING FROM THE CONCENTRATOR

text: Privacy Lack of anonymization No respect of data minimization The data that could identify consumers are anonymised at the concentrator level. Anonymisation requires an analysis to correctly identify a subset of fields that irreversibly prevents re-identification of data subjects and should be performed as early in the processing as possible. After this identification, a dedicated solution can be used to anonymise the data. It should also be remembered that the collected data are deleted in the concentrator after the aggregation of all data from different households.

text: June 2023

text: In this case the data that need to be anonymised at the concentrator level is the Energy consumption of inhabitants containing these fields [surname, first name, address, meter number, telephone number, electricity consumption]. After anonymisation, the remaining fields should be [city, electricity consumption], with the city field being derived from the address of the concentrator and the electricity consumption being the sum of consumption by all customers associated with the concentrator. This is the data that is sent to the data lake. In this case, in the event of a security breach, it may be more difficult to perform a cybersecurity forensic analysis on anonymised data than on personally identifiable data. This has the impact of significantly slowing down the work of those employed to determine the cause of a security issue. Ultimately, finding security measures for these kinds of vulnerabilities would also create other security challenges. 4.16 GENERATE LOGS AND PERFORM INTERNAL AUDIT

text: Type Associated Vulnerabilities Threats it mitigates • Unlawful processing • Unfair processing • Lack of auditability of processing • Lack of transparency Cybersecurity • Diversion of purpose • Lack of traceability of actions and/or & Privacy • No respect of data minimization modifications made to the assets • Compromise of Machine Learning application • No respect of storage limitation

text: Generating logs and performing internal audit allows for improvements in supervision of all assets of the model, creating a better understanding of the decisions made in real time by the algorithm. This also helps in understanding individual incidents, whilst auditing internal processes and questioning the processing carried out in the frame of the project reduces the likelihood of many threats in this scenario. Therefore, the process must be auditable in the sense that certain questions must always be answered clearly: Who accessed the data (especially at the concentrator level)? Why did the algorithm make a particular decision? How exactly was the data processed? To this end, the technical and organisational parts of the process must generate traces (computer logs, activity reports, etc.) so that they can be audited. These logs should be stored in a dedicated tool, such as a log management solution. The logs provided by the equipment must be signed (using their own private key) and their signature stored by the server that centralises the logs to ensure a principle of non-repudiation. In addition, at each (usually daily) backup of the log server, these backups must also be signed by the log sink to ensure once again the principle of nonrepudiation. Moreover, these logs should be analysed by a SOC and rules should be defined to detect such anomalies as many calls from a smart meter to the concentrator or an abnormal response. In addition, all processes must be regularly audited by the company's internal control teams to ensure compliance with the requirements. As far as privacy is concerned, these audits should at least ensure the lawfulness of the processing, its transparency, its application, the data minimisation, the respect of the storage limitation and the fairness aspect. These checks should be based in part on the logs collected. This control could have an impact on privacy because the generated logs can contain personal data. This log management system should be included in the privacy impact assessment scope of the system. Moreover, the logging system should be carefully implemented to avoid unnecessary overhead due to the extra operations it executes. 4.17 PERFORM A PRIVACY IMPACT ASSESSMENT

text: June 2023

text: • Lack of controls to ensure that data is used only for the purposes defined • Diversion of purpose • Lack of controls to ensure the adequacy of the • Unlawful processing Privacy purpose and its current use • Unfair processing • Lack of detail on the purposes and justification • Lack of transparency for their legitimacy

text: This privacy measure allows for an in-depth analysis of the impact of the processing on the privacy of users, compliance with the GDPR and to identify whether the associated risks are well addressed by the proposed privacy and security measures. The privacy impact assessments and general accountability actions described above (in the internal audit process control) help ensure that the purpose of the processing is well defined (the prediction of residents' consumption) and that the actual use of the data remains within the scope of this case. To do so, the electricity supplier should use the requirements described below, and asses the vulnerabilities of the implemented system, to illustrate privacy threats and counter measures. Such analysis may possibly impact the performance of the scenario if it results in one of the functionalities not allowing to minimise the data protection risks to the rights and freedoms of natural persons. 4.18 DEFINE AND IMPLEMENT A DATA RETENTION POLICY

text: • Lack of data deletion mechanisms Privacy No respect of storage limitation • Lack of data retention policy

text: This privacy control requires a storage duration value to be defined for each personal data involved in the processing, including individual detailed consumption data, individual daily consumption data etc. When this storage duration value is implemented, the privacy control acts to minimise the risk of keeping the data longer than it is strictly necessary. One way to implement it is by having a script that automatically deletes the data based on predefined criteria. However, once all that data is deleted, it cannot be used later for forensic analysis, as may be required when a company faces a security breach. 4.19 STUDY ON DATA FIELDS NECESSITY AND JUSTIFICATION IN THE PRIVACY POLICY

text: Type Associated Vulnerabilities Threats it mitigates • Lack of justification for the collection of individual personal data collected • Unlawful processing Privacy • Lack of transparency on the purpose of the • Lack of transparency processing, the exact consumption data that • No respect of data minimization are extracted, and how they are processed.

text: A lack of justification on how data are collected, correlated with a lack of transparency on the purpose of the processing or on the accuracy of the data collected could result in unlawful processing which would have moderate impact for the consumer (significant sense of invasion

text: June 2023

text: of privacy). Therefore, the electricity supplier must study the necessity of different data fields and justify this in the privacy policy. The personal data used is the consumption data (daily or hourly) of the inhabitants. The electricity supplier must therefore implement a privacy control in which they could explain why it is necessary to use this data specifically in the context of this scenario. The supplier must also formalise the explanation and make it freely available to consumers. Nevertheless, this practice may have some impact on the relevance of the data collected. Taking time to justify the need for data may lead to the abandonment of the collection of some data for which justification is difficult, which in turn, may reduce the quality of the data at hand. 4.20 FORMALISE A LIA (LEGITIMATE INTEREST ASSESSMENT)

text: Privacy Lack of legal basis related to legitimate interest Unlawful processing The Legitimate Interest Impact Assessment (LIA) is used to determine if an organisation can process data using the legitimate interest lawful basis. In our case, the legal basis for the extraction of daily consumption data is legitimate interest. If the electricity supplier does not justify this legal basis, it faces unlawful processing. To justify the legal basis, the electricity supplier must put in place a LIA. In this LIA, the electricity supplier must formalise a reflection on how the data processing is necessary, and how it balances with the rights and freedoms of consumers. The impact this could have on the electricity supplier would be a loss of time and energy spent formalising the LIA. 4.21 MINIMISE DATA AT EACH STEP OF THE PROCESSING; COLLECT ONLY WHAT IS NEEDED WHEN NEEDED

text: Type Associated Vulnerabilities Threats it mitigates • Lack of necessary data selection • Lack of verification that the data is Privacy adequate, relevant, and not excessive for No respect of data minimisation the purpose of estimating electricity consumption

text: Minimisation requires an analysis to correctly identify the subset of fields which are required, and should be performed as early as possible during processing. Non-minimisation of data is the lack of selection of necessary, adequate, and relevant data. For example, in our case, the electricity supplier only requires the consumption data of individuals. The electricity supplier extracts two types of consumption data: the daily consumption and the consumption at the half-hour scale. A study on the necessity of collecting data at the hourly scale must be done and a proof of its necessity made public. Then, the

text: June 2023

text: extracted individual data should be anonymised at the hub level and aggregated with other data from other households before being sent to the model. However, data minimisation also involves data anonymisation. In this case, in the event of a security breach, it may be more difficult to perform a cybersecurity forensic analysis on anonymised data than on personally identifiable data. This has the impact of significantly slowing down the work of those employed to determine the cause of a security issue. 4.22 IMPLEMENT A PRIVACY BY DESIGN PROCESS

text: Type Associated Vulnerabilities Threats it mitigates • Unlawful processing • Unfair processing Privacy Lack of Privacy by Design • Lack of transparency • Diversion of purpose • No respect of data minimization

text: The electricity supplier must ensure that a compliance study and privacy risk assessment is formalised in a Privacy Impact Analysis document, and that the identified action plan is implemented before the scenario is put into operation. Conceiving a project following a Privacy be Design methodology requires less effort than adding privacy on top of an existing project. However, there could be an impact on the functionality of the scenario if the outcome of the Privacy by Design methodology leads to functionality not being implemented due to the privacy risk it generates (bear in mind that in our case, personal data is anonymised and then aggregated and deleted at the concentrator). Another impact of note is related to security, as it may not be possible to collect data useful for forensic analysis following a cyber-attack due to privacy limitations. 4.23 RAISE AWARENESS OF SECURITY AND PRIVACY ISSUES AMONG ALL STAKEHOLDERS

text: Type Associated Vulnerabilities Threats it mitigates • Poisoning • Data disclosure • Unlawful processing Cybersecurity Lack of consideration of attacks to which the • Unfair processing & privacy energy forecasting system could be exposed • Lack of transparency • Diversion of purpose • No respect of data minimization

text: There are many threats with high impact in this scenario, and the company must ensure that such threats are comprehended by the teams. For instance, the company must ensure that all its teams (including Data Scientists) are trained in the specificities of machine learning and the new associated cyber and privacy risks. This can take the form of regular training sessions or local cyber and privacy risks reporting. This raises awareness of issues to teams, and in some cases can present solutions tailored to the specificities of forecasting demand on electricity grids scenario. This control does not directly impact performance of the system.

text: June 2023

text: 4.24 SUMMARY The following table summarises every control described in the previous section. Each control is associated with vulnerabilities, mitigated threats, and addressed privacy and security requirements. Figure 18: Summary of controls and mitigated threats

text: Control name and Privacy and security requirements Associated Vulnerabilities Threat mitigated type addressed

text: Compromise of ML application Integrity of the data components Implement a Availability of the data Lack of Security by Design Poisoning

text: Security by Design

text: process Confidentiality of the data Human error Traceability of the data Data disclosure

text: Integrity of the data

text: Availability of the data

text: Human error Confidentiality of the data Unlawful processing Traceability of the data

text: Unfair processing Lawfulness of the process

text: Document the

text: Lack of Electrical forecast system Electrical forecast Lack of transparency Fairness of the process documentation

text: system

text: Diversion of purpose Transparency of the process

text: No respect of data minimization Purpose limitation of the process

text: No respect of storage limitation Data minimization of the process

text: Accuracy of the data

text: Storage limitation of the data

text: Check the vulnerabilities of

text: the components Use of vulnerable components Integrity of the data used and Compromise of ML application Lack of security process to Availability of the data Implement components processes to maintain a good security level of Confidentiality of the data maintain security the components of the Electrical Data disclosure levels of ML forecast system Traceability of the data

text: components over time

text: Choose and define

text: a more resilient Model easy to poison Poisoning Integrity of the data

text: model design

text: Integrate No detection of poisoned samples poisoning control in the training dataset Poisoning Integrity of the data

text: in the training

text: dataset Lack of control for poisoning

text: Enlarge the Lack of data for increasing Poisoning Integrity of the data training dataset robustness to poisoning

text: Secure the transit

text: of the collected Poor data management Poisoning Integrity of the data

text: data

text: Control all data

text: used by the ML Use of uncontrolled data Poisoning Integrity of the data

text: Model

text: Ensure reliable Use of unsafe data or models Poisoning Integrity of the data sources are used (e.g., with transfer learning)

text: June 2023

text: Compromise of ML application Integrity of the data components Implement access Availability of the data Poor access rights management Poisoning

text: right management

text: process Confidentiality of the data Data disclosure Traceability of the data Human error

text: Weak access protection Compromise of ML application Ensure all systems mechanisms for machine learning Integrity of the data components and devices model components Availability of the data comply with Poisoning authentication, and Weak access protection Confidentiality of the data access control mechanisms of the personal data Data disclosure policies (encryption, access control Traceability of the data Human error mechanism…)

text: Reduce the

text: available Too much information available on Compromise of ML application Confidentiality of data information about the model components

text: the model

text: Identify a data

text: controller for the Unlawful processing Lawfulness of the process energy Absence of an identified data Unfair processing Fairness of the process consumption controller anticipation data Lack of transparency Transparency of the process

text: processing

text: Absence of mechanisms to ensure that the processing of consumer electricity affected by consent cannot be carried out without consent

text: Properly collect Lack of legal basis related to and maintain user user’s consent when their detailed consent when consumptions data (per hour or needed for detailed half hour) are processed or that Unlawful processing Lawfulness of the process energy the legitimate interest related to consumption the daily processing of the data is usage not properly justified or that no justification is provided at all

text: Lack of practical means and justification for obtaining the consents of the electricity consumers concerned

text: Anonymise data Confidentiality of the data coming from the Lack of anonymization No respect of data minimization concentrator Data minimization of the process

text: Unlawful processing Lawfulness of the process Unfair processing Fairness of the process Lack of auditability of processing Lack of transparency Generate Log Transparency of the process generation and Lack of traceability of actions Diversion of purpose Purpose limitation of the process perform Internal and/or modifications made to the No respect of data minimisation audit process assets Data minimisation of the process Compromise of Machine Accuracy of the data Learning application Storage limitation of the data No respect of storage limitation

text: Lack of controls to ensure that Diversion of purpose Purpose limitation of the process data is used only for the purposes Perform a privacy defined Unlawful processing Lawfulness of the process

text: Impact

text: Assessment Lack of controls to ensure the Unfair processing Data minimisation of the process adequacy of the purpose and its Lack of transparency Transparency of the process current use

text: June 2023

text: Lack of detail on the purposes and justification for their legitimacy

text: Define and Lack of data deletion mechanisms implement a data No respect of storage limitation Storage limitation of the data retention policy Lack of data retention policy

text: Lack of justification for the collection of individual personal data collected Unlawful processing Lawfulness of the process

text: Study on data

text: fields necessity Lack of transparency on the Lack of transparency Data minimization of the process and justification in purpose of the processing, the the privacy policy exact consumption data that are No respect of data minimisation Transparency of the process extracted, and how they are processed.

text: Formalize a LIA

text: Lack of legal basis related to (Legitimate Interest Unlawful processing Lawfulness of the process legitimate interest

text: Assessment)

text: Minimise data at Lack of necessary data selection

text: each step of the

text: processing; collect Lack of verification that the data is No respect of data minimisation Data minimisation of the process only what is adequate, relevant, and not needed when excessive for the purpose of needed estimating electricity consumption

text: Unlawful processing Lawfulness of the process

text: Unfair processing Fairness of the process

text: Implement a

text: Privacy by Design Lack of Privacy by Design Lack of transparency Transparency of the process

text: process

text: Diversion of purpose Purpose limitation of the process

text: No respect of data minimisation Data minimisation of the process

text: Integrity of the data

text: Availability of the data Poisoning Confidentiality of the data Data disclosure Traceability of the data Raise awareness Unlawful processing of security and Lack of consideration of attacks to Lawfulness of the process privacy issues which home assistant could be Unfair processing among all exposed Fairness of the process Lack of transparency

text: stakeholders

text: Transparency of the process Diversion of purpose Purpose limitation of the process No respect of data minimisation Data minimisation of the process

text: Accuracy of the data

text: June 2023

text: 5. CONCLUSION

text: In this report, analysis of forecasting demand on electricity grids supported by Artificial Intelligence (AI) is presented. AI is often used as an umbrella term that encompasses the technology behind many smart solutions and devices. It is a constantly evolving field where new innovations appear regularly in different areas of activity. Even though AI can be very beneficial for the industries areas it applies to, it can also have quite a significant impact for security and privacy, especially when these systems have sensitive functionalities, as for the scenario that is described in this report. Indeed, AI comes with a wide range of privacy and security vulnerabilities causing threats with heavy impacts for organisations. Regardless how AI is being used in support of business functionality, it should not be a surprise that the many identified threats are similar. However, we must be aware of the fact that depending on the context of the scenario, the same threats apply differently and have different levels of impact. Regarding the impact of each threat, it must be also noted that even in the same scenario every instance is unique, and a proper study must be carried out by each company using AI to maintain a proper security and privacy level. This guide helps in the identification and evaluation of threats in a specific business scenario which uses AI, but it is important to remember that while the analyzed scenario is based on real life examples, it includes assumptions which may not match the business context in which other organizations would like to implement in. Therefore, the entire cybersecurity and privacy context (requirements, threats, vulnerabilities, and controls) must be adapted to the context and reality of the individual business. In addition, the controls proposed in this document are not sufficient on their own, and must be complemented by the standard security measures that already exist. While security and privacy are not necessarily the same, they are intimately related, and equally important. In their management, a balance must be found between the two in the sense that one must always make sure that the regulations and recommendations concerning the two aspects are always respected. Unfortunately, these two parameters are regularly at the expense of performance. It is therefore an equation with three variables, two of which respond to the need for regulation and risk, which need to be correctly balanced to achieve the desired effect.

text: June 2023

text: ANNEX I: SECURITY AND PRIVACY SCALES AND REQUIREMENTS

text: A.1 CYBERSECURITY AND PRIVACY SEVERITY SCALES Availability Level Definition Low Service provided must be restored within few days or less. Moderate Service provided must be restored within a day or less. High Service provided must be restored within half a day or less. Critical Service provided must be restored within few hours or less. Integrity Level Definition Low A loss of integrity in the process does not need to be identified or corrected. Any degradation in the process must be identified but not necessarily Moderate corrected. High Any degradation in the process must be identified and corrected. Critical No degradation in the process is tolerated at any time. Confidentiality Level Definition Low Process-related data can be accessed by everyone. Access to process-related data is restricted to internal staff and trusted Moderate partners. Access to process-related data is restricted to employees having an High organisation or functional link with the process. Access to process-related data is restricted to a very limited number of Critical individuals.

text: June 2023

text: Traceability Level Definition Low The absence of traces of actions on the service provided is acceptable. Actions related to the service provided must be identified. They must be Moderate traced and detected. The actions related to the process and their actors must be identified and High dated. They must be imputable. Service provided actions must be legally enforceable and time stamped. Critical They must have a probative value. A.2 CYBERSECURITY SCALE OF IMPACT Severity Level Definition No operational impact on business performance or on the safety of people and 1 - Low property. The company/entity will overcome the situation without too much difficulty. Degradation of business performance without impact on safety of people and 2 - Moderate property. The company/entity will overcome the situation despite some difficulties (operation in degraded mode). Severe deterioration in the performance of the business, with possible significant impacts on the safety of people and property. The company/entity 3 - High will overcome the situation with serious difficulties (operation in very degraded mode). Inability of the company/entity to carry out all or part of its business, with 4 - Critical possible serious impacts on the safety of people and property. The company/entity is unlikely to overcome the situation (its survival is threatened). A.3 PRIVACY SCALE OF IMPACT Severity Level Definition The persons concerned affected will not be affected or may experience 1 - Low some inconvenience, which they overcome without difficulty. The persons concerned may experience significant inconvenience 2 - Moderate significant inconvenience, which they be able to overcome despite some difficulties. The persons concerned may experience significant consequences, which 3 - High they should be able be able to overcome, but with real and significant difficulties. The people concerned may experience significant consequences, if not 4 - Critical irreparable irremediable consequences, that they may not overcome.

text: June 2023

text: A.4 PRIVACY REQUIREMENTS CRITERIA Regarding the privacy, the applied requirements are based on the GDPR data protection principles. The figure below summarises such requirements. Requirements Article Lawfulness, fairness, and transparency Art. 5.a Purpose limitation Art. 5.b Data minimisation Art. 5.c Accuracy Art. 5.d Storage limitation Art. 5.e Security of personal data (integrity and confidentiality) Art. 5.f Moreover, as a complement to the GDPR requirements listed above, some key privacy topics related to AI systems need to be addressed (some of them are specifically mentioned by national data protection supervisory authorities ). These additional privacy requirements are listed below: Recommendations Details Projects must ensure the compliance of the data collected and injected into the database for training and in production. Moreover, they must Database creation ensure that only legitimate persons have access to the data in the database, prevent data loss and hide personal data. The data collected and the training model must be processed in accordance with the state of the art of Machine Learning development to guarantee control of all processes carried out. Compliance of the training model This consists, for instance, of good justifications for the chosen learning (i.e., before production) method, the reliability of the third-party tools used, paying attention to open-source data, conducting a meticulous training protocol based on the state of the art, and finally verifying the quality of the system once in the experimentation phase.

text: -N -EN 10 -0 -23 -09 TP ABOUT ENISA The European Union Agency for Cybersecurity, ENISA, is the Union’s agency dedicated to achieving a high common level of cybersecurity across Europe. Established in 2004 and strengthened by the EU Cybersecurity Act, the European Union Agency for Cybersecurity contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies, and helps Europe prepare for the cyber challenges of tomorrow. Through knowledge sharing, capacity building and awareness raising, the Agency works together with its key stakeholders to strengthen trust in the connected economy, to boost resilience of the Union’s infrastructure, and, ultimately, to keep Europe’s society and citizens digitally secure. More information about ENISA and its work can be found here: www.enisa.europa.eu. ISBN 978-92-9204-620-0 doi 10.2824/92851