2011 6th International Conference on System of Systems Engineering 2011
DOI: 10.1109/sysose.2011.5966566
|View full text |Cite
|
Sign up to set email alerts
|

Managing runtime re-engineering of a System-of-Systems for cyber security

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 12 publications
(6 citation statements)
references
References 16 publications
0
6
0
Order By: Relevance
“…It is recognised that cyber security is often "bolted on as an afterthought" and that "this is not effective in practice" [32] and indeed "dangerous" [33]. To overcome challenges in the efficacy of formal verification and security, we propose a methodology that combines the two processes: threat modelling and formal verification.…”
Section: Combining Formal Verification and Cyber Securitymentioning
confidence: 99%
“…It is recognised that cyber security is often "bolted on as an afterthought" and that "this is not effective in practice" [32] and indeed "dangerous" [33]. To overcome challenges in the efficacy of formal verification and security, we propose a methodology that combines the two processes: threat modelling and formal verification.…”
Section: Combining Formal Verification and Cyber Securitymentioning
confidence: 99%
“…On the contrary, SoSs pose new constraints to the threat analysis processes [2], especially regarding their (i) evolutionary nature and (ii) emergent properties. Evolution refers to long-term changes required to accomplish variations to the requirements in light of an always-changing environment [3].…”
Section: Introductionmentioning
confidence: 99%
“…Hence, it is important to consider the interdependence between quality attributes in scenarios where cascading failures and bottlenecks could result in a complete SoS blackout (Chiprianov et al, 2014). In this sense, quality attributes needs to be measured and controlled for each constituent system to address the impact on SoS quality (Chiprianov et al, 2014;Gorod et al, 2007;Waller and Craddock, 2011).…”
Section: Discussion and Evaluation Challengesmentioning
confidence: 99%
“…Moreover, it is necessary to take into account the SoS specific characteristics and how they impact the quality of SoS as a whole. For instance, considering performance and security, some example of the impact of SoS characteristics on these quality attributes are (Chiprianov et al, 2014;Gorod et al, 2007;Waller and Craddock, 2011): (i) the operational independence of the constituents can lead to potential incompatibilities and conflicts between security or performance of each system; then, some systems may be more vulnerable to attacks or have less critical real-time constraints than others and, therefore, their effects and consequences must be carefully considered in the SoS. (ii) due to managerial independence, constituents can have to protect themselves within the SoS from other systems and from SoS emerging activities, which can bring consequences to the SoS mission; (iii) evolutionary development of SoS makes difficult to completely specify quality requirements, such as performance and security at design time, and will need to evolve as the SoS evolves; (iv) emergent behavior difficults the clear identification of the source of a security fault or performance degradation; and (v) geographic distribution makes difficult to achieve security or performance in the SoS as a whole, mainly when different national regulations must be met and when functionalities are met due to numerous and long paths of interaction.…”
Section: Discussion and Evaluation Challengesmentioning
confidence: 99%