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 Intelligent Intrusion Detection System"

From OWASP
Jump to: navigation, search
(Created page with "<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</div> {| style="padding: 0;margin:0;margin-top:10px;text-alig...")
 
m
 
(3 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
<span style="color:#ff0000">
 
−
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
 
−
</span>
 
−
==Project About==
 
−
<span style="color:#ff0000">
 
−
{{:Projects/OWASP_Example_Project_About_Page}}
 
  
  
−
==OWASP Tool Project Template==
 
−
<span style="color:#ff0000">
 
−
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
 
−
</span>
 
  
−
The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.
+
==OWASP Tool Project==
 +
 
  
 
==Description==
 
==Description==
−
<span style="color:#ff0000">
 
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. 
 
−
</span>
 
  
−
The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project.  After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red.  Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
+
===Problem===
 +
In today's world, Network and System Security are of paramount importance in the digital communication environment. On par with the developments in technology, many threats have emerged for information security which has worse effects when it comes to sensitive transactions. Nowadays, intruders can easily break the walls of the network and can cause many kinds of breaches such as the crash of the networks, Denial Of Service, injecting Malware and so on. In order to avoid those breaches, it is badly needed for a security administrator to detect the intruder and prevent him from entering into the network. In daily life, new threats and associated solutions are emerging together.
  
−
Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
+
===Proposed Solution===
 +
A Hybrid Intrusion Detection System by leveraging the benefits of Machine Learning techniques to build a system which detects the intrusion and alerts the respective network administrator. This can be extended from Intrusion to breach detection as well. The developed system analyses and predicts the behavior of users which in turn classifies as an anomaly or a normal behavior.
  
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
+
===Use Case Scenarios===
 +
 
 +
* Denial of Service (DoS): Attacker tries to prevent legitimate users from using a service.
 +
* Probe: Attacker tries to gain information about the target host.
 +
* U2R: Attacker has local access to the victim machine and tries to gain super user privileges.
 +
* R2L: Attacker does not have an account on the victim machine, hence tries to gain access.
  
 
==Licensing==
 
==Licensing==
−
<span style="color:#ff0000">
 
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
 
−
</span>
 
  
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}. 
+
 
 +
OWASP Hybrid Intrusion Detection System is free to use. It is licensed under GNU GPL v3 License (allows commercial use, but requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)
  
 
==Roadmap==
 
==Roadmap==
−
<span style="color:#ff0000">
+
 
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
 
<strong>
 
<strong>
 
* Complete the first draft of the Tool Project Template
 
* Complete the first draft of the Tool Project Template
−
* Get other people to review the Tool Project Template and provide feedback
+
* Get more contributors to the project
−
* Incorporate feedback into changes in the Tool Project Template
+
* Push the project base to github repository
 
* Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
* Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
</strong>
 
</strong>
  
−
Subsequent Releases will add
+
 
−
<strong>
 
−
* Internationalization Support
 
−
* Additional Unit Tests
 
−
* Automated Regression tests
 
−
</strong>
 
  
 
==Getting Involved==
 
==Getting Involved==
−
<span style="color:#ff0000">
+
Feel free to contact the [mailto:[email protected] leader] to know how can you be part project growth.
−
Involvement in the development and promotion of <strong>Tool Project Template</strong> is actively encouraged!
+
 
−
You do not have to be a security expert or a programmer to contribute.
 
−
Some of the ways you can help are as follows:
 
  
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
 
== Project Resources ==
 
== Project Resources ==
−
<span style="color:#ff0000">
 
−
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
 
−
</span>
 
  
−
[https://github.com/SamanthaGroves Installation Package]
 
  
−
[https://github.com/SamanthaGroves Source Code]
+
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ Installation Package]
  
−
[https://github.com/SamanthaGroves What's New (Revision History)]
+
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ Source Code]
  
−
[https://github.com/SamanthaGroves Documentation]
+
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ What's New (Revision History)]
  
−
[https://github.com/SamanthaGroves Wiki Home Page]
+
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ Documentation]
  
−
[https://github.com/SamanthaGroves Issue Tracker]
+
[https://www.owasp.org/index.php/OWASP_Intelligent_Intrusion_Detection_System Wiki Home Page]
  
−
[https://github.com/SamanthaGroves Slide Presentation]
+
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ Issue Tracker]
  
−
[https://github.com/SamanthaGroves Video]
+
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ Slide Presentation]
 +
 
 +
[https://github.com/OWASP/Intelligent-Intrusion-Detection-System/ Video]
  
 
== Project Leader ==
 
== Project Leader ==
−
<span style="color:#ff0000">
 
−
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
 
−
</span>
 
  
−
Sri Harsha Gajavalli
+
[mailto:[email protected] Sri Harsha Gajavalli]
 +
 
  
−
== Related Projects ==
 
−
<span style="color:#ff0000">
 
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Documentation_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==

Latest revision as of 17:23, 22 February 2019

OWASP Project Header.jpg



OWASP Tool Project

Description

Problem

In today's world, Network and System Security are of paramount importance in the digital communication environment. On par with the developments in technology, many threats have emerged for information security which has worse effects when it comes to sensitive transactions. Nowadays, intruders can easily break the walls of the network and can cause many kinds of breaches such as the crash of the networks, Denial Of Service, injecting Malware and so on. In order to avoid those breaches, it is badly needed for a security administrator to detect the intruder and prevent him from entering into the network. In daily life, new threats and associated solutions are emerging together.

Proposed Solution

A Hybrid Intrusion Detection System by leveraging the benefits of Machine Learning techniques to build a system which detects the intrusion and alerts the respective network administrator. This can be extended from Intrusion to breach detection as well. The developed system analyses and predicts the behavior of users which in turn classifies as an anomaly or a normal behavior.

Use Case Scenarios

  • Denial of Service (DoS): Attacker tries to prevent legitimate users from using a service.
  • Probe: Attacker tries to gain information about the target host.
  • U2R: Attacker has local access to the victim machine and tries to gain super user privileges.
  • R2L: Attacker does not have an account on the victim machine, hence tries to gain access.

Licensing

OWASP Hybrid Intrusion Detection System is free to use. It is licensed under GNU GPL v3 License (allows commercial use, but requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)

Roadmap

  • Complete the first draft of the Tool Project Template
  • Get more contributors to the project
  • Push the project base to github repository
  • Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project


Getting Involved

Feel free to contact the leader to know how can you be part project growth.


Project Resources

Installation Package

Source Code

What's New (Revision History)

Documentation

Wiki Home Page

Issue Tracker

Slide Presentation

Video

Project Leader

Sri Harsha Gajavalli


Classifications

Project Type Files TOOL.jpg
Incubator Project
Owasp-defenders-small.png
GNU General Public License (GPL)
Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Intelligent_Intrusion_Detection_System&oldid=247730"