Major Discussion Points for CWE Content
|
Inclusion | how certain types of nodes should be captured in CWE |
Abstraction | whether some nodes are at the right level of abstraction, i.e. could be split into sub-nodes, or perhaps should be merged into a single node |
Perspective | whether nodes are really described from the core, underlying "weakness" - and how other types of issues should be represented in the Common "Weakness" Enumeration. |
Included with each discussion point is:
Language-Specific Issues (LANGSPEC) | There are entries in CWE that describe a weakness in a way that is specific to a certain language or even a particular function within a language. |
Resource-Specific Issues (RESSPEC) | Several groups of entries take a general weakness and create more specialized entries based on specific types of resources (e.g. files). |
Technology-Specific Issues (TECHSPEC) | A fairly large group of entries describe weaknesses specific to a particular technology, such as specific OSes, frameworks, representations, or protocols. |
Context-Specific Issues (CONSPEC) | Some issues are generally thought of to be "bad practice" or misuse, but they can be used in certain contexts that are legitimate. |
Quality Indicators (QUALITY) | Some CWE entries describe properties of code that are relevant to quality and security, but do not directly introduce other weaknesses or vulnerabilities. |
Other Discussion Points | Other discussion points exist, but they have not been fully
documented yet. MITRE will document and propose these over the
upcoming months, as community input helps to clarify them. These
issues include:
|
Document version: 0.1 Date: September 12, 2007
This is a draft document. It is intended to support maintenance of CWE, and to educate and solicit feedback from a specific technical audience. This document does not reflect any official position of the MITRE Corporation or its sponsors. Copyright © 2007, The MITRE Corporation. All rights reserved. Permission is granted to redistribute this document if this paragraph is not removed. This document is subject to change without notice.