OWASP Knowledge Graph

• Main
• FAQs
• Acknowledgements
• Road Map and Getting Involved
• Minimum Viable Product

OWASP Knowledge Graph A tool that makes possible to consult the knowledge base providing informations about web vulnerabilities, the tool will also provide a way to check servers detecting vulnerabilities contained in knowledge base. Description This project uses the knowledge graphs to represent web vulnerabilities into a knowledge base. Using this base will be possible to detect vulnerabilities in systems and have a better understand of how they work. Licensing This program is free software: you can redistribute it and/or modify it under the terms of the link GNU General Public License 3.0 as published by the Free Software Foundation.

Project Resources 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. Project Leader Cicero Gadelha Related Projects This is where you can link to other OWASP Projects that are similar to yours. Classifications

News and Events This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.

Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. The point of a document like this are the answers. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'

How can I participate in your project?

If I am not a programmer can I participate in your project?

Contributors

The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. Be sure to provide a link to a complete list of all the amazing people in your project's community as well.

The first contributors to the project were:

• Cicero Gadelha

A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership. Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.

Roadmap

1. Define the graph structure to store data in a efficient way. 2. Represent in graphs the top 10 vulnerabilities. 3. Create a tool to use the knowledge graph to detect vulnerabilities and explore theirs caracteristics. 4. Conduct an evaluation of results. 5. Expand the knwoledge graph storing more vulnerabilities.

Subsequent Releases will add

Getting Involved

This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern. Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.