What's next?

The potential uses for Aspect-oriented programming in application security are enormous. Here are a couple of other applications AOP in security:

• Implement access control independently of application logic. Instead of having explicit checks such as checkAccess(User) in each sensitive function, you can achieve this through aspects and let developers focus on business logic
• Implement application security policies such as explicitly forbidding programmers from calling dynamic SQL libraries (e.g. executeQuery()). Whenever that library is called, you can use aspects to throw an exception and record exactly where the offending call came from

Developers are already moving towards adopting AOP. JBoss, WebSphere, and WebLogic either have existing functionality to integrate AOP or have made announcements to do so in the future. Now the application security community needs to follow suit by providing guidance on how AOP can be used in a security context.

We can achieve this by ensuring we add AOP to our application security training curriculums (something we’ve included in our new class for SANS, and I hope other training companies do the same), do more research on how AOP works at securing applications in production (including benchmarks for performance impact), and providing more example code for developers to learn from.

Footnotes

1. Aspect-oriented programming with Spring; Spring Framework
2. Applying Aspect-Oriented Programming to Security; Viega, Bloch, and Chandra; Cutter IT Journal
3. Towards a security aspect for Java; Farías, Andrés
4. AspectJ
5. AsjectJ Development Tools
6. Using AspectJ with Spring Applications; Spring Framework Reference Guide
7. Data Validation, OWASP,

         public class MyFirstClass {
         public void amethod (String bar) {
                   Logger.doLoggingBefore();
                   //business logic goes here
                   Logger.doLoggingAfter();
           }
         }
         public class MySecondClass {
           public void function (Object arg) {
                   Logger.doLoggingBefore();
                   //business logic goes here
                   Logger.doLoggingAfter();
           }
         }
         public aspect LogInterceptor { 
   
         public Object invoke(){
         Logger.doLoggingBefore();
                   method.execute(); 
                   Logger.doLoggingAfter();
             }
         }
         public class MySecondClass {
           public void function (Object arg) {
                   //business logic goes here
           }
         }
         public class MyFirstClass {
           public void amethod (String bar) {            
                   //business logic goes here
           }
   

This article originally appeared in Security Focus.

Copyright © 2007, SecurityFocus

Related stories

Ubuntu to get open-source Java heart implant (23 July 2008)
Time to overcome Java misconceptions (22 May 2008)
Stay focused on fuzzy tests, warn security experts (7 April 2008)
Eclipse rounds up runtime project (17 March 2008)
Time for genuine 'write-once, run-anywhere' Java (14 March 2008)
Open sourciness (22 February 2008)
Red Hat sports BlackTie challenge to BEA's Tuxedo (15 February 2008)
Dip into concept programming (16 January 2008)
JBoss serves stuffed Eclipse IDE (11 December 2007)
Secure Java coding course aims to push best practice (23 November 2007)
Fat or thin: an insider's view on Java's destiny (9 November 2007)
Fatten or strip - the great Java debate (8 November 2007)
Designing software for testability (29 October 2007)
Of opposable thumbs and software engineering (19 October 2007)
Why UML won't save your project (8 October 2007)
Aspect oriented programming with Java (26 October 2006)
The No Fluff Just Stuff 2006 Anthology (28 September 2006)
Sun gets hooks into JBoss (6 September 2006)
Aspect orientation - the next big thing? (25 January 2005)