2003
DOI: 10.1002/spe.528
|View full text |Cite
|
Sign up to set email alerts
|

A security framework for reflective Java applications

Abstract: The advent of component‐based reflective applications raises the issue of protecting baselevel components from the actions performed by metalevel components. However, by their very nature, reflective applications are far more difficult to secure than non‐reflective applications, which certainly explains why the problem has received very little attention so far. In this paper we present a security framework for enforcing access control between metalevel components and the baselevel components they reflect on. R… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2008
2008
2013
2013

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 21 publications
0
2
0
Order By: Relevance
“…First, it will put an unendurable impact on the performance of business transactions because Java security manager checks any access appearing in Java Virtual Machine, which decreases the performance of the whole Java program by 13%∼14% [15] . Second, the specification of security policies is much more complex than that specified in the J2EE deployment descriptor.…”
Section: Handling Invocations To Meta Entitiesmentioning
confidence: 99%
See 1 more Smart Citation
“…First, it will put an unendurable impact on the performance of business transactions because Java security manager checks any access appearing in Java Virtual Machine, which decreases the performance of the whole Java program by 13%∼14% [15] . Second, the specification of security policies is much more complex than that specified in the J2EE deployment descriptor.…”
Section: Handling Invocations To Meta Entitiesmentioning
confidence: 99%
“…The composer is the unique point via which the meta entities can access the base entities. Caromel et al defined a set of Java permissions specific to the base entities and use Java security manager to control the access between the meta entities and the base entities [15] , which suffers the 13%∼14% performance overhead. As mentioned in the section about the access control mechanism between the meta entities, the standard JMX access control suffers the same performance overhead as that of Caromel et al and cannot be seamlessly integrated with the standard J2EE access control.…”
Section: Related Workmentioning
confidence: 99%