2011
DOI: 10.1007/978-3-642-22056-2_62
|View full text |Cite
|
Sign up to set email alerts
|

Taking into Account Functional Models in the Validation of IS Security Policies

Abstract: International audienceDesigning a security policy for an information system (IS) is a non-trivial task. Variants of the RBAC model can be used to express such policies as access-control rules associated to constraints. In this paper, we advocate that currently available tools do not take sufficiently into account the functional description of the application and its impact on authorisation constraints and dynamic aspects of security. We suggest to translate both security and functional models into a formal lan… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2011
2011
2018
2018

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 22 publications
0
9
0
Order By: Relevance
“…Logically, we recognize this when ROLES − ROLES IMP ≠ ∅. Thus, we define missed roles in (11) by the difference between the two sets of specified and implemented roles:…”
Section: Validation Propertiesmentioning
confidence: 99%
See 1 more Smart Citation
“…Logically, we recognize this when ROLES − ROLES IMP ≠ ∅. Thus, we define missed roles in (11) by the difference between the two sets of specified and implemented roles:…”
Section: Validation Propertiesmentioning
confidence: 99%
“…In [6], authors proposed to transform the specification realized with SecureUML to the Z language and to analyze the policy with the Jaza tool that allows animating the specification. Authors in [11] chose to transform the specification to the B notation using the B4Msecure tool and to analyze it with the ProB tool. Authors in [14] defined a logical framework to enforce the integrity of access control policies in relational databases.…”
Section: Related Workmentioning
confidence: 99%
“…This requires that the designer expresses the constraint as B statements. In SecureUML these constraints can be modeled using OCL; however, there is no tool that can validate both static and functional models with such constraints [16]. Figure 9 details the operation used in the rest of this paper: secure_MedicalRecord__GetData.…”
Section: Patienthospitalrel(patientmedicalrecordrel(instance)))mentioning
confidence: 99%
“…In [22], authors formalize the specified diagrams (SecureUML diagrams) in the Z language and analyze the policy based on the specification animator Jaza tool. Authors in [23] suggested translating the SecureUML diagrams in the B notation by using the B4Msecure tool and checking the obtained models via the ProB tool. In [24], authors structure the set of roles in a graph that captures different variants of RBAC models.…”
Section: Verification and Validation Of Access Control Policiesmentioning
confidence: 99%
“…The authors in [51,52] defined an UML-B-SQL transformation that allows specifying IS with UML, translating the specifications to the formal B notation, and generating after successive refinements Java/SQL codes. The authors in [23] proposed an approach to encode UML and SecureUML diagrams in the formal B notation. According to our knowledge, the transformation in the other way (from SQL to B notation so-called SQL-B mapping) is not addressed in literature.…”
Section: Reverse-engineering and Formalization Of Access Control Polimentioning
confidence: 99%