Difference between revisions of "Category:OWASP Honeycomb Project"

From OWASP
Jump to: navigation, search
m (Volunteers Needed)
m
Line 1: Line 1:
 
==Overview==
 
==Overview==
  
OWASP is assembling the most comprehensive and integrated guide to application security principles, threats, attacks, vulnerabilities, and countermeasures ever attempted.
+
In the Honeycomb project, OWASP is assembling the most comprehensive and integrated guide to the fundamental building blocks of application security (principles, threats, attacks, vulnerabilities, and countermeasures) ever attempted through collaborative community efforts.  
  
==What we are trying to accomplish and why?==
+
===What we are trying to accomplish?===
  
* the difficulties in organizing this information
+
===The difficulties in organizing this information===
  
* the approach we’ve taken
+
===The approach we’ve taken===
  
* why our approach solves the problems
+
===Why our approach solves the problems===
 +
 
 +
===Why the name Honeycomb?===
  
 
==How to use the information?==  
 
==How to use the information?==  
Line 32: Line 34:
 
* Merge duplicate vulnerability categories. (Replace "...problem/error" with "...vulnerability" when it is appropriate.)
 
* Merge duplicate vulnerability categories. (Replace "...problem/error" with "...vulnerability" when it is appropriate.)
 
* Make sure all articles that have code snippets are marked with the "Code Snippet" category and corresponding languages.
 
* Make sure all articles that have code snippets are marked with the "Code Snippet" category and corresponding languages.
 
  
 
===Specific tasks===
 
===Specific tasks===

Revision as of 09:18, 25 July 2006

Overview

In the Honeycomb project, OWASP is assembling the most comprehensive and integrated guide to the fundamental building blocks of application security (principles, threats, attacks, vulnerabilities, and countermeasures) ever attempted through collaborative community efforts.

What we are trying to accomplish?

The difficulties in organizing this information

The approach we’ve taken

Why our approach solves the problems

Why the name Honeycomb?

How to use the information?

Honeycomb User’s Guide

Volunteers Needed

what’s still left to do

  • Expand the stub articles (description and examples)
  • Fill in the related sections in the articles
  • Make sure that Honeycomb articles are tagged with appropriate categories
  • Eliminate redundancy
    • Merge duplicate articles on the same topic. For example, it is highly likely that a guide article, a top ten article and a vulnerability/attack article exist on a same topic.
    • Redirect well-know acronyms and case-sensitive titles to the master article. (Example, XSS to Cross Site Scripting")
    • Plan: go over by topics.
  • Go over the CLASP articles to:
    • Add the same article structure, i.e., the "Related ..." sections, to the CLASP articles;
    • Make sure they are marked with appropriate templates: vulnerability, attack, principle, etc;
    • Make sure they are tagged with appropriate categories.
  • Merge duplicate vulnerability categories. (Replace "...problem/error" with "...vulnerability" when it is appropriate.)
  • Make sure all articles that have code snippets are marked with the "Code Snippet" category and corresponding languages.

Specific tasks

  • Merge "Buffer overflow", "Buffer Overflow" and related redundant articles
  • Merge "Cross Site Scripting" and "Cross-site_scripting"
  • Merge "SQL Injection" and "SQL injection"

Roadmap

OWASP Honeycomb Project Roadmap

Subcategories

This category has the following 9 subcategories, out of 9 total.

C

C cont.

T

V

Pages in category "OWASP Honeycomb Project"

This category contains only the following page.