Proceedings DARPA Information Survivability Conference and Exposition
DOI: 10.1109/discex.2003.1194952
|View full text |Cite
|
Sign up to set email alerts
|

An aspect-oriented security framework

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
19
0

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 26 publications
(19 citation statements)
references
References 0 publications
0
19
0
Order By: Relevance
“…Current AOSD models aim at drawing an abstract pathway that concentrates on a general purpose modeling procedure within a certain domain, or to support particular NFRs in the system (e.g., performance or security [1,2]). In addition, these approaches do not fully support a smooth transition among the requirements, analysis and the design phases.…”
Section: Related Workmentioning
confidence: 99%
“…Current AOSD models aim at drawing an abstract pathway that concentrates on a general purpose modeling procedure within a certain domain, or to support particular NFRs in the system (e.g., performance or security [1,2]). In addition, these approaches do not fully support a smooth transition among the requirements, analysis and the design phases.…”
Section: Related Workmentioning
confidence: 99%
“…By using AOSD, software developers can focus on functional requirements, and, at the same time, well-trained software security engineers can focus on the security issues of the application separately. There are many security concerns addressed by AOSD in the existing work such as access control [6,7], security-flaw fixing [8,5], encryption [9,10], and audit [11,12]. However, there is no research on applying AOSD for intrusion detection.…”
Section: Introductionmentioning
confidence: 98%
“…The separated concerns are implemented as aspects and woven into the primary functionalities. As cross-cutting concerns, security concerns can be addressed by AOSD with good modularity, reusability, and flexibility [3][4][5]. By using AOSD, software developers can focus on functional requirements, and, at the same time, well-trained software security engineers can focus on the security issues of the application separately.…”
Section: Introductionmentioning
confidence: 99%
“…The approach is motivated by improved efficiency (since IRMs require fewer context switches than external monitors), deployment flexibility (since in-lining avoids modifying the VM or OS), and precision (since IRMs can monitor internal program operations not readily visible to an external monitor). Most modern IRM systems are implemented using some form of aspect-oriented programming (AOP) [32,28,7,8,14]. Such IRMs are implemented as pointcut -advice pairs: pointcuts identify securityrelevant program operations and advice prescribes local code transformations sufficient to guard such operations.…”
Section: Introductionmentioning
confidence: 99%