This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP AppSensor Project"
m (→Quick Download: Version number made major only) |
John Melton (talk | contribs) (→Road Map and Getting Involved) |
||
| Line 255: | Line 255: | ||
v2.0.0 final was released in late January 2015. | v2.0.0 final was released in late January 2015. | ||
v2.1.0 final was released in June 2015. | v2.1.0 final was released in June 2015. | ||
| + | v2.2.0 final was released in September 2015 | ||
The main reason for the rewrite was to allow a client-server style model as opposed to requiring AppSensor be fully embedded in the application. You can now have a central server collecting events from multiple applications and performing analysis. These front-end applications can be in any language as long as they speak rest/soap. There's been a host of other changes, but this was the primary one. A number of starter ideas for coding, user interface and documentation have been outlined via the mailing list at [http://lists.owasp.org/pipermail/owasp-appsensor-project/2014-March/000682.html 17th March 2014]. | The main reason for the rewrite was to allow a client-server style model as opposed to requiring AppSensor be fully embedded in the application. You can now have a central server collecting events from multiple applications and performing analysis. These front-end applications can be in any language as long as they speak rest/soap. There's been a host of other changes, but this was the primary one. A number of starter ideas for coding, user interface and documentation have been outlined via the mailing list at [http://lists.owasp.org/pipermail/owasp-appsensor-project/2014-March/000682.html 17th March 2014]. | ||
| Line 279: | Line 280: | ||
=== September 2015 (2.2) === | === September 2015 (2.2) === | ||
| − | * First version of administration UI for appsensor (monitoring UI) (github issues [https://github.com/jtmelton/appsensor/issues/10 here] and [https://github.com/jtmelton/appsensor/issues/11 here]) | + | * <strike>First version of administration UI for appsensor (monitoring UI) (github issues [https://github.com/jtmelton/appsensor/issues/10 here] and [https://github.com/jtmelton/appsensor/issues/11 here])</strike> -> DONE |
=== January 2016 (2.3) === | === January 2016 (2.3) === | ||
| − | * Get CI server (cloudbees?) setup ([https://github.com/jtmelton/appsensor/issues/15 github issue]) | + | * <strike>Get CI server (cloudbees?) setup ([https://github.com/jtmelton/appsensor/issues/15 github issue])</strike> -> DONE |
* Video demo of setting up appsensor (screen capture) (related to sample apps) | * Video demo of setting up appsensor (screen capture) (related to sample apps) | ||
* New detection point implementations ([https://github.com/jtmelton/appsensor/issues/8 github issue]) | * New detection point implementations ([https://github.com/jtmelton/appsensor/issues/8 github issue]) | ||
| Line 292: | Line 293: | ||
== Past activities == | == Past activities == | ||
| + | |||
| + | '''September 2015''' Final release v2.2.0 code | ||
'''June 2015''' Final release v2.1.0 code | '''June 2015''' Final release v2.1.0 code | ||
Revision as of 15:51, 18 February 2016
OWASP AppSensorThe AppSensor project defines a conceptual framework and methodology that offers prescriptive guidance to implement intrusion detection and automated response into applications. The project offers a comprehensive guide and a reference implementation. These resources can be used by architects, developers, security analyst and system administrators to plan, implement and monitor an AppSensor system. IntroductionIf you walk into a bank and try opening random doors, you will be identified, led out of the building and possibly arrested. However, if you log into an online banking application and start looking for vulnerabilities no one will say anything. This needs to change! As critical applications continue to become more accessible and inter-connected, it is paramount that critical information is sufficiently 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, we must 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. This project delivers a framework which can be used to build a robust system of attack detection, analysis, and response within an enterprise application.
Detect and Respond to Attacks from Within the ApplicationDetectionAppSensor defines over 50 different detection points which can be used to identify a malicious attacker. ResponseAppSensor provides guidance on how to respond once a malicious attacker has been identified. Possible actions include: logging out the user, locking the account or notifying an administrator. More than a dozen response actions are described. Defending the ApplicationAn attacker often requires numerous probes and attack attempts in order to locate an exploitable vulnerability within the application. By using AppSensor it is possible to identify and eliminate the threat of an attacker before they are able to successfully identify an exploitable flaw.
Citations
LicensingOWASP AppSensor is free to use. GuideThe guide is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. Reference ImplementationThe reference implementation is licensed under the MIT License, which is a permissive (commercial-friendly) license only requiring you to include a copy of the license upon distribution or copying. © OWASP Foundation
|
What is AppSensor?Detect and respond to attacks from within the application. This project includes both a well documented idea (the Guide) and a reference implementation (the Code).
Intro for Developers
AppSensor Website
See the AppSensor website for an introduction and quick start instructions. Overview
Project Founder
Project Leaders
Related Projects
|
Quick DownloadNews and Events
Code Repository
In Print
The AppSensor Guide and CISO Briefing can be purchased at cost as print on demand books. Classifications
| |||||||||
