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 key files are being translated and will be available soon. Project Leader Cicero Gadelha Related Projects OWASP Top Ten Project Classifications

News and Events First meeting, Chapter Fortaleza

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?

Team

• Felipe Albuquerque

The OWASP Knowledge Graph is selecting members for the team.

If you would like to contribute please contact:

• Cicero Gadelha

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.