Figure 7 - uploaded by Anas Motii
Content may be subject to copyright.
Source publication
![Figure 2.2: MDE: Overview on Model-To-Model Transformation [113]](profile/Anas-Motii-3/publication/329518798/figure/fig2/AS:11431281090862133@1666197932065/MDE-Overview-on-Model-To-Model-Transformation-113_Q320.jpg)
![Figure 2.5: ISO 27005 risk management process model [79]](profile/Anas-Motii-3/publication/329518798/figure/fig5/AS:11431281090817980@1666197932660/ISO-27005-risk-management-process-model-79_Q320.jpg)
Nowadays most organizations depend on Information and Communication Technologies (ICT) to perform their daily tasks (sometimes highly critical). However, in most cases, organizations and particularly small ones place limited value on information and its security. In the same time, achieving security in such systems is a difficult task because of th...
Contexts in source publication
Context 1
... the following sections we use the case study displayed in Figure 7.1. It shows a typical SCADA architecture used in the context of smart grids [161]. ...
Context 2
... SCADA system architecture is composed of two system components as shown in Figure 7.4: Control center and RTUs that communicate. ...
Context 3
... software architecture and platform refines the system architecture. Figure 7.5 shows the software architecture model based on [35]. In addition, ports, interfaces, data types and transmitted messages are added in Figure 7.6 to provide a more detailed model of the application. ...
Context 4
... 7.5 shows the software architecture model based on [35]. In addition, ports, interfaces, data types and transmitted messages are added in Figure 7.6 to provide a more detailed model of the application. The platform is modeled in Figure 7.7. ...
Context 5
... addition, ports, interfaces, data types and transmitted messages are added in Figure 7.6 to provide a more detailed model of the application. The platform is modeled in Figure 7.7. We show the relationship between the system components and hardware nodes. ...
Context 6
... System of Patterns is selected from the model repository protecting the system against the identified threats in Table 7.1. The System of Patterns is then instantiated in the modeling environment Papyrus (see Figure 7.8) thanks to Semco4Papyrus access tool. ...
Context 7
... is possible because each feared event is relevant to a system component and each threat is stopped or mitigated with an abstract pattern. Figure 7.9 shows where the abstract patterns are used with regards to the system architecture. ...
Context 8
... each configuration, patterns are integrated into the SCADA system software architecture described in Figure 7.5. Thus, we obtain software architecture candidates 1, 2, 3 and 4 for each pattern configuration 1, 2, 3 and 4. Figure 7.10 shows software architecture candidate 1. ...
Context 9
... each configuration, patterns are integrated into the SCADA system software architecture described in Figure 7.5. Thus, we obtain software architecture candidates 1, 2, 3 and 4 for each pattern configuration 1, 2, 3 and 4. Figure 7.10 shows software architecture candidate 1. ...
Context 10
... time analysis is performed for candidates 1, 2 and 3 since they pass the processor utilization test. Figure 7.14 shows task WCRTs for each software architecture candidate 1, 2 and 3. ...
Context 11
... show the feasibility of the approach through the execution of three activities: (1) threat analysis -we compare the detected threats to threats obtained with an attack scenario simulation framework named ASTORIA [161]; (2) pattern integrationwe compare threats before and after security pattern integration; (3) Real-time evaluation -we discuss the benefits of such evaluation at early stage. Figure 7.14: Task WCRTs ...
