Showing:

Annotations
Attributes
Diagrams
Facets
Source
Used by
Imported schema ap_schema_v2.5.xsd
Namespace http://capec.mitre.org/capec-2
Element capec:Attack_PatternType / capec:Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains a detailed description of the attack including the chain of actions taken by the attacker. More comprehensive descriptions could include relevant attack trees and/or exploit graphs to more clearly elaborate this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Description_Summary ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow
Children capec:Attack_Execution_Flow, capec:Summary
Source
<xs:element name="Description" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field contains a detailed description of the attack including the chain of actions taken by the attacker. More comprehensive descriptions could include relevant attack trees and/or exploit graphs to more clearly elaborate this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Summary" type="capec:Structured_Text_Type">
        <xs:annotation>
          <xs:documentation>Brief description of what the attack involves and what weaknesses it is leveraging for exploit.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Attack_Execution_Flow" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Outline of the steps involved in an attacker executing the typical flow of the attack.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Description / capec:Summary
Namespace http://capec.mitre.org/capec-2
Annotations
Brief description of what the attack involves and what weaknesses it is leveraging for exploit.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Summary" type="capec:Structured_Text_Type">
  <xs:annotation>
    <xs:documentation>Brief description of what the attack involves and what weaknesses it is leveraging for exploit.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Text_Title
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to definebold-faced title for a subsequent block of text.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Text_Title" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to definebold-faced title for a subsequent block of text.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Text
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to define a paragraph of text.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Text" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to define a paragraph of text.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Code_Example_Language
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to identify the programming language being used in the following block of Code
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Language_Type
Type capec:Language_Type
Facets
enumeration C
enumeration C++
enumeration C#
enumeration Java
enumeration JSP
enumeration Javascript
enumeration ASP.NET
enumeration SQL
enumeration Python
enumeration Perl
enumeration PHP
enumeration SOAP
enumeration Ruby
enumeration Shell
enumeration PseudoCode
enumeration .NET
enumeration Assembly
enumeration XML
enumeration HTML
Source
<xs:element name="Code_Example_Language" type="capec:Language_Type" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to identify the programming language being used in the following block of Code</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Code
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to define a line of code.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Code" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to define a line of code.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Comment
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to define a
comment in code.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Comment" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to define a comment in code.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Images
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to define an
image.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Structured_Text_Group_Images_Image
Children capec:Image
Source
<xs:element name="Images" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to define an image.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Image" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to define an image.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence maxOccurs="unbounded">
            <xs:element name="Image_Location" type="xs:string">
              <xs:annotation>
                <xs:documentation>This element provides the location of the image file.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Image_Title" type="xs:string">
              <xs:annotation>
                <xs:documentation>This element provides a title for the image.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Structured_Text_Group / capec:Images / capec:Image
Namespace http://capec.mitre.org/capec-2
Annotations
Presentation Element: This element is used to define an image.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Structured_Text_Group_Images_Structured_Text_Group_Structured_Text_Group_Images_Image_Image_Location ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Structured_Text_Group_Images_Structured_Text_Group_Structured_Text_Group_Images_Image_Image_Title
Children capec:Image_Location, capec:Image_Title
Source
<xs:element name="Image" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Presentation Element: This element is used to define an image.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence maxOccurs="unbounded">
      <xs:element name="Image_Location" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element provides the location of the image file.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Image_Title" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element provides a title for the image.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Structured_Text_Group / capec:Images / capec:Image / capec:Image_Location
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides the location of the image file.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Image_Location" type="xs:string">
  <xs:annotation>
    <xs:documentation>This element provides the location of the image file.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Structured_Text_Group / capec:Images / capec:Image / capec:Image_Title
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides a title for the image.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Image_Title" type="xs:string">
  <xs:annotation>
    <xs:documentation>This element provides a title for the image.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Block
Namespace http://capec.mitre.org/capec-2
Annotations
Block is a Structured_Text element consisting of one of Text_Title,
Text, Code_Example_Language, or Code followed by another Block element.
Structured_Text elements help define whitespace and text segments.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Block_Block_Nature ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block
Used by
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Attributes
QName Type Fixed Default Use Annotation
Block_Nature restriction of xs:string optional
This attribute identifies the nature of the content containedwithin the Block.
Source
<xs:element name="Block">
  <xs:annotation>
    <xs:documentation>Block is a Structured_Text element consisting of one of Text_Title, Text, Code_Example_Language, or Code followed by another Block element. Structured_Text elements help define whitespace and text segments.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:group ref="capec:Structured_Text_Group"/>
      <xs:element ref="capec:Block">
        <xs:annotation>
          <xs:documentation>Block is a Structured_Text element consisting of one of Text_Title,Text, Code_Example_Language, or Code followed by another Block element. Structured_Text elements help define whitespace and text segments.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:attribute name="Block_Nature">
      <xs:annotation>
        <xs:documentation>This attribute identifies the nature of the content containedwithin the Block.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Good_Code"/>
          <xs:enumeration value="Bad_Code"/>
          <xs:enumeration value="Mitigation_Code"/>
          <xs:enumeration value="Attack"/>
          <xs:enumeration value="Result"/>
          <xs:enumeration value="List"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Phases
Used by
Children capec:Attack_Phases
Source
<xs:element name="Attack_Execution_Flow">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Phases">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Attack_Phase" maxOccurs="3">
              <xs:annotation>
                <xs:documentation>Segment the attack steps into the various phases of attack. One of three phases "Explore," "Experiment," or "Exploit." Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out. The exploration and experimentation phases may or may not occur during a particular attack, because the attacker may already know exactly how to exploit a system.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:annotation>
                    <xs:documentation>One of three phases "Explore," "Experiment," or "Exploit." Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out.</xs:documentation>
                  </xs:annotation>
                  <xs:element name="Attack_Steps">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Attack_Step" maxOccurs="unbounded">
                          <xs:annotation>
                            <xs:documentation>Brief description of an individual action step in carrying out the attack</xs:documentation>
                          </xs:annotation>
                          <xs:complexType>
                            <xs:choice>
                              <xs:element name="Common_Attack_Step">
                                <xs:complexType>
                                  <xs:sequence>
                                    <xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
                                  </xs:sequence>
                                  <xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
                                </xs:complexType>
                              </xs:element>
                              <xs:element name="Custom_Attack_Step" type="capec:Custom_Attack_StepType"/>
                            </xs:choice>
                            <xs:attribute name="ID" type="xs:integer" use="required"/>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="ID" type="xs:integer" use="required"/>
                <xs:attribute name="Name" use="required">
                  <xs:annotation>
                    <xs:documentation>"Explore," "Experiment," or "Exploit."</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:token">
                      <xs:enumeration value="Explore"/>
                      <xs:enumeration value="Experiment"/>
                      <xs:enumeration value="Exploit"/>
                      <xs:enumeration value=""/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow / capec:Attack_Phases
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase
Children capec:Attack_Phase
Source
<xs:element name="Attack_Phases">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Phase" maxOccurs="3">
        <xs:annotation>
          <xs:documentation>Segment the attack steps into the various phases of attack. One of three phases "Explore," "Experiment," or "Exploit." Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out. The exploration and experimentation phases may or may not occur during a particular attack, because the attacker may already know exactly how to exploit a system.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:annotation>
              <xs:documentation>One of three phases "Explore," "Experiment," or "Exploit." Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out.</xs:documentation>
            </xs:annotation>
            <xs:element name="Attack_Steps">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Attack_Step" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:documentation>Brief description of an individual action step in carrying out the attack</xs:documentation>
                    </xs:annotation>
                    <xs:complexType>
                      <xs:choice>
                        <xs:element name="Common_Attack_Step">
                          <xs:complexType>
                            <xs:sequence>
                              <xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
                            </xs:sequence>
                            <xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
                          </xs:complexType>
                        </xs:element>
                        <xs:element name="Custom_Attack_Step" type="capec:Custom_Attack_StepType"/>
                      </xs:choice>
                      <xs:attribute name="ID" type="xs:integer" use="required"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required"/>
          <xs:attribute name="Name" use="required">
            <xs:annotation>
              <xs:documentation>"Explore," "Experiment," or "Exploit."</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:token">
                <xs:enumeration value="Explore"/>
                <xs:enumeration value="Experiment"/>
                <xs:enumeration value="Exploit"/>
                <xs:enumeration value=""/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase
Namespace http://capec.mitre.org/capec-2
Annotations
Segment the attack steps into the various phases of attack. One of three phases "Explore," "Experiment," or "Exploit."  Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out. The exploration and experimentation phases may or may not occur during a particular attack, because the attacker may already know exactly how to exploit a system.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_ID ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Name ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps
Children capec:Attack_Steps
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Name restriction of xs:token required
"Explore," "Experiment," or "Exploit."
Source
<xs:element name="Attack_Phase" maxOccurs="3">
  <xs:annotation>
    <xs:documentation>Segment the attack steps into the various phases of attack. One of three phases "Explore," "Experiment," or "Exploit." Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out. The exploration and experimentation phases may or may not occur during a particular attack, because the attacker may already know exactly how to exploit a system.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:annotation>
        <xs:documentation>One of three phases "Explore," "Experiment," or "Exploit." Each phase should appear at most once, and attack steps should be grouped by what kind of activities the attacker is carrying out.</xs:documentation>
      </xs:annotation>
      <xs:element name="Attack_Steps">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Attack_Step" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>Brief description of an individual action step in carrying out the attack</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:choice>
                  <xs:element name="Common_Attack_Step">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
                      </xs:sequence>
                      <xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
                    </xs:complexType>
                  </xs:element>
                  <xs:element name="Custom_Attack_Step" type="capec:Custom_Attack_StepType"/>
                </xs:choice>
                <xs:attribute name="ID" type="xs:integer" use="required"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
    <xs:attribute name="Name" use="required">
      <xs:annotation>
        <xs:documentation>"Explore," "Experiment," or "Exploit."</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:enumeration value="Explore"/>
          <xs:enumeration value="Experiment"/>
          <xs:enumeration value="Exploit"/>
          <xs:enumeration value=""/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step
Children capec:Attack_Step
Source
<xs:element name="Attack_Steps">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Step" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Brief description of an individual action step in carrying out the attack</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:choice>
            <xs:element name="Common_Attack_Step">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
                </xs:sequence>
                <xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
              </xs:complexType>
            </xs:element>
            <xs:element name="Custom_Attack_Step" type="capec:Custom_Attack_StepType"/>
          </xs:choice>
          <xs:attribute name="ID" type="xs:integer" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps / capec:Attack_Step
Namespace http://capec.mitre.org/capec-2
Annotations
Brief description of an individual action step
in carrying out the attack
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_ID ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_Common_Attack_Step ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_Custom_Attack_Step
Children capec:Common_Attack_Step, capec:Custom_Attack_Step
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Source
<xs:element name="Attack_Step" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Brief description of an individual action step in carrying out the attack</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="Common_Attack_Step">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
          </xs:sequence>
          <xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
        </xs:complexType>
      </xs:element>
      <xs:element name="Custom_Attack_Step" type="capec:Custom_Attack_StepType"/>
    </xs:choice>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps / capec:Attack_Step / capec:Common_Attack_Step
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_Common_Attack_Step_Common_Attack_Step_ID ap_schema_v2_5_xsd.tmp#Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Execution_Flow_Attack_Execution_Flow_Attack_Phases_Attack_Phase_Attack_Steps_Attack_Step_Common_Attack_Step_Pattern_Specific_Overrides
Children capec:Pattern_Specific_Overrides
Attributes
QName Type Fixed Default Use Annotation
Common_Attack_Step_ID xs:integer required
Source
<xs:element name="Common_Attack_Step">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
    </xs:sequence>
    <xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps / capec:Attack_Step / capec:Common_Attack_Step / capec:Pattern_Specific_Overrides
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Title ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Techniques ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Indicators ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Outcomes ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Security_Controls ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Observables ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType
Type capec:Custom_Attack_StepType
Children capec:Attack_Step_Description, capec:Attack_Step_Techniques, capec:Attack_Step_Title, capec:Indicators, capec:Observables, capec:Outcomes, capec:Security_Controls
Source
<xs:element name="Pattern_Specific_Overrides" type="capec:Custom_Attack_StepType"/>
Element capec:Custom_Attack_StepType / capec:Attack_Step_Title
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains a short descriptive title for the attack step. It should be kept as short as possible but also clearly convey the nature of the attack step being described.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Attack_Step_Title" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field contains a short descriptive title for the attack step. It should be kept as short as possible but also clearly convey the nature of the attack step being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Attack_Step_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains a brief description of the attack step.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Attack_Step_Description" type="capec:Structured_Text_Type">
  <xs:annotation>
    <xs:documentation>This field contains a brief description of the attack step.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Attack_Step_Techniques
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Step_Technique
Children capec:Attack_Step_Technique
Source
<xs:element name="Attack_Step_Techniques" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="capec:Attack_Step_Technique" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field captures various techniques that the attacker can use to achieve the attack step's goal. For example, an attacker may use tools such as WebScarab and Tamper Data in the experimentation phase of a SQL Injection attack pattern. The techniques include references to environments, because not all techniques work in all environments</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Step_Technique
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_ID ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_Attack_Step_Technique_Description ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_Leveraged_Attack_Patterns ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_Relevant_Attack_Surface_Elements ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_Observables ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_Environments
Used by
Children capec:Attack_Step_Technique_Description, capec:Environments, capec:Leveraged_Attack_Patterns, capec:Observables, capec:Relevant_Attack_Surface_Elements
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Source
<xs:element name="Attack_Step_Technique">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>A particular technique that may accomplish this attack step.</xs:documentation>
    </xs:annotation>
    <xs:all>
      <xs:element name="Attack_Step_Technique_Description" type="capec:Structured_Text_Type">
        <xs:annotation>
          <xs:documentation>This field contains a brief description of the attack step technique.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Leveraged_Attack_Patterns" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Leveraged_Attack_Pattern_ID" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
      <xs:element name="Environments" type="xs:IDREFS">
        <xs:annotation>
          <xs:documentation>References the defined environments where this attack step technique is applicable.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:all>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:Attack_Step_Technique / capec:Attack_Step_Technique_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains a brief description of the attack step technique.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Attack_Step_Technique_Description" type="capec:Structured_Text_Type">
  <xs:annotation>
    <xs:documentation>This field contains a brief description of the attack step technique.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_Step_Technique / capec:Leveraged_Attack_Patterns
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Step_Technique_Attack_Step_Technique_Leveraged_Attack_Patterns_Leveraged_Attack_Pattern_ID
Children capec:Leveraged_Attack_Pattern_ID
Source
<xs:element name="Leveraged_Attack_Patterns" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Leveraged_Attack_Pattern_ID" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Step_Technique / capec:Leveraged_Attack_Patterns / capec:Leveraged_Attack_Pattern_ID
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Source
<xs:element name="Leveraged_Attack_Pattern_ID" maxOccurs="unbounded"/>
Element capec:Attack_Step_Technique / capec:Relevant_Attack_Surface_Elements
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocols ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType
Type capec:Relevant_Attack_Surface_ElementsType
Children capec:Relevant_Command_Structures, capec:Relevant_Functional_Services, capec:Relevant_Protocol_Headers, capec:Relevant_Protocols
Source
<xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Functional_Services
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services_Relevant_Functional_Service_ID
Children capec:Relevant_Functional_Service_ID
Source
<xs:element name="Relevant_Functional_Services" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Functional_Service_ID" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Functional_Services / capec:Relevant_Functional_Service_ID
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Source
<xs:element name="Relevant_Functional_Service_ID" maxOccurs="unbounded"/>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Protocols
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Attack_Surface_ElementsType_Relevant_Protocols_Relevant_Protocol_ID
Children capec:Relevant_Protocol_ID
Source
<xs:element name="Relevant_Protocols" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Protocol_ID" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Protocols / capec:Relevant_Protocol_ID
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Source
<xs:element name="Relevant_Protocol_ID" maxOccurs="unbounded"/>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Protocol_Headers
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers_Relevant_Protocol_Header_ID
Children capec:Relevant_Protocol_Header_ID
Source
<xs:element name="Relevant_Protocol_Headers" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Protocol_Header_ID" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Protocol_Headers / capec:Relevant_Protocol_Header_ID
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Source
<xs:element name="Relevant_Protocol_Header_ID" maxOccurs="unbounded"/>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Command_Structures
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures_Relevant_Command_Structure_ID
Children capec:Relevant_Command_Structure_ID
Source
<xs:element name="Relevant_Command_Structures" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Command_Structure_ID" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Relevant_Attack_Surface_ElementsType / capec:Relevant_Command_Structures / capec:Relevant_Command_Structure_ID
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Source
<xs:element name="Relevant_Command_Structure_ID" maxOccurs="unbounded"/>
Element capec:Attack_Step_Technique / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Attack_Step_Technique / capec:Environments
Namespace http://capec.mitre.org/capec-2
Annotations
References the defined environments where this attack step technique is applicable.
Diagram
Diagram
Type xs:IDREFS
Source
<xs:element name="Environments" type="xs:IDREFS">
  <xs:annotation>
    <xs:documentation>References the defined environments where this attack step technique is applicable.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Indicators
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator
Children capec:Indicator
Source
<xs:element name="Indicators" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Indicator" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>These are indicators that the application may or may not be susceptible to the given attack step (not necessarily the pattern as a whole).</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:all>
            <xs:element name="Indicator_Description" type="capec:Structured_Text_Type">
              <xs:annotation>
                <xs:documentation>This field contains a brief description of the indicator.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
            <xs:element name="Environments" type="xs:IDREFS">
              <xs:annotation>
                <xs:documentation>References the defined environments where this indicator of susceptibility is applicable.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
          </xs:all>
          <xs:attribute name="ID" type="xs:integer" use="required">
            <xs:annotation>
              <xs:documentation>This field contains a unique integer identifier for the indicator.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="type" use="required">
            <xs:annotation>
              <xs:documentation>Each indicator has a mandatory type attribute that can be one of the values "Positive," "Negative," or "Inconclusive." For example, a positive indicator of susceptibility to parameter tampering is the existence of parameters in the URL. Although it does not guarantee susceptibility, it indicates a cause for further examination. A negative indicator for the technique of privilege escalation is a lack of credentials and user identifiers in an application. Again, this is not a conclusive measure of resistance to attack, but an indicator that the attack step technique is unlikely to bear significant fruit. An inconclusive indicator of susceptibility to dynamic code injection is a page whose URL ends in .jsp, .asp, or .do but which has no visible explicit parameters. Such URLs typically indicate dynamic processing, but since no visible parameters are passed, it is inconclusive whether dynamic code could be injected into the application.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:token">
                <xs:enumeration value="Positive"/>
                <xs:enumeration value="Negative"/>
                <xs:enumeration value="Inconclusive"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator
Namespace http://capec.mitre.org/capec-2
Annotations
These are indicators that the application may or may not be susceptible to the given attack step (not necessarily the pattern as a whole).
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator_ID ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator_type ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator_Indicator_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator_Relevant_Attack_Surface_Elements ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator_Environments ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Custom_Attack_StepType_Custom_Attack_StepType_Indicators_Indicator_Observables
Children capec:Environments, capec:Indicator_Description, capec:Observables, capec:Relevant_Attack_Surface_Elements
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
This field contains a unique integer identifier for the indicator.
type restriction of xs:token required
Each indicator has a mandatory type attribute that can be one of the values "Positive," "Negative," or "Inconclusive." For example, a positive indicator of susceptibility to parameter tampering is the existence of parameters in the URL. Although it does not guarantee susceptibility, it indicates a cause for further examination. A negative indicator for the technique of privilege escalation is a lack of credentials and user identifiers in an application. Again, this is not a conclusive measure of resistance to attack, but an indicator that the attack step technique is unlikely to bear significant fruit. An inconclusive indicator of susceptibility to dynamic code injection is a page whose URL ends in .jsp, .asp, or .do but which has no visible explicit parameters. Such URLs typically indicate dynamic processing, but since no visible parameters are passed, it is inconclusive whether dynamic code could be injected into the application.
Source
<xs:element name="Indicator" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>These are indicators that the application may or may not be susceptible to the given attack step (not necessarily the pattern as a whole).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:all>
      <xs:element name="Indicator_Description" type="capec:Structured_Text_Type">
        <xs:annotation>
          <xs:documentation>This field contains a brief description of the indicator.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
      <xs:element name="Environments" type="xs:IDREFS">
        <xs:annotation>
          <xs:documentation>References the defined environments where this indicator of susceptibility is applicable.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
    </xs:all>
    <xs:attribute name="ID" type="xs:integer" use="required">
      <xs:annotation>
        <xs:documentation>This field contains a unique integer identifier for the indicator.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="type" use="required">
      <xs:annotation>
        <xs:documentation>Each indicator has a mandatory type attribute that can be one of the values "Positive," "Negative," or "Inconclusive." For example, a positive indicator of susceptibility to parameter tampering is the existence of parameters in the URL. Although it does not guarantee susceptibility, it indicates a cause for further examination. A negative indicator for the technique of privilege escalation is a lack of credentials and user identifiers in an application. Again, this is not a conclusive measure of resistance to attack, but an indicator that the attack step technique is unlikely to bear significant fruit. An inconclusive indicator of susceptibility to dynamic code injection is a page whose URL ends in .jsp, .asp, or .do but which has no visible explicit parameters. Such URLs typically indicate dynamic processing, but since no visible parameters are passed, it is inconclusive whether dynamic code could be injected into the application.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:enumeration value="Positive"/>
          <xs:enumeration value="Negative"/>
          <xs:enumeration value="Inconclusive"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator / capec:Indicator_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains a brief description of the indicator.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Indicator_Description" type="capec:Structured_Text_Type">
  <xs:annotation>
    <xs:documentation>This field contains a brief description of the indicator.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator / capec:Relevant_Attack_Surface_Elements
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocols ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType
Type capec:Relevant_Attack_Surface_ElementsType
Children capec:Relevant_Command_Structures, capec:Relevant_Functional_Services, capec:Relevant_Protocol_Headers, capec:Relevant_Protocols
Source
<xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
Element capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator / capec:Environments
Namespace http://capec.mitre.org/capec-2
Annotations
References the defined environments where this indicator of susceptibility  is applicable.
Diagram
Diagram
Type xs:IDREFS
Source
<xs:element name="Environments" type="xs:IDREFS">
  <xs:annotation>
    <xs:documentation>References the defined environments where this indicator of susceptibility is applicable.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Custom_Attack_StepType / capec:Outcomes
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Outcome
Children capec:Outcome
Source
<xs:element name="Outcomes" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Outcome" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field captures possible outcomes for this attack step.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Outcome_Description" type="xs:string"/>
            <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
            <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required">
            <xs:annotation>
              <xs:documentation>This field contains a unique integer identifier for the outcome.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="type" use="required">
            <xs:annotation>
              <xs:documentation>An outcome has a mandatory type attribute that can be one of the values "success," "failure," or "inconclusive." It indicates what results of executing the attack step techniques should be considered successes, which should be considered failures, and which ones are inconclusive. Outcomes' successes are determined relative to the attacker's point of view. It is a success if the attack step got the attacker closer to his goal of attacking the application. It is a failure if the attacker got no closer to his goal.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:token">
                <xs:enumeration value="Success"/>
                <xs:enumeration value="Failure"/>
                <xs:enumeration value="Inconclusive"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Outcomes / capec:Outcome
Namespace http://capec.mitre.org/capec-2
Annotations
This field captures possible outcomes for this attack step.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Outcome_ID ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Outcome_type ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Outcome_Outcome_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Outcome_Relevant_Attack_Surface_Elements ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Custom_Attack_StepType_Custom_Attack_StepType_Outcomes_Outcome_Observables
Children capec:Observables, capec:Outcome_Description, capec:Relevant_Attack_Surface_Elements
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
This field contains a unique integer identifier for the outcome.
type restriction of xs:token required
An outcome has a mandatory type attribute that can be one of the values "success," "failure," or "inconclusive." It indicates what results of executing the attack step techniques should be considered successes, which should be considered failures, and which ones are inconclusive. Outcomes' successes are determined relative to the attacker's point of view. It is a success if the attack step got the attacker closer to his goal of attacking the application. It is a failure if the attacker got no closer to his goal.
Source
<xs:element name="Outcome" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field captures possible outcomes for this attack step.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Outcome_Description" type="xs:string"/>
      <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required">
      <xs:annotation>
        <xs:documentation>This field contains a unique integer identifier for the outcome.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="type" use="required">
      <xs:annotation>
        <xs:documentation>An outcome has a mandatory type attribute that can be one of the values "success," "failure," or "inconclusive." It indicates what results of executing the attack step techniques should be considered successes, which should be considered failures, and which ones are inconclusive. Outcomes' successes are determined relative to the attacker's point of view. It is a success if the attack step got the attacker closer to his goal of attacking the application. It is a failure if the attacker got no closer to his goal.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:enumeration value="Success"/>
          <xs:enumeration value="Failure"/>
          <xs:enumeration value="Inconclusive"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Outcomes / capec:Outcome / capec:Outcome_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Outcome_Description" type="xs:string"/>
Element capec:Custom_Attack_StepType / capec:Outcomes / capec:Outcome / capec:Relevant_Attack_Surface_Elements
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocols ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType
Type capec:Relevant_Attack_Surface_ElementsType
Children capec:Relevant_Command_Structures, capec:Relevant_Functional_Services, capec:Relevant_Protocol_Headers, capec:Relevant_Protocols
Source
<xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
Element capec:Custom_Attack_StepType / capec:Outcomes / capec:Outcome / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Custom_Attack_StepType / capec:Security_Controls
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control
Children capec:Security_Control
Source
<xs:element name="Security_Controls" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Security_Control" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field captures security controls for this attack step that describe ways in which the attack step can be detected, corrected, or prevented. These are presented from a defender's point of view, where the defender may be a developer, tester, operations administrator, or other resource resisting the attacker.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Security_Control_Description" type="xs:string"/>
            <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
            <xs:element name="Observable_Evidence" minOccurs="0">
              <xs:complexType>
                <xs:choice>
                  <xs:element name="IfPresent_Observables" type="cybox:ObservablesType"/>
                  <xs:element name="IfNotPresent_Observables" type="cybox:ObservablesType"/>
                </xs:choice>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required">
            <xs:annotation>
              <xs:documentation>This field contains a unique integer identifier for the security control.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="type" use="required">
            <xs:annotation>
              <xs:documentation>Each security control has a mandatory type attribute that can be one of the values "Detective," "Corrective," or "Preventative." Detective controls detect an attacker's activities in the attack step, whether the activities are successful or not. Corrective controls attempt to mitigate an attacker's success by responding to a successful outcome. They are not related to or normalized against outcomes. Preventative controls are those that make the attack step unlikely or impossible to succeed.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:token">
                <xs:enumeration value="Detective"/>
                <xs:enumeration value="Corrective"/>
                <xs:enumeration value="Preventative"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control
Namespace http://capec.mitre.org/capec-2
Annotations
This field captures security controls for this attack step that describe ways in which the attack step can be detected, corrected, or prevented. These are presented from a defender's point of view, where the defender may be a developer, tester, operations administrator, or other resource resisting the attacker.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_ID ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_type ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Security_Control_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Relevant_Attack_Surface_Elements ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Observable_Evidence
Children capec:Observable_Evidence, capec:Relevant_Attack_Surface_Elements, capec:Security_Control_Description
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
This field contains a unique integer identifier for the security control.
type restriction of xs:token required
Each security control has a mandatory type attribute that can be one of the values "Detective," "Corrective," or "Preventative." Detective controls detect an attacker's activities in the attack step, whether the activities are successful or not. Corrective controls attempt to mitigate an attacker's success by responding to a successful outcome. They are not related to or normalized against outcomes. Preventative controls are those that make the attack step unlikely or impossible to succeed.
Source
<xs:element name="Security_Control" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field captures security controls for this attack step that describe ways in which the attack step can be detected, corrected, or prevented. These are presented from a defender's point of view, where the defender may be a developer, tester, operations administrator, or other resource resisting the attacker.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Security_Control_Description" type="xs:string"/>
      <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
      <xs:element name="Observable_Evidence" minOccurs="0">
        <xs:complexType>
          <xs:choice>
            <xs:element name="IfPresent_Observables" type="cybox:ObservablesType"/>
            <xs:element name="IfNotPresent_Observables" type="cybox:ObservablesType"/>
          </xs:choice>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required">
      <xs:annotation>
        <xs:documentation>This field contains a unique integer identifier for the security control.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="type" use="required">
      <xs:annotation>
        <xs:documentation>Each security control has a mandatory type attribute that can be one of the values "Detective," "Corrective," or "Preventative." Detective controls detect an attacker's activities in the attack step, whether the activities are successful or not. Corrective controls attempt to mitigate an attacker's success by responding to a successful outcome. They are not related to or normalized against outcomes. Preventative controls are those that make the attack step unlikely or impossible to succeed.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:token">
          <xs:enumeration value="Detective"/>
          <xs:enumeration value="Corrective"/>
          <xs:enumeration value="Preventative"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / capec:Security_Control_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Security_Control_Description" type="xs:string"/>
Element capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / capec:Relevant_Attack_Surface_Elements
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocols ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType
Type capec:Relevant_Attack_Surface_ElementsType
Children capec:Relevant_Command_Structures, capec:Relevant_Functional_Services, capec:Relevant_Protocol_Headers, capec:Relevant_Protocols
Source
<xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
Element capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / capec:Observable_Evidence
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Observable_Evidence_IfPresent_Observables ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Custom_Attack_StepType_Custom_Attack_StepType_Security_Controls_Security_Control_Observable_Evidence_IfNotPresent_Observables
Children capec:IfNotPresent_Observables, capec:IfPresent_Observables
Source
<xs:element name="Observable_Evidence" minOccurs="0">
  <xs:complexType>
    <xs:choice>
      <xs:element name="IfPresent_Observables" type="cybox:ObservablesType"/>
      <xs:element name="IfNotPresent_Observables" type="cybox:ObservablesType"/>
    </xs:choice>
  </xs:complexType>
</xs:element>
Element capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / capec:Observable_Evidence / capec:IfPresent_Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="IfPresent_Observables" type="cybox:ObservablesType"/>
Element capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / capec:Observable_Evidence / capec:IfNotPresent_Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="IfNotPresent_Observables" type="cybox:ObservablesType"/>
Element capec:Custom_Attack_StepType / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps / capec:Attack_Step / capec:Custom_Attack_Step
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Title ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Techniques ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Indicators ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Outcomes ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Security_Controls ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Observables ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType
Type capec:Custom_Attack_StepType
Children capec:Attack_Step_Description, capec:Attack_Step_Techniques, capec:Attack_Step_Title, capec:Indicators, capec:Observables, capec:Outcomes, capec:Security_Controls
Source
<xs:element name="Custom_Attack_Step" type="capec:Custom_Attack_StepType"/>
Element capec:Alternate_Terms
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains one or more Alternate_Term elements, each of which contains other names used to describe this attack pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Alternate_Terms_Alternate_Term
Used by
Children capec:Alternate_Term
Source
<xs:element name="Alternate_Terms">
  <xs:annotation>
    <xs:documentation>This element contains one or more Alternate_Term elements, each of which contains other names used to describe this attack pattern.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Alternate_Term" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element contains alternate terms by which this attack pattern may be known and a description to explain the context in which the term may be relevant. This is not required for all entries and should only be included where appropriate.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Term" type="xs:string">
              <xs:annotation>
                <xs:documentation>This element contains the actual term for the Alternate_Term element. Each term should follow the same conventions as the entry Name attribute.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Alternate_Term_Description" type="capec:Structured_Text_Type" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element provides context to each Alternate_Term by which this attack pattern may be known.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Alternate_Terms / capec:Alternate_Term
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains alternate terms by which this
attack pattern may be known and a description to explain the context in which the term may be relevant. This is not required for all entries and should only be included where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Alternate_Terms_Alternate_Terms_Alternate_Term_Term ap_schema_v2_5_xsd.tmp#Alternate_Terms_Alternate_Terms_Alternate_Term_Alternate_Term_Description
Children capec:Alternate_Term_Description, capec:Term
Source
<xs:element name="Alternate_Term" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element contains alternate terms by which this attack pattern may be known and a description to explain the context in which the term may be relevant. This is not required for all entries and should only be included where appropriate.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Term" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element contains the actual term for the Alternate_Term element. Each term should follow the same conventions as the entry Name attribute.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Alternate_Term_Description" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element provides context to each Alternate_Term by which this attack pattern may be known.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Alternate_Terms / capec:Alternate_Term / capec:Term
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains the actual term for the Alternate_Term element. Each term should follow the same conventions as the entry Name attribute.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Term" type="xs:string">
  <xs:annotation>
    <xs:documentation>This element contains the actual term for the Alternate_Term element. Each term should follow the same conventions as the entry Name attribute.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Alternate_Terms / capec:Alternate_Term / capec:Alternate_Term_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides context to each
Alternate_Term by which this attack pattern may be known.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Alternate_Term_Description" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element provides context to each Alternate_Term by which this attack pattern may be known.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Target_Attack_Surface
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Common_Attack_Surface_Description ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Target_Attack_Surface_Description ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType
Type capec:Target_Attack_SurfaceType
Children capec:Common_Attack_Surface_Description, capec:Target_Attack_Surface_Description
Source
<xs:element name="Target_Attack_Surface" type="capec:Target_Attack_SurfaceType" minOccurs="0"/>
Element capec:Target_Attack_SurfaceType / capec:Common_Attack_Surface_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Target_Attack_SurfaceType_Common_Attack_Surface_Description_Common_Attack_Surface_ID ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Target_Attack_SurfaceType_Common_Attack_Surface_Description_Relevant_Attack_Surface_Elements ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Target_Attack_SurfaceType_Common_Attack_Surface_Description_Pattern_Specific_Overrides
Children capec:Pattern_Specific_Overrides, capec:Relevant_Attack_Surface_Elements
Attributes
QName Type Fixed Default Use Annotation
Common_Attack_Surface_ID optional
Source
<xs:element name="Common_Attack_Surface_Description">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType"/>
      <xs:element name="Pattern_Specific_Overrides" type="capec:Target_Attack_Surface_DescriptionType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="Common_Attack_Surface_ID"/>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_SurfaceType / capec:Common_Attack_Surface_Description / capec:Relevant_Attack_Surface_Elements
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocols ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType
Type capec:Relevant_Attack_Surface_ElementsType
Children capec:Relevant_Command_Structures, capec:Relevant_Functional_Services, capec:Relevant_Protocol_Headers, capec:Relevant_Protocols
Source
<xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType"/>
Element capec:Target_Attack_SurfaceType / capec:Common_Attack_Surface_Description / capec:Pattern_Specific_Overrides
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Targeted_OSI_Layers ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Localities ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Types ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Functional_Services ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType
Type capec:Target_Attack_Surface_DescriptionType
Children capec:Target_Attack_Surface_Localities, capec:Target_Attack_Surface_Types, capec:Target_Functional_Services, capec:Targeted_OSI_Layers
Source
<xs:element name="Pattern_Specific_Overrides" type="capec:Target_Attack_Surface_DescriptionType" minOccurs="0"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Targeted_OSI_Layers
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Targeted_OSI_Layers_Targeted_OSI_Layer
Children capec:Targeted_OSI_Layer
Source
<xs:element name="Targeted_OSI_Layers">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Targeted_OSI_Layer" maxOccurs="unbounded">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Physical Layer"/>
            <xs:enumeration value="Data Link Layer"/>
            <xs:enumeration value="Network Layer"/>
            <xs:enumeration value="Transport Layer"/>
            <xs:enumeration value="Session Layer"/>
            <xs:enumeration value="Presentation Layer"/>
            <xs:enumeration value="Application Layer"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Targeted_OSI_Layers / capec:Targeted_OSI_Layer
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Physical Layer
enumeration Data Link Layer
enumeration Network Layer
enumeration Transport Layer
enumeration Session Layer
enumeration Presentation Layer
enumeration Application Layer
Source
<xs:element name="Targeted_OSI_Layer" maxOccurs="unbounded">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Physical Layer"/>
      <xs:enumeration value="Data Link Layer"/>
      <xs:enumeration value="Network Layer"/>
      <xs:enumeration value="Transport Layer"/>
      <xs:enumeration value="Session Layer"/>
      <xs:enumeration value="Presentation Layer"/>
      <xs:enumeration value="Application Layer"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Attack_Surface_Localities
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Localities_Target_Attack_Surface_Locality
Children capec:Target_Attack_Surface_Locality
Source
<xs:element name="Target_Attack_Surface_Localities">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Target_Attack_Surface_Locality" maxOccurs="unbounded">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Client-side"/>
            <xs:enumeration value="Server-side"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Attack_Surface_Localities / capec:Target_Attack_Surface_Locality
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Client-side
enumeration Server-side
Source
<xs:element name="Target_Attack_Surface_Locality" maxOccurs="unbounded">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Client-side"/>
      <xs:enumeration value="Server-side"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Attack_Surface_Types
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Types_Target_Attack_Surface_Type
Children capec:Target_Attack_Surface_Type
Source
<xs:element name="Target_Attack_Surface_Types">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Target_Attack_Surface_Type" maxOccurs="unbounded">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Network"/>
            <xs:enumeration value="Host"/>
            <xs:enumeration value="Service"/>
            <xs:enumeration value="Non-Web Application"/>
            <xs:enumeration value="Web Application"/>
            <xs:enumeration value="Firewall"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Attack_Surface_Types / capec:Target_Attack_Surface_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Network
enumeration Host
enumeration Service
enumeration Non-Web Application
enumeration Web Application
enumeration Firewall
Source
<xs:element name="Target_Attack_Surface_Type" maxOccurs="unbounded">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Network"/>
      <xs:enumeration value="Host"/>
      <xs:enumeration value="Service"/>
      <xs:enumeration value="Non-Web Application"/>
      <xs:enumeration value="Web Application"/>
      <xs:enumeration value="Firewall"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service
Children capec:Target_Functional_Service
Source
<xs:element name="Target_Functional_Services" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Target_Functional_Service" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Protocol" minOccurs="0" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Protocol_Structure" minOccurs="0">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Protocol_Header" maxOccurs="unbounded">
                          <xs:complexType>
                            <xs:sequence>
                              <xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                              <xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                              <xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                              <xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                              <xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                              <xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                              <xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                            </xs:sequence>
                            <xs:attribute name="ID" type="xs:integer" use="required"/>
                            <xs:attribute name="Name" type="xs:string"/>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                  <xs:element name="Command_Structures" minOccurs="0">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Command_Structure" maxOccurs="unbounded">
                          <xs:complexType>
                            <xs:sequence>
                              <xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
                              <xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
                              <xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
                            </xs:sequence>
                            <xs:attribute name="ID" type="xs:integer" use="required"/>
                            <xs:attribute name="Name" type="xs:string" use="required"/>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                  <xs:element name="Related_Protocols" minOccurs="0">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Related_Protocol" maxOccurs="unbounded">
                          <xs:complexType>
                            <xs:sequence>
                              <xs:element name="Relationship_Type" maxOccurs="unbounded">
                                <xs:simpleType>
                                  <xs:restriction base="xs:string">
                                    <xs:enumeration value="Is an abstraction of"/>
                                    <xs:enumeration value="Is a refinement of"/>
                                    <xs:enumeration value="Is an alternative to"/>
                                    <xs:enumeration value="Uses Protocol"/>
                                    <xs:enumeration value="Is a service of"/>
                                    <xs:enumeration value="Is a command of"/>
                                  </xs:restriction>
                                </xs:simpleType>
                              </xs:element>
                            </xs:sequence>
                            <xs:attribute name="Name"/>
                            <xs:attribute name="RFC"/>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="ID" type="xs:integer" use="required"/>
                <xs:attribute name="Name" type="xs:string" use="required"/>
                <xs:attribute name="RFC" type="xs:string"/>
                <xs:attribute name="Encryption" type="xs:boolean"/>
                <xs:attribute name="Encryption_Type" type="xs:string"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required"/>
          <xs:attribute name="Name" type="xs:string" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_ID ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Name ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol
Children capec:Protocol
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Name xs:string required
Source
<xs:element name="Target_Functional_Service" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Protocol" minOccurs="0" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Protocol_Structure" minOccurs="0">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Protocol_Header" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                      </xs:sequence>
                      <xs:attribute name="ID" type="xs:integer" use="required"/>
                      <xs:attribute name="Name" type="xs:string"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="Command_Structures" minOccurs="0">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Command_Structure" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
                        <xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
                        <xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
                      </xs:sequence>
                      <xs:attribute name="ID" type="xs:integer" use="required"/>
                      <xs:attribute name="Name" type="xs:string" use="required"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="Related_Protocols" minOccurs="0">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Related_Protocol" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Relationship_Type" maxOccurs="unbounded">
                          <xs:simpleType>
                            <xs:restriction base="xs:string">
                              <xs:enumeration value="Is an abstraction of"/>
                              <xs:enumeration value="Is a refinement of"/>
                              <xs:enumeration value="Is an alternative to"/>
                              <xs:enumeration value="Uses Protocol"/>
                              <xs:enumeration value="Is a service of"/>
                              <xs:enumeration value="Is a command of"/>
                            </xs:restriction>
                          </xs:simpleType>
                        </xs:element>
                      </xs:sequence>
                      <xs:attribute name="Name"/>
                      <xs:attribute name="RFC"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required"/>
          <xs:attribute name="Name" type="xs:string" use="required"/>
          <xs:attribute name="RFC" type="xs:string"/>
          <xs:attribute name="Encryption" type="xs:boolean"/>
          <xs:attribute name="Encryption_Type" type="xs:string"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
    <xs:attribute name="Name" type="xs:string" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_ID ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Name ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_RFC ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Encryption ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Encryption_Type ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Related_Protocols
Children capec:Command_Structures, capec:Protocol_Structure, capec:Related_Protocols
Attributes
QName Type Fixed Default Use Annotation
Encryption xs:boolean optional
Encryption_Type xs:string optional
ID xs:integer required
Name xs:string required
RFC xs:string optional
Source
<xs:element name="Protocol" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Protocol_Structure" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Protocol_Header" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                  <xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                  <xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                  <xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                  <xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                  <xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                  <xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="ID" type="xs:integer" use="required"/>
                <xs:attribute name="Name" type="xs:string"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Command_Structures" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Command_Structure" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
                  <xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
                  <xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
                </xs:sequence>
                <xs:attribute name="ID" type="xs:integer" use="required"/>
                <xs:attribute name="Name" type="xs:string" use="required"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Related_Protocols" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Related_Protocol" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Relationship_Type" maxOccurs="unbounded">
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Is an abstraction of"/>
                        <xs:enumeration value="Is a refinement of"/>
                        <xs:enumeration value="Is an alternative to"/>
                        <xs:enumeration value="Uses Protocol"/>
                        <xs:enumeration value="Is a service of"/>
                        <xs:enumeration value="Is a command of"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="Name"/>
                <xs:attribute name="RFC"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
    <xs:attribute name="Name" type="xs:string" use="required"/>
    <xs:attribute name="RFC" type="xs:string"/>
    <xs:attribute name="Encryption" type="xs:boolean"/>
    <xs:attribute name="Encryption_Type" type="xs:string"/>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header
Children capec:Protocol_Header
Source
<xs:element name="Protocol_Structure" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Protocol_Header" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required"/>
          <xs:attribute name="Name" type="xs:string"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_ID ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Name ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_RFC ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_Field_Name ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_Field_Description ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_Flag_Description ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_Flag_Value ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_Operation_Code ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Protocol_Structure_Protocol_Header_Protocol_Data
Children capec:Protocol_Data, capec:Protocol_Field_Description, capec:Protocol_Field_Name, capec:Protocol_Flag_Description, capec:Protocol_Flag_Value, capec:Protocol_Operation_Code, capec:Protocol_RFC
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Name xs:string optional
Source
<xs:element name="Protocol_Header" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
    <xs:attribute name="Name" type="xs:string"/>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_RFC
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_Field_Name
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_Field_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_Flag_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_Flag_Value
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_Operation_Code
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / capec:Protocol_Data
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Command_Structure
Children capec:Command_Structure
Source
<xs:element name="Command_Structures" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Command_Structure" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
            <xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
            <xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
          </xs:sequence>
          <xs:attribute name="ID" type="xs:integer" use="required"/>
          <xs:attribute name="Name" type="xs:string" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures / capec:Command_Structure
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Command_Structure_ID ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Command_Structure_Name ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Command_Structure_Command_Description ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Command_Structure_Command_Type ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Attack_Surface_DescriptionType_Target_Attack_Surface_DescriptionType_Target_Functional_Services_Target_Functional_Service_Protocol_Command_Structures_Command_Structure_Command_Group_Label
Children capec:Command_Description, capec:Command_Group_Label, capec:Command_Type
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Name xs:string required
Source
<xs:element name="Command_Structure" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
      <xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
      <xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required"/>
    <xs:attribute name="Name" type="xs:string" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures / capec:Command_Structure / capec:Command_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures / capec:Command_Structure / capec:Command_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures / capec:Command_Structure / capec:Command_Group_Label
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Related_Protocols
Namespace http://capec.mitre.org/capec-2
Diagram
Children capec:Related_Protocol
Source
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Related_Protocols / capec:Related_Protocol
Namespace http://capec.mitre.org/capec-2
Diagram
Children capec:Relationship_Type
Attributes
Source
Element capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Related_Protocols / capec:Related_Protocol / capec:Relationship_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Type restriction of xs:string
Facets
Source
Element capec:Target_Attack_SurfaceType / capec:Target_Attack_Surface_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Targeted_OSI_Layers ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Localities ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Types ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Functional_Services ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType
Type capec:Target_Attack_Surface_DescriptionType
Children capec:Target_Attack_Surface_Localities, capec:Target_Attack_Surface_Types, capec:Target_Functional_Services, capec:Targeted_OSI_Layers
Source
<xs:element name="Target_Attack_Surface_Description" type="capec:Target_Attack_Surface_DescriptionType"/>
Element capec:Attack_PatternType / capec:Attack_Prerequisites
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the conditions that must exist or the functionality and characteristics that the target software must have or behavior it must exhibit for an attack of this type to succeed.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Attack_Prerequisites_Attack_Prerequisite
Children capec:Attack_Prerequisite
Source
<xs:element name="Attack_Prerequisites" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the conditions that must exist or the functionality and characteristics that the target software must have or behavior it must exhibit for an attack of this type to succeed.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Prerequisite" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual attack prerequisite.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Attack_Prerequisites / capec:Attack_Prerequisite
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual attack prerequisite.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Attack_Prerequisite" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual attack prerequisite.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Typical_Severity
Namespace http://capec.mitre.org/capec-2
Annotations
On a rough scale (Very Low, Low, Medium, High, Very high), what is the typical severity of impact to the targeted software if this attack occurs? The severity of a specific attack instance can vary greatly depending on the specific context of the target software under attack. This field is intended to capture an overall typical average value for this type of attack with the understanding that it will not be completely accurate for all attacks.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Very High
enumeration High
enumeration Medium
enumeration Low
enumeration Very Low
Source
<xs:element name="Typical_Severity" minOccurs="0">
  <xs:annotation>
    <xs:documentation>On a rough scale (Very Low, Low, Medium, High, Very high), what is the typical severity of impact to the targeted software if this attack occurs? The severity of a specific attack instance can vary greatly depending on the specific context of the target software under attack. This field is intended to capture an overall typical average value for this type of attack with the understanding that it will not be completely accurate for all attacks.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Very High"/>
      <xs:enumeration value="High"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="Low"/>
      <xs:enumeration value="Very Low"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Typical_Likelihood_of_Exploit
Namespace http://capec.mitre.org/capec-2
Annotations
On a rough scale (Very Low, Low Medium,  High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions? The likelihood of exploit of a specific attack instance can vary greatly depending on the specific context of the target software under attack. This field is intended to capture an overall typical average value for this type of attack with the understanding that it will not be completely accurate for all attacks.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Typical_Likelihood_of_Exploit_Likelihood ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Typical_Likelihood_of_Exploit_Explanation
Children capec:Explanation, capec:Likelihood
Source
<xs:element name="Typical_Likelihood_of_Exploit" minOccurs="0">
  <xs:annotation>
    <xs:documentation>On a rough scale (Very Low, Low Medium, High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions? The likelihood of exploit of a specific attack instance can vary greatly depending on the specific context of the target software under attack. This field is intended to capture an overall typical average value for this type of attack with the understanding that it will not be completely accurate for all attacks.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Likelihood" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>On a rough scale (Very Low, Low Medium, High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions?</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Explanation" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field captures any useful explanation for the defined Likelihood.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Typical_Likelihood_of_Exploit / capec:Likelihood
Namespace http://capec.mitre.org/capec-2
Annotations
On a rough scale (Very Low, Low Medium,  High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions?
Diagram
Diagram
Type xs:string
Source
<xs:element name="Likelihood" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>On a rough scale (Very Low, Low Medium, High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions?</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Typical_Likelihood_of_Exploit / capec:Explanation
Namespace http://capec.mitre.org/capec-2
Annotations
This field captures any useful explanation for the defined Likelihood.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Explanation" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field captures any useful explanation for the defined Likelihood.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Methods_of_Attack
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the mechanism of attack used by this pattern. This field can help define the applicable attack surface required for this attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Methods_of_Attack_Method_of_Attack
Children capec:Method_of_Attack
Source
<xs:element name="Methods_of_Attack" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the mechanism of attack used by this pattern. This field can help define the applicable attack surface required for this attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Method_of_Attack" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Injection"/>
            <xs:enumeration value="Modification of Resources"/>
            <xs:enumeration value="Protocol Manipulation"/>
            <xs:enumeration value="Analysis"/>
            <xs:enumeration value="API Abuse"/>
            <xs:enumeration value="Brute Force"/>
            <xs:enumeration value="Flooding"/>
            <xs:enumeration value="Time and State"/>
            <xs:enumeration value="Spoofing"/>
            <xs:enumeration value="Social Engineering"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Methods_of_Attack / capec:Method_of_Attack
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Injection
enumeration Modification of Resources
enumeration Protocol Manipulation
enumeration Analysis
enumeration API Abuse
enumeration Brute Force
enumeration Flooding
enumeration Time and State
enumeration Spoofing
enumeration Social Engineering
Source
<xs:element name="Method_of_Attack" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Injection"/>
      <xs:enumeration value="Modification of Resources"/>
      <xs:enumeration value="Protocol Manipulation"/>
      <xs:enumeration value="Analysis"/>
      <xs:enumeration value="API Abuse"/>
      <xs:enumeration value="Brute Force"/>
      <xs:enumeration value="Flooding"/>
      <xs:enumeration value="Time and State"/>
      <xs:enumeration value="Spoofing"/>
      <xs:enumeration value="Social Engineering"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Examples-Instances
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains explanatory examples or demonstrative exploit instances of this attack, which are intended to help the reader understand the nature, context and variability of the attack in more practical and concrete terms.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Examples-Instances_Example-Instance
Children capec:Example-Instance
Source
<xs:element name="Examples-Instances" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field contains explanatory examples or demonstrative exploit instances of this attack, which are intended to help the reader understand the nature, context and variability of the attack in more practical and concrete terms.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Example-Instance" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual example or exploit instance.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Example-Instance_Description" type="capec:Structured_Text_Type">
              <xs:annotation>
                <xs:documentation>This field describes in detail a specific example or exploit instance of this attack. It should outline the context of the attack, the targeted software, the targeted weaknesses or vulnerabilities, the specific set of actions involved in the attack and the resulting impact of the attacks success or failure (in the case of counterexamples).</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="References" minOccurs="0">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded"/>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="Example-Instance_Related_Vulnerabilities" minOccurs="0">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Example-Instance_Related_Vulnerability" type="capec:Structured_Text_Type" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:documentation>This field lists the specific vulnerabilities targeted by this exploit instance of the attack. Specific vulnerabilities should reference industry-standard identifiers such as Common Vulnerabilities and Exposures (CVE) numbers and/or US-CERT numbers.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Examples-Instances / capec:Example-Instance
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual example or exploit instance.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Examples-Instances_Attack_PatternType_Attack_PatternType_Examples-Instances_Example-Instance_Example-Instance_Description ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Examples-Instances_Attack_PatternType_Attack_PatternType_Examples-Instances_Example-Instance_References ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Examples-Instances_Attack_PatternType_Attack_PatternType_Examples-Instances_Example-Instance_Example-Instance_Related_Vulnerabilities
Children capec:Example-Instance_Description, capec:Example-Instance_Related_Vulnerabilities, capec:References
Source
<xs:element name="Example-Instance" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual example or exploit instance.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Example-Instance_Description" type="capec:Structured_Text_Type">
        <xs:annotation>
          <xs:documentation>This field describes in detail a specific example or exploit instance of this attack. It should outline the context of the attack, the targeted software, the targeted weaknesses or vulnerabilities, the specific set of actions involved in the attack and the resulting impact of the attacks success or failure (in the case of counterexamples).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="References" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Example-Instance_Related_Vulnerabilities" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Example-Instance_Related_Vulnerability" type="capec:Structured_Text_Type" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field lists the specific vulnerabilities targeted by this exploit instance of the attack. Specific vulnerabilities should reference industry-standard identifiers such as Common Vulnerabilities and Exposures (CVE) numbers and/or US-CERT numbers.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Examples-Instances / capec:Example-Instance / capec:Example-Instance_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes in detail a specific example or exploit instance of this attack. It should outline the context of the attack, the targeted software, the targeted weaknesses or vulnerabilities, the specific set of actions involved in the attack and the resulting impact of the attacks success or failure (in the case of counterexamples).
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Example-Instance_Description" type="capec:Structured_Text_Type">
  <xs:annotation>
    <xs:documentation>This field describes in detail a specific example or exploit instance of this attack. It should outline the context of the attack, the targeted software, the targeted weaknesses or vulnerabilities, the specific set of actions involved in the attack and the resulting impact of the attacks success or failure (in the case of counterexamples).</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Examples-Instances / capec:Example-Instance / capec:References
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Examples-Instances_Attack_PatternType_Attack_PatternType_Examples-Instances_Example-Instance_Attack_PatternType_Attack_PatternType_Examples-Instances_Attack_PatternType_Attack_PatternType_Examples-Instances_Example-Instance_References_Reference
Children capec:Reference
Source
<xs:element name="References" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Examples-Instances / capec:Example-Instance / capec:References / capec:Reference
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_ID ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Description ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Author ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Title ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Section ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Edition ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publication ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publisher ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Date ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_PubDate ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Link ap_schema_v2_5_xsd.tmp#Reference_Type
Type capec:Reference_Type
Children capec:Reference_Author, capec:Reference_Date, capec:Reference_Description, capec:Reference_Edition, capec:Reference_Link, capec:Reference_PubDate, capec:Reference_Publication, capec:Reference_Publisher, capec:Reference_Section, capec:Reference_Title
Attributes
QName Type Fixed Default Use Annotation
Reference_ID optional
The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.
Source
<xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded"/>
Element capec:Reference_Type / capec:Reference_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Reference_Description" type="capec:Structured_Text_Type" minOccurs="0"/>
Element capec:Reference_Type / capec:Reference_Author
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies an individual author of the material being referenced. It is not required, but may be repeated sequentially in order to identify multiple authors for a single piece of material.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_Author" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element identifies an individual author of the material being referenced. It is not required, but may be repeated sequentially in order to identify multiple authors for a single piece of material.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Title
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies the title of the material beingreferenced. It is not required if the material does not have a title.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_Title" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element identifies the title of the material beingreferenced. It is not required if the material does not have a title.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Section
Namespace http://capec.mitre.org/capec-2
Annotations
This element is intended to provide a means of identifying the exact location of the material inside of the publication source, such as the relevant pages of a research paper, the appropriate chapters from a book, etc. This is useful for both book references and internet references.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_Section" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element is intended to provide a means of identifying the exact location of the material inside of the publication source, such as the relevant pages of a research paper, the appropriate chapters from a book, etc. This is useful for both book references and internet references.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Edition
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies the edition of the material being
referenced in the event that multiple editions of the material exist. This will usually only be useful for book references.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_Edition" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element identifies the edition of the material being referenced in the event that multiple editions of the material exist. This will usually only be useful for book references.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Publication
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies the publication source of the reference material, if one exists.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_Publication" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element identifies the publication source of the reference material, if one exists.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Publisher
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies the publisher of the reference material, if one exists.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_Publisher" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element identifies the publisher of the reference material, if one exists.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Date
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies the date when the reference was included in the entry. This provides the reader with a time line for when the material in the reference, usually the link, was valid. The date should be of the format YYYY-MM-DD.
Diagram
Diagram
Type xs:date
Source
<xs:element name="Reference_Date" type="xs:date" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element identifies the date when the reference was included in the entry. This provides the reader with a time line for when the material in the reference, usually the link, was valid. The date should be of the format YYYY-MM-DD.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_PubDate
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the date when the reference was published YYYY.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Reference_PubDate" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the date when the reference was published YYYY.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_Type / capec:Reference_Link
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type xs:string
Source
Element capec:Attack_PatternType / capec:Examples-Instances / capec:Example-Instance / capec:Example-Instance_Related_Vulnerabilities
Namespace http://capec.mitre.org/capec-2
Diagram
Children capec:Example-Instance_Related_Vulnerability
Source
Element capec:Attack_PatternType / capec:Examples-Instances / capec:Example-Instance / capec:Example-Instance_Related_Vulnerabilities / capec:Example-Instance_Related_Vulnerability
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
Element capec:Attack_PatternType / capec:Attacker_Skills_or_Knowledge_Required
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the level of skills or specific knowledge required by an attacker to execute this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Attacker_Skills_or_Knowledge_Required_Attacker_Skill_or_Knowledge_Required
Children capec:Attacker_Skill_or_Knowledge_Required
Source
<xs:element name="Attacker_Skills_or_Knowledge_Required" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the level of skills or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attacker_Skill_or_Knowledge_Required" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Low"/>
                  <xs:enumeration value="Medium"/>
                  <xs:enumeration value="High"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Attacker_Skills_or_Knowledge_Required / capec:Attacker_Skill_or_Knowledge_Required
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Attacker_Skills_or_Knowledge_Required_Attack_PatternType_Attack_PatternType_Attacker_Skills_or_Knowledge_Required_Attacker_Skill_or_Knowledge_Required_Skill_or_Knowledge_Level ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Attacker_Skills_or_Knowledge_Required_Attack_PatternType_Attack_PatternType_Attacker_Skills_or_Knowledge_Required_Attacker_Skill_or_Knowledge_Required_Skill_or_Knowledge_Type
Children capec:Skill_or_Knowledge_Level, capec:Skill_or_Knowledge_Type
Source
<xs:element name="Attacker_Skill_or_Knowledge_Required" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Low"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="High"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Attacker_Skills_or_Knowledge_Required / capec:Attacker_Skill_or_Knowledge_Required / capec:Skill_or_Knowledge_Level
Namespace http://capec.mitre.org/capec-2
Annotations
This should be communicated on a rough scale (Low, Medium, High).
For example:
• Low - Basic computer familiarity
• Low - Basic SQL knowledge
• Medium - Moderate scripting and shell experience and ability to disassemble and decompile
• High - Expert knowledge of LINUX kernel
• High - Detailed knowledge of target software development practices and business context (former employee)
• Etc.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Low
enumeration Medium
enumeration High
Source
<xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Low"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="High"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Attacker_Skills_or_Knowledge_Required / capec:Attacker_Skill_or_Knowledge_Required / capec:Skill_or_Knowledge_Type
Namespace http://capec.mitre.org/capec-2
Annotations
This field provides contextual detail for the skill or knowledge level.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Resources_Required
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the resources (CPU cycles, IP addresses, tools, etc.) required by an attacker to effectively execute this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Resources_Required" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the resources (CPU cycles, IP addresses, tools, etc.) required by an attacker to effectively execute this type of attack.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Probing_Techniques
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes techniques typically used to probe and reconnoiter a potential target to determine vulnerability and/or to prepare for this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Probing_Techniques_Probing_Technique
Children capec:Probing_Technique
Source
<xs:element name="Probing_Techniques" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes techniques typically used to probe and reconnoiter a potential target to determine vulnerability and/or to prepare for this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Probing_Technique" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual probing technique.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
            <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Probing_Techniques / capec:Probing_Technique
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual probing technique.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Probing_Techniques_Attack_PatternType_Attack_PatternType_Probing_Techniques_Probing_Technique_Description ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Probing_Techniques_Attack_PatternType_Attack_PatternType_Probing_Techniques_Probing_Technique_Observables
Children capec:Description, capec:Observables
Source
<xs:element name="Probing_Technique" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual probing technique.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Probing_Techniques / capec:Probing_Technique / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Probing_Techniques / capec:Probing_Technique / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Indicators-Warnings_of_Attack
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes activities, events, conditions or behaviors that could serve as indicators that an attack of this type is imminent, in progress or has occurred.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Indicators-Warnings_of_Attack_Indicator-Warning_of_Attack
Children capec:Indicator-Warning_of_Attack
Source
<xs:element name="Indicators-Warnings_of_Attack" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes activities, events, conditions or behaviors that could serve as indicators that an attack of this type is imminent, in progress or has occurred.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Indicator-Warning_of_Attack" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual indicator/warning.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
            <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Indicators-Warnings_of_Attack / capec:Indicator-Warning_of_Attack
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual indicator/warning.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Indicators-Warnings_of_Attack_Attack_PatternType_Attack_PatternType_Indicators-Warnings_of_Attack_Indicator-Warning_of_Attack_Description ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Indicators-Warnings_of_Attack_Attack_PatternType_Attack_PatternType_Indicators-Warnings_of_Attack_Indicator-Warning_of_Attack_Observables
Children capec:Description, capec:Observables
Source
<xs:element name="Indicator-Warning_of_Attack" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual indicator/warning.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Indicators-Warnings_of_Attack / capec:Indicator-Warning_of_Attack / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Indicators-Warnings_of_Attack / capec:Indicator-Warning_of_Attack / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Obfuscation_Techniques
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes techniques typically used to disguise the fact that an attack of this type is imminent, in progress or has occurred.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Obfuscation_Techniques_Obfuscation_Technique
Children capec:Obfuscation_Technique
Source
<xs:element name="Obfuscation_Techniques" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes techniques typically used to disguise the fact that an attack of this type is imminent, in progress or has occurred.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual obfuscation technique.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
            <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Obfuscation_Techniques / capec:Obfuscation_Technique
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual obfuscation technique.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Obfuscation_Techniques_Attack_PatternType_Attack_PatternType_Obfuscation_Techniques_Obfuscation_Technique_Description ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Obfuscation_Techniques_Attack_PatternType_Attack_PatternType_Obfuscation_Techniques_Obfuscation_Technique_Observables
Children capec:Description, capec:Observables
Source
<xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual obfuscation technique.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Obfuscation_Techniques / capec:Obfuscation_Technique / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Obfuscation_Techniques / capec:Obfuscation_Technique / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Solutions_and_Mitigations
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes actions or approaches that can potentially prevent or mitigate the risk of this attack. These solutions and mitigations are targeted to improve the resistance of the target software and thereby reduce the likelihood of the attack's success or to improve the resilience of the target software and thereby reduce the impact of the attack if it is successful.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Solutions_and_Mitigations_Solution_or_Mitigation
Children capec:Solution_or_Mitigation
Source
<xs:element name="Solutions_and_Mitigations" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes actions or approaches that can potentially prevent or mitigate the risk of this attack. These solutions and mitigations are targeted to improve the resistance of the target software and thereby reduce the likelihood of the attack's success or to improve the resilience of the target software and thereby reduce the impact of the attack if it is successful.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Solution_or_Mitigation" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual blocking solution or mitigation.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Solutions_and_Mitigations / capec:Solution_or_Mitigation
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual blocking solution or mitigation.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Solution_or_Mitigation" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual blocking solution or mitigation.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Attack_Motivation-Consequences
Namespace http://capec.mitre.org/capec-2
Annotations
What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Attack_Motivation-Consequences_Attack_Motivation-Consequence
Children capec:Attack_Motivation-Consequence
Source
<xs:element name="Attack_Motivation-Consequences" minOccurs="0">
  <xs:annotation>
    <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Motivation-Consequence" type="capec:Common_ConsequenceType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Attack_Motivation-Consequences / capec:Attack_Motivation-Consequence
Namespace http://capec.mitre.org/capec-2
Annotations
What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Common_Consequence_ID ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Scope ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Technical_Impact ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Note ap_schema_v2_5_xsd.tmp#Common_ConsequenceType
Type capec:Common_ConsequenceType
Children capec:Consequence_Note, capec:Consequence_Scope, capec:Consequence_Technical_Impact
Attributes
QName Type Fixed Default Use Annotation
Common_Consequence_ID xs:string optional
The Common_Consequence_ID stores the value for the related
Common_Consequence entry identifier as a string. Only one
Common_Consequence_ID element can exist for each Common_Consequence element
(ex: CC-1). However, Common_Consequences across CAPEC with the same ID should
only vary in small details.
Source
<xs:element name="Attack_Motivation-Consequence" type="capec:Common_ConsequenceType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Common_ConsequenceType / capec:Consequence_Scope
Namespace http://capec.mitre.org/capec-2
Annotations
This subelement identifies an individual consequence that
may result from this attack pattern.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Confidentiality
enumeration Integrity
enumeration Availability
enumeration Access_Control
enumeration Non-Repudiation
enumeration Accountability
enumeration Authentication
enumeration Authorization
enumeration Other
Source
<xs:element name="Consequence_Scope" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This subelement identifies an individual consequence that may result from this attack pattern.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Confidentiality"/>
      <xs:enumeration value="Integrity"/>
      <xs:enumeration value="Availability"/>
      <xs:enumeration value="Access_Control"/>
      <xs:enumeration value="Non-Repudiation"/>
      <xs:enumeration value="Accountability"/>
      <xs:enumeration value="Authentication"/>
      <xs:enumeration value="Authorization"/>
      <xs:enumeration value="Other"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Common_ConsequenceType / capec:Consequence_Technical_Impact
Namespace http://capec.mitre.org/capec-2
Annotations
This subelement describes the technical impacts that can result from successful execution of this attack pattern.
Diagram
Diagram
Type restriction of xs:string
Facets
whiteSpace collapse
enumeration Modify memory
enumeration Read memory
enumeration Modify files or directories
enumeration Read files or directories
enumeration Modify application data
enumeration Read application data
enumeration DoS: crash / exit / restart
enumeration DoS: amplification
enumeration DoS: instability
enumeration DoS: resource consumption (CPU)
enumeration DoS: resource consumption (memory)
enumeration DoS: resource consumption (other)
enumeration Execute unauthorized code or commands
enumeration Gain privileges / assume identity
enumeration Bypass protection mechanism
enumeration Hide activities
enumeration Alter execution logic
enumeration Other
enumeration "Varies by context"
enumeration Quality degradation
enumeration Unexpected State
Source
<xs:element name="Consequence_Technical_Impact" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This subelement describes the technical impacts that can result from successful execution of this attack pattern.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:whiteSpace value="collapse"/>
      <xs:enumeration value="Modify memory"/>
      <xs:enumeration value="Read memory"/>
      <xs:enumeration value="Modify files or directories"/>
      <xs:enumeration value="Read files or directories"/>
      <xs:enumeration value="Modify application data"/>
      <xs:enumeration value="Read application data"/>
      <xs:enumeration value="DoS: crash / exit / restart"/>
      <xs:enumeration value="DoS: amplification"/>
      <xs:enumeration value="DoS: instability"/>
      <xs:enumeration value="DoS: resource consumption (CPU)"/>
      <xs:enumeration value="DoS: resource consumption (memory)"/>
      <xs:enumeration value="DoS: resource consumption (other)"/>
      <xs:enumeration value="Execute unauthorized code or commands"/>
      <xs:enumeration value="Gain privileges / assume identity"/>
      <xs:enumeration value="Bypass protection mechanism"/>
      <xs:enumeration value="Hide activities"/>
      <xs:enumeration value="Alter execution logic"/>
      <xs:enumeration value="Other"/>
      <xs:enumeration value=""Varies by context""/>
      <xs:enumeration value="Quality degradation"/>
      <xs:enumeration value="Unexpected State"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Common_ConsequenceType / capec:Consequence_Note
Namespace http://capec.mitre.org/capec-2
Annotations
This subelement provides additional commentary about this consequence.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Consequence_Note" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This subelement provides additional commentary about this consequence.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Injection_Vector
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes, as precisely as possible, the mechanism and format of an input-driven attack of this type. Injection vectors must take into account the grammar of an attack, the syntax accepted by the system, the position of various fields, and the ranges of data that are acceptable.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Injection_Vector" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes, as precisely as possible, the mechanism and format of an input-driven attack of this type. Injection vectors must take into account the grammar of an attack, the syntax accepted by the system, the position of various fields, and the ranges of data that are acceptable.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Payload
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the code, configuration or other data to be executed or otherwise activated as part of an injection-based attack of this type.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Payload" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the code, configuration or other data to be executed or otherwise activated as part of an injection-based attack of this type.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Activation_Zone
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the area within the target software that is capable of executing or otherwise activating the payload of an injection-based attack of this type. The activation zone is where the intent of the attacker is put into action. The activation zone may be a command interpreter, some active machine code in a buffer, a client browser, a system API call, etc.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Activation_Zone" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the area within the target software that is capable of executing or otherwise activating the payload of an injection-based attack of this type. The activation zone is where the intent of the attacker is put into action. The activation zone may be a command interpreter, some active machine code in a buffer, a client browser, a system API call, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Payload_Activation_Impact
Namespace http://capec.mitre.org/capec-2
Annotations
This field is a description of the impact that the activation of the attack payload for an injection-based attack of this type would typically have on the confidentiality, integrity or availability of the target software.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Payload_Activation_Impact_Description ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Payload_Activation_Impact_Observables
Children capec:Description, capec:Observables
Source
<xs:element name="Payload_Activation_Impact" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field is a description of the impact that the activation of the attack payload for an injection-based attack of this type would typically have on the confidentiality, integrity or availability of the target software.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
      <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Payload_Activation_Impact / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Payload_Activation_Impact / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram cybox_core_xsd.tmp#ObservablesType_cybox_major_version cybox_core_xsd.tmp#ObservablesType_cybox_minor_version cybox_core_xsd.tmp#ObservablesType_Observable_Package_Source cybox_core_xsd.tmp#Observable cybox_core_xsd.tmp#ObservablesType_Pools cybox_core_xsd.tmp#ObservablesType
Type cybox:ObservablesType
Children cybox:Observable, cybox:Observable_Package_Source, cybox:Pools
Attributes
QName Type Fixed Default Use Annotation
cybox_major_version xs:string required
The major_version field specifies the major version of the CybOX language utlized for this set of Observables.
cybox_minor_version xs:string required
The minor_version field specifies the minor version of the CybOX language utlized for this set of Observables.
Source
<xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Related_Weaknesses
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Related_Weakness
Source
Element capec:Attack_PatternType / capec:Related_Weaknesses / capec:Related_Weakness
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:CWE_ID, capec:Weakness_Relationship_Type
Source
Element capec:Attack_PatternType / capec:Related_Weaknesses / capec:Related_Weakness / capec:CWE_ID
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type xs:integer
Source
Element capec:Attack_PatternType / capec:Related_Weaknesses / capec:Related_Weakness / capec:Weakness_Relationship_Type
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type restriction of xs:string
Facets
Source
Element capec:Attack_PatternType / capec:Related_Vulnerabilities
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Related_Vulnerability
Source
Element capec:Attack_PatternType / capec:Related_Vulnerabilities / capec:Related_Vulnerability
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Vulnerability_Description, capec:Vulnerability_ID
Source
Element capec:Attack_PatternType / capec:Related_Vulnerabilities / capec:Related_Vulnerability / capec:Vulnerability_ID
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type xs:string
Source
Element capec:Attack_PatternType / capec:Related_Vulnerabilities / capec:Related_Vulnerability / capec:Vulnerability_Description
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
Element capec:Attack_PatternType / capec:Related_Attack_Patterns
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Related_Attack_Pattern
Source
Element capec:Attack_PatternType / capec:Related_Attack_Patterns / capec:Related_Attack_Pattern
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:RelationshipType
Children capec:Relationship_Chains, capec:Relationship_Description, capec:Relationship_Nature, capec:Relationship_Target_Form, capec:Relationship_Target_ID, capec:Relationship_Views
Source
Element capec:RelationshipType / capec:Relationship_Views
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains a list of the individual Views to which this relationship pertains.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#RelationshipType_RelationshipType_Relationship_Views_Relationship_View_ID
Children capec:Relationship_View_ID
Source
<xs:element name="Relationship_Views">
  <xs:annotation>
    <xs:documentation>This element contains a list of the individual Views to which this relationship pertains.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relationship_View_ID" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Specifies the unique ID of the individual view element to which this relationship pertains. This ID must correspond to a View.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:integer">
              <xs:attribute name="Ordinal">
                <xs:annotation>
                  <xs:documentation>The ordinal attribute is used to determine if this relationship is the primary ChildOf relationship for this entry for a given Relationship_View_ID element.. This attribute can only have the value "Primary" and should only be included for the primary parent/child relationship.</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:string">
                    <xs:enumeration value="Primary"/>
                  </xs:restriction>
                </xs:simpleType>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Views / capec:Relationship_View_ID
Namespace http://capec.mitre.org/capec-2
Annotations
Specifies the unique ID of the individual view element to which this relationship pertains. This ID must correspond to a View.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#RelationshipType_RelationshipType_Relationship_Views_RelationshipType_RelationshipType_Relationship_Views_Relationship_View_ID_Ordinal
Type extension of xs:integer
Attributes
QName Type Fixed Default Use Annotation
Ordinal restriction of xs:string optional
The ordinal attribute is used
to determine if this relationship is the primary ChildOf relationship for this
 entry for a given		Relationship_View_ID element.. This attribute can only have the value "Primary" and should only be included for the primary	parent/child relationship.
Source
<xs:element name="Relationship_View_ID" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Specifies the unique ID of the individual view element to which this relationship pertains. This ID must correspond to a View.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:integer">
        <xs:attribute name="Ordinal">
          <xs:annotation>
            <xs:documentation>The ordinal attribute is used to determine if this relationship is the primary ChildOf relationship for this entry for a given Relationship_View_ID element.. This attribute can only have the value "Primary" and should only be included for the primary parent/child relationship.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="Primary"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Chains
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains a list of the individual Chains this relationship pertains to.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#RelationshipType_RelationshipType_Relationship_Chains_Relationship_Chain_ID
Children capec:Relationship_Chain_ID
Source
<xs:element name="Relationship_Chains" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element contains a list of the individual Chains this relationship pertains to.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relationship_Chain_ID" type="xs:integer" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element specifies the unique ID of an individual chain element this relationship pertains to.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Chains / capec:Relationship_Chain_ID
Namespace http://capec.mitre.org/capec-2
Annotations
This element specifies the unique ID of an individual chain element this relationship pertains to.
Diagram
Diagram
Type xs:integer
Source
<xs:element name="Relationship_Chain_ID" type="xs:integer" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element specifies the unique ID of an individual chain element this relationship pertains to.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Target_Form
Namespace http://capec.mitre.org/capec-2
Annotations
The Relationship_Target_Form element defines the form of the target of this relationship, such as Category, Attack Pattern, View or	Compound_Element.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Category
enumeration Attack Pattern
enumeration View
enumeration Compound_Element
Source
<xs:element name="Relationship_Target_Form">
  <xs:annotation>
    <xs:documentation>The Relationship_Target_Form element defines the form of the target of this relationship, such as Category, Attack Pattern, View or Compound_Element.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Category"/>
      <xs:enumeration value="Attack Pattern"/>
      <xs:enumeration value="View"/>
      <xs:enumeration value="Compound_Element"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Nature
Namespace http://capec.mitre.org/capec-2
Annotations
The Relationship_Nature element defines the nature of the relationship between this element and the target element, such as ChildOf, HasMember or Requires to name a few.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration HasMember
This Relationship_Nature denotes the
specified entry as a top level member of this View. This
value for Relationship_Nature can only be used in Views. The
complementary relationship is MemberOf.
enumeration MemberOf
This Relationship_Nature denotes membership of
this entry in the top level of the View specified in
Relationship_Target_ID. The complementary relationship is
HasMember.
enumeration ChildOf
This Relationship_Nature denotes a specified
entry as a parent of this entry. In general, this means
that the parent will be a higher level representation of
this entry from the perspective of the View provided in
Relationship_View_ID. The complementary relationship is
ParentOf.
enumeration ParentOf
This Relationship_Nature denotes a specified
entry as a child of this entry. In general, this means
that the child will be a lower level representation of this
entry from the perspective of the View provided in
Relationship_View_ID. The complementary relationship is
ChildOf.
enumeration PeerOf
This Relationship_Nature denotes a specified
entry as having some similarity with this entry which does
not fit any of the other Relationship_Nature values. In this
case, a Relationship_Note should also be provided explaining
the connection. The complementary relationship is itself
(PeerOf).
enumeration Requires
This Relationship_Nature denotes a
Compound_Element of Compound_Element_Structure="Composite".
All entries that a Composite Requires must exist
simultaneously in order for the Compound_Element to exist.
The complementary relationship is
RequiredBy.
enumeration RequiredBy
This Relationship_Nature denotes an entry
that is required in order for the Compound_Element specified
in Relationship_Target_ID to exist. The complementary
relationship is Requires.
enumeration StartsWith
This Relationship_Nature denotes the starting
point in this chain as the entry specified by
Relationship_Target_ID. This Relationship_Nature can only be
used for Compound_Elements with
Compound_Element_Structure="Chain". For named chains, the
complementary relationship is
StartsChain.
enumeration StartsChain
This Relationship_Nature denotes this entry
as the starting point in the chain specified in
Relationship_Target_ID. For named chains, the complementary
relationship is StartsWith.
enumeration CanPrecede
This Relationship_Nature denotes a chain where
this entry can precede the entry specified by
Relationship_Target_ID in a sequential fashion. It is
important to note that not all CanPrecede relationships are
captured in a Compound_Element chain, only the most common
for now. The complementary relationship is
CanFollow.
enumeration CanFollow
This Relationship_Nature denotes a chain where
this entry can follow the entry specified by
Relationship_Target_ID in a sequential fashion. It is
important to note that not all CanFollow relationships are
captured in a Compound_Element chain, only the most common
for now. The complementary relationship is
CanPrecede.
enumeration CanAlsoBe
This Relationship_Nature denotes an entry
that, in the proper environment and context, can also be
perceived as the entry specified by Relationship_Target_ID.
This relationship is not necessarily reciprocal.
Source
<xs:element name="Relationship_Nature" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The Relationship_Nature element defines the nature of the relationship between this element and the target element, such as ChildOf, HasMember or Requires to name a few.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="HasMember">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes the specified entry as a top level member of this View. This value for Relationship_Nature can only be used in Views. The complementary relationship is MemberOf.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="MemberOf">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes membership of this entry in the top level of the View specified in Relationship_Target_ID. The complementary relationship is HasMember.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="ChildOf">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes a specified entry as a parent of this entry. In general, this means that the parent will be a higher level representation of this entry from the perspective of the View provided in Relationship_View_ID. The complementary relationship is ParentOf.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="ParentOf">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes a specified entry as a child of this entry. In general, this means that the child will be a lower level representation of this entry from the perspective of the View provided in Relationship_View_ID. The complementary relationship is ChildOf.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="PeerOf">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes a specified entry as having some similarity with this entry which does not fit any of the other Relationship_Nature values. In this case, a Relationship_Note should also be provided explaining the connection. The complementary relationship is itself (PeerOf).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="Requires">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes a Compound_Element of Compound_Element_Structure="Composite". All entries that a Composite Requires must exist simultaneously in order for the Compound_Element to exist. The complementary relationship is RequiredBy.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="RequiredBy">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes an entry that is required in order for the Compound_Element specified in Relationship_Target_ID to exist. The complementary relationship is Requires.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="StartsWith">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes the starting point in this chain as the entry specified by Relationship_Target_ID. This Relationship_Nature can only be used for Compound_Elements with Compound_Element_Structure="Chain". For named chains, the complementary relationship is StartsChain.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="StartsChain">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes this entry as the starting point in the chain specified in Relationship_Target_ID. For named chains, the complementary relationship is StartsWith.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="CanPrecede">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes a chain where this entry can precede the entry specified by Relationship_Target_ID in a sequential fashion. It is important to note that not all CanPrecede relationships are captured in a Compound_Element chain, only the most common for now. The complementary relationship is CanFollow.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="CanFollow">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes a chain where this entry can follow the entry specified by Relationship_Target_ID in a sequential fashion. It is important to note that not all CanFollow relationships are captured in a Compound_Element chain, only the most common for now. The complementary relationship is CanPrecede.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="CanAlsoBe">
        <xs:annotation>
          <xs:documentation>This Relationship_Nature denotes an entry that, in the proper environment and context, can also be perceived as the entry specified by Relationship_Target_ID. This relationship is not necessarily reciprocal.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Target_ID
Namespace http://capec.mitre.org/capec-2
Annotations
The Relationship_Target_ID specifies the unique ID of the
target element of the relationship.
Diagram
Diagram
Type xs:integer
Source
<xs:element name="Relationship_Target_ID" type="xs:integer">
  <xs:annotation>
    <xs:documentation>The Relationship_Target_ID specifies the unique ID of the target element of the relationship.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:RelationshipType / capec:Relationship_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Relationship_Description" type="capec:Structured_Text_Type" minOccurs="0"/>
Element capec:Attack_PatternType / capec:Relevant_Security_Requirements
Namespace http://capec.mitre.org/capec-2
Annotations
This field identifies specific security requirements that are relevant to this type of attack and are general enough to offer opportunities for reuse.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Relevant_Security_Requirements_Relevant_Security_Requirement
Children capec:Relevant_Security_Requirement
Source
<xs:element name="Relevant_Security_Requirements" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field identifies specific security requirements that are relevant to this type of attack and are general enough to offer opportunities for reuse.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Security_Requirement" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual relevant security requirement.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Relevant_Security_Requirements / capec:Relevant_Security_Requirement
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual relevant security requirement.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Relevant_Security_Requirement" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual relevant security requirement.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Relevant_Design_Patterns
Namespace http://capec.mitre.org/capec-2
Annotations
This field identifies specific relevant design patterns that are recommended as providing resistance or resilience to this attack, or which are not recommended as they are particularly susceptible to this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Relevant_Design_Patterns_Recommended_Design_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Relevant_Design_Patterns_Non-Recommended_Design_Patterns
Children capec:Non-Recommended_Design_Patterns, capec:Recommended_Design_Patterns
Source
<xs:element name="Relevant_Design_Patterns" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field identifies specific relevant design patterns that are recommended as providing resistance or resilience to this attack, or which are not recommended as they are particularly susceptible to this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Recommended_Design_Patterns">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Recommended_Design_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field describes an individual design pattern that is recommended due to its likelihood of increasing the software's resistance or resiliency to this type of attack.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Non-Recommended_Design_Patterns">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Non-Recommended_Design_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field describes an individual design pattern that is not recommended due to its likelihood of decreasing the software's resistance or resiliency to this type of attack.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Relevant_Design_Patterns / capec:Recommended_Design_Patterns
Namespace http://capec.mitre.org/capec-2
Diagram
Children capec:Recommended_Design_Pattern
Source
Element capec:Attack_PatternType / capec:Relevant_Design_Patterns / capec:Recommended_Design_Patterns / capec:Recommended_Design_Pattern
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
Element capec:Attack_PatternType / capec:Relevant_Design_Patterns / capec:Non-Recommended_Design_Patterns
Namespace http://capec.mitre.org/capec-2
Diagram
Children capec:Non-Recommended_Design_Pattern
Source
Element capec:Attack_PatternType / capec:Relevant_Design_Patterns / capec:Non-Recommended_Design_Patterns / capec:Non-Recommended_Design_Pattern
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
Element capec:Attack_PatternType / capec:Relevant_Security_Patterns
Namespace http://capec.mitre.org/capec-2
Annotations
This field identifies specific security patterns that are recommended as providing resistance or resilience to this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Relevant_Security_Patterns_Relevant_Security_Pattern
Children capec:Relevant_Security_Pattern
Source
<xs:element name="Relevant_Security_Patterns" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field identifies specific security patterns that are recommended as providing resistance or resilience to this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relevant_Security_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual relevant security pattern.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Relevant_Security_Patterns / capec:Relevant_Security_Pattern
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual relevant security pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Relevant_Security_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual relevant security pattern.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:Related_Security_Principles
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Related_Security_Principle
Source
Element capec:Attack_PatternType / capec:Related_Security_Principles / capec:Related_Security_Principle
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
Element capec:Attack_PatternType / capec:Related_Guidelines
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Related_Guideline
Source
Element capec:Attack_PatternType / capec:Related_Guidelines / capec:Related_Guideline
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
Element capec:Attack_PatternType / capec:Purposes
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the generalized purposes of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Purposes_Purpose
Children capec:Purpose
Source
<xs:element name="Purposes" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the generalized purposes of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Purpose" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes the generalized purpose of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Reconnaissance"/>
            <xs:enumeration value="Penetration"/>
            <xs:enumeration value="Exploitation"/>
            <xs:enumeration value="Obfuscation"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Purposes / capec:Purpose
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the generalized purpose of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Reconnaissance
enumeration Penetration
enumeration Exploitation
enumeration Obfuscation
Source
<xs:element name="Purpose" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes the generalized purpose of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Reconnaissance"/>
      <xs:enumeration value="Penetration"/>
      <xs:enumeration value="Exploitation"/>
      <xs:enumeration value="Obfuscation"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:CIA_Impact
Namespace http://capec.mitre.org/capec-2
Annotations
This field characterizes the typical relative impact of this pattern on the confidentiality, integrity and availability of the targeted software.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_CIA_Impact_Confidentiality_Impact ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_CIA_Impact_Integrity_Impact ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_CIA_Impact_Availability_Impact
Children capec:Availability_Impact, capec:Confidentiality_Impact, capec:Integrity_Impact
Source
<xs:element name="CIA_Impact" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field characterizes the typical relative impact of this pattern on the confidentiality, integrity and availability of the targeted software.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Confidentiality_Impact" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the typical impact of this pattern on the confidentiality characteristics of the targeted software and related data.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Low"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="High"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Integrity_Impact" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the typical impact of this pattern on the integrity characteristics of the targeted software and related data.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Low"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="High"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Availability_Impact" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the typical impact of this pattern on the availability characteristics of the targeted software and related data.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Low"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="High"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:CIA_Impact / capec:Confidentiality_Impact
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the typical impact of this pattern on the confidentiality characteristics of the targeted software and related data.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Low
enumeration Medium
enumeration High
Source
<xs:element name="Confidentiality_Impact" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the typical impact of this pattern on the confidentiality characteristics of the targeted software and related data.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Low"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="High"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:CIA_Impact / capec:Integrity_Impact
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the typical impact of this pattern on the integrity characteristics of the targeted software and related data.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Low
enumeration Medium
enumeration High
Source
<xs:element name="Integrity_Impact" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the typical impact of this pattern on the integrity characteristics of the targeted software and related data.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Low"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="High"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:CIA_Impact / capec:Availability_Impact
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the typical impact of this pattern on the availability characteristics of the targeted software and related data.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Low
enumeration Medium
enumeration High
Source
<xs:element name="Availability_Impact" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the typical impact of this pattern on the availability characteristics of the targeted software and related data.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Low"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="High"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context
Namespace http://capec.mitre.org/capec-2
Annotations
This field characterizes the technical context where this pattern is applicable.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Architectural_Paradigms ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Frameworks ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Platforms ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Languages
Children capec:Architectural_Paradigms, capec:Frameworks, capec:Languages, capec:Platforms
Source
<xs:element name="Technical_Context" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field characterizes the technical context where this pattern is applicable.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Architectural_Paradigms" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Architectural_Paradigm" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Mainframe"/>
                  <xs:enumeration value="Client-Server"/>
                  <xs:enumeration value="n-Tier"/>
                  <xs:enumeration value="Web"/>
                  <xs:enumeration value="SOA"/>
                  <xs:enumeration value="Other"/>
                  <xs:enumeration value="All"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Frameworks" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Framework" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="J2EE"/>
                  <xs:enumeration value=".NET"/>
                  <xs:enumeration value="Struts"/>
                  <xs:enumeration value="Spring"/>
                  <xs:enumeration value="Hibernate"/>
                  <xs:enumeration value="Other"/>
                  <xs:enumeration value="All"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Platforms" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Platform" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Windows"/>
                  <xs:enumeration value="UNIX-LINUX"/>
                  <xs:enumeration value="Solaris"/>
                  <xs:enumeration value="Other"/>
                  <xs:enumeration value="All"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Languages" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Language" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="AJAX"/>
                  <xs:enumeration value="ASP"/>
                  <xs:enumeration value="ASP.NET"/>
                  <xs:enumeration value="C"/>
                  <xs:enumeration value="C++"/>
                  <xs:enumeration value="C#"/>
                  <xs:enumeration value="Java"/>
                  <xs:enumeration value="JSP"/>
                  <xs:enumeration value="PHP"/>
                  <xs:enumeration value="PERL"/>
                  <xs:enumeration value="Ruby"/>
                  <xs:enumeration value="Visual Basic"/>
                  <xs:enumeration value="Other"/>
                  <xs:enumeration value="All"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Architectural_Paradigms
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Attack_PatternType_Attack_PatternType_Technical_Context_Architectural_Paradigms_Architectural_Paradigm
Children capec:Architectural_Paradigm
Source
<xs:element name="Architectural_Paradigms" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Architectural_Paradigm" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Mainframe"/>
            <xs:enumeration value="Client-Server"/>
            <xs:enumeration value="n-Tier"/>
            <xs:enumeration value="Web"/>
            <xs:enumeration value="SOA"/>
            <xs:enumeration value="Other"/>
            <xs:enumeration value="All"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Architectural_Paradigms / capec:Architectural_Paradigm
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Mainframe
enumeration Client-Server
enumeration n-Tier
enumeration Web
enumeration SOA
enumeration Other
enumeration All
Source
<xs:element name="Architectural_Paradigm" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Mainframe"/>
      <xs:enumeration value="Client-Server"/>
      <xs:enumeration value="n-Tier"/>
      <xs:enumeration value="Web"/>
      <xs:enumeration value="SOA"/>
      <xs:enumeration value="Other"/>
      <xs:enumeration value="All"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Frameworks
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Attack_PatternType_Attack_PatternType_Technical_Context_Frameworks_Framework
Children capec:Framework
Source
<xs:element name="Frameworks" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Framework" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="J2EE"/>
            <xs:enumeration value=".NET"/>
            <xs:enumeration value="Struts"/>
            <xs:enumeration value="Spring"/>
            <xs:enumeration value="Hibernate"/>
            <xs:enumeration value="Other"/>
            <xs:enumeration value="All"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Frameworks / capec:Framework
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration J2EE
enumeration .NET
enumeration Struts
enumeration Spring
enumeration Hibernate
enumeration Other
enumeration All
Source
<xs:element name="Framework" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="J2EE"/>
      <xs:enumeration value=".NET"/>
      <xs:enumeration value="Struts"/>
      <xs:enumeration value="Spring"/>
      <xs:enumeration value="Hibernate"/>
      <xs:enumeration value="Other"/>
      <xs:enumeration value="All"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Platforms
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Attack_PatternType_Attack_PatternType_Technical_Context_Platforms_Platform
Children capec:Platform
Source
<xs:element name="Platforms" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Platform" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Windows"/>
            <xs:enumeration value="UNIX-LINUX"/>
            <xs:enumeration value="Solaris"/>
            <xs:enumeration value="Other"/>
            <xs:enumeration value="All"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Platforms / capec:Platform
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Windows
enumeration UNIX-LINUX
enumeration Solaris
enumeration Other
enumeration All
Source
<xs:element name="Platform" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Windows"/>
      <xs:enumeration value="UNIX-LINUX"/>
      <xs:enumeration value="Solaris"/>
      <xs:enumeration value="Other"/>
      <xs:enumeration value="All"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Languages
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Technical_Context_Attack_PatternType_Attack_PatternType_Technical_Context_Languages_Language
Children capec:Language
Source
<xs:element name="Languages" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Language" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="AJAX"/>
            <xs:enumeration value="ASP"/>
            <xs:enumeration value="ASP.NET"/>
            <xs:enumeration value="C"/>
            <xs:enumeration value="C++"/>
            <xs:enumeration value="C#"/>
            <xs:enumeration value="Java"/>
            <xs:enumeration value="JSP"/>
            <xs:enumeration value="PHP"/>
            <xs:enumeration value="PERL"/>
            <xs:enumeration value="Ruby"/>
            <xs:enumeration value="Visual Basic"/>
            <xs:enumeration value="Other"/>
            <xs:enumeration value="All"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Technical_Context / capec:Languages / capec:Language
Namespace http://capec.mitre.org/capec-2
Annotations
This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration AJAX
enumeration ASP
enumeration ASP.NET
enumeration C
enumeration C++
enumeration C#
enumeration Java
enumeration JSP
enumeration PHP
enumeration PERL
enumeration Ruby
enumeration Visual Basic
enumeration Other
enumeration All
Source
<xs:element name="Language" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="AJAX"/>
      <xs:enumeration value="ASP"/>
      <xs:enumeration value="ASP.NET"/>
      <xs:enumeration value="C"/>
      <xs:enumeration value="C++"/>
      <xs:enumeration value="C#"/>
      <xs:enumeration value="Java"/>
      <xs:enumeration value="JSP"/>
      <xs:enumeration value="PHP"/>
      <xs:enumeration value="PERL"/>
      <xs:enumeration value="Ruby"/>
      <xs:enumeration value="Visual Basic"/>
      <xs:enumeration value="Other"/>
      <xs:enumeration value="All"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Attack_PatternType / capec:Keywords
Namespace http://capec.mitre.org/capec-2
Annotations
This field is intended to be a catch-all field for assisting in searching and subsecting a collection of patterns according to criteria not contained elsewehre in this schema.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_Keywords_Keyword
Children capec:Keyword
Source
<xs:element name="Keywords" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field is intended to be a catch-all field for assisting in searching and subsecting a collection of patterns according to criteria not contained elsewehre in this schema.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Keyword" type="xs:string" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field contains an individual keyword to be used for tagging and searching.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:Keywords / capec:Keyword
Namespace http://capec.mitre.org/capec-2
Annotations
This field contains an individual keyword to be used for tagging and searching.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Keyword" type="xs:string" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field contains an individual keyword to be used for tagging and searching.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_PatternType / capec:References
Namespace http://capec.mitre.org/capec-2
Annotations
This field enumerates reference resources that were used to develop the definition of this attack pattern and those that could prove valuable to the reader looking for further information on this attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_PatternType_References_Reference
Children capec:Reference
Source
<xs:element name="References" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field enumerates reference resources that were used to develop the definition of this attack pattern and those that could prove valuable to the reader looking for further information on this attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field should describe the reference clearly and unambiguously by name and with some method of address such that the reader can locate the resource for further reference.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_PatternType / capec:References / capec:Reference
Namespace http://capec.mitre.org/capec-2
Annotations
This field should describe the reference clearly and unambiguously by name and with some method of address such that the reader can locate the resource for further reference.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_ID ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Description ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Author ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Title ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Section ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Edition ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publication ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publisher ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Date ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_PubDate ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Link ap_schema_v2_5_xsd.tmp#Reference_Type
Type capec:Reference_Type
Children capec:Reference_Author, capec:Reference_Date, capec:Reference_Description, capec:Reference_Edition, capec:Reference_Link, capec:Reference_PubDate, capec:Reference_Publication, capec:Reference_Publisher, capec:Reference_Section, capec:Reference_Title
Attributes
QName Type Fixed Default Use Annotation
Reference_ID optional
The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.
Source
<xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field should describe the reference clearly and unambiguously by name and with some method of address such that the reader can locate the resource for further reference.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Other_Notes
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains one or more Note elements, each of which	provide any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Other_Notes_Note
Used by
Children capec:Note
Source
<xs:element name="Other_Notes">
  <xs:annotation>
    <xs:documentation>This element contains one or more Note elements, each of which provide any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Note" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element contains any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Other_Notes / capec:Note
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains any additional notes or comments
that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Note" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element contains any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Maintenance_Notes
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains one or more Maintenance_Note elements which each contain significant maintenance tasks within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Maintenance_Notes_Maintenance_Note
Used by
Children capec:Maintenance_Note
Source
<xs:element name="Maintenance_Notes">
  <xs:annotation>
    <xs:documentation>This element contains one or more Maintenance_Note elements which each contain significant maintenance tasks within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Maintenance_Note" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element describes a significant maintenance task within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Maintenance_Notes / capec:Maintenance_Note
Namespace http://capec.mitre.org/capec-2
Annotations
This element describes a significant maintenance task
within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Maintenance_Note" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element describes a significant maintenance task within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History
Namespace http://capec.mitre.org/capec-2
Annotations
This element is used to keep track of the author of the attack pattern entry and anyone who has made modifications to the content. This provides a means of contacting the authors and modifiers for clarifying ambiguities, merging overlapping contributions, etc. This should be filled out for all entries.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Submissions ap_schema_v2_5_xsd.tmp#Content_History_Contributions ap_schema_v2_5_xsd.tmp#Content_History_Modifications ap_schema_v2_5_xsd.tmp#Content_History_Previous_Entry_Names
Used by
Children capec:Contributions, capec:Modifications, capec:Previous_Entry_Names, capec:Submissions
Source
<xs:element name="Content_History">
  <xs:annotation>
    <xs:documentation>This element is used to keep track of the author of the attack pattern entry and anyone who has made modifications to the content. This provides a means of contacting the authors and modifiers for clarifying ambiguities, merging overlapping contributions, etc. This should be filled out for all entries.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Submissions" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Submission elements.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Submission" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This element houses the subelements which identify the submitter and the submitter's comments related to this entry. This element has a single attribute, Submission_Source, which provides a general idea of how the initial information for this entry was obtained, whether internal to the CAPEC team, external, donated, etc.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Submitter" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Submitter_Organization" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should identify the author's organization.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Submission_Date" type="xs:date" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Submission_Comment" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="Submission_Source" use="optional">
                  <xs:annotation>
                    <xs:documentation>This attribute identifies how the initial information for this entry was obtained.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Externally_Mined"/>
                      <xs:enumeration value="NDA"/>
                      <xs:enumeration value="Internal_CAPEC_Team"/>
                      <xs:enumeration value="External_Submission"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Contributions" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Contribution elements.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Contribution" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This element houses the subelements which identify the contributor and contributor's comments related to this entry. This element has a single attribute, Contribution_Mode, which indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Contributor" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Contribution_Organization" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should identify the author's organization.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Contribution_Date" type="xs:date" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Contribution_Comment" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack patterns entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="Contribution_Mode" use="optional">
                  <xs:annotation>
                    <xs:documentation>This attribute indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Content"/>
                      <xs:enumeration value="Feedback"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Modifications" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Modification elements.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Modification" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This element houses the subelements which identify the modifier and modifier's comments related to this entry. A new Modification element should exist for each modification of the entry content. This element has a single attribute, Modification_Source, which indicates whether this modification was made by a CAPEC team member or an external party.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Modifier" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should contain the name of the person modifying this entry.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Modifier_Organization" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should contain the modifier's organization.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Modification_Date" type="xs:date" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element should contain the date of the modifications.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Modification_Comment" type="xs:string" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This element provides the modifier with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="Modification_Importance">
                  <xs:annotation>
                    <xs:documentation>This attribute identifies how significant the modification is to the attack pattern with regard to the meaning and interpretation of the pattern. If a modification has a value of Critical, then the meaning of the entry or how it might be interpreted has changed and requires attention from anyone previously dependent on the attack pattern.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Normal"/>
                      <xs:enumeration value="Critical"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:attribute>
                <xs:attribute name="Modification_Source" use="optional">
                  <xs:annotation>
                    <xs:documentation>This attribute indicates whether this modification was created by a CAPEC team member or provided by an external party.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Internal"/>
                      <xs:enumeration value="External"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Previous_Entry_Names" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Previous_Entry_Name elements, each of which describes a previous name that was used for this entry. This should be filled out whenever a substantive name change occurs.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Previous_Entry_Name" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This element identifies a name that was previously used for this entry.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:simpleContent>
                  <xs:extension base="xs:string">
                    <xs:attribute name="Name_Change_Date" type="xs:date" use="required">
                      <xs:annotation>
                        <xs:documentation>This lists the date on which this name was changed to something else. Typically, this date will be closely aligned with new releases of CAPEC.</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:extension>
                </xs:simpleContent>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Submissions
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Submission elements.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Submissions_Submission
Children capec:Submission
Source
<xs:element name="Submissions" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Submission elements.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Submission" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element houses the subelements which identify the submitter and the submitter's comments related to this entry. This element has a single attribute, Submission_Source, which provides a general idea of how the initial information for this entry was obtained, whether internal to the CAPEC team, external, donated, etc.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Submitter" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Submitter_Organization" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should identify the author's organization.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Submission_Date" type="xs:date" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Submission_Comment" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="Submission_Source" use="optional">
            <xs:annotation>
              <xs:documentation>This attribute identifies how the initial information for this entry was obtained.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Externally_Mined"/>
                <xs:enumeration value="NDA"/>
                <xs:enumeration value="Internal_CAPEC_Team"/>
                <xs:enumeration value="External_Submission"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Submissions / capec:Submission
Namespace http://capec.mitre.org/capec-2
Annotations
This element houses the subelements which identify the submitter and the submitter's comments related to this entry. This element has a single attribute, Submission_Source, which provides a general idea of how the initial information for this entry was obtained, whether internal to the CAPEC team, external, donated, etc.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Submissions_Content_History_Content_History_Submissions_Submission_Submission_Source ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Submissions_Content_History_Content_History_Submissions_Submission_Submitter ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Submissions_Content_History_Content_History_Submissions_Submission_Submitter_Organization ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Submissions_Content_History_Content_History_Submissions_Submission_Submission_Date ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Submissions_Content_History_Content_History_Submissions_Submission_Submission_Comment
Children capec:Submission_Comment, capec:Submission_Date, capec:Submitter, capec:Submitter_Organization
Attributes
QName Type Fixed Default Use Annotation
Submission_Source restriction of xs:string optional
This attribute identifies how the initial	information for this entry was obtained.
Source
<xs:element name="Submission" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element houses the subelements which identify the submitter and the submitter's comments related to this entry. This element has a single attribute, Submission_Source, which provides a general idea of how the initial information for this entry was obtained, whether internal to the CAPEC team, external, donated, etc.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Submitter" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Submitter_Organization" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should identify the author's organization.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Submission_Date" type="xs:date" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Submission_Comment" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="Submission_Source" use="optional">
      <xs:annotation>
        <xs:documentation>This attribute identifies how the initial information for this entry was obtained.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Externally_Mined"/>
          <xs:enumeration value="NDA"/>
          <xs:enumeration value="Internal_CAPEC_Team"/>
          <xs:enumeration value="External_Submission"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Submissions / capec:Submission / capec:Submitter
Namespace http://capec.mitre.org/capec-2
Annotations
This element should contain the name of the author for this entry.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Submitter" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Submissions / capec:Submission / capec:Submitter_Organization
Namespace http://capec.mitre.org/capec-2
Annotations
This element should identify the author's organization.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Submitter_Organization" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should identify the author's organization.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Submissions / capec:Submission / capec:Submission_Date
Namespace http://capec.mitre.org/capec-2
Annotations
This element should provide the date on which this content was authored in YYYY-MM-DD format.
Diagram
Diagram
Type xs:date
Source
<xs:element name="Submission_Date" type="xs:date" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Submissions / capec:Submission / capec:Submission_Comment
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides the author with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Submission_Comment" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Contributions
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Contribution elements.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Contributions_Contribution
Children capec:Contribution
Source
<xs:element name="Contributions" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Contribution elements.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Contribution" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element houses the subelements which identify the contributor and contributor's comments related to this entry. This element has a single attribute, Contribution_Mode, which indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Contributor" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Contribution_Organization" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should identify the author's organization.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Contribution_Date" type="xs:date" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Contribution_Comment" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack patterns entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="Contribution_Mode" use="optional">
            <xs:annotation>
              <xs:documentation>This attribute indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Content"/>
                <xs:enumeration value="Feedback"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Contributions / capec:Contribution
Namespace http://capec.mitre.org/capec-2
Annotations
This element houses the subelements which identify the contributor and contributor's comments related to this entry. This element has a single attribute, Contribution_Mode, which indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Contributions_Content_History_Content_History_Contributions_Contribution_Contribution_Mode ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Contributions_Content_History_Content_History_Contributions_Contribution_Contributor ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Contributions_Content_History_Content_History_Contributions_Contribution_Contribution_Organization ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Contributions_Content_History_Content_History_Contributions_Contribution_Contribution_Date ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Contributions_Content_History_Content_History_Contributions_Contribution_Contribution_Comment
Children capec:Contribution_Comment, capec:Contribution_Date, capec:Contribution_Organization, capec:Contributor
Attributes
QName Type Fixed Default Use Annotation
Contribution_Mode restriction of xs:string optional
This attribute indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.
Source
<xs:element name="Contribution" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element houses the subelements which identify the contributor and contributor's comments related to this entry. This element has a single attribute, Contribution_Mode, which indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Contributor" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Contribution_Organization" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should identify the author's organization.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Contribution_Date" type="xs:date" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Contribution_Comment" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack patterns entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="Contribution_Mode" use="optional">
      <xs:annotation>
        <xs:documentation>This attribute indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Content"/>
          <xs:enumeration value="Feedback"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Contributions / capec:Contribution / capec:Contributor
Namespace http://capec.mitre.org/capec-2
Annotations
This element should contain the name of the author for this entry.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Contributor" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should contain the name of the author for this entry.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Contributions / capec:Contribution / capec:Contribution_Organization
Namespace http://capec.mitre.org/capec-2
Annotations
This element should identify the author's organization.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Contribution_Organization" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should identify the author's organization.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Contributions / capec:Contribution / capec:Contribution_Date
Namespace http://capec.mitre.org/capec-2
Annotations
This element should provide the date on which this content was authored in YYYY-MM-DD format.
Diagram
Diagram
Type xs:date
Source
<xs:element name="Contribution_Date" type="xs:date" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should provide the date on which this content was authored in YYYY-MM-DD format.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Contributions / capec:Contribution / capec:Contribution_Comment
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides the author with a place to store any comments regarding the content of this attack patterns entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Contribution_Comment" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element provides the author with a place to store any comments regarding the content of this attack patterns entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Modifications
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Modification elements.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Modification
Children capec:Modification
Source
<xs:element name="Modifications" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Modification elements.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Modification" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element houses the subelements which identify the modifier and modifier's comments related to this entry. A new Modification element should exist for each modification of the entry content. This element has a single attribute, Modification_Source, which indicates whether this modification was made by a CAPEC team member or an external party.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Modifier" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should contain the name of the person modifying this entry.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Modifier_Organization" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should contain the modifier's organization.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Modification_Date" type="xs:date" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element should contain the date of the modifications.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Modification_Comment" type="xs:string" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element provides the modifier with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="Modification_Importance">
            <xs:annotation>
              <xs:documentation>This attribute identifies how significant the modification is to the attack pattern with regard to the meaning and interpretation of the pattern. If a modification has a value of Critical, then the meaning of the entry or how it might be interpreted has changed and requires attention from anyone previously dependent on the attack pattern.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Normal"/>
                <xs:enumeration value="Critical"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
          <xs:attribute name="Modification_Source" use="optional">
            <xs:annotation>
              <xs:documentation>This attribute indicates whether this modification was created by a CAPEC team member or provided by an external party.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Internal"/>
                <xs:enumeration value="External"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Modifications / capec:Modification
Namespace http://capec.mitre.org/capec-2
Annotations
This element houses the subelements which identify the modifier and modifier's comments related to this entry. A new Modification element should exist for each modification of the entry content. This element has a single attribute, Modification_Source, which indicates whether this modification was made by a CAPEC team member or an external party.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Content_History_Content_History_Modifications_Modification_Modification_Importance ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Content_History_Content_History_Modifications_Modification_Modification_Source ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Content_History_Content_History_Modifications_Modification_Modifier ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Content_History_Content_History_Modifications_Modification_Modifier_Organization ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Content_History_Content_History_Modifications_Modification_Modification_Date ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Modifications_Content_History_Content_History_Modifications_Modification_Modification_Comment
Children capec:Modification_Comment, capec:Modification_Date, capec:Modifier, capec:Modifier_Organization
Attributes
QName Type Fixed Default Use Annotation
Modification_Importance restriction of xs:string optional
This attribute identifies how significant the modification is to the attack pattern with regard to the meaning and interpretation of the pattern. If a modification has a value of Critical, then the meaning of the entry or how it might be interpreted has changed and requires attention from anyone previously dependent on the attack pattern.
Modification_Source restriction of xs:string optional
This attribute indicates whether this modification was created by a CAPEC team member or provided by an
external party.
Source
<xs:element name="Modification" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element houses the subelements which identify the modifier and modifier's comments related to this entry. A new Modification element should exist for each modification of the entry content. This element has a single attribute, Modification_Source, which indicates whether this modification was made by a CAPEC team member or an external party.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Modifier" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should contain the name of the person modifying this entry.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Modifier_Organization" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should contain the modifier's organization.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Modification_Date" type="xs:date" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element should contain the date of the modifications.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Modification_Comment" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element provides the modifier with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="Modification_Importance">
      <xs:annotation>
        <xs:documentation>This attribute identifies how significant the modification is to the attack pattern with regard to the meaning and interpretation of the pattern. If a modification has a value of Critical, then the meaning of the entry or how it might be interpreted has changed and requires attention from anyone previously dependent on the attack pattern.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Normal"/>
          <xs:enumeration value="Critical"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Modification_Source" use="optional">
      <xs:annotation>
        <xs:documentation>This attribute indicates whether this modification was created by a CAPEC team member or provided by an external party.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Internal"/>
          <xs:enumeration value="External"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Modifications / capec:Modification / capec:Modifier
Namespace http://capec.mitre.org/capec-2
Annotations
This element should contain the name of the person modifying this entry.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Modifier" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should contain the name of the person modifying this entry.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Modifications / capec:Modification / capec:Modifier_Organization
Namespace http://capec.mitre.org/capec-2
Annotations
This element should contain the modifier's organization.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Modifier_Organization" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should contain the modifier's organization.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Modifications / capec:Modification / capec:Modification_Date
Namespace http://capec.mitre.org/capec-2
Annotations
This element should contain the date of the modifications.
Diagram
Diagram
Type xs:date
Source
<xs:element name="Modification_Date" type="xs:date" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element should contain the date of the modifications.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Modifications / capec:Modification / capec:Modification_Comment
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides the modifier with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Modification_Comment" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element provides the modifier with a place to store any comments regarding the content of this attack pattern entry, such as assumptions made, reasons for omitting elements, contact information, pending questions, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Content_History / capec:Previous_Entry_Names
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Previous_Entry_Name elements, each of which describes a previous name that was used for this entry. This should be filled out whenever a substantive name change occurs.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Previous_Entry_Names_Previous_Entry_Name
Children capec:Previous_Entry_Name
Source
<xs:element name="Previous_Entry_Names" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Previous_Entry_Name elements, each of which describes a previous name that was used for this entry. This should be filled out whenever a substantive name change occurs.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Previous_Entry_Name" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element identifies a name that was previously used for this entry.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="Name_Change_Date" type="xs:date" use="required">
                <xs:annotation>
                  <xs:documentation>This lists the date on which this name was changed to something else. Typically, this date will be closely aligned with new releases of CAPEC.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Content_History / capec:Previous_Entry_Names / capec:Previous_Entry_Name
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies a name that was previously used for this entry.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Content_History_Content_History_Previous_Entry_Names_Content_History_Content_History_Previous_Entry_Names_Previous_Entry_Name_Name_Change_Date
Type extension of xs:string
Attributes
QName Type Fixed Default Use Annotation
Name_Change_Date xs:date required
This lists the date on which this name was changed to something else. 	Typically, this date will be closely aligned with new releases of CAPEC.
Source
<xs:element name="Previous_Entry_Name" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element identifies a name that was previously used for this entry.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="Name_Change_Date" type="xs:date" use="required">
          <xs:annotation>
            <xs:documentation>This lists the date on which this name was changed to something else. Typically, this date will be closely aligned with new releases of CAPEC.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern_Catalog
Namespace http://capec.mitre.org/capec-2
Annotations
This is the enumerated catalog of common attack patterns.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Catalog_Name ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Catalog_Version ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Catalog_Date ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Views ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Categories ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Attack_Patterns ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Compound_Elements ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Common_Attack_Steps ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Common_Attack_Surfaces ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Environments
Children capec:Attack_Patterns, capec:Categories, capec:Common_Attack_Steps, capec:Common_Attack_Surfaces, capec:Compound_Elements, capec:Environments, capec:Views
Attributes
QName Type Fixed Default Use Annotation
Catalog_Date xs:date optional
Catalog_Name xs:string required
Catalog_Version xs:string required
Source
<xs:element name="Attack_Pattern_Catalog">
  <xs:annotation>
    <xs:documentation>This is the enumerated catalog of common attack patterns.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Views" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="capec:View" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Categories" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="capec:Category" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>A category is a collection of attack patterns sharing a common attribute. The shared attribute may any number of things.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Attack_Patterns" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="capec:Attack_Pattern" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Compound_Elements" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="capec:Compound_Element">
              <xs:annotation>
                <xs:documentation>The Compound_Element structure represents a meaningful aggregation of several attack patterns.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Common_Attack_Steps" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Common_Attack_Step" maxOccurs="unbounded">
              <xs:complexType>
                <xs:complexContent>
                  <xs:extension base="capec:Custom_Attack_StepType">
                    <xs:attribute name="ID" type="xs:integer" use="required"/>
                  </xs:extension>
                </xs:complexContent>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Common_Attack_Surfaces" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Common_Attack_Surface" maxOccurs="unbounded">
              <xs:complexType>
                <xs:complexContent>
                  <xs:extension base="capec:Target_Attack_Surface_DescriptionType">
                    <xs:attribute name="ID" type="xs:integer" use="required"/>
                  </xs:extension>
                </xs:complexContent>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Environments" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="capec:Environment" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="Catalog_Name" type="xs:string" use="required"/>
    <xs:attribute name="Catalog_Version" type="xs:string" use="required"/>
    <xs:attribute name="Catalog_Date" type="xs:date"/>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Views
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#View
Children capec:View
Source
<xs:element name="Views" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="capec:View" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:View
Namespace http://capec.mitre.org/capec-2
Annotations
Each View element represents a perspective with which one might look at the attack patterns in CAPEC.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#View_ID ap_schema_v2_5_xsd.tmp#View_Name ap_schema_v2_5_xsd.tmp#View_Status ap_schema_v2_5_xsd.tmp#View_Attributes_View_Structure ap_schema_v2_5_xsd.tmp#View_Attributes_View_Objective ap_schema_v2_5_xsd.tmp#View_Attributes_View_Audience ap_schema_v2_5_xsd.tmp#Relationships ap_schema_v2_5_xsd.tmp#Relationship_Notes ap_schema_v2_5_xsd.tmp#Maintenance_Notes ap_schema_v2_5_xsd.tmp#Other_Notes ap_schema_v2_5_xsd.tmp#Alternate_Terms ap_schema_v2_5_xsd.tmp#Research_Gaps ap_schema_v2_5_xsd.tmp#View_Attributes_References ap_schema_v2_5_xsd.tmp#View_Attributes_View_Filter ap_schema_v2_5_xsd.tmp#Content_History ap_schema_v2_5_xsd.tmp#View_Attributes
Used by
Children capec:Alternate_Terms, capec:Content_History, capec:Maintenance_Notes, capec:Other_Notes, capec:References, capec:Relationship_Notes, capec:Relationships, capec:Research_Gaps, capec:View_Audience, capec:View_Filter, capec:View_Objective, capec:View_Structure
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
The ID attribute provides a unique identifier for the entry.			It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Views.
Name xs:string required
The Name is a descriptive attribute used to give the reader an idea of what perspective this view represents. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Views.
Status capec:Status_Type required
The Status attribute defines the status level for this view.
Source
<xs:element name="View">
  <xs:annotation>
    <xs:documentation>Each View element represents a perspective with which one might look at the attack patterns in CAPEC.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:group ref="capec:View_Attributes">
      <xs:annotation>
        <xs:documentation>The View_Attributes structure is a collection of common elements which might be shared by all Views.</xs:documentation>
      </xs:annotation>
    </xs:group>
    <xs:attribute name="ID" type="xs:integer" use="required">
      <xs:annotation>
        <xs:documentation>The ID attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Views.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="Name" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>The Name is a descriptive attribute used to give the reader an idea of what perspective this view represents. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Views.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="Status" type="capec:Status_Type" use="required">
      <xs:annotation>
        <xs:documentation>The Status attribute defines the status level for this view.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:View_Attributes / capec:View_Structure
Namespace http://capec.mitre.org/capec-2
Annotations
The View_Structure element describes how this view is being constructed. Valid values are: Implicit Slice = a slice based on a filter criteria; Explicit Slice = a slice based on arbitrary membership, as defined by specific relationships between entries; Graph = a bounded graphical slice based on ChildOf relationships.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Implicit_Slice
enumeration Explicit_Slice
enumeration Graph
Source
<xs:element name="View_Structure">
  <xs:annotation>
    <xs:documentation>The View_Structure element describes how this view is being constructed. Valid values are: Implicit Slice = a slice based on a filter criteria; Explicit Slice = a slice based on arbitrary membership, as defined by specific relationships between entries; Graph = a bounded graphical slice based on ChildOf relationships.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Implicit_Slice"/>
      <xs:enumeration value="Explicit_Slice"/>
      <xs:enumeration value="Graph"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:View_Attributes / capec:View_Objective
Namespace http://capec.mitre.org/capec-2
Annotations
The View_Objective element describes the perspective from which this View is constructed.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="View_Objective" type="capec:Structured_Text_Type">
  <xs:annotation>
    <xs:documentation>The View_Objective element describes the perspective from which this View is constructed.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:View_Attributes / capec:View_Audience
Namespace http://capec.mitre.org/capec-2
Annotations
The View_Audience element provides a reference to the targeted audiences or groups for this view.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#View_Attributes_View_Attributes_View_Audience_Audience
Children capec:Audience
Source
<xs:element name="View_Audience" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The View_Audience element provides a reference to the targeted audiences or groups for this view.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Audience" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>The Audience element provides a reference to the target audience or group for this view.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Stakeholder">
              <xs:annotation>
                <xs:documentation>The Stakeholder element specifies what types of members of the CAPEC community might be interested in this view.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Developers"/>
                  <xs:enumeration value="Software_Vendors"/>
                  <xs:enumeration value="Assessment_Vendors"/>
                  <xs:enumeration value="Educators"/>
                  <xs:enumeration value="OWGV"/>
                  <xs:enumeration value="SAMATE"/>
                  <xs:enumeration value="CAPEC_Formalization"/>
                  <xs:enumeration value="CAPEC_Team"/>
                  <xs:enumeration value="Software_Customers"/>
                  <xs:enumeration value="Assessment_Customers"/>
                  <xs:enumeration value="Academic_Researchers"/>
                  <xs:enumeration value="Applied_Researchers"/>
                  <xs:enumeration value="Information_Providers"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="Stakeholder_Description" type="capec:Structured_Text_Type" minOccurs="0">
              <xs:annotation>
                <xs:documentation>The Stakeholder_Description el provides some text describing what properties of this View this particular Stakeholder might find useful.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:View_Attributes / capec:View_Audience / capec:Audience
Namespace http://capec.mitre.org/capec-2
Annotations
The Audience element provides a reference to the
target audience or group for this view.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#View_Attributes_View_Attributes_View_Audience_View_Attributes_View_Attributes_View_Audience_Audience_Stakeholder ap_schema_v2_5_xsd.tmp#View_Attributes_View_Attributes_View_Audience_View_Attributes_View_Attributes_View_Audience_Audience_Stakeholder_Description
Children capec:Stakeholder, capec:Stakeholder_Description
Source
<xs:element name="Audience" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The Audience element provides a reference to the target audience or group for this view.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Stakeholder">
        <xs:annotation>
          <xs:documentation>The Stakeholder element specifies what types of members of the CAPEC community might be interested in this view.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Developers"/>
            <xs:enumeration value="Software_Vendors"/>
            <xs:enumeration value="Assessment_Vendors"/>
            <xs:enumeration value="Educators"/>
            <xs:enumeration value="OWGV"/>
            <xs:enumeration value="SAMATE"/>
            <xs:enumeration value="CAPEC_Formalization"/>
            <xs:enumeration value="CAPEC_Team"/>
            <xs:enumeration value="Software_Customers"/>
            <xs:enumeration value="Assessment_Customers"/>
            <xs:enumeration value="Academic_Researchers"/>
            <xs:enumeration value="Applied_Researchers"/>
            <xs:enumeration value="Information_Providers"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Stakeholder_Description" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The Stakeholder_Description el provides some text describing what properties of this View this particular Stakeholder might find useful.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:View_Attributes / capec:View_Audience / capec:Audience / capec:Stakeholder
Namespace http://capec.mitre.org/capec-2
Annotations
The Stakeholder element specifies what types of members of the CAPEC community might be
interested in this view.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Developers
enumeration Software_Vendors
enumeration Assessment_Vendors
enumeration Educators
enumeration OWGV
enumeration SAMATE
enumeration CAPEC_Formalization
enumeration CAPEC_Team
enumeration Software_Customers
enumeration Assessment_Customers
enumeration Academic_Researchers
enumeration Applied_Researchers
enumeration Information_Providers
Source
<xs:element name="Stakeholder">
  <xs:annotation>
    <xs:documentation>The Stakeholder element specifies what types of members of the CAPEC community might be interested in this view.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Developers"/>
      <xs:enumeration value="Software_Vendors"/>
      <xs:enumeration value="Assessment_Vendors"/>
      <xs:enumeration value="Educators"/>
      <xs:enumeration value="OWGV"/>
      <xs:enumeration value="SAMATE"/>
      <xs:enumeration value="CAPEC_Formalization"/>
      <xs:enumeration value="CAPEC_Team"/>
      <xs:enumeration value="Software_Customers"/>
      <xs:enumeration value="Assessment_Customers"/>
      <xs:enumeration value="Academic_Researchers"/>
      <xs:enumeration value="Applied_Researchers"/>
      <xs:enumeration value="Information_Providers"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:View_Attributes / capec:View_Audience / capec:Audience / capec:Stakeholder_Description
Namespace http://capec.mitre.org/capec-2
Annotations
The Stakeholder_Description el provides some text describing what properties of this View this particular Stakeholder might find
useful.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Stakeholder_Description" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The Stakeholder_Description el provides some text describing what properties of this View this particular Stakeholder might find useful.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Relationships
Namespace http://capec.mitre.org/capec-2
Annotations
The Relationships structure contains one or more Relationship elements, each of which identifies an association between this structure, whether it	is a Attack Pattern, Category, or Compound_Element and another structure.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relationships_Relationship
Used by
Children capec:Relationship
Source
<xs:element name="Relationships">
  <xs:annotation>
    <xs:documentation>The Relationships structure contains one or more Relationship elements, each of which identifies an association between this structure, whether it is a Attack Pattern, Category, or Compound_Element and another structure.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relationship" type="capec:RelationshipType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Each Relationship identifies an association between this structure, whether it is an Attack Pattern, Category, or Compound_Element and another structure. The relationship also identifies the views under which the relationship is applicable.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Relationships / capec:Relationship
Namespace http://capec.mitre.org/capec-2
Annotations
Each Relationship identifies an association between this structure, whether it is an Attack Pattern, Category, or Compound_Element and another structure. The relationship also identifies the views under which the relationship is applicable.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Views ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Chains ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Target_Form ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Nature ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Target_ID ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Description ap_schema_v2_5_xsd.tmp#RelationshipType
Type capec:RelationshipType
Children capec:Relationship_Chains, capec:Relationship_Description, capec:Relationship_Nature, capec:Relationship_Target_Form, capec:Relationship_Target_ID, capec:Relationship_Views
Source
<xs:element name="Relationship" type="capec:RelationshipType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Each Relationship identifies an association between this structure, whether it is an Attack Pattern, Category, or Compound_Element and another structure. The relationship also identifies the views under which the relationship is applicable.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Relationship_Notes
Namespace http://capec.mitre.org/capec-2
Annotations
This structure houses one or more Relationship_Note elements, which each contain details regarding the relationships between CAPEC entries.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relationship_Notes_Relationship_Note
Used by
Children capec:Relationship_Note
Source
<xs:element name="Relationship_Notes">
  <xs:annotation>
    <xs:documentation>This structure houses one or more Relationship_Note elements, which each contain details regarding the relationships between CAPEC entries.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Relationship_Note" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element contains a note regarding the relationships between CAPEC entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Relationship_Notes / capec:Relationship_Note
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains a note regarding the relationships between CAPEC entries.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Relationship_Note" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element contains a note regarding the relationships between CAPEC entries.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Research_Gaps
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Research gap elements, each of	which identifies potential opportunities for the attack research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Research_Gaps_Research_Gap
Used by
Children capec:Research_Gap
Source
<xs:element name="Research_Gaps">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Research gap elements, each of which identifies potential opportunities for the attack research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Research_Gap" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element identifies potential opportunities for the vulnerability research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Research_Gaps / capec:Research_Gap
Namespace http://capec.mitre.org/capec-2
Annotations
This element identifies potential opportunities for the
vulnerability research community to conduct further exploration of 	issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Research_Gap" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element identifies potential opportunities for the vulnerability research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:View_Attributes / capec:References
Namespace http://capec.mitre.org/capec-2
Annotations
The References element contains one or more Reference elements, each of which provide further reading and insight into this view. This should be filled out when the view is based on sources or projects that are external to the CAPEC project.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_List_Type_Reference ap_schema_v2_5_xsd.tmp#Reference_List_Type
Type capec:Reference_List_Type
Children capec:Reference
Source
<xs:element name="References" type="capec:Reference_List_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The References element contains one or more Reference elements, each of which provide further reading and insight into this view. This should be filled out when the view is based on sources or projects that are external to the CAPEC project.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Reference_List_Type / capec:Reference
Namespace http://capec.mitre.org/capec-2
Annotations
Each Reference subelement should provide a single source from which more information and deeper insight can be obtained, such as a research paper or an excerpt from a publication. Multiple Reference subelements can exist. The sole attribute of this element is the id. The id is optional and translates to a preceding footnote below the context notes if the author of the entry wants to cite a reference. Not all subelements need to be completed, since some are designed for web references and others are designed for book references. The fields Reference_Author and Reference_Title should be filled out for all references if possible. Reference_Section and Reference_Date can be included for either book references or online references. Reference_Edition, Reference_Publication, Reference_Publisher, and Reference_PubDate are intended for book references,
however they can be included where appropriate for other types of references. Reference_Link is intended for web references, however it can be included for book references as well if applicable.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_ID ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Description ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Author ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Title ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Section ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Edition ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publication ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publisher ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Date ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_PubDate ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Link ap_schema_v2_5_xsd.tmp#Reference_Type
Type capec:Reference_Type
Children capec:Reference_Author, capec:Reference_Date, capec:Reference_Description, capec:Reference_Edition, capec:Reference_Link, capec:Reference_PubDate, capec:Reference_Publication, capec:Reference_Publisher, capec:Reference_Section, capec:Reference_Title
Attributes
QName Type Fixed Default Use Annotation
Reference_ID optional
The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.
Source
<xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Each Reference subelement should provide a single source from which more information and deeper insight can be obtained, such as a research paper or an excerpt from a publication. Multiple Reference subelements can exist. The sole attribute of this element is the id. The id is optional and translates to a preceding footnote below the context notes if the author of the entry wants to cite a reference. Not all subelements need to be completed, since some are designed for web references and others are designed for book references. The fields Reference_Author and Reference_Title should be filled out for all references if possible. Reference_Section and Reference_Date can be included for either book references or online references. Reference_Edition, Reference_Publication, Reference_Publisher, and Reference_PubDate are intended for book references, however they can be included where appropriate for other types of references. Reference_Link is intended for web references, however it can be included for book references as well if applicable.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:View_Attributes / capec:View_Filter
Namespace http://capec.mitre.org/capec-2
Annotations
The View_Filter element holds an XSL query for identifying which elements are members of an implicit slice. This should only be present for implicit slices.
Diagram
Diagram
Type xs:string
Source
<xs:element name="View_Filter" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The View_Filter element holds an XSL query for identifying which elements are members of an implicit slice. This should only be present for implicit slices.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Categories
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category
Children capec:Category
Source
<xs:element name="Categories" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="capec:Category" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>A category is a collection of attack patterns sharing a common attribute. The shared attribute may any number of things.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_ID ap_schema_v2_5_xsd.tmp#Category_Name ap_schema_v2_5_xsd.tmp#Category_Status ap_schema_v2_5_xsd.tmp#Category_Description ap_schema_v2_5_xsd.tmp#Category_Related_Weaknesses ap_schema_v2_5_xsd.tmp#Category_Attack_Prerequisites ap_schema_v2_5_xsd.tmp#Category_Methods_of_Attack ap_schema_v2_5_xsd.tmp#Category_Attacker_Skills_or_Knowledge_Required ap_schema_v2_5_xsd.tmp#Category_Resources_Required ap_schema_v2_5_xsd.tmp#Category_Attack_Motivation-Consequences ap_schema_v2_5_xsd.tmp#Relationships ap_schema_v2_5_xsd.tmp#Relationship_Notes ap_schema_v2_5_xsd.tmp#Maintenance_Notes ap_schema_v2_5_xsd.tmp#Category_Background_Details ap_schema_v2_5_xsd.tmp#Other_Notes ap_schema_v2_5_xsd.tmp#Alternate_Terms ap_schema_v2_5_xsd.tmp#Research_Gaps ap_schema_v2_5_xsd.tmp#Category_References ap_schema_v2_5_xsd.tmp#Content_History
Used by
Children capec:Alternate_Terms, capec:Attack_Motivation-Consequences, capec:Attack_Prerequisites, capec:Attacker_Skills_or_Knowledge_Required, capec:Background_Details, capec:Content_History, capec:Description, capec:Maintenance_Notes, capec:Methods_of_Attack, capec:Other_Notes, capec:References, capec:Related_Weaknesses, capec:Relationship_Notes, capec:Relationships, capec:Research_Gaps, capec:Resources_Required
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Categories.
Name xs:string required
The Name is a descriptive name used to give the reader an idea of what the commonality is amongst the children of this category. All
words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Categories.
Status capec:Status_Type required
The Status attribute defines the status level for this category.
Source
<xs:element name="Category">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description">
        <xs:annotation>
          <xs:documentation>This field provides a description of this Category. Its primary subelement is Description_Summary which is intended to serve as a minimalistic description which provides the information necessary to understand the primary focus of this entry. Additionally, it has the subelement Extended_Description which is optional and is used to provide further information pertaining to this attack pattern.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description_Summary" type="xs:string">
              <xs:annotation>
                <xs:documentation>This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Extended_Description" type="capec:Structured_Text_Type" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Related_Weaknesses" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Which specific weaknesses does this attack target and leverage? Specific weaknesses (underlying issues that may cause vulnerabilities) reference the industry-standard Common Weakness Enumeration (CWE). This list should include not only those weaknesses that are directly targeted by the attack but also those whose presence can directly increase the likelihood of the attack succeeding or the impact if it does succeed.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Related_Weakness" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field describes an individual related weakness.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="CWE_ID" type="xs:integer">
                    <xs:annotation>
                      <xs:documentation>The CWE_ID is a field that exists for all weaknesses enumerated in the Common Weakness Enumeration (CWE). It is a unique value that allows each weakness to be unambiguously identified. The CWE_ID field for the attack pattern contains the value of the CWE_ID for the specific related weakness.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Weakness_Relationship_Type">
                    <xs:annotation>
                      <xs:documentation>This field describes the nature of the relationship between this weakness and the attack pattern. Weaknesses that are specifically targeted by the attack are of type "Targeted". Weaknesses which are not specifically targeted but whose presence may increase the likelihood of the attack succeeding or the impact of the attack if it does succeed are of type "Secondary".</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Targeted"/>
                        <xs:enumeration value="Secondary"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Attack_Prerequisites" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the conditions that must exist or the functionality and characteristics that the target software must have or behavior it must exhibit for an attack of this type to succeed.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Attack_Prerequisite" type="capec:Structured_Text_Type" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field describes an individual attack prerequisite.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Methods_of_Attack" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the mechanism of attack used by this pattern. This field can help define the applicable attack surface required for this attack.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Method_of_Attack" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Injection"/>
                  <xs:enumeration value="Modification of Resources"/>
                  <xs:enumeration value="Protocol Manipulation"/>
                  <xs:enumeration value="Analysis"/>
                  <xs:enumeration value="API Abuse"/>
                  <xs:enumeration value="Brute Force"/>
                  <xs:enumeration value="Flooding"/>
                  <xs:enumeration value="Time and State"/>
                  <xs:enumeration value="Spoofing"/>
                  <xs:enumeration value="Social Engineering"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Attacker_Skills_or_Knowledge_Required" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the level of skills or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Attacker_Skill_or_Knowledge_Required" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Low"/>
                        <xs:enumeration value="Medium"/>
                        <xs:enumeration value="High"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                  <xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
                    <xs:annotation>
                      <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Resources_Required" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field describes the resources (CPU cycles, IP addresses, tools, etc.) required by an attacker to effectively execute this type of attack.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Attack_Motivation-Consequences" minOccurs="0">
        <xs:annotation>
          <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Attack_Motivation-Consequence" type="capec:Common_ConsequenceType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element ref="capec:Relationships" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The Relationships structure contains one or more Relationship elements, each of which identifies an association between this structure, whether it is an Attack Pattern, Category, or Compound_Element and another structure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Relationship_Notes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure houses one or more Relationship_Note elements, which each contain details regarding the relationships between CAPEC entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Maintenance_Notes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element contains one or more Maintenance_Note elements which each contain significant maintenance tasks within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Background_Details" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Background_Detail elements, each of which holds information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the entry itself. It should be filled out where appropriate.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Background_Detail" type="capec:Structured_Text_Type" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the category itself. It should be filled out where appropriate.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element ref="capec:Other_Notes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element contains one or more Note elements, each of which provide any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Alternate_Terms" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element contains one or more Alternate_Term elements, each of which contains other names used to describe this attack pattern.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Research_Gaps" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Research gap elements, each of which identifies potential opportunities for the vulnerability research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="References" type="capec:Reference_List_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The References element contains one or more Reference elements, each of which provide further reading and insight into this attack pattern.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Content_History" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element is used to keep track of the author of the attack pattern entry and anyone who has made modifications to the content. This provides a means of contacting the authors and modifiers for clarifying ambiguities, merging overlapping contributions, etc. This should be filled out for all entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required">
      <xs:annotation>
        <xs:documentation>This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Categories.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="Name" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>The Name is a descriptive name used to give the reader an idea of what the commonality is amongst the children of this category. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Categories.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="Status" type="capec:Status_Type" use="required">
      <xs:annotation>
        <xs:documentation>The Status attribute defines the status level for this category.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field provides a description of this Category. Its primary subelement is Description_Summary which is intended to serve as a minimalistic description which provides the information necessary to understand the primary focus of this entry. Additionally, it has the subelement Extended_Description which is optional and is used to provide further information pertaining to this attack pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Description_Description_Summary ap_schema_v2_5_xsd.tmp#Category_Category_Description_Extended_Description
Children capec:Description_Summary, capec:Extended_Description
Source
<xs:element name="Description">
  <xs:annotation>
    <xs:documentation>This field provides a description of this Category. Its primary subelement is Description_Summary which is intended to serve as a minimalistic description which provides the information necessary to understand the primary focus of this entry. Additionally, it has the subelement Extended_Description which is optional and is used to provide further information pertaining to this attack pattern.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description_Summary" type="xs:string">
        <xs:annotation>
          <xs:documentation>This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Extended_Description" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Description / capec:Description_Summary
Namespace http://capec.mitre.org/capec-2
Annotations
This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Description_Summary" type="xs:string">
  <xs:annotation>
    <xs:documentation>This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:Description / capec:Extended_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Extended_Description" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:Related_Weaknesses
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:Related_Weakness
Source
Element capec:Category / capec:Related_Weaknesses / capec:Related_Weakness
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Children capec:CWE_ID, capec:Weakness_Relationship_Type
Source
Element capec:Category / capec:Related_Weaknesses / capec:Related_Weakness / capec:CWE_ID
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type xs:integer
Source
Element capec:Category / capec:Related_Weaknesses / capec:Related_Weakness / capec:Weakness_Relationship_Type
Namespace http://capec.mitre.org/capec-2
Annotations
Diagram
Type restriction of xs:string
Facets
Source
Element capec:Category / capec:Attack_Prerequisites
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the conditions that must exist or the functionality and characteristics that the target software must have or behavior it must exhibit for an attack of this type to succeed.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Attack_Prerequisites_Attack_Prerequisite
Children capec:Attack_Prerequisite
Source
<xs:element name="Attack_Prerequisites" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the conditions that must exist or the functionality and characteristics that the target software must have or behavior it must exhibit for an attack of this type to succeed.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Prerequisite" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes an individual attack prerequisite.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Attack_Prerequisites / capec:Attack_Prerequisite
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes an individual attack prerequisite.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Attack_Prerequisite" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes an individual attack prerequisite.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:Methods_of_Attack
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the mechanism of attack used by this pattern. This field can help define the applicable attack surface required for this attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Methods_of_Attack_Method_of_Attack
Children capec:Method_of_Attack
Source
<xs:element name="Methods_of_Attack" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the mechanism of attack used by this pattern. This field can help define the applicable attack surface required for this attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Method_of_Attack" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Injection"/>
            <xs:enumeration value="Modification of Resources"/>
            <xs:enumeration value="Protocol Manipulation"/>
            <xs:enumeration value="Analysis"/>
            <xs:enumeration value="API Abuse"/>
            <xs:enumeration value="Brute Force"/>
            <xs:enumeration value="Flooding"/>
            <xs:enumeration value="Time and State"/>
            <xs:enumeration value="Spoofing"/>
            <xs:enumeration value="Social Engineering"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Methods_of_Attack / capec:Method_of_Attack
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Injection
enumeration Modification of Resources
enumeration Protocol Manipulation
enumeration Analysis
enumeration API Abuse
enumeration Brute Force
enumeration Flooding
enumeration Time and State
enumeration Spoofing
enumeration Social Engineering
Source
<xs:element name="Method_of_Attack" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Injection"/>
      <xs:enumeration value="Modification of Resources"/>
      <xs:enumeration value="Protocol Manipulation"/>
      <xs:enumeration value="Analysis"/>
      <xs:enumeration value="API Abuse"/>
      <xs:enumeration value="Brute Force"/>
      <xs:enumeration value="Flooding"/>
      <xs:enumeration value="Time and State"/>
      <xs:enumeration value="Spoofing"/>
      <xs:enumeration value="Social Engineering"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Category / capec:Attacker_Skills_or_Knowledge_Required
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the level of skills or specific knowledge required by an attacker to execute this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Attacker_Skills_or_Knowledge_Required_Attacker_Skill_or_Knowledge_Required
Children capec:Attacker_Skill_or_Knowledge_Required
Source
<xs:element name="Attacker_Skills_or_Knowledge_Required" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the level of skills or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attacker_Skill_or_Knowledge_Required" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Low"/>
                  <xs:enumeration value="Medium"/>
                  <xs:enumeration value="High"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Attacker_Skills_or_Knowledge_Required / capec:Attacker_Skill_or_Knowledge_Required
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Attacker_Skills_or_Knowledge_Required_Category_Category_Attacker_Skills_or_Knowledge_Required_Attacker_Skill_or_Knowledge_Required_Skill_or_Knowledge_Level ap_schema_v2_5_xsd.tmp#Category_Category_Attacker_Skills_or_Knowledge_Required_Category_Category_Attacker_Skills_or_Knowledge_Required_Attacker_Skill_or_Knowledge_Required_Skill_or_Knowledge_Type
Children capec:Skill_or_Knowledge_Level, capec:Skill_or_Knowledge_Type
Source
<xs:element name="Attacker_Skill_or_Knowledge_Required" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Low"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="High"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Attacker_Skills_or_Knowledge_Required / capec:Attacker_Skill_or_Knowledge_Required / capec:Skill_or_Knowledge_Level
Namespace http://capec.mitre.org/capec-2
Annotations
This should be communicated on a rough scale (Low, Medium, High).
For example:
• Low - Basic computer familiarity
• Low - Basic SQL knowledge
• Medium - Moderate scripting and shell experience and ability to disassemble and decompile
• High - Expert knowledge of LINUX kernel
• High - Detailed knowledge of target software development practices and business context (former employee)
• Etc.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Low
enumeration Medium
enumeration High
Source
<xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Low"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="High"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:Category / capec:Attacker_Skills_or_Knowledge_Required / capec:Attacker_Skill_or_Knowledge_Required / capec:Skill_or_Knowledge_Type
Namespace http://capec.mitre.org/capec-2
Annotations
This field provides contextual detail for the skill or knowledge level.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:Resources_Required
Namespace http://capec.mitre.org/capec-2
Annotations
This field describes the resources (CPU cycles, IP addresses, tools, etc.) required by an attacker to effectively execute this type of attack.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Resources_Required" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This field describes the resources (CPU cycles, IP addresses, tools, etc.) required by an attacker to effectively execute this type of attack.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:Attack_Motivation-Consequences
Namespace http://capec.mitre.org/capec-2
Annotations
What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Attack_Motivation-Consequences_Attack_Motivation-Consequence
Children capec:Attack_Motivation-Consequence
Source
<xs:element name="Attack_Motivation-Consequences" minOccurs="0">
  <xs:annotation>
    <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Attack_Motivation-Consequence" type="capec:Common_ConsequenceType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Attack_Motivation-Consequences / capec:Attack_Motivation-Consequence
Namespace http://capec.mitre.org/capec-2
Annotations
What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Common_Consequence_ID ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Scope ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Technical_Impact ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Note ap_schema_v2_5_xsd.tmp#Common_ConsequenceType
Type capec:Common_ConsequenceType
Children capec:Consequence_Note, capec:Consequence_Scope, capec:Consequence_Technical_Impact
Attributes
QName Type Fixed Default Use Annotation
Common_Consequence_ID xs:string optional
The Common_Consequence_ID stores the value for the related
Common_Consequence entry identifier as a string. Only one
Common_Consequence_ID element can exist for each Common_Consequence element
(ex: CC-1). However, Common_Consequences across CAPEC with the same ID should
only vary in small details.
Source
<xs:element name="Attack_Motivation-Consequence" type="capec:Common_ConsequenceType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:Background_Details
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Background_Detail elements, each of which holds information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the entry itself. It should be filled out where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Category_Category_Background_Details_Background_Detail
Children capec:Background_Detail
Source
<xs:element name="Background_Details" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Background_Detail elements, each of which holds information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the entry itself. It should be filled out where appropriate.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Background_Detail" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the category itself. It should be filled out where appropriate.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Category / capec:Background_Details / capec:Background_Detail
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the category itself. It should be filled out where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Background_Detail" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the category itself. It should be filled out where appropriate.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Category / capec:References
Namespace http://capec.mitre.org/capec-2
Annotations
The References element contains one or more Reference elements, each of which provide further reading and insight into this
attack pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_List_Type_Reference ap_schema_v2_5_xsd.tmp#Reference_List_Type
Type capec:Reference_List_Type
Children capec:Reference
Source
<xs:element name="References" type="capec:Reference_List_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The References element contains one or more Reference elements, each of which provide further reading and insight into this attack pattern.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Attack_Patterns
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Pattern
Children capec:Attack_Pattern
Source
<xs:element name="Attack_Patterns" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="capec:Attack_Pattern" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern
Namespace http://capec.mitre.org/capec-2
Annotations
This element is an individual attack pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_ID ap_schema_v2_5_xsd.tmp#Attack_PatternType_Name ap_schema_v2_5_xsd.tmp#Attack_PatternType_Pattern_Completeness ap_schema_v2_5_xsd.tmp#Attack_PatternType_Pattern_Abstraction ap_schema_v2_5_xsd.tmp#Attack_PatternType_Status ap_schema_v2_5_xsd.tmp#Attack_PatternType_Description ap_schema_v2_5_xsd.tmp#Alternate_Terms ap_schema_v2_5_xsd.tmp#Attack_PatternType_Target_Attack_Surface ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_Prerequisites ap_schema_v2_5_xsd.tmp#Attack_PatternType_Typical_Severity ap_schema_v2_5_xsd.tmp#Attack_PatternType_Typical_Likelihood_of_Exploit ap_schema_v2_5_xsd.tmp#Attack_PatternType_Methods_of_Attack ap_schema_v2_5_xsd.tmp#Attack_PatternType_Examples-Instances ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attacker_Skills_or_Knowledge_Required ap_schema_v2_5_xsd.tmp#Attack_PatternType_Resources_Required ap_schema_v2_5_xsd.tmp#Attack_PatternType_Probing_Techniques ap_schema_v2_5_xsd.tmp#Attack_PatternType_Indicators-Warnings_of_Attack ap_schema_v2_5_xsd.tmp#Attack_PatternType_Obfuscation_Techniques ap_schema_v2_5_xsd.tmp#Attack_PatternType_Solutions_and_Mitigations ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_Motivation-Consequences ap_schema_v2_5_xsd.tmp#Attack_PatternType_Injection_Vector ap_schema_v2_5_xsd.tmp#Attack_PatternType_Payload ap_schema_v2_5_xsd.tmp#Attack_PatternType_Activation_Zone ap_schema_v2_5_xsd.tmp#Attack_PatternType_Payload_Activation_Impact ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Weaknesses ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Vulnerabilities ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Attack_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Relevant_Security_Requirements ap_schema_v2_5_xsd.tmp#Attack_PatternType_Relevant_Design_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Relevant_Security_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Security_Principles ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Guidelines ap_schema_v2_5_xsd.tmp#Attack_PatternType_Purposes ap_schema_v2_5_xsd.tmp#Attack_PatternType_CIA_Impact ap_schema_v2_5_xsd.tmp#Attack_PatternType_Technical_Context ap_schema_v2_5_xsd.tmp#Attack_PatternType_Keywords ap_schema_v2_5_xsd.tmp#Attack_PatternType_References ap_schema_v2_5_xsd.tmp#Other_Notes ap_schema_v2_5_xsd.tmp#Maintenance_Notes ap_schema_v2_5_xsd.tmp#Content_History ap_schema_v2_5_xsd.tmp#Attack_PatternType
Type capec:Attack_PatternType
Used by
Children capec:Activation_Zone, capec:Alternate_Terms, capec:Attack_Motivation-Consequences, capec:Attack_Prerequisites, capec:Attacker_Skills_or_Knowledge_Required, capec:CIA_Impact, capec:Content_History, capec:Description, capec:Examples-Instances, capec:Indicators-Warnings_of_Attack, capec:Injection_Vector, capec:Keywords, capec:Maintenance_Notes, capec:Methods_of_Attack, capec:Obfuscation_Techniques, capec:Other_Notes, capec:Payload, capec:Payload_Activation_Impact, capec:Probing_Techniques, capec:Purposes, capec:References, capec:Related_Attack_Patterns, capec:Related_Guidelines, capec:Related_Security_Principles, capec:Related_Vulnerabilities, capec:Related_Weaknesses, capec:Relevant_Design_Patterns, capec:Relevant_Security_Patterns, capec:Relevant_Security_Requirements, capec:Resources_Required, capec:Solutions_and_Mitigations, capec:Target_Attack_Surface, capec:Technical_Context, capec:Typical_Likelihood_of_Exploit, capec:Typical_Severity
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer 0 optional
Name xs:string required
Pattern_Abstraction restriction of xs:string optional
Pattern_Completeness restriction of xs:string optional
Status capec:Status_Type required
The Status attribute defines the status level for this view.
Source
<xs:element name="Attack_Pattern" type="capec:Attack_PatternType">
  <xs:annotation>
    <xs:documentation>This element is an individual attack pattern.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Compound_Elements
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Compound_Element
Children capec:Compound_Element
Source
<xs:element name="Compound_Elements" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="capec:Compound_Element">
        <xs:annotation>
          <xs:documentation>The Compound_Element structure represents a meaningful aggregation of several attack patterns.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Compound_Element
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Compound_Element_ID ap_schema_v2_5_xsd.tmp#Compound_Element_Name ap_schema_v2_5_xsd.tmp#Compound_Element_Compound_Element_Abstraction ap_schema_v2_5_xsd.tmp#Compound_Element_Compound_Element_Completeness ap_schema_v2_5_xsd.tmp#Compound_Element_Compound_Element_Structure ap_schema_v2_5_xsd.tmp#Compound_Element_Status ap_schema_v2_5_xsd.tmp#Compound_Element_Description ap_schema_v2_5_xsd.tmp#Relationships ap_schema_v2_5_xsd.tmp#Relationship_Notes ap_schema_v2_5_xsd.tmp#Maintenance_Notes ap_schema_v2_5_xsd.tmp#Compound_Element_Background_Details ap_schema_v2_5_xsd.tmp#Other_Notes ap_schema_v2_5_xsd.tmp#Alternate_Terms ap_schema_v2_5_xsd.tmp#Research_Gaps ap_schema_v2_5_xsd.tmp#Compound_Element_References ap_schema_v2_5_xsd.tmp#Content_History
Used by
Children capec:Alternate_Terms, capec:Background_Details, capec:Content_History, capec:Description, capec:Maintenance_Notes, capec:Other_Notes, capec:References, capec:Relationship_Notes, capec:Relationships, capec:Research_Gaps
Attributes
QName Type Fixed Default Use Annotation
Compound_Element_Abstraction restriction of xs:string required
The Abstraction defines the abstraction level for this attack pattern. The abstraction levels for Compound_Elements and Attack Patterns are the same. For example, if the Compound_Element is a chain, and all elements of the chain are Meta level, then the Compound_Element Abstraction attribute is Meta. This is required for all Compound_Elements.
Compound_Element_Completeness restriction of xs:string required
Compound_Element_Structure restriction of xs:string required
The Structure attribute defines the structural nature of this compound element - that is, composed of other attack patterns concurrently, as in a composite, or consecutively, as in a chain.
ID xs:integer required
This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Compound_Elements.
Name xs:string required
The Name is a descriptive name used to give the reader an idea of the meaning behind the compound attack pattern structure. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Compound_Elements.
Status capec:Status_Type required
The Status attribute defines the status level for this compound element.
Source
<xs:element name="Compound_Element">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description">
        <xs:annotation>
          <xs:documentation>This field provides a description of this Structure, whether it is an Attack Pattern, Category or Compound Element. Its primary subelement is Description_Summary which is intended to serve as a minimalistic description which provides the information necessary to understand the primary focus of this entry. Additionally, it has the subelement Extended_Description which is optional and is used to provide further information pertaining to this attack pattern.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description_Summary" type="xs:string">
              <xs:annotation>
                <xs:documentation>This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="Extended_Description" type="capec:Structured_Text_Type" minOccurs="0">
              <xs:annotation>
                <xs:documentation>This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element ref="capec:Relationships" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The Relationships structure contains one or more Relationship elements, each of which identifies an association between this structure, whether it is an Attack Pattern, Category, or Compound_Element and another structure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Relationship_Notes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure houses one or more Relationship_Note elements, which each contain details regarding the relationships between CAPEC entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Maintenance_Notes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element contains one or more Maintenance_Note elements which each contain significant maintenance tasks within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Background_Details" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Background_Detail elements, each of which holds information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the entry itself. It should be filled out where appropriate.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Background_Detail" type="capec:Structured_Text_Type" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the attack pattern itself. It should be filled out where appropriate.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element ref="capec:Other_Notes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element contains one or more Note elements, each of which provide any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Alternate_Terms" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element contains one or more Alternate_Term elements, each of which contains other names used to describe this attack pattern.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Research_Gaps" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This structure contains one or more Research gap elements, each of which identifies potential opportunities for the vulnerability research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="References" type="capec:Reference_List_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>The References element contains one or more Reference elements, each of which provide further reading and insight into this attack pattern.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element ref="capec:Content_History" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element is used to keep track of the author of the attack pattern entry and anyone who has made modifications to the content. This provides a means of contacting the authors and modifiers for clarifying ambiguities, merging overlapping contributions, etc. This should be filled out for all entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="xs:integer" use="required">
      <xs:annotation>
        <xs:documentation>This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Compound_Elements.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="Name" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>The Name is a descriptive name used to give the reader an idea of the meaning behind the compound attack pattern structure. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Compound_Elements.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="Compound_Element_Abstraction" use="required">
      <xs:annotation>
        <xs:documentation>The Abstraction defines the abstraction level for this attack pattern. The abstraction levels for Compound_Elements and Attack Patterns are the same. For example, if the Compound_Element is a chain, and all elements of the chain are Meta level, then the Compound_Element Abstraction attribute is Meta. This is required for all Compound_Elements.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Meta"/>
          <xs:enumeration value="Standard"/>
          <xs:enumeration value="Detailed"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Compound_Element_Completeness" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Complete"/>
          <xs:enumeration value="Stub"/>
          <xs:enumeration value="Hook"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Compound_Element_Structure" use="required">
      <xs:annotation>
        <xs:documentation>The Structure attribute defines the structural nature of this compound element - that is, composed of other attack patterns concurrently, as in a composite, or consecutively, as in a chain.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Composite"/>
          <xs:enumeration value="Chain"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="Status" type="capec:Status_Type" use="required">
      <xs:annotation>
        <xs:documentation>The Status attribute defines the status level for this compound element.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Element capec:Compound_Element / capec:Description
Namespace http://capec.mitre.org/capec-2
Annotations
This field provides a description of this Structure, whether it is an Attack Pattern, Category or Compound Element. Its primary subelement is Description_Summary which is intended to serve as a minimalistic description which provides the information necessary to understand the primary focus of this entry. Additionally, it has the subelement Extended_Description which is optional and is used to provide further information pertaining to this attack pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Compound_Element_Compound_Element_Description_Description_Summary ap_schema_v2_5_xsd.tmp#Compound_Element_Compound_Element_Description_Extended_Description
Children capec:Description_Summary, capec:Extended_Description
Source
<xs:element name="Description">
  <xs:annotation>
    <xs:documentation>This field provides a description of this Structure, whether it is an Attack Pattern, Category or Compound Element. Its primary subelement is Description_Summary which is intended to serve as a minimalistic description which provides the information necessary to understand the primary focus of this entry. Additionally, it has the subelement Extended_Description which is optional and is used to provide further information pertaining to this attack pattern.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description_Summary" type="xs:string">
        <xs:annotation>
          <xs:documentation>This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Extended_Description" type="capec:Structured_Text_Type" minOccurs="0">
        <xs:annotation>
          <xs:documentation>This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Compound_Element / capec:Description / capec:Description_Summary
Namespace http://capec.mitre.org/capec-2
Annotations
This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.
Diagram
Diagram
Type xs:string
Source
<xs:element name="Description_Summary" type="xs:string">
  <xs:annotation>
    <xs:documentation>This description should be short and should limit itself to describing the key points that define this entry. Further explanation can be included in the extended description element. This is required for all entries.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Compound_Element / capec:Description / capec:Extended_Description
Namespace http://capec.mitre.org/capec-2
Annotations
This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Extended_Description" type="capec:Structured_Text_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This element provides a place for details important to the description of this entry to be included that are not necessary to convey the fundamental concept behind the entry. This is not required for all entries and should only be included where appropriate.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Compound_Element / capec:Background_Details
Namespace http://capec.mitre.org/capec-2
Annotations
This structure contains one or more Background_Detail elements, each of which holds information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the entry itself. It should be filled out where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Compound_Element_Compound_Element_Background_Details_Background_Detail
Children capec:Background_Detail
Source
<xs:element name="Background_Details" minOccurs="0">
  <xs:annotation>
    <xs:documentation>This structure contains one or more Background_Detail elements, each of which holds information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the entry itself. It should be filled out where appropriate.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Background_Detail" type="capec:Structured_Text_Type" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the attack pattern itself. It should be filled out where appropriate.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Compound_Element / capec:Background_Details / capec:Background_Detail
Namespace http://capec.mitre.org/capec-2
Annotations
This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the attack pattern itself. It should be filled out where appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Background_Detail" type="capec:Structured_Text_Type" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>This element contains background information regarding the entry or any technologies that are related to it, where the background information is not related to the nature of the attack pattern itself. It should be filled out where appropriate.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Compound_Element / capec:References
Namespace http://capec.mitre.org/capec-2
Annotations
The References element contains one or more Reference elements, each of which provide further reading and insight into this
attack pattern.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_List_Type_Reference ap_schema_v2_5_xsd.tmp#Reference_List_Type
Type capec:Reference_List_Type
Children capec:Reference
Source
<xs:element name="References" type="capec:Reference_List_Type" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The References element contains one or more Reference elements, each of which provide further reading and insight into this attack pattern.</xs:documentation>
  </xs:annotation>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Common_Attack_Steps
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Attack_Pattern_Catalog_Common_Attack_Steps_Common_Attack_Step
Children capec:Common_Attack_Step
Source
<xs:element name="Common_Attack_Steps" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Common_Attack_Step" maxOccurs="unbounded">
        <xs:complexType>
          <xs:complexContent>
            <xs:extension base="capec:Custom_Attack_StepType">
              <xs:attribute name="ID" type="xs:integer" use="required"/>
            </xs:extension>
          </xs:complexContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Common_Attack_Steps / capec:Common_Attack_Step
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Title ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Techniques ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Indicators ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Outcomes ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Security_Controls ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Observables ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Attack_Pattern_Catalog_Common_Attack_Steps_Attack_Pattern_Catalog_Attack_Pattern_Catalog_Common_Attack_Steps_Common_Attack_Step_ID
Type extension of capec:Custom_Attack_StepType
Type hierarchy
Children capec:Attack_Step_Description, capec:Attack_Step_Techniques, capec:Attack_Step_Title, capec:Indicators, capec:Observables, capec:Outcomes, capec:Security_Controls
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Source
<xs:element name="Common_Attack_Step" maxOccurs="unbounded">
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="capec:Custom_Attack_StepType">
        <xs:attribute name="ID" type="xs:integer" use="required"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Common_Attack_Surfaces
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Attack_Pattern_Catalog_Common_Attack_Surfaces_Common_Attack_Surface
Children capec:Common_Attack_Surface
Source
<xs:element name="Common_Attack_Surfaces" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Common_Attack_Surface" maxOccurs="unbounded">
        <xs:complexType>
          <xs:complexContent>
            <xs:extension base="capec:Target_Attack_Surface_DescriptionType">
              <xs:attribute name="ID" type="xs:integer" use="required"/>
            </xs:extension>
          </xs:complexContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Common_Attack_Surfaces / capec:Common_Attack_Surface
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Targeted_OSI_Layers ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Localities ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Types ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Functional_Services ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType ap_schema_v2_5_xsd.tmp#Attack_Pattern_Catalog_Attack_Pattern_Catalog_Common_Attack_Surfaces_Attack_Pattern_Catalog_Attack_Pattern_Catalog_Common_Attack_Surfaces_Common_Attack_Surface_ID
Type extension of capec:Target_Attack_Surface_DescriptionType
Type hierarchy
Children capec:Target_Attack_Surface_Localities, capec:Target_Attack_Surface_Types, capec:Target_Functional_Services, capec:Targeted_OSI_Layers
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer required
Source
<xs:element name="Common_Attack_Surface" maxOccurs="unbounded">
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="capec:Target_Attack_Surface_DescriptionType">
        <xs:attribute name="ID" type="xs:integer" use="required"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Element capec:Attack_Pattern_Catalog / capec:Environments
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Environment
Children capec:Environment
Source
<xs:element name="Environments" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element ref="capec:Environment" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:Environment
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Environment_ID ap_schema_v2_5_xsd.tmp#Environment_Environment_Title ap_schema_v2_5_xsd.tmp#Environment_Environment_Description
Used by
Children capec:Environment_Description, capec:Environment_Title
Attributes
QName Type Fixed Default Use Annotation
ID xs:ID required
Source
<xs:element name="Environment">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>Description and globally unique ID for a kind of environment or context that is required. Used in Attack Steps, Indicators of Susceptibility, and Security Controls, etc.</xs:documentation>
    </xs:annotation>
    <xs:all>
      <xs:element name="Environment_Title" type="xs:token"/>
      <xs:element name="Environment_Description" type="xs:token"/>
    </xs:all>
    <xs:attribute name="ID" type="xs:ID" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:Environment / capec:Environment_Title
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:token
Source
<xs:element name="Environment_Title" type="xs:token"/>
Element capec:Environment / capec:Environment_Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:token
Source
<xs:element name="Environment_Description" type="xs:token"/>
Element capec:ObservablesType / capec:Observable
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Noisiness ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Ease_of_Obfuscation ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Obfuscation_Techniques
Children capec:Ease_of_Obfuscation, capec:Noisiness, capec:Obfuscation_Techniques, capec:Signature
Source
<xs:element name="Observable" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Signature">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Location-Sensor" minOccurs="0"/>
            <xs:element name="Stateful_Measure">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Description" type="capec:Structured_Text_Type"/>
                  <xs:element name="Value_Type">
                    <xs:complexType>
                      <xs:choice>
                        <xs:element name="Objective_Value" type="xs:string"/>
                        <xs:element name="Trend">
                          <xs:simpleType>
                            <xs:restriction base="xs:string">
                              <xs:enumeration value="Increasing"/>
                              <xs:enumeration value="Decreasing"/>
                            </xs:restriction>
                          </xs:simpleType>
                        </xs:element>
                        <xs:element name="Frequency">
                          <xs:complexType>
                            <xs:attribute name="Rate" type="xs:float" use="required"/>
                            <xs:attribute name="Units" type="xs:string" use="required"/>
                            <xs:attribute name="Scale" type="xs:string" use="required"/>
                          </xs:complexType>
                        </xs:element>
                      </xs:choice>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="Name"/>
              </xs:complexType>
            </xs:element>
            <xs:element name="Event">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Description" type="capec:Structured_Text_Type"/>
                  <xs:element name="Action">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Object" maxOccurs="unbounded">
                          <xs:complexType>
                            <xs:sequence>
                              <xs:element name="Value" maxOccurs="unbounded">
                                <xs:complexType>
                                  <xs:sequence>
                                    <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
                                    <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
                                    <xs:element name="Delta" minOccurs="0">
                                      <xs:complexType>
                                        <xs:choice>
                                          <xs:element name="Trend">
                                            <xs:simpleType>
                                              <xs:restriction base="xs:string">
                                                <xs:enumeration value="Increasing"/>
                                                <xs:enumeration value="Decreasing"/>
                                              </xs:restriction>
                                            </xs:simpleType>
                                          </xs:element>
                                          <xs:element name="Frequency">
                                            <xs:complexType>
                                              <xs:attribute name="Rate" type="xs:float" use="required"/>
                                              <xs:attribute name="Units" type="xs:string" use="required"/>
                                              <xs:attribute name="Scale" type="xs:string" use="required"/>
                                            </xs:complexType>
                                          </xs:element>
                                        </xs:choice>
                                      </xs:complexType>
                                    </xs:element>
                                  </xs:sequence>
                                </xs:complexType>
                              </xs:element>
                            </xs:sequence>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="Event_Type" type="xs:string"/>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="Noisiness" minOccurs="0">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="High"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="Low"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Ease_of_Obfuscation" minOccurs="0">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="High"/>
            <xs:enumeration value="Medium"/>
            <xs:enumeration value="Low"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Obfuscation_Techniques" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Description" type="capec:Structured_Text_Type"/>
                  <xs:element name="Observables" type="capec:ObservablesType"/>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Location-Sensor ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event
Children capec:Event, capec:Location-Sensor, capec:Stateful_Measure
Source
<xs:element name="Signature">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Location-Sensor" minOccurs="0"/>
      <xs:element name="Stateful_Measure">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="capec:Structured_Text_Type"/>
            <xs:element name="Value_Type">
              <xs:complexType>
                <xs:choice>
                  <xs:element name="Objective_Value" type="xs:string"/>
                  <xs:element name="Trend">
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Increasing"/>
                        <xs:enumeration value="Decreasing"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                  <xs:element name="Frequency">
                    <xs:complexType>
                      <xs:attribute name="Rate" type="xs:float" use="required"/>
                      <xs:attribute name="Units" type="xs:string" use="required"/>
                      <xs:attribute name="Scale" type="xs:string" use="required"/>
                    </xs:complexType>
                  </xs:element>
                </xs:choice>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="Name"/>
        </xs:complexType>
      </xs:element>
      <xs:element name="Event">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="capec:Structured_Text_Type"/>
            <xs:element name="Action">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Object" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Value" maxOccurs="unbounded">
                          <xs:complexType>
                            <xs:sequence>
                              <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
                              <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
                              <xs:element name="Delta" minOccurs="0">
                                <xs:complexType>
                                  <xs:choice>
                                    <xs:element name="Trend">
                                      <xs:simpleType>
                                        <xs:restriction base="xs:string">
                                          <xs:enumeration value="Increasing"/>
                                          <xs:enumeration value="Decreasing"/>
                                        </xs:restriction>
                                      </xs:simpleType>
                                    </xs:element>
                                    <xs:element name="Frequency">
                                      <xs:complexType>
                                        <xs:attribute name="Rate" type="xs:float" use="required"/>
                                        <xs:attribute name="Units" type="xs:string" use="required"/>
                                        <xs:attribute name="Scale" type="xs:string" use="required"/>
                                      </xs:complexType>
                                    </xs:element>
                                  </xs:choice>
                                </xs:complexType>
                              </xs:element>
                            </xs:sequence>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="Event_Type" type="xs:string"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Location-Sensor
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Source
<xs:element name="Location-Sensor" minOccurs="0"/>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Name ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Description ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type
Children capec:Description, capec:Value_Type
Attributes
QName Type Fixed Default Use Annotation
Name optional
Source
<xs:element name="Stateful_Measure">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type"/>
      <xs:element name="Value_Type">
        <xs:complexType>
          <xs:choice>
            <xs:element name="Objective_Value" type="xs:string"/>
            <xs:element name="Trend">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Increasing"/>
                  <xs:enumeration value="Decreasing"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="Frequency">
              <xs:complexType>
                <xs:attribute name="Rate" type="xs:float" use="required"/>
                <xs:attribute name="Units" type="xs:string" use="required"/>
                <xs:attribute name="Scale" type="xs:string" use="required"/>
              </xs:complexType>
            </xs:element>
          </xs:choice>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="Name"/>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type"/>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_Objective_Value ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_Trend ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_Frequency
Children capec:Frequency, capec:Objective_Value, capec:Trend
Source
<xs:element name="Value_Type">
  <xs:complexType>
    <xs:choice>
      <xs:element name="Objective_Value" type="xs:string"/>
      <xs:element name="Trend">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Increasing"/>
            <xs:enumeration value="Decreasing"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Frequency">
        <xs:complexType>
          <xs:attribute name="Rate" type="xs:float" use="required"/>
          <xs:attribute name="Units" type="xs:string" use="required"/>
          <xs:attribute name="Scale" type="xs:string" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type / capec:Objective_Value
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Objective_Value" type="xs:string"/>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type / capec:Trend
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Increasing
enumeration Decreasing
Source
<xs:element name="Trend">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Increasing"/>
      <xs:enumeration value="Decreasing"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type / capec:Frequency
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_Frequency_Rate ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_Frequency_Units ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Stateful_Measure_Value_Type_Frequency_Scale
Attributes
QName Type Fixed Default Use Annotation
Rate xs:float required
Scale xs:string required
Units xs:string required
Source
<xs:element name="Frequency">
  <xs:complexType>
    <xs:attribute name="Rate" type="xs:float" use="required"/>
    <xs:attribute name="Units" type="xs:string" use="required"/>
    <xs:attribute name="Scale" type="xs:string" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Event_Type ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Description ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action
Children capec:Action, capec:Description
Attributes
QName Type Fixed Default Use Annotation
Event_Type xs:string optional
Source
<xs:element name="Event">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type"/>
      <xs:element name="Action">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Object" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Value" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:sequence>
                        <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
                        <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
                        <xs:element name="Delta" minOccurs="0">
                          <xs:complexType>
                            <xs:choice>
                              <xs:element name="Trend">
                                <xs:simpleType>
                                  <xs:restriction base="xs:string">
                                    <xs:enumeration value="Increasing"/>
                                    <xs:enumeration value="Decreasing"/>
                                  </xs:restriction>
                                </xs:simpleType>
                              </xs:element>
                              <xs:element name="Frequency">
                                <xs:complexType>
                                  <xs:attribute name="Rate" type="xs:float" use="required"/>
                                  <xs:attribute name="Units" type="xs:string" use="required"/>
                                  <xs:attribute name="Scale" type="xs:string" use="required"/>
                                </xs:complexType>
                              </xs:element>
                            </xs:choice>
                          </xs:complexType>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="Event_Type" type="xs:string"/>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type"/>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object
Children capec:Object
Source
<xs:element name="Action">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Object" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Value" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
                  <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
                  <xs:element name="Delta" minOccurs="0">
                    <xs:complexType>
                      <xs:choice>
                        <xs:element name="Trend">
                          <xs:simpleType>
                            <xs:restriction base="xs:string">
                              <xs:enumeration value="Increasing"/>
                              <xs:enumeration value="Decreasing"/>
                            </xs:restriction>
                          </xs:simpleType>
                        </xs:element>
                        <xs:element name="Frequency">
                          <xs:complexType>
                            <xs:attribute name="Rate" type="xs:float" use="required"/>
                            <xs:attribute name="Units" type="xs:string" use="required"/>
                            <xs:attribute name="Scale" type="xs:string" use="required"/>
                          </xs:complexType>
                        </xs:element>
                      </xs:choice>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value
Children capec:Value
Source
<xs:element name="Object" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Value" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
            <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
            <xs:element name="Delta" minOccurs="0">
              <xs:complexType>
                <xs:choice>
                  <xs:element name="Trend">
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Increasing"/>
                        <xs:enumeration value="Decreasing"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                  <xs:element name="Frequency">
                    <xs:complexType>
                      <xs:attribute name="Rate" type="xs:float" use="required"/>
                      <xs:attribute name="Units" type="xs:string" use="required"/>
                      <xs:attribute name="Scale" type="xs:string" use="required"/>
                    </xs:complexType>
                  </xs:element>
                </xs:choice>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Objective_Value ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Change ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta
Children capec:Change, capec:Delta, capec:Objective_Value
Source
<xs:element name="Value" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
      <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
      <xs:element name="Delta" minOccurs="0">
        <xs:complexType>
          <xs:choice>
            <xs:element name="Trend">
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="Increasing"/>
                  <xs:enumeration value="Decreasing"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="Frequency">
              <xs:complexType>
                <xs:attribute name="Rate" type="xs:float" use="required"/>
                <xs:attribute name="Units" type="xs:string" use="required"/>
                <xs:attribute name="Scale" type="xs:string" use="required"/>
              </xs:complexType>
            </xs:element>
          </xs:choice>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Objective_Value
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:string
Source
<xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Change
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type xs:boolean
Source
<xs:element name="Change" type="xs:boolean" minOccurs="0"/>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Delta
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_Trend ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_Frequency
Children capec:Frequency, capec:Trend
Source
<xs:element name="Delta" minOccurs="0">
  <xs:complexType>
    <xs:choice>
      <xs:element name="Trend">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Increasing"/>
            <xs:enumeration value="Decreasing"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="Frequency">
        <xs:complexType>
          <xs:attribute name="Rate" type="xs:float" use="required"/>
          <xs:attribute name="Units" type="xs:string" use="required"/>
          <xs:attribute name="Scale" type="xs:string" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Delta / capec:Trend
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Increasing
enumeration Decreasing
Source
<xs:element name="Trend">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Increasing"/>
      <xs:enumeration value="Decreasing"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Delta / capec:Frequency
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_Frequency_Rate ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_Frequency_Units ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Signature_Event_Action_Object_Value_Delta_Frequency_Scale
Attributes
QName Type Fixed Default Use Annotation
Rate xs:float required
Scale xs:string required
Units xs:string required
Source
<xs:element name="Frequency">
  <xs:complexType>
    <xs:attribute name="Rate" type="xs:float" use="required"/>
    <xs:attribute name="Units" type="xs:string" use="required"/>
    <xs:attribute name="Scale" type="xs:string" use="required"/>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Noisiness
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration High
enumeration Medium
enumeration Low
Source
<xs:element name="Noisiness" minOccurs="0">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="High"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="Low"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Ease_of_Obfuscation
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration High
enumeration Medium
enumeration Low
Source
<xs:element name="Ease_of_Obfuscation" minOccurs="0">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="High"/>
      <xs:enumeration value="Medium"/>
      <xs:enumeration value="Low"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Obfuscation_Techniques
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Obfuscation_Techniques_Obfuscation_Technique
Children capec:Obfuscation_Technique
Source
<xs:element name="Obfuscation_Techniques" minOccurs="0">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="capec:Structured_Text_Type"/>
            <xs:element name="Observables" type="capec:ObservablesType"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Obfuscation_Techniques / capec:Obfuscation_Technique
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Obfuscation_Techniques_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Obfuscation_Techniques_Obfuscation_Technique_Description ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Obfuscation_Techniques_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_http___capec.mitre.org_capec-2_ObservablesType_http___capec.mitre.org_capec-2_ObservablesType_Observable_Obfuscation_Techniques_Obfuscation_Technique_Observables
Children capec:Description, capec:Observables
Source
<xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="capec:Structured_Text_Type"/>
      <xs:element name="Observables" type="capec:ObservablesType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Element capec:ObservablesType / capec:Observable / capec:Obfuscation_Techniques / capec:Obfuscation_Technique / capec:Description
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block ap_schema_v2_5_xsd.tmp#Structured_Text_Type
Type capec:Structured_Text_Type
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:element name="Description" type="capec:Structured_Text_Type"/>
Element capec:ObservablesType / capec:Observable / capec:Obfuscation_Techniques / capec:Obfuscation_Technique / capec:Observables
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_Observable ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType
Type capec:ObservablesType
Children capec:Observable
Source
<xs:element name="Observables" type="capec:ObservablesType"/>
Complex Type capec:Attack_PatternType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Attack_PatternType_ID ap_schema_v2_5_xsd.tmp#Attack_PatternType_Name ap_schema_v2_5_xsd.tmp#Attack_PatternType_Pattern_Completeness ap_schema_v2_5_xsd.tmp#Attack_PatternType_Pattern_Abstraction ap_schema_v2_5_xsd.tmp#Attack_PatternType_Status ap_schema_v2_5_xsd.tmp#Attack_PatternType_Description ap_schema_v2_5_xsd.tmp#Alternate_Terms ap_schema_v2_5_xsd.tmp#Attack_PatternType_Target_Attack_Surface ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_Prerequisites ap_schema_v2_5_xsd.tmp#Attack_PatternType_Typical_Severity ap_schema_v2_5_xsd.tmp#Attack_PatternType_Typical_Likelihood_of_Exploit ap_schema_v2_5_xsd.tmp#Attack_PatternType_Methods_of_Attack ap_schema_v2_5_xsd.tmp#Attack_PatternType_Examples-Instances ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attacker_Skills_or_Knowledge_Required ap_schema_v2_5_xsd.tmp#Attack_PatternType_Resources_Required ap_schema_v2_5_xsd.tmp#Attack_PatternType_Probing_Techniques ap_schema_v2_5_xsd.tmp#Attack_PatternType_Indicators-Warnings_of_Attack ap_schema_v2_5_xsd.tmp#Attack_PatternType_Obfuscation_Techniques ap_schema_v2_5_xsd.tmp#Attack_PatternType_Solutions_and_Mitigations ap_schema_v2_5_xsd.tmp#Attack_PatternType_Attack_Motivation-Consequences ap_schema_v2_5_xsd.tmp#Attack_PatternType_Injection_Vector ap_schema_v2_5_xsd.tmp#Attack_PatternType_Payload ap_schema_v2_5_xsd.tmp#Attack_PatternType_Activation_Zone ap_schema_v2_5_xsd.tmp#Attack_PatternType_Payload_Activation_Impact ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Weaknesses ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Vulnerabilities ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Attack_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Relevant_Security_Requirements ap_schema_v2_5_xsd.tmp#Attack_PatternType_Relevant_Design_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Relevant_Security_Patterns ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Security_Principles ap_schema_v2_5_xsd.tmp#Attack_PatternType_Related_Guidelines ap_schema_v2_5_xsd.tmp#Attack_PatternType_Purposes ap_schema_v2_5_xsd.tmp#Attack_PatternType_CIA_Impact ap_schema_v2_5_xsd.tmp#Attack_PatternType_Technical_Context ap_schema_v2_5_xsd.tmp#Attack_PatternType_Keywords ap_schema_v2_5_xsd.tmp#Attack_PatternType_References ap_schema_v2_5_xsd.tmp#Other_Notes ap_schema_v2_5_xsd.tmp#Maintenance_Notes ap_schema_v2_5_xsd.tmp#Content_History
Used by
Children capec:Activation_Zone, capec:Alternate_Terms, capec:Attack_Motivation-Consequences, capec:Attack_Prerequisites, capec:Attacker_Skills_or_Knowledge_Required, capec:CIA_Impact, capec:Content_History, capec:Description, capec:Examples-Instances, capec:Indicators-Warnings_of_Attack, capec:Injection_Vector, capec:Keywords, capec:Maintenance_Notes, capec:Methods_of_Attack, capec:Obfuscation_Techniques, capec:Other_Notes, capec:Payload, capec:Payload_Activation_Impact, capec:Probing_Techniques, capec:Purposes, capec:References, capec:Related_Attack_Patterns, capec:Related_Guidelines, capec:Related_Security_Principles, capec:Related_Vulnerabilities, capec:Related_Weaknesses, capec:Relevant_Design_Patterns, capec:Relevant_Security_Patterns, capec:Relevant_Security_Requirements, capec:Resources_Required, capec:Solutions_and_Mitigations, capec:Target_Attack_Surface, capec:Technical_Context, capec:Typical_Likelihood_of_Exploit, capec:Typical_Severity
Attributes
QName Type Fixed Default Use Annotation
ID xs:integer 0 optional
Name xs:string required
Pattern_Abstraction restriction of xs:string optional
Pattern_Completeness restriction of xs:string optional
Status capec:Status_Type required
The Status attribute defines the status level for this view.
Source
<xs:complexType name="Attack_PatternType">
  <xs:sequence>
    <xs:element name="Description" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field contains a detailed description of the attack including the chain of actions taken by the attacker. More comprehensive descriptions could include relevant attack trees and/or exploit graphs to more clearly elaborate this type of attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Summary" type="capec:Structured_Text_Type">
            <xs:annotation>
              <xs:documentation>Brief description of what the attack involves and what weaknesses it is leveraging for exploit.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element ref="capec:Attack_Execution_Flow" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Outline of the steps involved in an attacker executing the typical flow of the attack.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element ref="capec:Alternate_Terms" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element contains one or more Alternate_Term elements, each ofwhich contains other names used to describe this attack pattern.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Target_Attack_Surface" type="capec:Target_Attack_SurfaceType" minOccurs="0"/>
    <xs:element name="Attack_Prerequisites" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the conditions that must exist or the functionality and characteristics that the target software must have or behavior it must exhibit for an attack of this type to succeed.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Attack_Prerequisite" type="capec:Structured_Text_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual attack prerequisite.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Typical_Severity" minOccurs="0">
      <xs:annotation>
        <xs:documentation>On a rough scale (Very Low, Low, Medium, High, Very high), what is the typical severity of impact to the targeted software if this attack occurs? The severity of a specific attack instance can vary greatly depending on the specific context of the target software under attack. This field is intended to capture an overall typical average value for this type of attack with the understanding that it will not be completely accurate for all attacks.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Very High"/>
          <xs:enumeration value="High"/>
          <xs:enumeration value="Medium"/>
          <xs:enumeration value="Low"/>
          <xs:enumeration value="Very Low"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="Typical_Likelihood_of_Exploit" minOccurs="0">
      <xs:annotation>
        <xs:documentation>On a rough scale (Very Low, Low Medium, High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions? The likelihood of exploit of a specific attack instance can vary greatly depending on the specific context of the target software under attack. This field is intended to capture an overall typical average value for this type of attack with the understanding that it will not be completely accurate for all attacks.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Likelihood" type="xs:string" minOccurs="0">
            <xs:annotation>
              <xs:documentation>On a rough scale (Very Low, Low Medium, High, Very High), what is the overall likelihood of this type of attack typically succeeding considering the attack prerequisites, targeted weakness attack surface, skill required and resources required as well as available and likely implemented blocking solutions?</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="Explanation" type="capec:Structured_Text_Type" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field captures any useful explanation for the defined Likelihood.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Methods_of_Attack" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the mechanism of attack used by this pattern. This field can help define the applicable attack surface required for this attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Method_of_Attack" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes the mechanism of attack used by this pattern. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined vectors which is currently incomplete and will grow as new relevant vectors are identified. This field can help define the applicable attack surface required for this attack.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Injection"/>
                <xs:enumeration value="Modification of Resources"/>
                <xs:enumeration value="Protocol Manipulation"/>
                <xs:enumeration value="Analysis"/>
                <xs:enumeration value="API Abuse"/>
                <xs:enumeration value="Brute Force"/>
                <xs:enumeration value="Flooding"/>
                <xs:enumeration value="Time and State"/>
                <xs:enumeration value="Spoofing"/>
                <xs:enumeration value="Social Engineering"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Examples-Instances" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field contains explanatory examples or demonstrative exploit instances of this attack, which are intended to help the reader understand the nature, context and variability of the attack in more practical and concrete terms.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Example-Instance" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual example or exploit instance.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Example-Instance_Description" type="capec:Structured_Text_Type">
                  <xs:annotation>
                    <xs:documentation>This field describes in detail a specific example or exploit instance of this attack. It should outline the context of the attack, the targeted software, the targeted weaknesses or vulnerabilities, the specific set of actions involved in the attack and the resulting impact of the attacks success or failure (in the case of counterexamples).</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="References" minOccurs="0">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded"/>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
                <xs:element name="Example-Instance_Related_Vulnerabilities" minOccurs="0">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Example-Instance_Related_Vulnerability" type="capec:Structured_Text_Type" maxOccurs="unbounded">
                        <xs:annotation>
                          <xs:documentation>This field lists the specific vulnerabilities targeted by this exploit instance of the attack. Specific vulnerabilities should reference industry-standard identifiers such as Common Vulnerabilities and Exposures (CVE) numbers and/or US-CERT numbers.</xs:documentation>
                        </xs:annotation>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Attacker_Skills_or_Knowledge_Required" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the level of skills or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Attacker_Skill_or_Knowledge_Required" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes the level of skill or specific knowledge required by an attacker to execute this type of attack.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Skill_or_Knowledge_Level" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>This should be communicated on a rough scale (Low, Medium, High). For example: • Low - Basic computer familiarity • Low - Basic SQL knowledge • Medium - Moderate scripting and shell experience and ability to disassemble and decompile • High - Expert knowledge of LINUX kernel • High - Detailed knowledge of target software development practices and business context (former employee) • Etc.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Low"/>
                      <xs:enumeration value="Medium"/>
                      <xs:enumeration value="High"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="Skill_or_Knowledge_Type" type="capec:Structured_Text_Type" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>This field provides contextual detail for the skill or knowledge level.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Resources_Required" type="capec:Structured_Text_Type" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the resources (CPU cycles, IP addresses, tools, etc.) required by an attacker to effectively execute this type of attack.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Probing_Techniques" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes techniques typically used to probe and reconnoiter a potential target to determine vulnerability and/or to prepare for this type of attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Probing_Technique" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual probing technique.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
                <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Indicators-Warnings_of_Attack" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes activities, events, conditions or behaviors that could serve as indicators that an attack of this type is imminent, in progress or has occurred.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Indicator-Warning_of_Attack" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual indicator/warning.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
                <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Obfuscation_Techniques" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes techniques typically used to disguise the fact that an attack of this type is imminent, in progress or has occurred.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual obfuscation technique.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
                <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Solutions_and_Mitigations" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes actions or approaches that can potentially prevent or mitigate the risk of this attack. These solutions and mitigations are targeted to improve the resistance of the target software and thereby reduce the likelihood of the attack's success or to improve the resilience of the target software and thereby reduce the impact of the attack if it is successful.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Solution_or_Mitigation" type="capec:Structured_Text_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual blocking solution or mitigation.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Attack_Motivation-Consequences" minOccurs="0">
      <xs:annotation>
        <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Attack_Motivation-Consequence" type="capec:Common_ConsequenceType" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>What is the attacker trying to achieve by using this attack? This is not the end business/mission goal of the attack within the target context but rather the specific technical result desired that could be leveraged to achieve the end business/mission objective. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined motivations/consequences which is currently incomplete and will grow as new relevant possibilities are identified. This information is useful for aligning attack patterns to threat models and for determining which attack patterns are relevant for a given context.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Injection_Vector" type="capec:Structured_Text_Type" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes, as precisely as possible, the mechanism and format of an input-driven attack of this type. Injection vectors must take into account the grammar of an attack, the syntax accepted by the system, the position of various fields, and the ranges of data that are acceptable.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Payload" type="capec:Structured_Text_Type" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the code, configuration or other data to be executed or otherwise activated as part of an injection-based attack of this type.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Activation_Zone" type="capec:Structured_Text_Type" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the area within the target software that is capable of executing or otherwise activating the payload of an injection-based attack of this type. The activation zone is where the intent of the attacker is put into action. The activation zone may be a command interpreter, some active machine code in a buffer, a client browser, a system API call, etc.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Payload_Activation_Impact" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field is a description of the impact that the activation of the attack payload for an injection-based attack of this type would typically have on the confidentiality, integrity or availability of the target software.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Description" type="capec:Structured_Text_Type" minOccurs="0"/>
          <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Related_Weaknesses" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Which specific weaknesses does this attack target and leverage? Specific weaknesses (underlying issues that may cause vulnerabilities) reference the industry-standard Common Weakness Enumeration (CWE). This list should include not only those weaknesses that are directly targeted by the attack but also those whose presence can directly increase the likelihood of the attack succeeding or the impact if it does succeed.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Related_Weakness" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual related weakness.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="CWE_ID" type="xs:integer">
                  <xs:annotation>
                    <xs:documentation>The CWE_ID is a field that exists for all weaknesses enumerated in the Common Weakness Enumeration (CWE). It is a unique value that allows each weakness to be unambiguously identified. The CWE_ID field for the attack pattern contains the value of the CWE_ID for the specific related weakness.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="Weakness_Relationship_Type">
                  <xs:annotation>
                    <xs:documentation>This field describes the nature of the relationship between this weakness and the attack pattern. Weaknesses that are specifically targeted by the attack are of type "Targeted". Weaknesses which are not specifically targeted but whose presence may increase the likelihood of the attack succeeding or the impact of the attack if it does succeed are of type "Secondary".</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Targeted"/>
                      <xs:enumeration value="Secondary"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Related_Vulnerabilities" minOccurs="0">
      <xs:annotation>
        <xs:documentation>What specific vulnerabilities does this attack target and leverage? Specific vulnerabilities should reference industry-standard identifiers such as Common Vulnerabilities and Exposures (CVE ) numbers and/or US-CERT numbers. As vulnerabilities are much more specific and localized than weaknesses, it is typically rare that an attack pattern will target specific vulnerabilities. This would most likely occur if they are targeting vulnerabilities in underlying platforms, frameworks, libraries, etc.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Related_Vulnerability" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual related vulnerability.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Vulnerability_ID" type="xs:string">
                  <xs:annotation>
                    <xs:documentation>This field uses the unique reference ID for a specific related vulnerability utilizing an industry standard vulnerability listing (e.g., CVE-2006-4192, VU#650769, etc.).</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="Vulnerability_Description" type="capec:Structured_Text_Type">
                  <xs:annotation>
                    <xs:documentation>This field contains a short textual description of the specific related vulnerability taken from the industry standard vulnerability listing.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Related_Attack_Patterns" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field identifies other attack patterns that are somehow related to, dependent on, typically chained together, etc. with this pattern.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Related_Attack_Pattern" type="capec:RelationshipType" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual related attack pattern.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relevant_Security_Requirements" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field identifies specific security requirements that are relevant to this type of attack and are general enough to offer opportunities for reuse.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Security_Requirement" type="capec:Structured_Text_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual relevant security requirement.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relevant_Design_Patterns" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field identifies specific relevant design patterns that are recommended as providing resistance or resilience to this attack, or which are not recommended as they are particularly susceptible to this type of attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Recommended_Design_Patterns">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Recommended_Design_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation>This field describes an individual design pattern that is recommended due to its likelihood of increasing the software's resistance or resiliency to this type of attack.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="Non-Recommended_Design_Patterns">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Non-Recommended_Design_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation>This field describes an individual design pattern that is not recommended due to its likelihood of decreasing the software's resistance or resiliency to this type of attack.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relevant_Security_Patterns" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field identifies specific security patterns that are recommended as providing resistance or resilience to this type of attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Security_Pattern" type="capec:Structured_Text_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual relevant security pattern.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Related_Security_Principles" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field identifies specific security principles relevant to this attack pattern. The security principles that this field references come from the set available on the Build Security In website.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Related_Security_Principle" type="capec:Structured_Text_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual security principle.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Related_Guidelines" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field identifies existing security guidelines that are relevant to identifying or mitigating this type of attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Related_Guideline" type="capec:Structured_Text_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes an individual related guideline.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Purposes" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the generalized purposes of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Purpose" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field describes the generalized purpose of the pattern in order to enable the capture of pattern composibility. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined purposes which may be currently incomplete and may grow as new relevant possibilities are identified.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Reconnaissance"/>
                <xs:enumeration value="Penetration"/>
                <xs:enumeration value="Exploitation"/>
                <xs:enumeration value="Obfuscation"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="CIA_Impact" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field characterizes the typical relative impact of this pattern on the confidentiality, integrity and availability of the targeted software.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Confidentiality_Impact" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field describes the typical impact of this pattern on the confidentiality characteristics of the targeted software and related data.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Low"/>
                <xs:enumeration value="Medium"/>
                <xs:enumeration value="High"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="Integrity_Impact" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field describes the typical impact of this pattern on the integrity characteristics of the targeted software and related data.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Low"/>
                <xs:enumeration value="Medium"/>
                <xs:enumeration value="High"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="Availability_Impact" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field describes the typical impact of this pattern on the availability characteristics of the targeted software and related data.</xs:documentation>
            </xs:annotation>
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Low"/>
                <xs:enumeration value="Medium"/>
                <xs:enumeration value="High"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Technical_Context" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field characterizes the technical context where this pattern is applicable.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Architectural_Paradigms" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Architectural_Paradigm" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation>This field outlines the architectural paradigms of target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined paradigms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Mainframe"/>
                      <xs:enumeration value="Client-Server"/>
                      <xs:enumeration value="n-Tier"/>
                      <xs:enumeration value="Web"/>
                      <xs:enumeration value="SOA"/>
                      <xs:enumeration value="Other"/>
                      <xs:enumeration value="All"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="Frameworks" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Framework" minOccurs="0" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation>This field outlines the frameworks used as part of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined frameworks which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="J2EE"/>
                      <xs:enumeration value=".NET"/>
                      <xs:enumeration value="Struts"/>
                      <xs:enumeration value="Spring"/>
                      <xs:enumeration value="Hibernate"/>
                      <xs:enumeration value="Other"/>
                      <xs:enumeration value="All"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="Platforms" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Platform" minOccurs="0" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation>This field outlines the platforms (OS) of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Windows"/>
                      <xs:enumeration value="UNIX-LINUX"/>
                      <xs:enumeration value="Solaris"/>
                      <xs:enumeration value="Other"/>
                      <xs:enumeration value="All"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="Languages" minOccurs="0">
            <xs:annotation>
              <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Language" minOccurs="0" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation>This field outlines the implementation languages of the target software where the pattern is possible and relevant. In order to assist in normalization and classification, this field involves a selection from an enumerated list of defined platforms which may be currently incomplete and may grow or change as new relevant possibilities are identified.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="AJAX"/>
                      <xs:enumeration value="ASP"/>
                      <xs:enumeration value="ASP.NET"/>
                      <xs:enumeration value="C"/>
                      <xs:enumeration value="C++"/>
                      <xs:enumeration value="C#"/>
                      <xs:enumeration value="Java"/>
                      <xs:enumeration value="JSP"/>
                      <xs:enumeration value="PHP"/>
                      <xs:enumeration value="PERL"/>
                      <xs:enumeration value="Ruby"/>
                      <xs:enumeration value="Visual Basic"/>
                      <xs:enumeration value="Other"/>
                      <xs:enumeration value="All"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Keywords" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field is intended to be a catch-all field for assisting in searching and subsecting a collection of patterns according to criteria not contained elsewehre in this schema.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Keyword" type="xs:string" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field contains an individual keyword to be used for tagging and searching.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="References" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field enumerates reference resources that were used to develop the definition of this attack pattern and those that could prove valuable to the reader looking for further information on this attack.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field should describe the reference clearly and unambiguously by name and with some method of address such that the reader can locate the resource for further reference.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element ref="capec:Other_Notes" minOccurs="0"/>
    <xs:element ref="capec:Maintenance_Notes" minOccurs="0"/>
    <xs:element ref="capec:Content_History" minOccurs="0"/>
  </xs:sequence>
  <xs:attribute name="ID" type="xs:integer" use="optional" default="0"/>
  <xs:attribute name="Name" type="xs:string" use="required"/>
  <xs:attribute name="Pattern_Completeness">
    <xs:simpleType>
      <xs:restriction base="xs:string">
        <xs:enumeration value="Complete"/>
        <xs:enumeration value="Stub"/>
        <xs:enumeration value="Hook"/>
      </xs:restriction>
    </xs:simpleType>
  </xs:attribute>
  <xs:attribute name="Pattern_Abstraction" use="optional">
    <xs:simpleType>
      <xs:restriction base="xs:string">
        <xs:enumeration value="Meta"/>
        <xs:enumeration value="Standard"/>
        <xs:enumeration value="Detailed"/>
      </xs:restriction>
    </xs:simpleType>
  </xs:attribute>
  <xs:attribute name="Status" type="capec:Status_Type" use="required">
    <xs:annotation>
      <xs:documentation>The Status attribute defines the status level for this view.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type capec:Structured_Text_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images ap_schema_v2_5_xsd.tmp#Structured_Text_Group ap_schema_v2_5_xsd.tmp#Block
Used by
Elements capec:Alternate_Terms/capec:Alternate_Term/capec:Alternate_Term_Description, capec:Attack_PatternType/capec:Activation_Zone, capec:Attack_PatternType/capec:Attack_Prerequisites/capec:Attack_Prerequisite, capec:Attack_PatternType/capec:Attacker_Skills_or_Knowledge_Required/capec:Attacker_Skill_or_Knowledge_Required/capec:Skill_or_Knowledge_Type, capec:Attack_PatternType/capec:Description/capec:Summary, capec:Attack_PatternType/capec:Examples-Instances/capec:Example-Instance/capec:Example-Instance_Description, capec:Attack_PatternType/capec:Examples-Instances/capec:Example-Instance/capec:Example-Instance_Related_Vulnerabilities/capec:Example-Instance_Related_Vulnerability, capec:Attack_PatternType/capec:Indicators-Warnings_of_Attack/capec:Indicator-Warning_of_Attack/capec:Description, capec:Attack_PatternType/capec:Injection_Vector, capec:Attack_PatternType/capec:Obfuscation_Techniques/capec:Obfuscation_Technique/capec:Description, capec:Attack_PatternType/capec:Payload, capec:Attack_PatternType/capec:Payload_Activation_Impact/capec:Description, capec:Attack_PatternType/capec:Probing_Techniques/capec:Probing_Technique/capec:Description, capec:Attack_PatternType/capec:Related_Guidelines/capec:Related_Guideline, capec:Attack_PatternType/capec:Related_Security_Principles/capec:Related_Security_Principle, capec:Attack_PatternType/capec:Related_Vulnerabilities/capec:Related_Vulnerability/capec:Vulnerability_Description, capec:Attack_PatternType/capec:Relevant_Design_Patterns/capec:Non-Recommended_Design_Patterns/capec:Non-Recommended_Design_Pattern, capec:Attack_PatternType/capec:Relevant_Design_Patterns/capec:Recommended_Design_Patterns/capec:Recommended_Design_Pattern, capec:Attack_PatternType/capec:Relevant_Security_Patterns/capec:Relevant_Security_Pattern, capec:Attack_PatternType/capec:Relevant_Security_Requirements/capec:Relevant_Security_Requirement, capec:Attack_PatternType/capec:Resources_Required, capec:Attack_PatternType/capec:Solutions_and_Mitigations/capec:Solution_or_Mitigation, capec:Attack_PatternType/capec:Typical_Likelihood_of_Exploit/capec:Explanation, capec:Attack_Step_Technique/capec:Attack_Step_Technique_Description, capec:Category/capec:Attack_Prerequisites/capec:Attack_Prerequisite, capec:Category/capec:Attacker_Skills_or_Knowledge_Required/capec:Attacker_Skill_or_Knowledge_Required/capec:Skill_or_Knowledge_Type, capec:Category/capec:Background_Details/capec:Background_Detail, capec:Category/capec:Description/capec:Extended_Description, capec:Category/capec:Resources_Required, capec:Common_ConsequenceType/capec:Consequence_Note, capec:Compound_Element/capec:Background_Details/capec:Background_Detail, capec:Compound_Element/capec:Description/capec:Extended_Description, capec:Custom_Attack_StepType/capec:Attack_Step_Description, capec:Custom_Attack_StepType/capec:Indicators/capec:Indicator/capec:Indicator_Description, capec:Maintenance_Notes/capec:Maintenance_Note, capec:ObservablesType/capec:Observable/capec:Obfuscation_Techniques/capec:Obfuscation_Technique/capec:Description, capec:ObservablesType/capec:Observable/capec:Signature/capec:Event/capec:Description, capec:ObservablesType/capec:Observable/capec:Signature/capec:Stateful_Measure/capec:Description, capec:Other_Notes/capec:Note, capec:Reference_Type/capec:Reference_Description, capec:RelationshipType/capec:Relationship_Description, capec:Relationship_Notes/capec:Relationship_Note, capec:Research_Gaps/capec:Research_Gap, capec:View_Attributes/capec:View_Audience/capec:Audience/capec:Stakeholder_Description, capec:View_Attributes/capec:View_Objective
Children capec:Block, capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:complexType name="Structured_Text_Type">
  <xs:sequence>
    <xs:choice maxOccurs="unbounded">
      <xs:group ref="capec:Structured_Text_Group"/>
      <xs:element ref="capec:Block">
        <xs:annotation>
          <xs:documentation>Block is a Structured_Text element consisting of one of Text_Title, Text, Code_Example_Language, or Code followed by another Block element. Structured_Text elements help define whitespace and text segments.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:complexType>
Simple Type capec:Language_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration C
enumeration C++
enumeration C#
enumeration Java
enumeration JSP
enumeration Javascript
enumeration ASP.NET
enumeration SQL
enumeration Python
enumeration Perl
enumeration PHP
enumeration SOAP
enumeration Ruby
enumeration Shell
enumeration PseudoCode
enumeration .NET
enumeration Assembly
enumeration XML
enumeration HTML
Used by
Source
<xs:simpleType name="Language_Type">
  <xs:restriction base="xs:string">
    <xs:enumeration value="C"/>
    <xs:enumeration value="C++"/>
    <xs:enumeration value="C#"/>
    <xs:enumeration value="Java"/>
    <xs:enumeration value="JSP"/>
    <xs:enumeration value="Javascript"/>
    <xs:enumeration value="ASP.NET"/>
    <xs:enumeration value="SQL"/>
    <xs:enumeration value="Python"/>
    <xs:enumeration value="Perl"/>
    <xs:enumeration value="PHP"/>
    <xs:enumeration value="SOAP"/>
    <xs:enumeration value="Ruby"/>
    <xs:enumeration value="Shell"/>
    <xs:enumeration value="PseudoCode"/>
    <xs:enumeration value=".NET"/>
    <xs:enumeration value="Assembly"/>
    <xs:enumeration value="XML"/>
    <xs:enumeration value="HTML"/>
  </xs:restriction>
</xs:simpleType>
Complex Type capec:Custom_Attack_StepType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Title ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Description ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Attack_Step_Techniques ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Indicators ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Outcomes ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Security_Controls ap_schema_v2_5_xsd.tmp#Custom_Attack_StepType_Observables
Used by
Children capec:Attack_Step_Description, capec:Attack_Step_Techniques, capec:Attack_Step_Title, capec:Indicators, capec:Observables, capec:Outcomes, capec:Security_Controls
Source
<xs:complexType name="Custom_Attack_StepType">
  <xs:sequence>
    <xs:element name="Attack_Step_Title" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field contains a short descriptive title for the attack step. It should be kept as short as possible but also clearly convey the nature of the attack step being described.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Attack_Step_Description" type="capec:Structured_Text_Type">
      <xs:annotation>
        <xs:documentation>This field contains a brief description of the attack step.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Attack_Step_Techniques" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element ref="capec:Attack_Step_Technique" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field captures various techniques that the attacker can use to achieve the attack step's goal. For example, an attacker may use tools such as WebScarab and Tamper Data in the experimentation phase of a SQL Injection attack pattern. The techniques include references to environments, because not all techniques work in all environments</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Indicators" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Indicator" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>These are indicators that the application may or may not be susceptible to the given attack step (not necessarily the pattern as a whole).</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:all>
                <xs:element name="Indicator_Description" type="capec:Structured_Text_Type">
                  <xs:annotation>
                    <xs:documentation>This field contains a brief description of the indicator.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
                <xs:element name="Environments" type="xs:IDREFS">
                  <xs:annotation>
                    <xs:documentation>References the defined environments where this indicator of susceptibility is applicable.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
              </xs:all>
              <xs:attribute name="ID" type="xs:integer" use="required">
                <xs:annotation>
                  <xs:documentation>This field contains a unique integer identifier for the indicator.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="type" use="required">
                <xs:annotation>
                  <xs:documentation>Each indicator has a mandatory type attribute that can be one of the values "Positive," "Negative," or "Inconclusive." For example, a positive indicator of susceptibility to parameter tampering is the existence of parameters in the URL. Although it does not guarantee susceptibility, it indicates a cause for further examination. A negative indicator for the technique of privilege escalation is a lack of credentials and user identifiers in an application. Again, this is not a conclusive measure of resistance to attack, but an indicator that the attack step technique is unlikely to bear significant fruit. An inconclusive indicator of susceptibility to dynamic code injection is a page whose URL ends in .jsp, .asp, or .do but which has no visible explicit parameters. Such URLs typically indicate dynamic processing, but since no visible parameters are passed, it is inconclusive whether dynamic code could be injected into the application.</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:token">
                    <xs:enumeration value="Positive"/>
                    <xs:enumeration value="Negative"/>
                    <xs:enumeration value="Inconclusive"/>
                  </xs:restriction>
                </xs:simpleType>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Outcomes" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Outcome" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field captures possible outcomes for this attack step.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Outcome_Description" type="xs:string"/>
                <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
                <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
              </xs:sequence>
              <xs:attribute name="ID" type="xs:integer" use="required">
                <xs:annotation>
                  <xs:documentation>This field contains a unique integer identifier for the outcome.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="type" use="required">
                <xs:annotation>
                  <xs:documentation>An outcome has a mandatory type attribute that can be one of the values "success," "failure," or "inconclusive." It indicates what results of executing the attack step techniques should be considered successes, which should be considered failures, and which ones are inconclusive. Outcomes' successes are determined relative to the attacker's point of view. It is a success if the attack step got the attacker closer to his goal of attacking the application. It is a failure if the attacker got no closer to his goal.</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:token">
                    <xs:enumeration value="Success"/>
                    <xs:enumeration value="Failure"/>
                    <xs:enumeration value="Inconclusive"/>
                  </xs:restriction>
                </xs:simpleType>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Security_Controls" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Security_Control" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This field captures security controls for this attack step that describe ways in which the attack step can be detected, corrected, or prevented. These are presented from a defender's point of view, where the defender may be a developer, tester, operations administrator, or other resource resisting the attacker.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Security_Control_Description" type="xs:string"/>
                <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType" minOccurs="0"/>
                <xs:element name="Observable_Evidence" minOccurs="0">
                  <xs:complexType>
                    <xs:choice>
                      <xs:element name="IfPresent_Observables" type="cybox:ObservablesType"/>
                      <xs:element name="IfNotPresent_Observables" type="cybox:ObservablesType"/>
                    </xs:choice>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="ID" type="xs:integer" use="required">
                <xs:annotation>
                  <xs:documentation>This field contains a unique integer identifier for the security control.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="type" use="required">
                <xs:annotation>
                  <xs:documentation>Each security control has a mandatory type attribute that can be one of the values "Detective," "Corrective," or "Preventative." Detective controls detect an attacker's activities in the attack step, whether the activities are successful or not. Corrective controls attempt to mitigate an attacker's success by responding to a successful outcome. They are not related to or normalized against outcomes. Preventative controls are those that make the attack step unlikely or impossible to succeed.</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:token">
                    <xs:enumeration value="Detective"/>
                    <xs:enumeration value="Corrective"/>
                    <xs:enumeration value="Preventative"/>
                  </xs:restriction>
                </xs:simpleType>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Observables" type="cybox:ObservablesType" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>
Complex Type capec:Relevant_Attack_Surface_ElementsType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Functional_Services ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocols ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Protocol_Headers ap_schema_v2_5_xsd.tmp#Relevant_Attack_Surface_ElementsType_Relevant_Command_Structures
Used by
Children capec:Relevant_Command_Structures, capec:Relevant_Functional_Services, capec:Relevant_Protocol_Headers, capec:Relevant_Protocols
Source
<xs:complexType name="Relevant_Attack_Surface_ElementsType">
  <xs:sequence>
    <xs:element name="Relevant_Functional_Services" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Functional_Service_ID" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relevant_Protocols" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Protocol_ID" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relevant_Protocol_Headers" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Protocol_Header_ID" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relevant_Command_Structures" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Command_Structure_ID" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type capec:Target_Attack_SurfaceType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Common_Attack_Surface_Description ap_schema_v2_5_xsd.tmp#Target_Attack_SurfaceType_Target_Attack_Surface_Description
Used by
Children capec:Common_Attack_Surface_Description, capec:Target_Attack_Surface_Description
Source
<xs:complexType name="Target_Attack_SurfaceType">
  <xs:choice>
    <xs:element name="Common_Attack_Surface_Description">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relevant_Attack_Surface_Elements" type="capec:Relevant_Attack_Surface_ElementsType"/>
          <xs:element name="Pattern_Specific_Overrides" type="capec:Target_Attack_Surface_DescriptionType" minOccurs="0"/>
        </xs:sequence>
        <xs:attribute name="Common_Attack_Surface_ID"/>
      </xs:complexType>
    </xs:element>
    <xs:element name="Target_Attack_Surface_Description" type="capec:Target_Attack_Surface_DescriptionType"/>
  </xs:choice>
</xs:complexType>
Complex Type capec:Target_Attack_Surface_DescriptionType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Targeted_OSI_Layers ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Localities ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Attack_Surface_Types ap_schema_v2_5_xsd.tmp#Target_Attack_Surface_DescriptionType_Target_Functional_Services
Used by
Children capec:Target_Attack_Surface_Localities, capec:Target_Attack_Surface_Types, capec:Target_Functional_Services, capec:Targeted_OSI_Layers
Source
<xs:complexType name="Target_Attack_Surface_DescriptionType">
  <xs:sequence>
    <xs:element name="Targeted_OSI_Layers">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Targeted_OSI_Layer" maxOccurs="unbounded">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Physical Layer"/>
                <xs:enumeration value="Data Link Layer"/>
                <xs:enumeration value="Network Layer"/>
                <xs:enumeration value="Transport Layer"/>
                <xs:enumeration value="Session Layer"/>
                <xs:enumeration value="Presentation Layer"/>
                <xs:enumeration value="Application Layer"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Target_Attack_Surface_Localities">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Target_Attack_Surface_Locality" maxOccurs="unbounded">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Client-side"/>
                <xs:enumeration value="Server-side"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Target_Attack_Surface_Types">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Target_Attack_Surface_Type" maxOccurs="unbounded">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Network"/>
                <xs:enumeration value="Host"/>
                <xs:enumeration value="Service"/>
                <xs:enumeration value="Non-Web Application"/>
                <xs:enumeration value="Web Application"/>
                <xs:enumeration value="Firewall"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Target_Functional_Services" minOccurs="0">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Target_Functional_Service" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Protocol" minOccurs="0" maxOccurs="unbounded">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Protocol_Structure" minOccurs="0">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:element name="Protocol_Header" maxOccurs="unbounded">
                              <xs:complexType>
                                <xs:sequence>
                                  <xs:element name="Protocol_RFC" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                  <xs:element name="Protocol_Field_Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                  <xs:element name="Protocol_Field_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                  <xs:element name="Protocol_Flag_Description" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                  <xs:element name="Protocol_Flag_Value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                  <xs:element name="Protocol_Operation_Code" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                  <xs:element name="Protocol_Data" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                                </xs:sequence>
                                <xs:attribute name="ID" type="xs:integer" use="required"/>
                                <xs:attribute name="Name" type="xs:string"/>
                              </xs:complexType>
                            </xs:element>
                          </xs:sequence>
                        </xs:complexType>
                      </xs:element>
                      <xs:element name="Command_Structures" minOccurs="0">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:element name="Command_Structure" maxOccurs="unbounded">
                              <xs:complexType>
                                <xs:sequence>
                                  <xs:element name="Command_Description" type="xs:string" minOccurs="0"/>
                                  <xs:element name="Command_Type" type="xs:string" minOccurs="0"/>
                                  <xs:element name="Command_Group_Label" type="xs:string" minOccurs="0"/>
                                </xs:sequence>
                                <xs:attribute name="ID" type="xs:integer" use="required"/>
                                <xs:attribute name="Name" type="xs:string" use="required"/>
                              </xs:complexType>
                            </xs:element>
                          </xs:sequence>
                        </xs:complexType>
                      </xs:element>
                      <xs:element name="Related_Protocols" minOccurs="0">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:element name="Related_Protocol" maxOccurs="unbounded">
                              <xs:complexType>
                                <xs:sequence>
                                  <xs:element name="Relationship_Type" maxOccurs="unbounded">
                                    <xs:simpleType>
                                      <xs:restriction base="xs:string">
                                        <xs:enumeration value="Is an abstraction of"/>
                                        <xs:enumeration value="Is a refinement of"/>
                                        <xs:enumeration value="Is an alternative to"/>
                                        <xs:enumeration value="Uses Protocol"/>
                                        <xs:enumeration value="Is a service of"/>
                                        <xs:enumeration value="Is a command of"/>
                                      </xs:restriction>
                                    </xs:simpleType>
                                  </xs:element>
                                </xs:sequence>
                                <xs:attribute name="Name"/>
                                <xs:attribute name="RFC"/>
                              </xs:complexType>
                            </xs:element>
                          </xs:sequence>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                    <xs:attribute name="ID" type="xs:integer" use="required"/>
                    <xs:attribute name="Name" type="xs:string" use="required"/>
                    <xs:attribute name="RFC" type="xs:string"/>
                    <xs:attribute name="Encryption" type="xs:boolean"/>
                    <xs:attribute name="Encryption_Type" type="xs:string"/>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="ID" type="xs:integer" use="required"/>
              <xs:attribute name="Name" type="xs:string" use="required"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type capec:Reference_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_ID ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Description ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Author ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Title ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Section ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Edition ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publication ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Publisher ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Date ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_PubDate ap_schema_v2_5_xsd.tmp#Reference_Type_Reference_Link
Used by
Children capec:Reference_Author, capec:Reference_Date, capec:Reference_Description, capec:Reference_Edition, capec:Reference_Link, capec:Reference_PubDate, capec:Reference_Publication, capec:Reference_Publisher, capec:Reference_Section, capec:Reference_Title
Attributes
QName Type Fixed Default Use Annotation
Reference_ID optional
The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.
Source
<xs:complexType name="Reference_Type">
  <xs:sequence>
    <xs:element name="Reference_Description" type="capec:Structured_Text_Type" minOccurs="0"/>
    <xs:element name="Reference_Author" type="xs:string" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>This element identifies an individual author of the material being referenced. It is not required, but may be repeated sequentially in order to identify multiple authors for a single piece of material.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Title" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element identifies the title of the material beingreferenced. It is not required if the material does not have a title.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Section" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element is intended to provide a means of identifying the exact location of the material inside of the publication source, such as the relevant pages of a research paper, the appropriate chapters from a book, etc. This is useful for both book references and internet references.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Edition" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element identifies the edition of the material being referenced in the event that multiple editions of the material exist. This will usually only be useful for book references.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Publication" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element identifies the publication source of the reference material, if one exists.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Publisher" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element identifies the publisher of the reference material, if one exists.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Date" type="xs:date" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element identifies the date when the reference was included in the entry. This provides the reader with a time line for when the material in the reference, usually the link, was valid. The date should be of the format YYYY-MM-DD.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_PubDate" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This field describes the date when the reference was published YYYY.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Reference_Link" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element should hold the URL for the material being referenced, if one exists. This should always be used for web references, and may optionally be used for book and other publication references.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="Reference_ID">
    <xs:annotation>
      <xs:documentation>The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type capec:Common_ConsequenceType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Common_Consequence_ID ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Scope ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Technical_Impact ap_schema_v2_5_xsd.tmp#Common_ConsequenceType_Consequence_Note
Used by
Children capec:Consequence_Note, capec:Consequence_Scope, capec:Consequence_Technical_Impact
Attributes
QName Type Fixed Default Use Annotation
Common_Consequence_ID xs:string optional
The Common_Consequence_ID stores the value for the related
Common_Consequence entry identifier as a string. Only one
Common_Consequence_ID element can exist for each Common_Consequence element
(ex: CC-1). However, Common_Consequences across CAPEC with the same ID should
only vary in small details.
Source
<xs:complexType name="Common_ConsequenceType">
  <xs:sequence>
    <xs:element name="Consequence_Scope" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>This subelement identifies an individual consequence that may result from this attack pattern.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Confidentiality"/>
          <xs:enumeration value="Integrity"/>
          <xs:enumeration value="Availability"/>
          <xs:enumeration value="Access_Control"/>
          <xs:enumeration value="Non-Repudiation"/>
          <xs:enumeration value="Accountability"/>
          <xs:enumeration value="Authentication"/>
          <xs:enumeration value="Authorization"/>
          <xs:enumeration value="Other"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="Consequence_Technical_Impact" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>This subelement describes the technical impacts that can result from successful execution of this attack pattern.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:whiteSpace value="collapse"/>
          <xs:enumeration value="Modify memory"/>
          <xs:enumeration value="Read memory"/>
          <xs:enumeration value="Modify files or directories"/>
          <xs:enumeration value="Read files or directories"/>
          <xs:enumeration value="Modify application data"/>
          <xs:enumeration value="Read application data"/>
          <xs:enumeration value="DoS: crash / exit / restart"/>
          <xs:enumeration value="DoS: amplification"/>
          <xs:enumeration value="DoS: instability"/>
          <xs:enumeration value="DoS: resource consumption (CPU)"/>
          <xs:enumeration value="DoS: resource consumption (memory)"/>
          <xs:enumeration value="DoS: resource consumption (other)"/>
          <xs:enumeration value="Execute unauthorized code or commands"/>
          <xs:enumeration value="Gain privileges / assume identity"/>
          <xs:enumeration value="Bypass protection mechanism"/>
          <xs:enumeration value="Hide activities"/>
          <xs:enumeration value="Alter execution logic"/>
          <xs:enumeration value="Other"/>
          <xs:enumeration value=""Varies by context""/>
          <xs:enumeration value="Quality degradation"/>
          <xs:enumeration value="Unexpected State"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="Consequence_Note" type="capec:Structured_Text_Type" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This subelement provides additional commentary about this consequence.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="Common_Consequence_ID" type="xs:string">
    <xs:annotation>
      <xs:documentation>The Common_Consequence_ID stores the value for the related Common_Consequence entry identifier as a string. Only one Common_Consequence_ID element can exist for each Common_Consequence element (ex: CC-1). However, Common_Consequences across CAPEC with the same ID should only vary in small details.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
Complex Type capec:RelationshipType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Views ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Chains ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Target_Form ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Nature ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Target_ID ap_schema_v2_5_xsd.tmp#RelationshipType_Relationship_Description
Used by
Children capec:Relationship_Chains, capec:Relationship_Description, capec:Relationship_Nature, capec:Relationship_Target_Form, capec:Relationship_Target_ID, capec:Relationship_Views
Source
<xs:complexType name="RelationshipType">
  <xs:sequence>
    <xs:element name="Relationship_Views">
      <xs:annotation>
        <xs:documentation>This element contains a list of the individual Views to which this relationship pertains.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relationship_View_ID" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Specifies the unique ID of the individual view element to which this relationship pertains. This ID must correspond to a View.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:simpleContent>
                <xs:extension base="xs:integer">
                  <xs:attribute name="Ordinal">
                    <xs:annotation>
                      <xs:documentation>The ordinal attribute is used to determine if this relationship is the primary ChildOf relationship for this entry for a given Relationship_View_ID element.. This attribute can only have the value "Primary" and should only be included for the primary parent/child relationship.</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Primary"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:attribute>
                </xs:extension>
              </xs:simpleContent>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relationship_Chains" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element contains a list of the individual Chains this relationship pertains to.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Relationship_Chain_ID" type="xs:integer" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>This element specifies the unique ID of an individual chain element this relationship pertains to.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Relationship_Target_Form">
      <xs:annotation>
        <xs:documentation>The Relationship_Target_Form element defines the form of the target of this relationship, such as Category, Attack Pattern, View or Compound_Element.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Category"/>
          <xs:enumeration value="Attack Pattern"/>
          <xs:enumeration value="View"/>
          <xs:enumeration value="Compound_Element"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="Relationship_Nature" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The Relationship_Nature element defines the nature of the relationship between this element and the target element, such as ChildOf, HasMember or Requires to name a few.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="HasMember">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes the specified entry as a top level member of this View. This value for Relationship_Nature can only be used in Views. The complementary relationship is MemberOf.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="MemberOf">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes membership of this entry in the top level of the View specified in Relationship_Target_ID. The complementary relationship is HasMember.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="ChildOf">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes a specified entry as a parent of this entry. In general, this means that the parent will be a higher level representation of this entry from the perspective of the View provided in Relationship_View_ID. The complementary relationship is ParentOf.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="ParentOf">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes a specified entry as a child of this entry. In general, this means that the child will be a lower level representation of this entry from the perspective of the View provided in Relationship_View_ID. The complementary relationship is ChildOf.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="PeerOf">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes a specified entry as having some similarity with this entry which does not fit any of the other Relationship_Nature values. In this case, a Relationship_Note should also be provided explaining the connection. The complementary relationship is itself (PeerOf).</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="Requires">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes a Compound_Element of Compound_Element_Structure="Composite". All entries that a Composite Requires must exist simultaneously in order for the Compound_Element to exist. The complementary relationship is RequiredBy.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="RequiredBy">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes an entry that is required in order for the Compound_Element specified in Relationship_Target_ID to exist. The complementary relationship is Requires.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="StartsWith">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes the starting point in this chain as the entry specified by Relationship_Target_ID. This Relationship_Nature can only be used for Compound_Elements with Compound_Element_Structure="Chain". For named chains, the complementary relationship is StartsChain.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="StartsChain">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes this entry as the starting point in the chain specified in Relationship_Target_ID. For named chains, the complementary relationship is StartsWith.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="CanPrecede">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes a chain where this entry can precede the entry specified by Relationship_Target_ID in a sequential fashion. It is important to note that not all CanPrecede relationships are captured in a Compound_Element chain, only the most common for now. The complementary relationship is CanFollow.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="CanFollow">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes a chain where this entry can follow the entry specified by Relationship_Target_ID in a sequential fashion. It is important to note that not all CanFollow relationships are captured in a Compound_Element chain, only the most common for now. The complementary relationship is CanPrecede.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="CanAlsoBe">
            <xs:annotation>
              <xs:documentation>This Relationship_Nature denotes an entry that, in the proper environment and context, can also be perceived as the entry specified by Relationship_Target_ID. This relationship is not necessarily reciprocal.</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="Relationship_Target_ID" type="xs:integer">
      <xs:annotation>
        <xs:documentation>The Relationship_Target_ID specifies the unique ID of the target element of the relationship.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Relationship_Description" type="capec:Structured_Text_Type" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>
Simple Type capec:Status_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Deprecated
enumeration Incomplete
enumeration Draft
enumeration Usable
enumeration Stable
Used by
Source
<xs:simpleType name="Status_Type">
  <xs:restriction base="xs:string">
    <xs:enumeration value="Deprecated"/>
    <xs:enumeration value="Incomplete"/>
    <xs:enumeration value="Draft"/>
    <xs:enumeration value="Usable"/>
    <xs:enumeration value="Stable"/>
  </xs:restriction>
</xs:simpleType>
Complex Type capec:Reference_List_Type
Namespace http://capec.mitre.org/capec-2
Annotations
The References_List_Type contains one or more Reference elements, each
of which provide further reading and insight into the item. This should be filled
out as appropriate.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Reference_List_Type_Reference
Used by
Children capec:Reference
Source
<xs:complexType name="Reference_List_Type">
  <xs:annotation>
    <xs:documentation>The References_List_Type contains one or more Reference elements, each of which provide further reading and insight into the item. This should be filled out as appropriate.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Reference" type="capec:Reference_Type" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Each Reference subelement should provide a single source from which more information and deeper insight can be obtained, such as a research paper or an excerpt from a publication. Multiple Reference subelements can exist. The sole attribute of this element is the id. The id is optional and translates to a preceding footnote below the context notes if the author of the entry wants to cite a reference. Not all subelements need to be completed, since some are designed for web references and others are designed for book references. The fields Reference_Author and Reference_Title should be filled out for all references if possible. Reference_Section and Reference_Date can be included for either book references or online references. Reference_Edition, Reference_Publication, Reference_Publisher, and Reference_PubDate are intended for book references, however they can be included where appropriate for other types of references. Reference_Link is intended for web references, however it can be included for book references as well if applicable.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Complex Type capec:ObservablesType
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#http___capec.mitre.org_capec-2_ObservablesType_Observable
Used by
Children capec:Observable
Source
<xs:complexType name="ObservablesType">
  <xs:sequence>
    <xs:element name="Observable" maxOccurs="unbounded">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Signature">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Location-Sensor" minOccurs="0"/>
                <xs:element name="Stateful_Measure">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Description" type="capec:Structured_Text_Type"/>
                      <xs:element name="Value_Type">
                        <xs:complexType>
                          <xs:choice>
                            <xs:element name="Objective_Value" type="xs:string"/>
                            <xs:element name="Trend">
                              <xs:simpleType>
                                <xs:restriction base="xs:string">
                                  <xs:enumeration value="Increasing"/>
                                  <xs:enumeration value="Decreasing"/>
                                </xs:restriction>
                              </xs:simpleType>
                            </xs:element>
                            <xs:element name="Frequency">
                              <xs:complexType>
                                <xs:attribute name="Rate" type="xs:float" use="required"/>
                                <xs:attribute name="Units" type="xs:string" use="required"/>
                                <xs:attribute name="Scale" type="xs:string" use="required"/>
                              </xs:complexType>
                            </xs:element>
                          </xs:choice>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                    <xs:attribute name="Name"/>
                  </xs:complexType>
                </xs:element>
                <xs:element name="Event">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Description" type="capec:Structured_Text_Type"/>
                      <xs:element name="Action">
                        <xs:complexType>
                          <xs:sequence>
                            <xs:element name="Object" maxOccurs="unbounded">
                              <xs:complexType>
                                <xs:sequence>
                                  <xs:element name="Value" maxOccurs="unbounded">
                                    <xs:complexType>
                                      <xs:sequence>
                                        <xs:element name="Objective_Value" type="xs:string" minOccurs="0"/>
                                        <xs:element name="Change" type="xs:boolean" minOccurs="0"/>
                                        <xs:element name="Delta" minOccurs="0">
                                          <xs:complexType>
                                            <xs:choice>
                                              <xs:element name="Trend">
                                                <xs:simpleType>
                                                  <xs:restriction base="xs:string">
                                                    <xs:enumeration value="Increasing"/>
                                                    <xs:enumeration value="Decreasing"/>
                                                  </xs:restriction>
                                                </xs:simpleType>
                                              </xs:element>
                                              <xs:element name="Frequency">
                                                <xs:complexType>
                                                  <xs:attribute name="Rate" type="xs:float" use="required"/>
                                                  <xs:attribute name="Units" type="xs:string" use="required"/>
                                                  <xs:attribute name="Scale" type="xs:string" use="required"/>
                                                </xs:complexType>
                                              </xs:element>
                                            </xs:choice>
                                          </xs:complexType>
                                        </xs:element>
                                      </xs:sequence>
                                    </xs:complexType>
                                  </xs:element>
                                </xs:sequence>
                              </xs:complexType>
                            </xs:element>
                          </xs:sequence>
                        </xs:complexType>
                      </xs:element>
                    </xs:sequence>
                    <xs:attribute name="Event_Type" type="xs:string"/>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="Noisiness" minOccurs="0">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="High"/>
                <xs:enumeration value="Medium"/>
                <xs:enumeration value="Low"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="Ease_of_Obfuscation" minOccurs="0">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="High"/>
                <xs:enumeration value="Medium"/>
                <xs:enumeration value="Low"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="Obfuscation_Techniques" minOccurs="0">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Obfuscation_Technique" maxOccurs="unbounded">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Description" type="capec:Structured_Text_Type"/>
                      <xs:element name="Observables" type="capec:ObservablesType"/>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
Simple Type capec:Frequency_Type
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration Often
enumeration Sometimes
enumeration Rarely
Source
<xs:simpleType name="Frequency_Type">
  <xs:restriction base="xs:string">
    <xs:enumeration value="Often"/>
    <xs:enumeration value="Sometimes"/>
    <xs:enumeration value="Rarely"/>
  </xs:restriction>
</xs:simpleType>
Attribute capec:Block / @Block_Nature
Namespace No namespace
Annotations
This attribute identifies the nature of the content containedwithin the Block.
Type restriction of xs:string
Facets
enumeration Good_Code
enumeration Bad_Code
enumeration Mitigation_Code
enumeration Attack
enumeration Result
enumeration List
Used by
Element capec:Block
Source
<xs:attribute name="Block_Nature">
  <xs:annotation>
    <xs:documentation>This attribute identifies the nature of the content containedwithin the Block.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Good_Code"/>
      <xs:enumeration value="Bad_Code"/>
      <xs:enumeration value="Mitigation_Code"/>
      <xs:enumeration value="Attack"/>
      <xs:enumeration value="Result"/>
      <xs:enumeration value="List"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Attack_Step_Technique / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator / @ID
Namespace No namespace
Annotations
This field contains a unique integer identifier for the indicator.
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>This field contains a unique integer identifier for the indicator.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Custom_Attack_StepType / capec:Indicators / capec:Indicator / @type
Namespace No namespace
Annotations
Each indicator has a mandatory type attribute that can be one of the values "Positive," "Negative," or "Inconclusive." For example, a positive indicator of susceptibility to parameter tampering is the existence of parameters in the URL. Although it does not guarantee susceptibility, it indicates a cause for further examination. A negative indicator for the technique of privilege escalation is a lack of credentials and user identifiers in an application. Again, this is not a conclusive measure of resistance to attack, but an indicator that the attack step technique is unlikely to bear significant fruit. An inconclusive indicator of susceptibility to dynamic code injection is a page whose URL ends in .jsp, .asp, or .do but which has no visible explicit parameters. Such URLs typically indicate dynamic processing, but since no visible parameters are passed, it is inconclusive whether dynamic code could be injected into the application.
Type restriction of xs:token
Facets
enumeration Positive
enumeration Negative
enumeration Inconclusive
Used by
Source
<xs:attribute name="type" use="required">
  <xs:annotation>
    <xs:documentation>Each indicator has a mandatory type attribute that can be one of the values "Positive," "Negative," or "Inconclusive." For example, a positive indicator of susceptibility to parameter tampering is the existence of parameters in the URL. Although it does not guarantee susceptibility, it indicates a cause for further examination. A negative indicator for the technique of privilege escalation is a lack of credentials and user identifiers in an application. Again, this is not a conclusive measure of resistance to attack, but an indicator that the attack step technique is unlikely to bear significant fruit. An inconclusive indicator of susceptibility to dynamic code injection is a page whose URL ends in .jsp, .asp, or .do but which has no visible explicit parameters. Such URLs typically indicate dynamic processing, but since no visible parameters are passed, it is inconclusive whether dynamic code could be injected into the application.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:token">
      <xs:enumeration value="Positive"/>
      <xs:enumeration value="Negative"/>
      <xs:enumeration value="Inconclusive"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Custom_Attack_StepType / capec:Outcomes / capec:Outcome / @ID
Namespace No namespace
Annotations
This field contains a unique integer identifier for the outcome.
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>This field contains a unique integer identifier for the outcome.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Custom_Attack_StepType / capec:Outcomes / capec:Outcome / @type
Namespace No namespace
Annotations
An outcome has a mandatory type attribute that can be one of the values "success," "failure," or "inconclusive." It indicates what results of executing the attack step techniques should be considered successes, which should be considered failures, and which ones are inconclusive. Outcomes' successes are determined relative to the attacker's point of view. It is a success if the attack step got the attacker closer to his goal of attacking the application. It is a failure if the attacker got no closer to his goal.
Type restriction of xs:token
Facets
enumeration Success
enumeration Failure
enumeration Inconclusive
Used by
Source
<xs:attribute name="type" use="required">
  <xs:annotation>
    <xs:documentation>An outcome has a mandatory type attribute that can be one of the values "success," "failure," or "inconclusive." It indicates what results of executing the attack step techniques should be considered successes, which should be considered failures, and which ones are inconclusive. Outcomes' successes are determined relative to the attacker's point of view. It is a success if the attack step got the attacker closer to his goal of attacking the application. It is a failure if the attacker got no closer to his goal.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:token">
      <xs:enumeration value="Success"/>
      <xs:enumeration value="Failure"/>
      <xs:enumeration value="Inconclusive"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / @ID
Namespace No namespace
Annotations
This field contains a unique integer identifier for the security control.
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>This field contains a unique integer identifier for the security control.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Custom_Attack_StepType / capec:Security_Controls / capec:Security_Control / @type
Namespace No namespace
Annotations
Each security control has a mandatory type attribute that can be one of the values "Detective," "Corrective," or "Preventative." Detective controls detect an attacker's activities in the attack step, whether the activities are successful or not. Corrective controls attempt to mitigate an attacker's success by responding to a successful outcome. They are not related to or normalized against outcomes. Preventative controls are those that make the attack step unlikely or impossible to succeed.
Type restriction of xs:token
Facets
enumeration Detective
enumeration Corrective
enumeration Preventative
Used by
Source
<xs:attribute name="type" use="required">
  <xs:annotation>
    <xs:documentation>Each security control has a mandatory type attribute that can be one of the values "Detective," "Corrective," or "Preventative." Detective controls detect an attacker's activities in the attack step, whether the activities are successful or not. Corrective controls attempt to mitigate an attacker's success by responding to a successful outcome. They are not related to or normalized against outcomes. Preventative controls are those that make the attack step unlikely or impossible to succeed.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:token">
      <xs:enumeration value="Detective"/>
      <xs:enumeration value="Corrective"/>
      <xs:enumeration value="Preventative"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps / capec:Attack_Step / capec:Common_Attack_Step / @Common_Attack_Step_ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="Common_Attack_Step_ID" type="xs:integer" use="required"/>
Attribute capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / capec:Attack_Steps / capec:Attack_Step / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Attack_Execution_Flow / capec:Attack_Phases / capec:Attack_Phase / @Name
Namespace No namespace
Annotations
"Explore," "Experiment," or "Exploit."
Type restriction of xs:token
Facets
enumeration Explore
enumeration Experiment
enumeration Exploit
enumeration
Used by
Source
<xs:attribute name="Name" use="required">
  <xs:annotation>
    <xs:documentation>"Explore," "Experiment," or "Exploit."</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:token">
      <xs:enumeration value="Explore"/>
      <xs:enumeration value="Experiment"/>
      <xs:enumeration value="Exploit"/>
      <xs:enumeration value=""/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Protocol_Structure / capec:Protocol_Header / @Name
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Name" type="xs:string"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures / capec:Command_Structure / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Command_Structures / capec:Command_Structure / @Name
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Name" type="xs:string" use="required"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Related_Protocols / capec:Related_Protocol / @Name
Namespace No namespace
Used by
Source
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / capec:Related_Protocols / capec:Related_Protocol / @RFC
Namespace No namespace
Used by
Source
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / @Name
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Name" type="xs:string" use="required"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / @RFC
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="RFC" type="xs:string"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / @Encryption
Namespace No namespace
Type xs:boolean
Used by
Source
<xs:attribute name="Encryption" type="xs:boolean"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / capec:Protocol / @Encryption_Type
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Encryption_Type" type="xs:string"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Target_Attack_Surface_DescriptionType / capec:Target_Functional_Services / capec:Target_Functional_Service / @Name
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Name" type="xs:string" use="required"/>
Attribute capec:Target_Attack_SurfaceType / capec:Common_Attack_Surface_Description / @Common_Attack_Surface_ID
Namespace No namespace
Used by
Source
<xs:attribute name="Common_Attack_Surface_ID"/>
Attribute capec:Reference_Type / @Reference_ID
Namespace No namespace
Annotations
The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.
Used by
Complex Type capec:Reference_Type
Source
<xs:attribute name="Reference_ID">
  <xs:annotation>
    <xs:documentation>The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Common_ConsequenceType / @Common_Consequence_ID
Namespace No namespace
Annotations
The Common_Consequence_ID stores the value for the related
Common_Consequence entry identifier as a string. Only one
Common_Consequence_ID element can exist for each Common_Consequence element
(ex: CC-1). However, Common_Consequences across CAPEC with the same ID should
only vary in small details.
Type xs:string
Used by
Source
<xs:attribute name="Common_Consequence_ID" type="xs:string">
  <xs:annotation>
    <xs:documentation>The Common_Consequence_ID stores the value for the related Common_Consequence entry identifier as a string. Only one Common_Consequence_ID element can exist for each Common_Consequence element (ex: CC-1). However, Common_Consequences across CAPEC with the same ID should only vary in small details.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:RelationshipType / capec:Relationship_Views / capec:Relationship_View_ID / @Ordinal
Namespace No namespace
Annotations
The ordinal attribute is used
to determine if this relationship is the primary ChildOf relationship for this
 entry for a given		Relationship_View_ID element.. This attribute can only have the value "Primary" and should only be included for the primary	parent/child relationship.
Type restriction of xs:string
Facets
enumeration Primary
Used by
Source
<xs:attribute name="Ordinal">
  <xs:annotation>
    <xs:documentation>The ordinal attribute is used to determine if this relationship is the primary ChildOf relationship for this entry for a given Relationship_View_ID element.. This attribute can only have the value "Primary" and should only be included for the primary parent/child relationship.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Primary"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Content_History / capec:Submissions / capec:Submission / @Submission_Source
Namespace No namespace
Annotations
This attribute identifies how the initial	information for this entry was obtained.
Type restriction of xs:string
Facets
enumeration Externally_Mined
enumeration NDA
enumeration Internal_CAPEC_Team
enumeration External_Submission
Used by
Source
<xs:attribute name="Submission_Source" use="optional">
  <xs:annotation>
    <xs:documentation>This attribute identifies how the initial information for this entry was obtained.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Externally_Mined"/>
      <xs:enumeration value="NDA"/>
      <xs:enumeration value="Internal_CAPEC_Team"/>
      <xs:enumeration value="External_Submission"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Content_History / capec:Contributions / capec:Contribution / @Contribution_Mode
Namespace No namespace
Annotations
This attribute indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.
Type restriction of xs:string
Facets
enumeration Content
enumeration Feedback
Used by
Source
<xs:attribute name="Contribution_Mode" use="optional">
  <xs:annotation>
    <xs:documentation>This attribute indicates whether the contribution was part of feedback given to the CAPEC team or actual content that was donated.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Content"/>
      <xs:enumeration value="Feedback"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Content_History / capec:Modifications / capec:Modification / @Modification_Importance
Namespace No namespace
Annotations
This attribute identifies how significant the modification is to the attack pattern with regard to the meaning and interpretation of the pattern. If a modification has a value of Critical, then the meaning of the entry or how it might be interpreted has changed and requires attention from anyone previously dependent on the attack pattern.
Type restriction of xs:string
Facets
enumeration Normal
enumeration Critical
Used by
Source
<xs:attribute name="Modification_Importance">
  <xs:annotation>
    <xs:documentation>This attribute identifies how significant the modification is to the attack pattern with regard to the meaning and interpretation of the pattern. If a modification has a value of Critical, then the meaning of the entry or how it might be interpreted has changed and requires attention from anyone previously dependent on the attack pattern.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Normal"/>
      <xs:enumeration value="Critical"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Content_History / capec:Modifications / capec:Modification / @Modification_Source
Namespace No namespace
Annotations
This attribute indicates whether this modification was created by a CAPEC team member or provided by an
external party.
Type restriction of xs:string
Facets
enumeration Internal
enumeration External
Used by
Source
<xs:attribute name="Modification_Source" use="optional">
  <xs:annotation>
    <xs:documentation>This attribute indicates whether this modification was created by a CAPEC team member or provided by an external party.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Internal"/>
      <xs:enumeration value="External"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Content_History / capec:Previous_Entry_Names / capec:Previous_Entry_Name / @Name_Change_Date
Namespace No namespace
Annotations
This lists the date on which this name was changed to something else. 	Typically, this date will be closely aligned with new releases of CAPEC.
Type xs:date
Used by
Element capec:Content_History/capec:Previous_Entry_Names/capec:Previous_Entry_Name
Source
<xs:attribute name="Name_Change_Date" type="xs:date" use="required">
  <xs:annotation>
    <xs:documentation>This lists the date on which this name was changed to something else. Typically, this date will be closely aligned with new releases of CAPEC.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Attack_PatternType / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="optional" default="0"/>
Attribute capec:Attack_PatternType / @Name
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Name" type="xs:string" use="required"/>
Attribute capec:Attack_PatternType / @Pattern_Completeness
Namespace No namespace
Type restriction of xs:string
Facets
enumeration Complete
enumeration Stub
enumeration Hook
Used by
Source
<xs:attribute name="Pattern_Completeness">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Complete"/>
      <xs:enumeration value="Stub"/>
      <xs:enumeration value="Hook"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Attack_PatternType / @Pattern_Abstraction
Namespace No namespace
Type restriction of xs:string
Facets
enumeration Meta
enumeration Standard
enumeration Detailed
Used by
Source
<xs:attribute name="Pattern_Abstraction" use="optional">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Meta"/>
      <xs:enumeration value="Standard"/>
      <xs:enumeration value="Detailed"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Attack_PatternType / @Status
Namespace No namespace
Annotations
The Status attribute defines the status level for this view.
Type capec:Status_Type
Facets
enumeration Deprecated
enumeration Incomplete
enumeration Draft
enumeration Usable
enumeration Stable
Used by
Source
<xs:attribute name="Status" type="capec:Status_Type" use="required">
  <xs:annotation>
    <xs:documentation>The Status attribute defines the status level for this view.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:View_Attributes / @ID
Namespace No namespace
Annotations
The ID attribute provides a unique identifier for the entry.			It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Views.
Type xs:integer
Used by
Element capec:View
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>The ID attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Views.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:View_Attributes / @Name
Namespace No namespace
Annotations
The Name is a descriptive attribute used to give the reader an idea of what perspective this view represents. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Views.
Type xs:string
Used by
Element capec:View
Source
<xs:attribute name="Name" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>The Name is a descriptive attribute used to give the reader an idea of what perspective this view represents. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Views.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:View_Attributes / @Status
Namespace No namespace
Annotations
The Status attribute defines the status level for this view.
Type capec:Status_Type
Facets
enumeration Deprecated
enumeration Incomplete
enumeration Draft
enumeration Usable
enumeration Stable
Used by
Element capec:View
Source
<xs:attribute name="Status" type="capec:Status_Type" use="required">
  <xs:annotation>
    <xs:documentation>The Status attribute defines the status level for this view.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:View / @ID
Namespace No namespace
Annotations
The ID attribute provides a unique identifier for the entry.			It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Views.
Type xs:integer
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>The ID attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Views.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:View / @Name
Namespace No namespace
Annotations
The Name is a descriptive attribute used to give the reader an idea of what perspective this view represents. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Views.
Type xs:string
Source
<xs:attribute name="Name" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>The Name is a descriptive attribute used to give the reader an idea of what perspective this view represents. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Views.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:View / @Status
Namespace No namespace
Annotations
The Status attribute defines the status level for this view.
Type capec:Status_Type
Facets
enumeration Deprecated
enumeration Incomplete
enumeration Draft
enumeration Usable
enumeration Stable
Source
<xs:attribute name="Status" type="capec:Status_Type" use="required">
  <xs:annotation>
    <xs:documentation>The Status attribute defines the status level for this view.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Category / @ID
Namespace No namespace
Annotations
This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Categories.
Type xs:integer
Used by
Element capec:Category
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Categories.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Category / @Name
Namespace No namespace
Annotations
The Name is a descriptive name used to give the reader an idea of what the commonality is amongst the children of this category. All
words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Categories.
Type xs:string
Used by
Element capec:Category
Source
<xs:attribute name="Name" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>The Name is a descriptive name used to give the reader an idea of what the commonality is amongst the children of this category. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Categories.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Category / @Status
Namespace No namespace
Annotations
The Status attribute defines the status level for this category.
Type capec:Status_Type
Facets
enumeration Deprecated
enumeration Incomplete
enumeration Draft
enumeration Usable
enumeration Stable
Used by
Element capec:Category
Source
<xs:attribute name="Status" type="capec:Status_Type" use="required">
  <xs:annotation>
    <xs:documentation>The Status attribute defines the status level for this category.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Compound_Element / @ID
Namespace No namespace
Annotations
This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Compound_Elements.
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required">
  <xs:annotation>
    <xs:documentation>This attribute provides a unique identifier for the entry. It will be static for the lifetime of the entry. In the event that this entry becomes deprecated, the ID will not be reused and a pointer will be left in this entry to the replacement. This is required for all Compound_Elements.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Compound_Element / @Name
Namespace No namespace
Annotations
The Name is a descriptive name used to give the reader an idea of the meaning behind the compound attack pattern structure. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Compound_Elements.
Type xs:string
Used by
Source
<xs:attribute name="Name" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>The Name is a descriptive name used to give the reader an idea of the meaning behind the compound attack pattern structure. All words in the name should be capitalized except for articles and prepositions unless they begin or end the name. Subsequent words in a hyphenated chain are also not capitalized. This is required for all Compound_Elements.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Compound_Element / @Compound_Element_Abstraction
Namespace No namespace
Annotations
The Abstraction defines the abstraction level for this attack pattern. The abstraction levels for Compound_Elements and Attack Patterns are the same. For example, if the Compound_Element is a chain, and all elements of the chain are Meta level, then the Compound_Element Abstraction attribute is Meta. This is required for all Compound_Elements.
Type restriction of xs:string
Facets
enumeration Meta
enumeration Standard
enumeration Detailed
Used by
Source
<xs:attribute name="Compound_Element_Abstraction" use="required">
  <xs:annotation>
    <xs:documentation>The Abstraction defines the abstraction level for this attack pattern. The abstraction levels for Compound_Elements and Attack Patterns are the same. For example, if the Compound_Element is a chain, and all elements of the chain are Meta level, then the Compound_Element Abstraction attribute is Meta. This is required for all Compound_Elements.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Meta"/>
      <xs:enumeration value="Standard"/>
      <xs:enumeration value="Detailed"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Compound_Element / @Compound_Element_Completeness
Namespace No namespace
Type restriction of xs:string
Facets
enumeration Complete
enumeration Stub
enumeration Hook
Used by
Source
<xs:attribute name="Compound_Element_Completeness" use="required">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Complete"/>
      <xs:enumeration value="Stub"/>
      <xs:enumeration value="Hook"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Compound_Element / @Compound_Element_Structure
Namespace No namespace
Annotations
The Structure attribute defines the structural nature of this compound element - that is, composed of other attack patterns concurrently, as in a composite, or consecutively, as in a chain.
Type restriction of xs:string
Facets
enumeration Composite
enumeration Chain
Used by
Source
<xs:attribute name="Compound_Element_Structure" use="required">
  <xs:annotation>
    <xs:documentation>The Structure attribute defines the structural nature of this compound element - that is, composed of other attack patterns concurrently, as in a composite, or consecutively, as in a chain.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Composite"/>
      <xs:enumeration value="Chain"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute capec:Compound_Element / @Status
Namespace No namespace
Annotations
The Status attribute defines the status level for this compound element.
Type capec:Status_Type
Facets
enumeration Deprecated
enumeration Incomplete
enumeration Draft
enumeration Usable
enumeration Stable
Used by
Source
<xs:attribute name="Status" type="capec:Status_Type" use="required">
  <xs:annotation>
    <xs:documentation>The Status attribute defines the status level for this compound element.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute capec:Attack_Pattern_Catalog / capec:Common_Attack_Steps / capec:Common_Attack_Step / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Attack_Pattern_Catalog / capec:Common_Attack_Surfaces / capec:Common_Attack_Surface / @ID
Namespace No namespace
Type xs:integer
Used by
Source
<xs:attribute name="ID" type="xs:integer" use="required"/>
Attribute capec:Environment / @ID
Namespace No namespace
Type xs:ID
Used by
Source
<xs:attribute name="ID" type="xs:ID" use="required"/>
Attribute capec:Attack_Pattern_Catalog / @Catalog_Name
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Catalog_Name" type="xs:string" use="required"/>
Attribute capec:Attack_Pattern_Catalog / @Catalog_Version
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Catalog_Version" type="xs:string" use="required"/>
Attribute capec:Attack_Pattern_Catalog / @Catalog_Date
Namespace No namespace
Type xs:date
Used by
Source
<xs:attribute name="Catalog_Date" type="xs:date"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type / capec:Frequency / @Rate
Namespace No namespace
Type xs:float
Used by
Source
<xs:attribute name="Rate" type="xs:float" use="required"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type / capec:Frequency / @Units
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Units" type="xs:string" use="required"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / capec:Value_Type / capec:Frequency / @Scale
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Scale" type="xs:string" use="required"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Stateful_Measure / @Name
Namespace No namespace
Used by
Source
<xs:attribute name="Name"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Delta / capec:Frequency / @Rate
Namespace No namespace
Type xs:float
Used by
Source
<xs:attribute name="Rate" type="xs:float" use="required"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Delta / capec:Frequency / @Units
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Units" type="xs:string" use="required"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / capec:Action / capec:Object / capec:Value / capec:Delta / capec:Frequency / @Scale
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Scale" type="xs:string" use="required"/>
Attribute capec:ObservablesType / capec:Observable / capec:Signature / capec:Event / @Event_Type
Namespace No namespace
Type xs:string
Used by
Source
<xs:attribute name="Event_Type" type="xs:string"/>
Element Group capec:Structured_Text_Group
Namespace http://capec.mitre.org/capec-2
Diagram
Diagram ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text_Title ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Text ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code_Example_Language ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Code ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Comment ap_schema_v2_5_xsd.tmp#Structured_Text_Group_Images
Used by
Children capec:Code, capec:Code_Example_Language, capec:Comment, capec:Images, capec:Text, capec:Text_Title
Source
<xs:group name="Structured_Text_Group">
  <xs:sequence>
    <xs:choice>
      <xs:element name="Text_Title" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to definebold-faced title for a subsequent block of text.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Text" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to define a paragraph of text.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Code_Example_Language" type="capec:Language_Type" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to identify the programming language being used in the following block of Code</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Code" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to define a line of code.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Comment" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to define a comment in code.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Images" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Presentation Element: This element is used to define an image.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Image" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>Presentation Element: This element is used to define an image.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence maxOccurs="unbounded">
                  <xs:element name="Image_Location" type="xs:string">
                    <xs:annotation>
                      <xs:documentation>This element provides the location of the image file.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Image_Title" type="xs:string">
                    <xs:annotation>
                      <xs:documentation>This element provides a title for the image.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:sequence>
</xs:group>
Element Group capec:View_Attributes
Namespace http://capec.mitre.org/capec-2
Annotations
The View_Attributes structure is a collection of common elements	which might be shared by all Views.
Diagram
Diagram ap_schema_v2_5_xsd.tmp#View_Attributes_View_Structure ap_schema_v2_5_xsd.tmp#View_Attributes_View_Objective ap_schema_v2_5_xsd.tmp#View_Attributes_View_Audience ap_schema_v2_5_xsd.tmp#Relationships ap_schema_v2_5_xsd.tmp#Relationship_Notes ap_schema_v2_5_xsd.tmp#Maintenance_Notes ap_schema_v2_5_xsd.tmp#Other_Notes ap_schema_v2_5_xsd.tmp#Alternate_Terms ap_schema_v2_5_xsd.tmp#Research_Gaps ap_schema_v2_5_xsd.tmp#View_Attributes_References ap_schema_v2_5_xsd.tmp#View_Attributes_View_Filter ap_schema_v2_5_xsd.tmp#Content_History
Used by
Element capec:View
Children capec:Alternate_Terms, capec:Content_History, capec:Maintenance_Notes, capec:Other_Notes, capec:References, capec:Relationship_Notes, capec:Relationships, capec:Research_Gaps, capec:View_Audience, capec:View_Filter, capec:View_Objective, capec:View_Structure
Source
<xs:group name="View_Attributes">
  <xs:annotation>
    <xs:documentation>The View_Attributes structure is a collection of common elements which might be shared by all Views.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="View_Structure">
      <xs:annotation>
        <xs:documentation>The View_Structure element describes how this view is being constructed. Valid values are: Implicit Slice = a slice based on a filter criteria; Explicit Slice = a slice based on arbitrary membership, as defined by specific relationships between entries; Graph = a bounded graphical slice based on ChildOf relationships.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="Implicit_Slice"/>
          <xs:enumeration value="Explicit_Slice"/>
          <xs:enumeration value="Graph"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="View_Objective" type="capec:Structured_Text_Type">
      <xs:annotation>
        <xs:documentation>The View_Objective element describes the perspective from which this View is constructed.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="View_Audience" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The View_Audience element provides a reference to the targeted audiences or groups for this view.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Audience" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>The Audience element provides a reference to the target audience or group for this view.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Stakeholder">
                  <xs:annotation>
                    <xs:documentation>The Stakeholder element specifies what types of members of the CAPEC community might be interested in this view.</xs:documentation>
                  </xs:annotation>
                  <xs:simpleType>
                    <xs:restriction base="xs:string">
                      <xs:enumeration value="Developers"/>
                      <xs:enumeration value="Software_Vendors"/>
                      <xs:enumeration value="Assessment_Vendors"/>
                      <xs:enumeration value="Educators"/>
                      <xs:enumeration value="OWGV"/>
                      <xs:enumeration value="SAMATE"/>
                      <xs:enumeration value="CAPEC_Formalization"/>
                      <xs:enumeration value="CAPEC_Team"/>
                      <xs:enumeration value="Software_Customers"/>
                      <xs:enumeration value="Assessment_Customers"/>
                      <xs:enumeration value="Academic_Researchers"/>
                      <xs:enumeration value="Applied_Researchers"/>
                      <xs:enumeration value="Information_Providers"/>
                    </xs:restriction>
                  </xs:simpleType>
                </xs:element>
                <xs:element name="Stakeholder_Description" type="capec:Structured_Text_Type" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>The Stakeholder_Description el provides some text describing what properties of this View this particular Stakeholder might find useful.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element ref="capec:Relationships" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The Relationships structure contains one or more Relationship elements, each of which identifies an association between this structure, whether it is a Attack Pattern, Category, or Compound_Element and another structure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element ref="capec:Relationship_Notes" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This structure houses one or more Relationship_Note elements, which each contain details regarding the relationships between CAPEC entries.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element ref="capec:Maintenance_Notes" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element contains one or more Maintenance_Note elements which each contain significant maintenance tasks within this entry that still need to be addressed, such as clarifying the concepts involved or improving relationships. It should be filled out in any entry that is still undergoing significant review by the CAPEC team.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element ref="capec:Other_Notes" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element contains one or more Note elements, each of which provide any additional notes or comments that cannot be captured using other elements. New elements might be defined in the future to contain this information. It should be filled out where needed.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element ref="capec:Alternate_Terms" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element contains one or more Alternate_Term elements, each of which contains other names used to describe this attack pattern.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element ref="capec:Research_Gaps" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This structure contains one or more Research gap elements, each of which identifies potential opportunities for the vulnerability research community to conduct further exploration of issues related to this attack pattern. It is intended to highlight parts of CAPEC that have not received sufficient attention from researchers. This should be filled out where appropriate for attack patterns and categories.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="References" type="capec:Reference_List_Type" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The References element contains one or more Reference elements, each of which provide further reading and insight into this view. This should be filled out when the view is based on sources or projects that are external to the CAPEC project.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="View_Filter" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The View_Filter element holds an XSL query for identifying which elements are members of an implicit slice. This should only be present for implicit slices.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element ref="capec:Content_History" minOccurs="0">
      <xs:annotation>
        <xs:documentation>This element is used to keep track of the author of the attack pattern entry and anyone who has made modifications to the content. This provides a means of contacting the authors and modifiers for clarifying ambiguities, merging overlapping contributions, etc. This should be filled out for all entries.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:group>