2007
DOI: 10.1109/compsac.2007.55
|View full text |Cite
|
Sign up to set email alerts
|

An Adaptive Security Model for Multi-agent Systems and Application to a Clinical Trials Environment

Abstract: We present in this paper an adaptive security model for Multi-agent

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
11
0

Year Published

2008
2008
2018
2018

Publication Types

Select...
5
2
1

Relationship

4
4

Authors

Journals

citations
Cited by 22 publications
(12 citation statements)
references
References 9 publications
(8 reference statements)
0
11
0
Order By: Relevance
“…This is achieved through an integrated role concept [8]. Here agent's functional duty role as described by the Agent-Oriented Software Engineering (AOSE) [8] and agent's social rights role as described by the Role-Based Access Control (RBAC) [10] are seamlessly integrated. The principle is:…”
Section: Figure 8 An Example Reaction Rulementioning
confidence: 99%
See 1 more Smart Citation
“…This is achieved through an integrated role concept [8]. Here agent's functional duty role as described by the Agent-Oriented Software Engineering (AOSE) [8] and agent's social rights role as described by the Role-Based Access Control (RBAC) [10] are seamlessly integrated. The principle is:…”
Section: Figure 8 An Example Reaction Rulementioning
confidence: 99%
“…But he/she will be rejected of the reputation updating request since its precondition of policy rule satisfaction fails. Both RR and security PR have been formalised in the XML model so that agents can uniformly perform their duties if they are found having the appropriate rights [5] [6] [8].…”
Section: Figure 8 An Example Reaction Rulementioning
confidence: 99%
“…a particular clinician can/cannot access particular resource items. A generic security policy schema for healthcare is described in Xiao et al (2007) that can complement the metarule with any number of specific policies. The following shows the LCC constraints used by the database agent, being a resource manager, for permission checking before the actual role functions are carried out.…”
Section: Level 2: Case Level Constraintsmentioning
confidence: 99%
“…In our previous work [9], we have developed a Security Model and an associated Policy Rule Model. Briefly, they borrow the role permission association from Role-Based Access Control [11], avoid its weaknesses, and extend it towards a seamless integration with the role playing pattern from Agent-Oriented Software Engineering.…”
Section: The Authorisation Mechanismmentioning
confidence: 99%