change. Issue #257.
66 | Behaviors is missing from win:serviceeffectiverights_object. Issue #279
67 | Use schematron to validate DWORD values (require >0). Issue #192.
68 | Added linux-def:apparmorstatus_test.
69 | Added Windows audit subcategory GUID 0cce924a-69ae-11d9-bed3-505054503030
70 | Add a way to retrieve the expanded value of a REG_EXPAND_SZ. Issue #280.
71 | Platform schema versions should use a minimum base schema version prefix. Issue #281.
72 | MacOS:pwpolicy59_object schematron update. Issue #282.
73 | Implement SPAWAR change proposal for win-def:userright_test. Issue #283.
74 | Add missing evaluation-ids.xsd schema. Issue #284.
75 | Replace MITRE attributions with OVAL Community attributions. Issue #285.
76 | Make pwpolicy59_test/target_user nillable. Issue #286.
77 | Added this changelog document.
78 | Added schema documentation markdown and tools for generation of the same.
79 |
--------------------------------------------------------------------------------
/docs/README.md:
--------------------------------------------------------------------------------
1 | # Schema Documentation for OVAL 5.11.2
2 |
3 | This is an index page for quick reference to generated schema documentation. For more information
4 | about the Open Vulnerability and Assessment Language (OVAL) language, or to raise an issue concerning the language
5 | (including issues concerning documentation), see the [OVAL Language Project Homepage](https://github.com/OVALProject/Language) on Github.
6 |
7 | The OVAL Language operates under the [OVAL Terms of Use](http://oval.cisecurity.org/terms).
8 |
9 | ## Core Schemas
10 |
11 | * [Common](oval-common-schema.md)
12 | * [Definitions](oval-definitions-schema.md)
13 | * [System-Characteristics](oval-systm-characteristics.md)
14 | * [Results](oval-results-schema.md)
15 |
16 | ## OVAL Interpreter Schemas
17 |
18 | * [Directives](oval-directives-schema.md)
19 | * [Evaluation-IDs](evaluation-ids.md)
20 | * [External Variables](oval-variables-schema.md)
21 |
22 | ## Platform Schemas
23 |
24 | ### Independent
25 |
26 | * Platform-Independent: [Definitions](independent-definitions-schema.md), [System Characteristics](independent-system-characteristics-schema.md)
27 |
28 | ### Mobile Devices
29 |
30 | * Apple iOS: [Definitions](apple-ios-definitions-schema.md), [System Characteristics](apple-ios-system-characteristics-schema.md)
31 | * Google Andriod: [Definitions](android-definitions-schema.md), [System Characteristics](android-system-characteristics-schema.md)
32 |
33 | ### Network Devices
34 |
35 | * Cisco ASA: [Definitions](asa-definitions-schema.md), [System Characteristics](asa-system-characteristics-schema.md)
36 | * Cisco CATOS: [Definitions](catos-definitions-schema.md), [System Characteristics](catos-system-characteristics-schema.md)
37 | * Cisco IOS: [Definitions](ios-definitions-schema.md), [System Characteristics](ios-system-characteristics-schema.md)
38 | * Cisco IOS-XE: [Definitions](iosxe-definitions-schema.md), [System Characteristics](iosxe-system-characteristics-schema.md)
39 | * Cisco PIX: [Definitions](pixos-definitions-schema.md), [System Characteristics](pixos-system-characteristics-schema.md)
40 | * Juniper JunOS: [Definitions](junos-definitions-schema.md), [System Characteristics](junos-system-characteristics-schema.md)
41 | * NETCONF: [Definitions](netconf-definitions-schema.md), [System Characteristics](netconf-system-characteristics-schema.md)
42 |
43 | ### Microsoft-Specific
44 |
45 | * Windows: [Definitions](windows-definitions-schema.md), [System Characteristics](windows-system-characteristics-schema.md)
46 | * Sharepoint: [Definitions](sharepoint-definitions-schema.md), [System Characteristics](sharepoint-system-characteristics-schema.md)
47 |
48 | ### Unix Operating Systems
49 |
50 | * Unix (Generic): [Definitions](unix-definitions-schema.md), [System Characteristics](unix-system-characteristics-schema.md)
51 | * Apple MacOS: [Definitions](macos-definitions-schema.md), [System Characteristics](macos-system-characteristics-schema.md)
52 | * FreeBSD: [Definitions](freebsd-definitions-schema.md), [System Characteristics](freebsd-system-characteristics-schema.md)
53 | * HP-UX: [Definitions](hpux-definitions-schema.md), [System Characteristics](hpux-system-characteristics-schema.md)
54 | * IBM AIX: [Definitions](aix-definitions-schema.md), [System Characteristics](aix-system-characteristics-schema.md)
55 | * Linux: [Definitions](linux-definitions-schema.md), [System Characteristics](linux-system-characteristics-schema.md)
56 | * Oracle Solaris: [Definitions](solaris-definitions-schema.md), [System Characteristics](solaris-system-characteristics-schema.md)
57 | * VMWare ESX: [Definitions](esx-definitions-schema.md), [System Characteristics](esx-system-characteristics-schema.md)
58 |
59 | ### Application-Specific
60 |
61 | * Apache: [Definitions](apache-definitions-schema.md), [System Characteristics](apache-system-characteristics-schema.md)
62 |
--------------------------------------------------------------------------------
/docs/aix-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: AIX System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the AIX specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | This schema was originally developed by Yuzheng Zhou and Todd Dolinsky at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < interim_fix_item >
14 |
15 | From emgr -l -u VUID Command. See instfix manpage for specific fields.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | vuid | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | ||Virtually Unique ID. A combination of time and cpuid, this ID can be used to differentiate fixes that are otherwise identical.
|
23 | | label | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | ||Each efix that is installed on a given system has a unique efix label.
|
25 | | abstract | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
26 | ||Describes the efix package.
|
27 | | state | [aix-sc:EntityItemInterimFixStateType](#EntityItemInterimFixStateType) (0..1) |
28 | ||The the emergency fix state.
|
29 |
30 | ______________
31 |
32 | ## < fileset_item >
33 |
34 | Output of /usr/bin/lslpp -l FilesetName. See lslpp manpage for specific fields.
35 |
36 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
37 |
38 | | Child Elements | Type (MinOccurs..MaxOccurs) |
39 | |:-------------- |:--------------------------- |
40 | | flstinst | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
41 | ||Represents the name of the fileset being checked.
|
42 | | level | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
43 | ||Maintenance level (also known as version in Solaris or Linux) of the fileset. For example, "5.3.0.10" is the level for 'bos.txt.tfs' fileset in one AIX machine.
|
44 | | state | [aix-sc:EntityItemFilesetStateType](#EntityItemFilesetStateType) (0..1) |
45 | ||This gives the state of the fileset being checked. The state can be 'APPLIED', 'APPLYING','BROKEN', 'COMMITTED', 'EFIX LOCKED', 'OBSOLETE', 'COMMITTING','REJECTING'. See the manpage of the 'lslpp' command more information.
|
46 | | description | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
47 | ||Short description of the fileset being checked.
|
48 |
49 | ______________
50 |
51 | ## < fix_item >
52 |
53 | From /usr/sbin/instfix -iavk APARNum Command. See instfix manpage for specific fields.
54 |
55 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
56 |
57 | | Child Elements | Type (MinOccurs..MaxOccurs) |
58 | |:-------------- |:--------------------------- |
59 | | apar_number | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
60 | ||APAR is the short for 'Authorized Program Analysis Report'. APAR identifies and describes a software product defect. An APAR number can obtain a PTF (Program Temporary Fix) for the defect, if a PTF is available. An example of an apar_number is 'IY78751', it includes two alphabetic characters and a 5-digit integer.
|
61 | | abstract | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
62 | ||The abstract of the APAR being checked. For instance, 'LL syas rXct are available even when not susea' is the abstract of APAR 'IY78751'.
|
63 | | symptom | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
64 | ||The symptom text related to the APAR being checked. For example, the symptom text for 'IY75211' is 'Daylight savings change for year 2007 and beyond'.
|
65 | | installation_status | [aix-sc:EntityItemFixInstallationStatusType](#EntityItemFixInstallationStatusType) (0..1) |
66 | ||The installation status of files associated with the APAR.
|
67 |
68 | ______________
69 |
70 | ## < no_item >
71 |
72 | The no_item is used to hold information related to the /usr/sbin/no command and the tunable parameters it manages. Currently, /usr/sbin/no is used to configure network tuning parameters. The /usr/sbin/no command sets or displays current or next boot values for network tuning parameters. The /usr/sbin/no command queries the named parameter, retrieves the value associated with the specified parameter, and displays it.
73 |
74 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
75 |
76 | | Child Elements | Type (MinOccurs..MaxOccurs) |
77 | |:-------------- |:--------------------------- |
78 | | tunable | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
79 | ||The name of the target parameter to be queried by the /usr/sbin/no command. Examples include ip_forwarding and tcp_keepalive_interval.
|
80 | | value | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..1) |
81 | ||The value entity defines the value assigned to the tunable parameter being examined.
|
82 |
83 | ______________
84 |
85 | ## < oslevel_item >
86 |
87 | Information about the release and maintenance level of AIX operating system. This information can be retrieved by the /usr/bin/oslevel -r command.
88 |
89 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
90 |
91 | | Child Elements | Type (MinOccurs..MaxOccurs) |
92 | |:-------------- |:--------------------------- |
93 | | maintenance_level | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
94 | ||This is the maintenance level (system version) of current AIX operating system.
|
95 |
96 | ## == EntityItemFilesetStateType ==
97 |
98 | The EntityStateFilesetStateType complex type defines the different values that are valid for the state entity of a fileset state. The empty string value is permitted here to allow for detailed error reporting.
99 |
100 | **Restricts:** [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType)
101 |
102 | | Value | Description |
103 | | ----- | ----------- |
104 | | APPLIED | The specified fileset is installed on the system. The APPLIED state means that the fileset can be rejected with the installp command and the previous level of the fileset restored. This state is only valid for Version 4 fileset updates and 3.2 migrated filesets.
|
105 | | APPLYING | An attempt was made to apply the specified fileset, but it did not complete successfully, and cleanup was not performed.
|
106 | | BROKEN | The specified fileset or fileset update is broken and should be reinstalled before being used.
|
107 | | COMMITTED | The specified fileset is installed on the system. The COMMITTED state means that a commitment has been made to this level of the software. A committed fileset update cannot be rejected, but a committed fileset base level and its updates (regardless of state) can be removed or deinstalled by the installp command.
|
108 | | COMMITTING | An attempt was made to commit the specified fileset, but it did not complete successfully, and cleanup was not performed.
|
109 | | EFIX LOCKED | The specified fileset was installed sucessfully and locked by the interim fix (interim fix) manager.
|
110 | | OBSOLETE | The specified fileset was installed with an earlier version of the operating system but has been replaced by a repackaged (renamed) newer version. Some of the files that belonged to this fileset have been replaced by versions from the repackaged fileset.
|
111 | | REJECTING | An attempt was made to reject the specified fileset, but it did not complete successfully, and cleanup was not performed.
|
112 | | | |
113 |
114 | ## == EntityItemFixInstallationStatusType ==
115 |
116 | The EntityStateFixInstallationStatusType defines the different values that are valid for the installation_status entity of a fix_state item. The empty string is also allowed as a valid value to support empty emlements associated with error conditions.
117 |
118 | **Restricts:** [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType)
119 |
120 | | Value | Description |
121 | | ----- | ----------- |
122 | | ALL_INSTALLED | All filesets for XXXXXXX were found
|
123 | | SOME_INSTALLED | Not all filesets for XXXXXXX were found
|
124 | | NONE_INSTALLED | No filesets which have fixes for XXXXXXX are currently installed.
|
125 | | | The empty string value is permitted here to allow for detailed error reporting.
|
126 |
127 | ## == EntityItemInterimFixStateType ==
128 |
129 | The EntityItemInterimFixStateType complex type defines the different values that are valid for the state entity of a interim_fix_state state. Please refer to the AIX documentation of Emergency Fix States. The empty string value is permitted here to allow for detailed error reporting.
130 |
131 | **Restricts:** [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType)
132 |
133 | | Value | Description |
134 | | ----- | ----------- |
135 | | STABLE | The efix was installed with a standard installation, and successfully completed the last installation operation.
|
136 | | MOUNTED | The efix was installed with a mount installation operation, and successfully completed the last installation or mount operation.
|
137 | | UNMOUNTED | The efix was installed with a mount installation operation and one or more efix files were unmounted in a previous emgr command operation.
|
138 | | BROKEN | An unrecoverable error occurred during an installation or removal operation. The status of the efix is unreliable.
|
139 | | INSTALLING | The efix is in the process of installing.
|
140 | | REBOOT_REQUIRED | The efix was installed successfully and requires a reboot to fully integrate into the target system.
|
141 | | REMOVING | The efix is in the process of being removed.
|
142 | | | The empty string value is permitted here to allow for detailed error reporting.
|
143 |
144 |
--------------------------------------------------------------------------------
/docs/apache-definitions-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: Apache Definition
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the Apache specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ## Test Listing
12 |
13 | *[ ~~httpd_test~~ ](#httpd_test)
14 |
15 | ______________
16 |
17 | ## < ~~httpd_test~~ >
18 |
19 | > :small_red_triangle: **Deprecated As Of Version 5.8** :small_red_triangle:
**Reason:** The httpd_test does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
**Comment:** This test has been deprecated and may be removed in a future version of the language.
20 |
21 | The httpd test is used to check the version of an installed httpd binary. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an httpd_test and the optional state element specifies the data to check.
22 |
23 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
24 |
25 | | Child Elements | Type (MinOccurs..MaxOccurs) |
26 | |:-------------- |:--------------------------- |
27 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
28 | |||
29 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
30 | |||
31 |
32 | ## < ~~httpd_object~~ >
33 |
34 | > :small_red_triangle: **Deprecated As Of Version 5.8** :small_red_triangle:
**Reason:** The httpd_object does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
**Comment:** This object has been deprecated and may be removed in a future version of the language.
35 |
36 | The httpd_object element is used by a httpd test to define the different httpd binary installed on a system. There is actually only one object relating to this and it is the collection of all httpd binaries. Therefore, there are no child entities defined. Any OVAL Test written to check version will reference the same httpd_object which is basically an empty object element. A tool that implements the httpd_test and collects the httpd_object must know how to find all the httpd binaries on the system and verify that they are in fact httpd binaries.
37 |
38 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
39 |
40 | ## < ~~httpd_state~~ >
41 |
42 | > :small_red_triangle: **Deprecated As Of Version 5.8** :small_red_triangle:
**Reason:** The httpd_state does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
**Comment:** This state has been deprecated and may be removed in a future version of the language.
43 |
44 | The httpd_state element defines information associated with a specific httpd binary.
45 |
46 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
47 |
48 | | Child Elements | Type (MinOccurs..MaxOccurs) |
49 | |:-------------- |:--------------------------- |
50 | | path | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
51 | ||The path element specifies the directory component of the absolute path to a httpd binary on the system.
|
52 | | binary_name | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
53 | ||The binary_name element specifies the name of the file. If the xsi:nil attribute is set to true, then the object being specified is the higher level path. In this case, the binary_name element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match, says to collect every file under a given path.
|
54 | | version | [oval-def:EntityStateVersionType](oval-definitions-schema.md#EntityStateVersionType) (0..1) |
55 | ||The version entity is used to check the version of the httpd binary. The datatype for the version entity is 'version' which means the value should be a delimited set of numbers. It is obtained by running 'httpd -v'.
|
56 |
57 |
--------------------------------------------------------------------------------
/docs/apache-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: Apache System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the Apache specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard item element defined in the Core System Characteristic Schema. Through extension, each item inherits a set of elements and attributes that are shared amongst all OVAL Items. Each item is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core System Characteristic Schema is not outlined here.
8 |
9 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < ~~httpd_item~~ >
14 |
15 | > :small_red_triangle: **Deprecated As Of Version 5.8** :small_red_triangle:
**Reason:** The httpd_item does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
**Comment:** This item has been deprecated and may be removed in a future version of the language.
16 |
17 | The httpd item holds information about a installed Apache HTTPD binary. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.
18 |
19 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
20 |
21 | | Child Elements | Type (MinOccurs..MaxOccurs) |
22 | |:-------------- |:--------------------------- |
23 | | path | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | ||The path element specifies the directory component of the absolute path to a httpd binary found on the system.
|
25 | | binary_name | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
26 | ||The name of the httpd binary.
|
27 | | version | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
28 | ||The version entity holds the version of the specified httpd binary.
|
29 |
30 |
--------------------------------------------------------------------------------
/docs/catos-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: CatOS System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the Cisco CatOS specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | This schema was originally developed by Yuzheng Zhou at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < line_item >
14 |
15 | Stores the properties of specific lines in the catos config file.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | show_subcommand | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | ||The name of the SHOW sub-command.
|
23 | | config_line | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | ||The value returned from by the specified SHOW sub-command.
|
25 |
26 | ______________
27 |
28 | ## < module_item >
29 |
30 | Stores results from SHOW MODULE command.
31 |
32 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
33 |
34 | | Child Elements | Type (MinOccurs..MaxOccurs) |
35 | |:-------------- |:--------------------------- |
36 | | module_number | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
37 | |||
38 | | type | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
39 | |||
40 | | model | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
41 | |||
42 | | software_major_release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
43 | |||
44 | | software_individual_release | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
45 | |||
46 | | software_version_id | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
47 | |||
48 | | hardware_major_release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
49 | |||
50 | | hardware_individual_release | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
51 | |||
52 | | firmware_major_release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
53 | |||
54 | | firmware_individual_release | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
55 | |||
56 |
57 | ______________
58 |
59 | ## < version_item >
60 |
61 | Stores results from SHOW VERSION command.
62 |
63 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
64 |
65 | | Child Elements | Type (MinOccurs..MaxOccurs) |
66 | |:-------------- |:--------------------------- |
67 | | switch_series | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
68 | ||The switch_series entity specifies the target Catalyst switch series for the given version of CatOS.
|
69 | | image_name | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
70 | ||The image_name entity specifies the name of the CatOS image.
|
71 | | catos_release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
72 | ||The catos_release entity specifies the release version of CatOS.
|
73 | | ~~catos_major_release~~ | ~~[oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1~~) |
74 | ||~~~~|
75 | | ~~catos_individual_release~~ | ~~[oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1~~) |
76 | ||~~~~|
77 | | ~~catos_version_id~~ | ~~[oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1~~) |
78 | ||~~~~|
79 |
80 |
--------------------------------------------------------------------------------
/docs/esx-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: VMware ESX server System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the VMware ESX server specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | This schema was originally developed by Yuzheng Zhou and Todd Dolinsky at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < patch_item >
14 |
15 | Installation information about a specific patch in the VMware ESX server. This information can be retrieved by the "esxupdate query | grep ESX-xxxxxxx" command.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | ~~patch_number~~ | ~~[oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1~~) |
22 | ||~~This is the patch number which identifies the patch being checked in current VMware ESX server. Many of the security bulletins for VMWARE ESX Server contain non-numerical characters in the patch number, therefore this entity has a datatype of string.
~~|
23 | | patch_name | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | ||The patch_name entity indetifies the name of the patch. For example: ESX-200603 or ESX350-200904401-BG. The value of this entity should correspond to the values returned under the "name" column of the "esxupdate query" command.
|
25 | | knowledge_base_id | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
26 | ||The knowledge_base_id entity specifies the knowledge base article identifier number associated with a given patch from ESX versions 3.0.2 and earlier. It is comprised of the numerical string at the end of the patch name. For example, the patch ESX-200603 would have a knowledge base identifier of 200603. For patches from ESX version 3.0.3 and later, the patch name uses a different format and does not include the knowledge base id. This entity should be marked with a status of 'does not exist' in those cases.
|
27 | | bundle_id | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
28 | ||The bundle_id entity specifies the unique ID for the patch. Note that for version 3.0.3 and version 3.5 this is comprised of the year and month the bundle was released and a 3-digit unique ID. It is in the format YYYYMM###. For example, the first patch released in January 2008 might have a BundleID of 200801001. For patches from ESX version 3.0.2 and earlier, this entity should be marked with a status of 'does not exist' since patch name has a different format and doesn't include a bundle id.
|
29 | | classification | [esx-sc:EntityItemClassificationType](#EntityItemClassificationType) (0..1) |
30 | ||The classification entity specifies the type of patch. It can be one of: B - bug, U - update, S - security, or R - roll-up. For patches from ESX version 3.0.2 and earlier, this entity should be marked with a status of 'does not exist' since patch name has a different format and doesn't include a classification.
|
31 | | support_level | [esx-sc:EntityItemSupportLevelType](#EntityItemSupportLevelType) (0..1) |
32 | ||The support_level entity specifies the support level of the patch. If can be one of: G - GA patch, H - hot patch, D - debugging patch, or C - custom patch. For patches from ESX version 3.0.2 and earlier, this entity should be marked with a status of 'does not exist' since patch name has a different format and doesn't include a support level.
|
33 | | status | [oval-sc:EntityItemBoolType](oval-system-characteristics-schema.md#EntityItemBoolType) (0..1) |
34 | ||This is the installtaion status of the specific patch.
|
35 |
36 | ______________
37 |
38 | ## < version_item >
39 |
40 | Information about the release and build version of VMware ESX server. This information can be retrieved by the "vmware -v" command or by checking the /proc/vmware/version file.
41 |
42 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
43 |
44 | | Child Elements | Type (MinOccurs..MaxOccurs) |
45 | |:-------------- |:--------------------------- |
46 | | release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
47 | ||This is the release of current VMware ESX server.
|
48 | | build | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
49 | ||This is the build version of current VMware ESX server.
|
50 |
51 | ______________
52 |
53 | ## < visdkmanagedobject_item >
54 |
55 | The visdkmanagedobject_item is used to represent information about Managed Objects in the VMware Infrastructure.
56 |
57 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
58 |
59 | | Child Elements | Type (MinOccurs..MaxOccurs) |
60 | |:-------------- |:--------------------------- |
61 | | property | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
62 | ||The property entity holds a string that represents the object path and name of a particular setting for the Managed Entity. In the VMware Infrastructure SDK, property names are case-sensitive and thus case must be correct relative to the properties in the SDK. For example, a Virtual Machine might have ethernet0.connectionType of 'bridged'.
|
63 | | value | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..unbounded) |
64 | ||The value entity holds a string that represents a value that's associated with the specified setting for the Managed Entity. Some properties will return an array of values. In such cases consider each value individually and then make final evaluation based on the entity_check attribute.
|
65 |
66 | ## == EntityItemClassificationType ==
67 |
68 | The EntityItemClassificationType complex type restricts a string value to a specific set of values that describe the classification of a given ESX Server patch. The empty string is also allowed to support empty elements associated with error conditions.
69 |
70 | **Restricts:** [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType)
71 |
72 | | Value | Description |
73 | | ----- | ----------- |
74 | | B | Bug patches fix minor flaws that affect product functionality or behavior. Bug patches are optional. Before they are applied, one should determine whether they are necessary for your environment.
|
75 | | R | Roll‐up patches contain any number of bundles for ESX Server 3.0.3 or ESX Server 3.5 hosts. They can contain bug patches, update patches, and security patches. They do not contain upgrade bundles for minor releases or update bundles for maintenance releases.
|
76 | | S | Security patches fix one or more potential security vulnerabilities in the product. They should be implemented immediately to prevent the vulnerabilities from being exploited.
|
77 | | U | Update patches can contain new driver updates and small non‐intrusive enhancements. Before they are applied, one should determine whether they are necessary for your environment.
|
78 | | | The empty string value is permitted here to allow for detailed error reporting.
|
79 |
80 | ## == EntityItemSupportLevelType ==
81 |
82 | The EntityItemSupportLevelType complex type restricts a string value to a specific set of values that describe the support level of a given ESX Server patch. The empty string is also allowed to support empty elements associated with error conditions.
83 |
84 | **Restricts:** [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType)
85 |
86 | | Value | Description |
87 | | ----- | ----------- |
88 | | C | Custom patches are special fixes provided to a customer. They are usually specific to customer's environment, and are most likely not required by customers not reporting the issue. Custom patches have been tested in the customer's environment.
|
89 | | D | Debugging patches are released to all customers and are used by VMware to troubleshoot complex product issues. They can contain debug messages and code, and drivers. Debugging patches usually require VMware assistance to install.
|
90 | | G | GA patches are released to all customers and have been thoroughly tested. They contain fixes for ESX Server 3 software issues.
|
91 | | H | Hot patches are released to specific customers for solving critical problems specific to their environment. They contain fixes for security issues or problems that can potentially cause data loss or severe service disruptions. Hot patches should be implemented immediately.
|
92 | | | The empty string value is permitted here to allow for detailed error reporting.
|
93 |
94 |
--------------------------------------------------------------------------------
/docs/evaluation-ids.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: OVAL Definition Interpreter - Evaluation Id Schema
4 | * Version: 5.11.2
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | This schema defines an xml format for inputing a set of OVAL Definition ids into the reference OVAL Interpreter for evaluation.
8 |
9 | ______________
10 |
11 | ## < evalutation-definition-ids >
12 |
13 | The evaluation-definition-ids element is the root the Document. Its purpose is to bind together the a set of definition elements.
14 |
15 | | Child Elements | Type (MinOccurs..MaxOccurs) |
16 | |:-------------- |:--------------------------- |
17 | | definition | [oval:DefinitionIDPattern](oval-common-schema.md#DefinitionIDPattern) (1..unbounded) |
18 | ||Each definition represents the id of a definition to be evaluated.
|
19 |
20 |
--------------------------------------------------------------------------------
/docs/freebsd-definitions-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: FreeBSD Definition
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the FreeBSD specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ## Test Listing
12 |
13 | *[ portinfo_test ](#portinfo_test)
14 |
15 | ______________
16 |
17 | ## < portinfo_test >
18 |
19 | The port info test is used to check the properties of a component of a FreeBSD system. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an portinfo_object and the optional state element specifies the data to check.
20 |
21 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
22 |
23 | | Child Elements | Type (MinOccurs..MaxOccurs) |
24 | |:-------------- |:--------------------------- |
25 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
26 | |||
27 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
28 | |||
29 |
30 | ## < portinfo_object >
31 |
32 | The portinfo_object element is used by a port info test to define the specific FreeBSD package to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
33 |
34 | A port info object consists of a single pkginst element that identifies a specific package.
35 |
36 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
37 |
38 | | Child Elements | Type (MinOccurs..MaxOccurs) |
39 | |:-------------- |:--------------------------- |
40 | | pkginst | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
41 | |||
42 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
43 | |||
44 |
45 | ## < portinfo_state >
46 |
47 | The portinfo_state element defines the different information that can be used to evaluate the specified package. This includes the name, category, version, vendor, and description. Please refer to the individual elements in the schema for more details about what each represents.
48 |
49 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
50 |
51 | | Child Elements | Type (MinOccurs..MaxOccurs) |
52 | |:-------------- |:--------------------------- |
53 | | pkginst | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
54 | |||
55 | | name | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
56 | ||The name of a package.
|
57 | | category | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
58 | |||
59 | | version | Restriction of [oval-def:EntityStateAnySimpleType](oval-definitions-schema.md#EntityStateAnySimpleType) . See schema for details. (0..1) |
60 | ||The version of a package.
|
61 | | vendor | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
62 | |||
63 | | description | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
64 | |||
65 |
66 |
--------------------------------------------------------------------------------
/docs/freebsd-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: FreeBSD System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the FreeBSD specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < portinfo_item >
14 |
15 |
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | pkginst | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | |||
23 | | name | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | |||
25 | | category | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
26 | |||
27 | | version | Restriction of [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) . See schema for details. (0..1) |
28 | |||
29 | | vendor | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
30 | |||
31 | | description | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
32 | |||
33 |
34 |
--------------------------------------------------------------------------------
/docs/hpux-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: HP-UX System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the HP-UX specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard item element defined in the Core System Characteristic Schema. Through extension, each item inherits a set of elements and attributes that are shared amongst all OVAL Items. Each item is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core System Characteristic Schema is not outlined here.
8 |
9 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < getconf_item >
14 |
15 | These items contain getconf items.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | parameter_name | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | ||This is the parameter name to check
|
23 | | pathname | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | ||This is the pathname to check
|
25 | | output | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..1) |
26 | ||The output produced by the getconf command.
|
27 |
28 | ______________
29 |
30 | ## < ndd_item >
31 |
32 | This item represents data collected by the ndd command.
33 |
34 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
35 |
36 | | Child Elements | Type (MinOccurs..MaxOccurs) |
37 | |:-------------- |:--------------------------- |
38 | | device | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
39 | ||The name of the device for which the parameter was collected.
|
40 | | parameter | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
41 | ||The name of a parameter for example, ip_forwarding
|
42 | | value | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..1) |
43 | ||The observed value of the named parameter.
|
44 |
45 | ______________
46 |
47 | ## < patch_item >
48 |
49 | From /usr/sbin/swlist -l patch PHxx_yyyyy. See swlist manpage for specific fields
50 |
51 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
52 |
53 | | Child Elements | Type (MinOccurs..MaxOccurs) |
54 | |:-------------- |:--------------------------- |
55 | | patch_name | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
56 | ||This is the patch name to check.
|
57 | | swtype | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
58 | ||HP-UX patch names begin with 'PH'
|
59 | | area_patched | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
60 | ||The third and fourth characters in HP-UX patch names indicate the area of software being patched. CO - General HP-UX commands KL - Kernel patches NE - Network specific patches SS - All other subsystems (X11, starbase, etc.)
|
61 | | patch_base | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
62 | ||The sixth through tenth characters in HP-UX patch names represent a unique numeric identifier for the patch.
|
63 |
64 | ______________
65 |
66 | ## < swlist_item >
67 |
68 | Output of /usr/sbin/swlist command. Note: A quick way to check for the installation of a specific fileset is to use the command 'swlist -a version -l fileset filesetname'. See manpage for swlist for explanation of additional command options.
69 |
70 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
71 |
72 | | Child Elements | Type (MinOccurs..MaxOccurs) |
73 | |:-------------- |:--------------------------- |
74 | | swlist | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
75 | ||This is the name of the bundle or fileset to check.
|
76 | | bundle | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
77 | |||
78 | | fileset | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
79 | |||
80 | | version | Restriction of [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) . See schema for details. (0..1) |
81 | |||
82 | | title | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
83 | |||
84 | | vendor | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
85 | |||
86 |
87 | ______________
88 |
89 | ## < trusted_item >
90 |
91 | These items contain account settings for trusted HP-UX installations.
92 |
93 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
94 |
95 | | Child Elements | Type (MinOccurs..MaxOccurs) |
96 | |:-------------- |:--------------------------- |
97 | | username | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
98 | ||This is the name of the user being checked
|
99 | | uid | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
100 | ||The user's ID
|
101 | | password | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
102 | ||This is the encrypted version of the user's password
|
103 | | account_owner | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
104 | ||The Account owner for pseudo-users
|
105 | | boot_auth | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
106 | ||Boot authorization
|
107 | | audit_id | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
108 | ||getprpwaid uses the audit ID rather than the UID
|
109 | | audit_flag | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
110 | |||
111 | | pw_change_min | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
112 | ||Minimum time between password changes
|
113 | | pw_max_size | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
114 | ||Maximum password length in characters
|
115 | | pw_expiration | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
116 | ||Password expiration time in seconds
|
117 | | pw_life | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
118 | ||Trusted lifetime, after which the account is locked
|
119 | | pw_change_s | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
120 | ||Time of last successful password change
|
121 | | pw_change_u | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
122 | ||Time of last unsuccessful password change
|
123 | | acct_expire | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
124 | ||Absolute account lifetime in seconds
|
125 | | max_llogin | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
126 | ||Maximum time allowed between logins before the account is locked
|
127 | | exp_warning | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
128 | ||The time in seconds before expiration when a warning will appear
|
129 | | usr_chg_pw | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
130 | ||Who can change this user's password
|
131 | | gen_pw | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
132 | ||Allows user to use system-generated passwords
|
133 | | pw_restrict | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
134 | ||Whether a triviality check is performed on user-generated passwords
|
135 | | pw_null | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
136 | ||Determines if null passwords are allowed for this account
|
137 | | pw_gen_char | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
138 | ||Allows password generator to use random printable ASCII characters
|
139 | | pw_gen_let | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
140 | ||Allows password generator to use random letters
|
141 | | login_time | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
142 | ||Specifies the times when the user may login to this account
|
143 | | pw_changer | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
144 | ||The user ID of the user who last changed the password on the user's account, if it was not the account owner
|
145 | | login_time_s | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
146 | ||The time of the last successful login using this account
|
147 | | login_time_u | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
148 | ||The time of the last unsuccessful login using this account
|
149 | | login_tty_s | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
150 | ||The terminal or remote host associated with the last successful login to the account
|
151 | | login_tty_u | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
152 | ||The terminal or remote hosts associated with the last unsuccessful login to the account
|
153 | | num_u_logins | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
154 | ||The number of unsuccessful login attempts since that last successful login
|
155 | | max_u_logins | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
156 | ||The maximum number of unsuccessful login attempts before the account is locked
|
157 | | lock_flag | [oval-sc:EntityItemBoolType](oval-system-characteristics-schema.md#EntityItemBoolType) (0..1) |
158 | ||Indicates whether the administrative lock on the account is set
|
159 |
160 |
--------------------------------------------------------------------------------
/docs/junos-definitions-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: Junos Definition
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the Junos-specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | This schema was originally developed by David Solin at jOVAL.org. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ## Test Listing
12 |
13 | *[ xml_config_test ](#xml_config_test)
14 | *[ show_test ](#show_test)
15 | *[ version_test ](#version_test)
16 | *[ xml_show_test ](#xml_show_test)
17 |
18 | ______________
19 |
20 | ## < xml_config_test >
21 |
22 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
23 |
24 | | Child Elements | Type (MinOccurs..MaxOccurs) |
25 | |:-------------- |:--------------------------- |
26 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
27 | |||
28 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
29 | |||
30 |
31 | ## < xml_config_object >
32 |
33 | The xml_config_object element is used by an XML config test to define the object to be evaluated. For the most part this object checks for existence and is used without a state comparision. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
34 |
35 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
36 |
37 | | Child Elements | Type (MinOccurs..MaxOccurs) |
38 | |:-------------- |:--------------------------- |
39 | | xpath | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
40 | ||An XPATH 1.0 expression that should be evaluated against the XML configuration file. Any valid XPATH 1.0 statement is usable with one exception, at most one field may be identified in the XPATH. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible.
|
41 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
42 | |||
43 |
44 | ## < xml_config_state >
45 |
46 | The xml_config_state element defines the different information that can be used to evaluate the result of an XPATH query against the XML configuration file. Please refer to the individual elements in the schema for more details about what each represents.
47 |
48 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
49 |
50 | | Child Elements | Type (MinOccurs..MaxOccurs) |
51 | |:-------------- |:--------------------------- |
52 | | xpath | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
53 | ||An XPATH 1.0 expression that was evaluated against the XML config file.
|
54 | | value_of | [oval-def:EntityStateAnySimpleType](oval-definitions-schema.md#EntityStateAnySimpleType) (0..1) |
55 | ||The result of the evaluation of the XPATH expression against the XML config file.
|
56 |
57 | ______________
58 |
59 | ## < show_test >
60 |
61 | The show test is used to check the properties of specific output lines from a SHOW command, such as "show configuration". It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a show_object and the optional state element specifies the data to check.
62 |
63 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
64 |
65 | | Child Elements | Type (MinOccurs..MaxOccurs) |
66 | |:-------------- |:--------------------------- |
67 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
68 | |||
69 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
70 | |||
71 |
72 | ## < show_object >
73 |
74 | The show_object element is used by a show test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
75 |
76 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
77 |
78 | | Child Elements | Type (MinOccurs..MaxOccurs) |
79 | |:-------------- |:--------------------------- |
80 | | subcommand | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
81 | ||The name of a SHOW sub-command to be tested.
|
82 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
83 | |||
84 |
85 | ## < show_state >
86 |
87 | The show_state element defines the different information that can be used to evaluate the result of a specific SHOW sub-command. This includes the name of the sub-command and the corresponding config output. Please refer to the individual elements in the schema for more details about what each represents.
88 |
89 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
90 |
91 | | Child Elements | Type (MinOccurs..MaxOccurs) |
92 | |:-------------- |:--------------------------- |
93 | | subcommand | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
94 | ||The name of the SHOW sub-command.
|
95 | | value | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
96 | ||The value returned from by the specified SHOW sub-command. This may consist of multiple lines of information, whose raw form will be captured by the item.
|
97 |
98 | ______________
99 |
100 | ## < version_test >
101 |
102 | The version_test is used to check the version of components of the JunOS operating system. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a version_object and the optional state element specifies the data to check.
103 |
104 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
105 |
106 | | Child Elements | Type (MinOccurs..MaxOccurs) |
107 | |:-------------- |:--------------------------- |
108 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
109 | |||
110 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
111 | |||
112 |
113 | ## < version_object >
114 |
115 | The version_object element is used by a version_test to define the different version information associated with a JunOS system.
116 |
117 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
118 |
119 | | Child Elements | Type (MinOccurs..MaxOccurs) |
120 | |:-------------- |:--------------------------- |
121 | | component | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
122 | ||The name of the JunOS component whose version should be retrieved.
|
123 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
124 | |||
125 |
126 | ## < version_state >
127 |
128 | The version_state element defines the version information held by a JunOS component.
129 |
130 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
131 |
132 | | Child Elements | Type (MinOccurs..MaxOccurs) |
133 | |:-------------- |:--------------------------- |
134 | | component | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
135 | ||The name of the JunOS component whose version should be retrieved.
|
136 | | raw_value | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
137 | ||The raw release version string for the component, e.g., 12.2R6.1 or 12.1X44-D10.4.
|
138 | | major | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
139 | ||The part of the release version of the component corresponding to the year in which the release occurred. For example, the major value for 12.2R6.1 would be '12'.
|
140 | | minor | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
141 | ||The part of the release version of the component corresponding to the quarter in which the release occurred. For example, the minor value for 12.2R6.1 would be '2'.
|
142 | | type | [junos-def:EntityStateJunosReleaseTypeType](#EntityStateJunosReleaseTypeType) (0..1) |
143 | ||The release type embedded in the version of the component. For example, the type value for 12.2R6.1 is 'R'.
|
144 | | build | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
145 | ||The build number of the component's version. For example, the revision for 12.2R6.1 has a build number of '6'; 12.1X44-D10.4 has a build number of '44'.
|
146 | | maintenance_release | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
147 | ||A maintenance_release value can appear in an R-type service release or an X-type release (where it takes the value of the D-number). For example, version 14.2R3-S4.5 has a maintenance_release of '4'. For version 10.4S4.2, the maintenance_release entity would have a status of 'does not exist'. For version 12.1X44-D10.4, the maintenance_release entity value would be '10'.
|
148 | | spin | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
149 | ||The spin number of the component. For example, 12.2R6.1 has a spin value of '1'; 12.1X44-D10.4 has a spin value of '4'.
|
150 | | build_date | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
151 | ||The build date of the component, specified in milliseconds since the Epoch (midnight, January 1, 1970 GMT).
|
152 |
153 | ______________
154 |
155 | ## < xml_show_test >
156 |
157 | The XML show test is used to check the properties of specific output from an XML SHOW command, such as "show configuration | display xml". It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a xml_show_object and the optional state element specifies the data to check.
158 |
159 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
160 |
161 | | Child Elements | Type (MinOccurs..MaxOccurs) |
162 | |:-------------- |:--------------------------- |
163 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
164 | |||
165 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
166 | |||
167 |
168 | ## < xml_show_object >
169 |
170 | The xml_show_object element is used by an XML show test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
171 |
172 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
173 |
174 | | Child Elements | Type (MinOccurs..MaxOccurs) |
175 | |:-------------- |:--------------------------- |
176 | | subcommand | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
177 | ||The name of a SHOW sub-command to be tested.
|
178 | | xpath | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
179 | ||An XPATH 1.0 expression that should be evaluated against the XML data resulting from the XML show subcommand. Any valid XPATH 1.0 statement is usable with one exception, at most one field may be identified in the XPATH. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible.
|
180 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
181 | |||
182 |
183 | ## < xml_show_state >
184 |
185 | The xml_show_state element defines the different information that can be used to evaluate the result of a specific XML SHOW sub-command. This includes the name of the sub-command, the XPATH and the corresponding XPATH query result. Please refer to the individual elements in the schema for more details about what each represents.
186 |
187 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
188 |
189 | | Child Elements | Type (MinOccurs..MaxOccurs) |
190 | |:-------------- |:--------------------------- |
191 | | subcommand | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
192 | ||The name of a SHOW sub-command to be tested.
|
193 | | xpath | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
194 | ||An XPATH 1.0 expression that should be evaluated against the XML data resulting from the XML show subcommand.
|
195 | | value_of | [oval-def:EntityStateAnySimpleType](oval-definitions-schema.md#EntityStateAnySimpleType) (0..1) |
196 | ||The result of the evaluation of the XPATH expression against the XML data returned from the XML show subcommand.
|
197 |
198 | ## == EntityStateJunosReleaseTypeType ==
199 |
200 | The EntityStateJunosReleaseTypeType complex type defines the different values that are valid for the release_type entity of a system_metric state. These values describe the release type specified in the raw version string.
201 |
202 | **Restricts:** [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType)
203 |
204 | | Value | Description |
205 | | ----- | ----------- |
206 | | R | Indicates a normal release.
|
207 | | I | Indicates an internal release.
|
208 | | F | Indicates a feature release.
|
209 | | S | Indicates a service release.
|
210 | | B | Indicates a beta release.
|
211 | | X | Indicates an exception release (e.g., every release of the SRX branch so far).
|
212 | | | The empty string value is permitted here to allow for empty elements associated with variable references.
|
213 |
214 |
--------------------------------------------------------------------------------
/docs/junos-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: Junos System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the Junos-specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard item element defined in the Core System Characteristic Schema. Through extension, each item inherits a set of elements and attributes that are shared amongst all OVAL Items. Each item is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core System Characteristic Schema is not outlined here.
8 |
9 | This schema was originally developed by David Solin at jOVAL.org. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < xml_config_item >
14 |
15 | Stores information about the existence of a particular XPATH query result from the JunOS XML config file.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | xpath | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | ||An XPATH 1.0 expression that was evaluated against the XML config file.
|
23 | | value_of | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..unbounded) |
24 | ||The result of the evaluation of the XPATH expression against the XML config file.
|
25 |
26 | ______________
27 |
28 | ## < show_item >
29 |
30 | Stores the resulting configuration data provided by the execution of a specific show command.
31 |
32 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
33 |
34 | | Child Elements | Type (MinOccurs..MaxOccurs) |
35 | |:-------------- |:--------------------------- |
36 | | subcommand | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
37 | ||The name of the SHOW sub-command.
|
38 | | value | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
39 | ||The value returned from by the specified SHOW sub-command. This may consist of multiple lines of information.
|
40 |
41 | ______________
42 |
43 | ## < version_item >
44 |
45 | The version_item holds information about the version of a particular component of the JunOS operating system. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.
46 |
47 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
48 |
49 | | Child Elements | Type (MinOccurs..MaxOccurs) |
50 | |:-------------- |:--------------------------- |
51 | | component | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
52 | ||The name of the JunOS component whose version should be retrieved.
|
53 | | raw_value | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
54 | ||The raw release version string for the component, e.g., 12.2R6.1 or 12.1X44-D10.4.
|
55 | | major | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
56 | ||The part of the release version of the component corresponding to the year in which the release occurred. For example, the major value for 12.2R6.1 would be '12'.
|
57 | | minor | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
58 | ||The part of the release version of the component corresponding to the quarter in which the release occurred. For example, the minor value for 12.2R6.1 would be '2'.
|
59 | | type | [junos-sc:EntityItemJunosReleaseTypeType](#EntityItemJunosReleaseTypeType) (0..1) |
60 | ||The release type embedded in the version of the component. For example, the type value for 12.2R6.1 is 'R'.
|
61 | | build | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
62 | ||The build number of the component's version. For example, the revision for 12.2R6.1 has a build number of '6'; 12.1X44-D10.4 has a build number of '44'.
|
63 | | maintenance_release | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
64 | ||A maintenance_release value can appear in an R-type service release or an X-type release (where it takes the value of the D-number). For example, version 14.2R3-S4.5 has a maintenance_release of '4'. For version 10.4S4.2, the maintenance_release entity would have a status of 'does not exist'. For version 12.1X44-D10.4, the maintenance_release entity value would be '10'.
|
65 | | spin | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
66 | ||The spin number of the component. For example, 12.2R6.1 has a spin value of '1'; 12.1X44-D10.4 has a spin value of '4'.
|
67 | | build_date | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
68 | ||The build date of the component, specified in milliseconds since the Epoch (midnight, January 1, 1970 GMT).
|
69 |
70 | ______________
71 |
72 | ## < xml_show_item >
73 |
74 | Stores the result of the application of an XPATH query applied to the JunOS configuration data provided by the execution of a specific show command, which has been piped to "display xml".
75 |
76 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
77 |
78 | | Child Elements | Type (MinOccurs..MaxOccurs) |
79 | |:-------------- |:--------------------------- |
80 | | subcommand | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
81 | ||The name of a SHOW sub-command to be tested.
|
82 | | xpath | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
83 | ||An XPATH 1.0 expression that should be evaluated against the XML data resulting from the XML show subcommand.
|
84 | | value_of | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..unbounded) |
85 | ||The result of the evaluation of the XPATH expression against the XML data returned from the XML show subcommand.
|
86 |
87 | ## == EntityItemJunosReleaseTypeType ==
88 |
89 | The EntityItemJunosReleaseTypeType complex type defines the different values that are valid for the release_type entity of a system_metric state. These values describe the release type specified in the raw version string.
90 |
91 | **Restricts:** [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType)
92 |
93 | | Value | Description |
94 | | ----- | ----------- |
95 | | R | Indicates a normal release.
|
96 | | I | Indicates an internal release.
|
97 | | F | Indicates a feature release.
|
98 | | S | Indicates a service release.
|
99 | | B | Indicates a beta release.
|
100 | | X | Indicates an exception release (e.g., every release of the SRX branch so far).
|
101 | | | The empty string value is permitted here to allow for empty elements associated with error conditions.
|
102 |
103 |
--------------------------------------------------------------------------------
/docs/netconf-definitions-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: NETCONF Definitions
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the NETCONF (RFC 6241) protocol-specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here
8 |
9 | This schema was originally developed by David Solin at jOVAL.org. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ## Test Listing
12 |
13 | *[ config_test ](#config_test)
14 |
15 | ______________
16 |
17 | ## < config_test >
18 |
19 | The config_test is used to check the properties of the XML output from a GET-CONFIG command, for the running configuration. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a config_object and the optional state element specifies the data to check.
20 |
21 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
22 |
23 | | Child Elements | Type (MinOccurs..MaxOccurs) |
24 | |:-------------- |:--------------------------- |
25 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
26 | |||
27 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
28 | |||
29 |
30 | ## < config_object >
31 |
32 | The config_object element is used by a config_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
33 |
34 | A config_object consists of an xpath entity that contains an XPATH 1.0 query to perform on the NETCONF get-config response XML data. The response data is assumed to consist of a entity in the urn:ietf:params:xml:ns:netconf:base:1.0 XML namespace, with arbitrary (i.e., vendor-specific) child nodes.
35 |
36 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
37 |
38 | | Child Elements | Type (MinOccurs..MaxOccurs) |
39 | |:-------------- |:--------------------------- |
40 | | xpath | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
41 | ||Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. Any valid Xpath 1.0 statement is usable with one exception, at most one field may be identified in the Xpath. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible.
|
42 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
43 | |||
44 |
45 | ## < config_state >
46 |
47 | The config_state element defines the different information that can be used to evaluate the result of a specific config xpath evaluation. This includes the xpath used and the value of this xpath.
48 |
49 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
50 |
51 | | Child Elements | Type (MinOccurs..MaxOccurs) |
52 | |:-------------- |:--------------------------- |
53 | | xpath | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
54 | ||Specifies an Xpath expression describing the text node(s) or attribute(s) to look at.
|
55 | | value_of | [oval-def:EntityStateAnySimpleType](oval-definitions-schema.md#EntityStateAnySimpleType) (0..1) |
56 | ||The value_of element checks the value(s) of the text node(s) or attribute(s) found.
|
57 |
58 |
--------------------------------------------------------------------------------
/docs/netconf-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: NETCONF System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | This document outlines the items of the OVAL System Characteristics XML schema that are composed of NETCONF (RFC 6241) protocol-specific tests. Each item is an extention of a basic System Characteristics item defined in the core System Characteristics XML schema.
8 |
9 | This schema was originally developed by David Solin at jOVAL.org. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < config_item >
14 |
15 | This item stores results from checking the contents of an xml configuration.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | xpath | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | ||Specifies an Xpath expression describing the text node(s) or attribute(s) to look at.
|
23 | | value_of | [oval-sc:EntityItemAnySimpleType](oval-system-characteristics-schema.md#EntityItemAnySimpleType) (0..unbounded) |
24 | ||The value_of element checks the value(s) of the text node(s) or attribute(s) found. How this is used is entirely controlled by operator attributes.
|
25 |
26 |
--------------------------------------------------------------------------------
/docs/oval-directives-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: Core Directives
4 | * Version: 5.11.2
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the core schema for encoding Open Vulnerability and Assessment Language (OVAL) Directives. Each of the elements, types, and attributes that make up the Core Directives Schema are described in detail and should provide the information necessary to understand what each object represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between these objects is not outlined here.
8 |
9 | The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.
10 |
11 | ______________
12 |
13 | ## < oval_directives >
14 |
15 | The oval_directives element is the root of an OVAL Directive Document. Its purpose is to bind together the generator and the set of directives contained in the document. The generator section must be present and provides information about when the directives document was compiled and under what version. The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrity to be provided to the user. Enveloped signatures are supported. More information about the official W3C Recommendation regarding XML digital signatures can be found at http://www.w3.org/TR/xmldsig-core/.
16 |
17 | | Child Elements | Type (MinOccurs..MaxOccurs) |
18 | |:-------------- |:--------------------------- |
19 | | generator | [oval:GeneratorType](oval-common-schema.md#GeneratorType) (1..1) |
20 | ||The required generator section provides information about when the directives document was compiled and under what version.
|
21 | | directives | [oval-res:DefaultDirectivesType](oval-results-schema.md#DefaultDirectivesType) (1..1) |
22 | ||The required directives section presents flags describing what information must be been included in an oval results document. This element represents the default set of directives. These directives apply to all classes of definitions for which there is not a class specific set of directives.
|
23 | | class_directives | [oval-res:ClassDirectivesType](oval-results-schema.md#ClassDirectivesType) (0..5) |
24 | ||The optional class_directives section presents flags describing what information has been included in the results document for a specific OVAL Definition class. The directives for a particlar class override the default directives.
|
25 | | [ds:Signature](http://www.w3.org/TR/xmldsig-core/#sec-Signature) | n/a (0..1) |
26 | ||The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrity to be provided to the user. Enveloped signatures are supported. More information about the official W3C Recommendation regarding XML digital signatures can be found at http://www.w3.org/TR/xmldsig-core/.
|
27 |
28 |
--------------------------------------------------------------------------------
/docs/oval-variables-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: Core Variable
4 | * Version: 5.11.2
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 |
8 |
9 | The following is a description of the elements, types, and attributes that compose the core schema for encoding Open Vulnerability and Assessment Language (OVAL) Variables. This schema is provided to give structure to any external variables and their values that an OVAL Definition is expecting.
10 |
11 | The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.
12 |
13 | ______________
14 |
15 | ## < oval_variables >
16 |
17 | The oval_variables element is the root of an OVAL Variable Document. Its purpose is to bind together the different variables contained in the document. The generator section must be present and provides information about when the variable file was compiled and under what version. The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrity to be provided to the user. Enveloped signatures are supported. More information about the official W3C Recommendation regarding XML digital signatures can be found at http://www.w3.org/TR/xmldsig-core/.
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | generator | [oval:GeneratorType](oval-common-schema.md#GeneratorType) (1..1) |
22 | |||
23 | | variables | [oval-var:VariablesType](oval-variables-schema.md#VariablesType) (0..1) |
24 | |||
25 | | [ds:Signature](http://www.w3.org/TR/xmldsig-core/#sec-Signature) | n/a (0..1) |
26 | |||
27 |
28 | ______________
29 |
30 | ## == VariablesType ==
31 |
32 | The VariablesType complex type is a container for one or more variable elements. Each variable element holds the value of an external variable used in an OVAL Definition. Please refer to the description of the VariableType for more information about an individual variable.
33 |
34 | | Child Elements | Type (MinOccurs..MaxOccurs) |
35 | |:-------------- |:--------------------------- |
36 | | variable | [oval-var:VariableType](oval-variables-schema.md#VariableType) (1..unbounded) |
37 | |||
38 |
39 | ## == VariableType ==
40 |
41 | Each variable element contains the associated datatype and value which will be substituted into the OVAL Definition that is referencing this specific variable.
42 |
43 | The notes section of a variable should be used to hold information that might be helpful to someone examining the technical aspects of the variable. Please refer to the description of the NotesType complex type for more information about the notes element.
44 |
45 | #### Attributes:
46 |
47 | * **id** [oval:VariableIDPattern](oval-common-schema.md#VariableIDPattern) (required)
48 | * **datatype** [oval:SimpleDatatypeEnumeration](oval-common-schema.md#SimpleDatatypeEnumeration) (required)
49 | Note that the 'record' datatype is not permitted on variables.
50 | * **instance** xsd:nonNegativeInteger
51 | Use to specify multiple variable instances.
52 | * **comment** xsd:string (required)
53 |
54 | | Child Elements | Type (MinOccurs..MaxOccurs) |
55 | |:-------------- |:--------------------------- |
56 | | value | xsd:anySimpleType (1..unbounded) |
57 | |||
58 | | notes | [oval:NotesType](oval-common-schema.md#NotesType) (0..1) |
59 | |||
60 |
61 |
--------------------------------------------------------------------------------
/docs/pixos-definitions-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: PixOS Definition
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the PIX specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | This schema was originally developed by Yuzheng Zhou and Eric Grey at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ## Test Listing
12 |
13 | *[ line_test ](#line_test)
14 | *[ version_test ](#version_test)
15 |
16 | ______________
17 |
18 | ## < line_test >
19 |
20 | The line_test is used to check the properties of specific output lines from a SHOW command, such as SHOW RUNNING-CONFIG. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a line_object and the optional state element specifies the data to check.
21 |
22 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
23 |
24 | | Child Elements | Type (MinOccurs..MaxOccurs) |
25 | |:-------------- |:--------------------------- |
26 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
27 | |||
28 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
29 | |||
30 |
31 | ## < line_object >
32 |
33 | The line_object element is used by a line_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
34 |
35 | A line object consists of a show_subcommand entity that is the name of a SHOW sub-command to be tested.
36 |
37 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
38 |
39 | | Child Elements | Type (MinOccurs..MaxOccurs) |
40 | |:-------------- |:--------------------------- |
41 | | show_subcommand | [oval-def:EntityObjectStringType](oval-definitions-schema.md#EntityObjectStringType) (1..1) |
42 | ||The name of a SHOW sub-command.
|
43 | | [oval-def:filter](oval-definitions-schema.md#filter) | n/a (0..unbounded) |
44 | |||
45 |
46 | ## < line_state >
47 |
48 | The line_state element defines the different information that can be used to evaluate the result of a specific SHOW sub-command. This includes the name of ths sub-command and the corresponding config line. Please refer to the individual elements in the schema for more details about what each represents.
49 |
50 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
51 |
52 | | Child Elements | Type (MinOccurs..MaxOccurs) |
53 | |:-------------- |:--------------------------- |
54 | | show_subcommand | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
55 | ||The name of the SHOW sub-command.
|
56 | | config_line | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
57 | ||The value returned from by the specified SHOW sub-command.
|
58 |
59 | ______________
60 |
61 | ## < version_test >
62 |
63 | The version test is used to check the version of the PIX operating system. It is based off of the SHOW VERSION command. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a version_object and the optional state element specifies the data to check.
64 |
65 | **Extends:** [oval-def:TestType](oval-definitions-schema.md#TestType)
66 |
67 | | Child Elements | Type (MinOccurs..MaxOccurs) |
68 | |:-------------- |:--------------------------- |
69 | | object | [oval-def:ObjectRefType](oval-definitions-schema.md#ObjectRefType) (1..1) |
70 | |||
71 | | state | [oval-def:StateRefType](oval-definitions-schema.md#StateRefType) (0..unbounded) |
72 | |||
73 |
74 | ## < version_object >
75 |
76 | The version_object element is used by a version test to define the different version information associated with a PIX system. There is actually only one object relating to version and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check version will reference the same version_object which is basically an empty object element.
77 |
78 | **Extends:** [oval-def:ObjectType](oval-definitions-schema.md#ObjectType)
79 |
80 | ## < version_state >
81 |
82 | The version_state element defines the version information held within a Cisco PIX software release. The pix_release element specifies the whole PIX version information. The pix_major_release, pix_minor_release and pix_build elements specify seperated parts of PIX software version information. For instance, if the PIX version is 7.1(2.3)49, then pix_release is 7.1(2.3)49, pix_major_release is 7.1, pix_minor_release is 2.3 and pix_build is 49. See the SHOW VERSION command within PIX for more information.
83 |
84 | **Extends:** [oval-def:StateType](oval-definitions-schema.md#StateType)
85 |
86 | | Child Elements | Type (MinOccurs..MaxOccurs) |
87 | |:-------------- |:--------------------------- |
88 | | pix_release | [oval-def:EntityStateStringType](oval-definitions-schema.md#EntityStateStringType) (0..1) |
89 | ||The pix_release element specifies the whole PIX version information.
|
90 | | pix_major_release | [oval-def:EntityStateVersionType](oval-definitions-schema.md#EntityStateVersionType) (0..1) |
91 | ||The pix_major_release is the dotted version that starts a version string. For example the pix_release 7.1(2.3)49 has a pix_major_release of 7.1.
|
92 | | pix_minor_release | [oval-def:EntityStateVersionType](oval-definitions-schema.md#EntityStateVersionType) (0..1) |
93 | ||The pix_minor_release is the dotted version that starts a version string. For example the pix_release 7.1(2.3)49 has a pix_minor_release of 2.3.
|
94 | | pix_build | [oval-def:EntityStateIntType](oval-definitions-schema.md#EntityStateIntType) (0..1) |
95 | ||The pix_build is an integer. For example the pix_release 7.1(2.3)49 has a pix_build of 49.
|
96 |
97 |
--------------------------------------------------------------------------------
/docs/pixos-system-characteristics-schema.md:
--------------------------------------------------------------------------------
1 | # Open Vulnerability and Assessment Language: Element Dictionary
2 |
3 | * Schema: PixOS System Characteristics
4 | * Version: 5.11.1:1.1
5 | * Release Date: 11/30/2016 09:00:00 AM
6 |
7 | The following is a description of the elements, types, and attributes that compose the Cisco PIX (Private Internet Exchange) specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
8 |
9 | This schema was originally developed by Yuzheng Zhou and Eric Grey at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
10 |
11 | ______________
12 |
13 | ## < line_item >
14 |
15 | Stores the properties of specific lines in the PIX config file.
16 |
17 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
18 |
19 | | Child Elements | Type (MinOccurs..MaxOccurs) |
20 | |:-------------- |:--------------------------- |
21 | | show_subcommand | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
22 | ||The name of the SHOW sub-command.
|
23 | | config_line | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
24 | ||The value returned from by the specified SHOW sub-command.
|
25 |
26 | ______________
27 |
28 | ## < version_item >
29 |
30 | Stores results from SHOW VERSION command.
31 |
32 | **Extends:** [oval-sc:ItemType](oval-system-characteristics-schema.md#ItemType)
33 |
34 | | Child Elements | Type (MinOccurs..MaxOccurs) |
35 | |:-------------- |:--------------------------- |
36 | | pix_release | [oval-sc:EntityItemStringType](oval-system-characteristics-schema.md#EntityItemStringType) (0..1) |
37 | |||
38 | | pix_major_release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
39 | |||
40 | | pix_minor_release | [oval-sc:EntityItemVersionType](oval-system-characteristics-schema.md#EntityItemVersionType) (0..1) |
41 | |||
42 | | pix_build | [oval-sc:EntityItemIntType](oval-system-characteristics-schema.md#EntityItemIntType) (0..1) |
43 | |||
44 |
45 |
--------------------------------------------------------------------------------
/schemas/apache-definitions-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 |
12 | The following is a description of the elements, types, and attributes that compose the Apache specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
13 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
14 |
15 | Apache Definition
16 | 5.11.1:1.1
17 | 11/30/2016 09:00:00 AM
18 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | The httpd test is used to check the version of an installed httpd binary. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an httpd_test and the optional state element specifies the data to check.
30 |
31 |
32 | httpd_test
33 | httpd_object
34 | httpd_state
35 | httpd_item
36 |
37 |
38 |
39 |
40 | 5.8
41 | The httpd_test does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
42 | This test has been deprecated and may be removed in a future version of the language.
43 |
44 |
45 |
46 | DEPRECATED TEST: ID:
47 |
48 |
49 |
50 |
51 |
52 |
53 | - the object child element of a httpd_test must reference a httpd_object
54 |
55 |
56 | - the state child element of a httpd_test must reference a httpd_state
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 | The httpd_object element is used by a httpd test to define the different httpd binary installed on a system. There is actually only one object relating to this and it is the collection of all httpd binaries. Therefore, there are no child entities defined. Any OVAL Test written to check version will reference the same httpd_object which is basically an empty object element. A tool that implements the httpd_test and collects the httpd_object must know how to find all the httpd binaries on the system and verify that they are in fact httpd binaries.
75 |
76 |
77 | 5.8
78 | The httpd_object does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
79 | This object has been deprecated and may be removed in a future version of the language.
80 |
81 |
82 |
83 | DEPRECATED OBJECT: ID:
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
92 |
93 |
94 |
95 |
96 | The httpd_state element defines information associated with a specific httpd binary.
97 |
98 |
99 | 5.8
100 | The httpd_state does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
101 | This state has been deprecated and may be removed in a future version of the language.
102 |
103 |
104 |
105 | DEPRECATED STATE: ID:
106 |
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 |
115 |
116 | The path element specifies the directory component of the absolute path to a httpd binary on the system.
117 |
118 |
119 |
120 |
121 | The binary_name element specifies the name of the file. If the xsi:nil attribute is set to true, then the object being specified is the higher level path. In this case, the binary_name element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match, says to collect every file under a given path.
122 |
123 |
124 |
125 |
126 | The version entity is used to check the version of the httpd binary. The datatype for the version entity is 'version' which means the value should be a delimited set of numbers. It is obtained by running 'httpd -v'.
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
--------------------------------------------------------------------------------
/schemas/apache-system-characteristics-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 | The following is a description of the elements, types, and attributes that compose the Apache specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard item element defined in the Core System Characteristic Schema. Through extension, each item inherits a set of elements and attributes that are shared amongst all OVAL Items. Each item is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core System Characteristic Schema is not outlined here.
12 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
13 |
14 | Apache System Characteristics
15 | 5.11.1:1.1
16 | 11/30/2016 09:00:00 AM
17 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 | The httpd item holds information about a installed Apache HTTPD binary. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.
29 |
30 |
31 | 5.8
32 | The httpd_item does not specify how to detect instances of httpd and cannot be reasonably specified to allow for products to detect all instances of httpd across platforms, packaging systems, and typical user compiled and configured installations. Without a proper definition of how to identify instances of httpd products will not reliably produce consistent assessment results because they will naturally utilize different approaches to locating instances of httpd which will lead to differences in the set of collected instances of https.
33 | This item has been deprecated and may be removed in a future version of the language.
34 |
35 |
36 |
37 | DEPRECATED ITEM: ID:
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 | The path element specifies the directory component of the absolute path to a httpd binary found on the system.
49 |
50 |
51 |
52 |
53 | The name of the httpd binary.
54 |
55 |
56 |
57 |
58 | The version entity holds the version of the specified httpd binary.
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
--------------------------------------------------------------------------------
/schemas/catos-system-characteristics-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 | The following is a description of the elements, types, and attributes that compose the Cisco CatOS specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
12 | This schema was originally developed by Yuzheng Zhou at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
13 |
14 | CatOS System Characteristics
15 | 5.11.1:1.1
16 | 11/30/2016 09:00:00 AM
17 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 | Stores the properties of specific lines in the catos config file.
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 | The name of the SHOW sub-command.
37 |
38 |
39 |
40 |
41 | The value returned from by the specified SHOW sub-command.
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 | Stores results from SHOW MODULE command.
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
92 |
93 |
94 |
95 |
96 |
97 |
98 |
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 |
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 |
115 |
116 |
117 |
118 |
119 |
120 | Stores results from SHOW VERSION command.
121 |
122 |
123 |
124 |
125 |
126 |
127 |
128 | The switch_series entity specifies the target Catalyst switch series for the given version of CatOS.
129 |
130 |
131 |
132 |
133 | The image_name entity specifies the name of the CatOS image.
134 |
135 |
136 |
137 |
138 | The catos_release entity specifies the release version of CatOS.
139 |
140 |
141 |
142 |
143 |
144 |
145 | 5.5
146 | Due to the fact it's not clear on how to separate the CatOS version, it was decided that the catos_major_release, catos_individual_release, and catos_version_id entities would be combined into a new single entity catos_release. Therefore, the catos_major_release entity is no longer needed.
147 | This entity has been deprecated and will be removed in version 6.0 of the language.
148 |
149 |
150 |
151 | DEPRECATED ELEMENT: ID:
152 |
153 |
154 |
155 |
156 |
157 |
158 |
159 |
160 |
161 | 5.5
162 | Due to the fact it's not clear on how to separate the CatOS version, it was decided that the catos_major_release, catos_individual_release, and catos_version_id entities would be combined into a new single entity catos_release. Therefore, the catos_individual_release entity is no longer needed.
163 | This entity has been deprecated and will be removed in version 6.0 of the language.
164 |
165 |
166 |
167 | DEPRECATED ELEMENT: ID:
168 |
169 |
170 |
171 |
172 |
173 |
174 |
175 |
176 |
177 | 5.5
178 | Due to the fact it's not clear on how to separate the CatOS version, it was decided that the catos_major_release, catos_individual_release, and catos_version_id entities would be combined into a new single entity catos_release. Therefore, the catos_version_id entity is no longer needed.
179 | This entity has been deprecated and will be removed in version 6.0 of the language.
180 |
181 |
182 |
183 | DEPRECATED ELEMENT: ID:
184 |
185 |
186 |
187 |
188 |
189 |
190 |
191 |
192 |
193 |
194 |
195 |
196 |
197 |
198 |
--------------------------------------------------------------------------------
/schemas/evaluation-ids.xsd:
--------------------------------------------------------------------------------
1 |
4 |
5 |
6 | This schema defines an xml format for inputing a set of OVAL Definition ids into the reference OVAL Interpreter for evaluation.
7 |
8 | OVAL Definition Interpreter - Evaluation Id Schema
9 | 5.11.2
10 | 11/30/2016 09:00:00 AM
11 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
12 |
13 |
14 |
15 |
16 |
17 | The evaluation-definition-ids element is the root the Document. Its purpose is to bind together the a set of definition elements.
18 |
19 |
20 |
21 |
22 |
23 | Each definition represents the id of a definition to be evaluated.
24 |
25 |
26 |
27 |
28 |
29 |
30 | Enforce uniqueness amongst the definition ids found in the document.
31 |
32 |
33 |
34 |
35 |
36 |
37 |
--------------------------------------------------------------------------------
/schemas/freebsd-definitions-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 |
12 | The following is a description of the elements, types, and attributes that compose the FreeBSD specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
13 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
14 |
15 | FreeBSD Definition
16 | 5.11.1:1.1
17 | 11/30/2016 09:00:00 AM
18 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 | The port info test is used to check the properties of a component of a FreeBSD system. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an portinfo_object and the optional state element specifies the data to check.
31 |
32 |
33 | portinfo_test
34 | portinfo_object
35 | portinfo_state
36 | portinfo_item
37 |
38 |
39 |
40 |
41 |
42 | - the object child element of a portinfo_test must reference an portinfo_object
43 |
44 |
45 | - the state child element of a portinfo_test must reference an portinfo_state
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 | The portinfo_object element is used by a port info test to define the specific FreeBSD package to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
64 | A port info object consists of a single pkginst element that identifies a specific package.
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 | State referenced in filter for '' is of the wrong type.
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
92 |
93 |
94 |
95 |
96 |
97 |
98 |
99 |
100 |
101 | The portinfo_state element defines the different information that can be used to evaluate the specified package. This includes the name, category, version, vendor, and description. Please refer to the individual elements in the schema for more details about what each represents.
102 |
103 |
104 |
105 |
106 |
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 | The name of a package.
115 |
116 |
117 |
118 |
119 |
120 |
121 |
122 |
123 |
124 | The version of a package.
125 |
126 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
139 |
140 |
141 |
142 |
143 |
144 |
145 |
146 |
147 |
148 |
149 |
150 |
151 |
152 |
153 |
154 |
155 |
156 |
157 |
158 |
159 |
160 |
--------------------------------------------------------------------------------
/schemas/freebsd-system-characteristics-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 |
12 | The following is a description of the elements, types, and attributes that compose the FreeBSD specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
13 | The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
14 |
15 | FreeBSD System Characteristics
16 | 5.11.1:1.1
17 | 11/30/2016 09:00:00 AM
18 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
--------------------------------------------------------------------------------
/schemas/netconf-definitions-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 | The following is a description of the elements, types, and attributes that compose the NETCONF (RFC 6241) protocol-specific tests found in Open Vulnerability and Assessment Language (OVAL). Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here
12 | This schema was originally developed by David Solin at jOVAL.org. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
13 |
14 | NETCONF Definitions
15 | 5.11.1:1.1
16 | 11/30/2016 09:00:00 AM
17 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 | The config_test is used to check the properties of the XML output from a GET-CONFIG command, for the running configuration. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a config_object and the optional state element specifies the data to check.
29 |
30 |
31 | config_test
32 | config_object
33 | config_state
34 | config_item
35 |
36 |
37 |
38 |
39 |
40 | - the object child element of a config_test must reference a config_object
41 |
42 |
43 | - the state child element of a config_test must reference a config_state
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 | The config_object element is used by a config_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
62 | A config_object consists of an xpath entity that contains an XPATH 1.0 query to perform on the NETCONF get-config response XML data. The response data is assumed to consist of a <data> entity in the urn:ietf:params:xml:ns:netconf:base:1.0 XML namespace, with arbitrary (i.e., vendor-specific) child nodes.
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 | State referenced in filter for '' is of the wrong type.
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 | Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. Any valid Xpath 1.0 statement is usable with one exception, at most one field may be identified in the Xpath. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible.
87 |
88 |
89 |
90 | - operation attribute for the xpath entity of a config_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one)
91 |
92 |
93 |
94 |
95 |
96 |
97 |
98 |
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 | The config_state element defines the different information that can be used to evaluate the result of a specific config xpath evaluation. This includes the xpath used and the value of this xpath.
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 | Specifies an Xpath expression describing the text node(s) or attribute(s) to look at.
115 |
116 |
117 |
118 |
119 | The value_of element checks the value(s) of the text node(s) or attribute(s) found.
120 |
121 |
122 |
123 |
124 |
125 |
126 |
127 |
128 |
--------------------------------------------------------------------------------
/schemas/netconf-system-characteristics-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
8 |
9 |
10 | This document outlines the items of the OVAL System Characteristics XML schema that are composed of NETCONF (RFC 6241) protocol-specific tests. Each item is an extention of a basic System Characteristics item defined in the core System Characteristics XML schema.
11 | This schema was originally developed by David Solin at jOVAL.org. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
12 |
13 | NETCONF System Characteristics
14 | 5.11.1:1.1
15 | 11/30/2016 09:00:00 AM
16 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 | This item stores results from checking the contents of an xml configuration.
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 | Specifies an Xpath expression describing the text node(s) or attribute(s) to look at.
36 |
37 |
38 |
39 |
40 | The value_of element checks the value(s) of the text node(s) or attribute(s) found. How this is used is entirely controlled by operator attributes.
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
--------------------------------------------------------------------------------
/schemas/oval-directives-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
10 |
11 |
12 |
13 |
14 | The following is a description of the elements, types, and attributes that compose the core schema for encoding Open Vulnerability and Assessment Language (OVAL) Directives. Each of the elements, types, and attributes that make up the Core Directives Schema are described in detail and should provide the information necessary to understand what each object represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between these objects is not outlined here.
15 | The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.
16 |
17 | Core Directives
18 | 5.11.2
19 | 11/30/2016 09:00:00 AM
20 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | The oval_directives element is the root of an OVAL Directive Document. Its purpose is to bind together the generator and the set of directives contained in the document. The generator section must be present and provides information about when the directives document was compiled and under what version. The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrity to be provided to the user. Enveloped signatures are supported. More information about the official W3C Recommendation regarding XML digital signatures can be found at http://www.w3.org/TR/xmldsig-core/.
30 |
31 |
32 |
33 |
34 |
35 | The required generator section provides information about when the directives document was compiled and under what version.
36 |
37 |
38 |
39 |
40 | The required directives section presents flags describing what information must be been included in an oval results document. This element represents the default set of directives. These directives apply to all classes of definitions for which there is not a class specific set of directives.
41 |
42 |
43 |
44 |
45 | The optional class_directives section presents flags describing what information has been included in the results document for a specific OVAL Definition class. The directives for a particlar class override the default directives.
46 |
47 |
48 |
49 |
50 | The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrity to be provided to the user. Enveloped signatures are supported. More information about the official W3C Recommendation regarding XML digital signatures can be found at http://www.w3.org/TR/xmldsig-core/.
51 |
52 |
53 |
54 |
55 |
56 |
57 | The class attribute on class_directives must be unique.
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
71 |
72 |
73 |
74 |
78 |
79 |
80 |
81 |
85 |
86 |
--------------------------------------------------------------------------------
/schemas/oval-variables-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
9 |
10 |
11 |
12 |
13 | The following is a description of the elements, types, and attributes that compose the core schema for encoding Open Vulnerability and Assessment Language (OVAL) Variables. This schema is provided to give structure to any external variables and their values that an OVAL Definition is expecting.
14 | The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.
15 |
16 | Core Variable
17 | 5.11.2
18 | 11/30/2016 09:00:00 AM
19 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 | The oval_variables element is the root of an OVAL Variable Document. Its purpose is to bind together the different variables contained in the document. The generator section must be present and provides information about when the variable file was compiled and under what version. The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrity to be provided to the user. Enveloped signatures are supported. More information about the official W3C Recommendation regarding XML digital signatures can be found at http://www.w3.org/TR/xmldsig-core/.
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 | Enforce uniqueness amongst the variable ids found in the variable document.
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
52 |
53 |
54 |
55 |
56 |
57 | The VariablesType complex type is a container for one or more variable elements. Each variable element holds the value of an external variable used in an OVAL Definition. Please refer to the description of the VariableType for more information about an individual variable.
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 | Each variable element contains the associated datatype and value which will be substituted into the OVAL Definition that is referencing this specific variable.
66 | The notes section of a variable should be used to hold information that might be helpful to someone examining the technical aspects of the variable. Please refer to the description of the NotesType complex type for more information about the notes element.
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 | Note that the 'record' datatype is not permitted on variables.
76 |
77 |
78 |
79 |
80 | Use to specify multiple variable instances.
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
94 |
95 |
96 |
97 |
98 |
--------------------------------------------------------------------------------
/schemas/pixos-system-characteristics-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
8 |
9 |
10 | The following is a description of the elements, types, and attributes that compose the Cisco PIX (Private Internet Exchange) specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
11 | This schema was originally developed by Yuzheng Zhou and Eric Grey at Hewlett-Packard. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org.
12 |
13 | PixOS System Characteristics
14 | 5.11.1:1.1
15 | 11/30/2016 09:00:00 AM
16 | Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 | Stores the properties of specific lines in the PIX config file.
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 | The name of the SHOW sub-command.
36 |
37 |
38 |
39 |
40 | The value returned from by the specified SHOW sub-command.
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 | Stores results from SHOW VERSION command.
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
--------------------------------------------------------------------------------
/schemas/xmldsig-core-schema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
3 |
18 |
19 |
20 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
92 |
93 |
94 |
95 |
96 |
97 |
98 |
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 |
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 |
115 |
116 |
117 |
118 |
119 |
120 |
121 |
122 |
123 |
124 |
125 |
126 |
127 |
128 |
129 |
130 |
131 |
132 |
133 |
134 |
135 |
136 |
137 |
138 |
139 |
140 |
141 |
142 |
143 |
144 |
145 |
146 |
147 |
148 |
149 |
150 |
151 |
152 |
153 |
154 |
155 |
156 |
157 |
158 |
159 |
160 |
161 |
162 |
163 |
164 |
165 |
166 |
167 |
168 |
169 |
170 |
171 |
172 |
173 |
174 |
175 |
176 |
177 |
178 |
179 |
180 |
181 |
182 |
183 |
184 |
185 |
186 |
187 |
188 |
189 |
190 |
191 |
192 |
193 |
194 |
195 |
196 |
197 |
198 |
199 |
200 |
201 |
202 |
203 |
204 |
205 |
207 |
208 |
209 |
210 |
212 |
213 |
214 |
215 |
216 |
217 |
218 |
219 |
220 |
221 |
222 |
223 |
224 |
225 |
226 |
227 |
228 |
229 |
230 |
231 |
232 |
233 |
234 |
235 |
236 |
237 |
238 |
239 |
240 |
241 |
242 |
243 |
244 |
245 |
246 |
247 |
248 |
249 |
250 |
251 |
252 |
253 |
254 |
255 |
256 |
257 |
258 |
259 |
260 |
261 |
262 |
263 |
264 |
265 |
266 |
267 |
268 |
269 |
270 |
271 |
272 |
273 |
274 |
275 |
276 |
277 |
278 |
279 |
280 |
281 |
282 |
283 |
284 |
285 |
286 |
287 |
288 |
289 |
290 |
291 |
292 |
293 |
294 |
295 |
296 |
297 |
298 |
299 |
300 |
301 |
302 |
303 |
304 |
305 |
306 |
307 |
308 |
309 |
310 |
--------------------------------------------------------------------------------
/specifications/oval-language-specification.docx:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OVALProject/Language/7a3efac6429f9378fea3b3929cdf316ecf14d491/specifications/oval-language-specification.docx
--------------------------------------------------------------------------------
/specifications/oval-unix-extension-specification.docx:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OVALProject/Language/7a3efac6429f9378fea3b3929cdf316ecf14d491/specifications/oval-unix-extension-specification.docx
--------------------------------------------------------------------------------
/specifications/oval-windows-extension-specification.docx:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OVALProject/Language/7a3efac6429f9378fea3b3929cdf316ecf14d491/specifications/oval-windows-extension-specification.docx
--------------------------------------------------------------------------------
/tools/ExtractSchFromXSD.xsl:
--------------------------------------------------------------------------------
1 |
2 |
8 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
40 |
41 |
42 |
43 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
--------------------------------------------------------------------------------