2014
DOI: 10.1504/ijcc.2014.058831
|View full text |Cite
|
Sign up to set email alerts
|

Expressing cloud security requirements for SLAs in deontic contract languages for cloud brokers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0
1

Year Published

2015
2015
2019
2019

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 15 publications
(10 citation statements)
references
References 21 publications
0
9
0
1
Order By: Relevance
“…Nevertheless some works have been done in order to address this issue as we will explain in the next section. Here we just show an example schema from the paper [12], which extends the standard WS-Agreement [31] schema to cover the security requirements. Table 1 shows how we could specify the security requirement on data retention in an SLA.…”
Section: A Security Requirements and Slasmentioning
confidence: 99%
See 1 more Smart Citation
“…Nevertheless some works have been done in order to address this issue as we will explain in the next section. Here we just show an example schema from the paper [12], which extends the standard WS-Agreement [31] schema to cover the security requirements. Table 1 shows how we could specify the security requirement on data retention in an SLA.…”
Section: A Security Requirements and Slasmentioning
confidence: 99%
“…As shown in Figure 3, it gives a very good example about what needs to be covered in the SLAs for a composed online meeting service, which has four individual services: VOICE, MSG, PRESENCE, and CONF. Furthermore, paper [12] proposed a scheme to let the service broker bridge the security requirements from service consumers and the security guarantees promised by service providers. The broker is in charge of compositing web services and maintaining a mutually agreed contract.…”
Section: Figure 2 Composition Of Three Servicesmentioning
confidence: 99%
“…To this list, Breaux and Gordon [39] add the dimension of constraint changes across jurisdictions when regulations share a common focus. Further, a comparison of the potential languages that can be used by cloud users to express such requirements, has been made by Meland et al [59]. The authors examine several languages usable for cloud SLAs, among which there are also XACML, WSAgreement, LegalXML; however, they conclude that prior to choosing how to express security requirements, it is more stringent to converge towards common concepts of security contracts.…”
Section: Existing Workmentioning
confidence: 99%
“…CloudSurfer depends on that the Cloud providers advertise their offered security controls in a machinereadable form, as shown in the lower-most part of Figure 1. There is no prevalent standard for expressing contract requirements and offerings, but based on the recommendations by Meland et al (Meland et al, 2013), WS-Agreement (Andrieux et al, 2003) was chosen. This language is extensible and allows the use of any service terms, but has no built-in predicates for security.…”
Section: Design and Interactionmentioning
confidence: 99%