Overview of Basic Azure Security Components

2021 ◽  
pp. 11-35
Author(s):  
Pushpa Herath
Keyword(s):  
2013 ◽  
Vol 5 (4) ◽  
pp. 67-81
Author(s):  
Kamel Karoui ◽  
Fakher Ben Ftima ◽  
Henda Ben Ghezala
Keyword(s):  

2018 ◽  
pp. 551-592
Author(s):  
Holger Schmidt ◽  
Denis Hatebur ◽  
Maritta Heisel

This chapter presents a security engineering process based on UML security problem frames and concretized UML security problem frames. Both kinds of frames constitute patterns for analyzing security problems and associated solution approaches. They are arranged in a pattern system that makes dependencies between them explicit. The authors describe step-by-step how the pattern system can be used to analyze a given security problem and how solution approaches can be found. Then, solution approaches are specified by generic security components and generic security architectures, which constitute architectural patterns. Finally, the generic security components and the generic security architecture that composes them are refined, and the result is a secure software product built from existing and/or tailor-made security components.


Author(s):  
Holger Schmidt ◽  
Denis Hatebur ◽  
Maritta Heisel

The authors present a security engineering process based on security problem frames and concretized security problem frames. Both kinds of frames constitute patterns for analyzing security problems and associated solution approaches. They are arranged in a pattern system that makes dependencies between them explicit. The authors describe step-by-step how the pattern system can be used to analyze a given security problem and how solution approaches can be found. Afterwards, the security problems and the solution approaches are formally modeled in detail. The formal models serve to prove that the solution approaches are correct solutions to the security problems. Furthermore, the formal models of the solution approaches constitute a formal specification of the software to be developed. Then, the specification is implemented by generic security components and generic security architectures, which constitute architectural patterns. Finally, the generic security components and the generic security architecture that composes them are refined and the result is a secure software product built from existing and/or tailor-made security components.


Author(s):  
N. Nobelis ◽  
K. Boudaoud ◽  
C. Delettre ◽  
M. Riveill

Numerous communication protocols have been designed offering a set of security properties through the use of cryptographic tools to secure electronic document transfer. However, there is no clear match between the tools used and security properties they offer. To solve this problem, the authors propose to use a component-based approach; more specifically the authors introduce the notion of high-level security component where each component provides an atomic security property. This approach will facilitate the design of new protocols that fulfill any specific set of security properties by assembling the appropriate components. At the same time, users using a protocol designed with these security components will have the assurance that the protocol satisfies the security properties required for the electronic document transfer. The authors validate the approach by showing how the integrity property can be added to the HTTP protocol to design a security property-centric HTTPS and in this case an integrity-only HTTPS.


Cloud computing, the utility base computing, is going to become the mainstream of IT future. Governments and enterprises are realizing that by immigrating into the cloud they can significantly enhance their current infrastructure or application services with minimum cost and maximum elasticity. But securing cloud user digital assets and addressing privacy concerns of cloud costumers has become serious challenge. Providing security in cloud always has to consider performance. Employing high secure methods with massive complexity will increase overall service cost, to address this problem in this paper a two- tier security architecture is proposed. This architecture use multiple work mode for security components in guest level to decrease security process over-head and a security supervisory in hypervisor layer to make sure avoiding from false security alarms


Sign in / Sign up

Export Citation Format

Share Document