Difference between revisions of "Category:OWASP AppSensor Project"

Jump to: navigation, search
m (Project Lead)
(Replaced content with '#REDIRECT OWASP AppSensor Project')
(43 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[:Category:OWASP Project|Click here to return to OWASP Projects page.]]<br>
#REDIRECT [[OWASP AppSensor Project]]
[[:Project Information:template AppSensor Project|Click here to see (& edit, if wanted) the template.]]  
{{:Project Information:template AppSensor Project}}
[[Category:OWASP Project]]
'''Summer of Code 2008 Project!'''
As critical applications continue to become more accessible and inter-connected, it is paramount that the information be protected. We must also realize that our defenses may not be perfect. Given enough time, attackers can identify security flaws in the design or implementation of an application. In addition to implementing layers of defense within an application, it is critical that we identify malicious individuals before they are able to identify any gaps in our defenses. The best place to identify malicious activity against the application is within the application itself. Network based intrusion detection systems are not appropriate to handle the custom and intricate workings of an enterprise application and are ill-suited to detect attacks focusing on application logic such as authentication, access control, etc. The application itself is the best place to identify and respond to malicious activity. This project will create the framework which can be used to build a robust system of attack detection, analysis, and response within an enterprise application
For example, when an architect considers the design of their authentication system (or any other critical system) they would reference the AppSensor guidelines on authentication. The AppSensor guidance will indicate what sort of authentication actions need to be logged (failed login attempt, use of multiple user-names from a single IP, high rate of login attempts etc) and what information must be captured (e.g. user-name, ip, timestamp ). Further, the AppSensor guidance will detail how all the events should be handled. Events will be sent to a centralized logging system within the application. This system collect the security events from throughout the application (e.g. authorization attacks, business logic attacks, force browsing attempts) and will then be able to take appropriate action against the user. This could include locking out an account, generating alerts to sys-admins, shutting down portions of the application, and more. Essentially, the AppSensor project is defining how an Intrusion Detection System should be designed, configured and built into the code of any custom application. By building the Application Level IDS within the application itself, we are in the best place to capture and respond to all malicious actions performed against the application.
==Project Lead==
Michael Coates (mwcoates [at] aspectsecurity [dot] com)
==Project Roadmap==
'''April 16, 2008 - Project Begins'''
High level planning & design
Identify and define attack patterns against applications
Document points of detection within the application for the attack patterns & identify key information to log
Pier Review & Revisions
'''June 29, 2008 - Status Report'''
Create thresholds for generating security alerts
Define recommended response actions for the security alerts
Pier Review & Revisions
'''Aug 31, 2008 - Project Complete'''

Latest revision as of 11:35, 6 October 2010

Pages in category "OWASP AppSensor Project"

The following 4 pages are in this category, out of 4 total.