The following is a description of the elements, types, and attributes that compose the Windows 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.
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.
Windows Definition
5.7
5/3/2010 8:41:21 PM
Copyright (c) 2002-2010, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at http://oval.mitre.org/oval/about/termsofuse.html. 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.
- the value "" found in platform element as part of the affected element is not a valid windows platform.
The accesstoken_test is used to check the properties of a Windows access token as well as individual privileges and rights associated with it. 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 accesstoken_object and the optional state element specifies the data to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of an accesstoken_test must reference an accesstoken_object
- the state child element of an accesstoken_test must reference an accesstoken_state
The accesstoken_object element is used by an access token test to define the object to be evaluated. Each object extends the standard ObjectType as definied 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.
An accesstoken_object consists of a single security principal that identifies user, group, or computer account that is associated with the token.
The security_principle element defines the access token being specified. Security principals include users or groups with either local or domain accounts, and computer accounts created when a computer joins a domain. User rights and permissions to access objects such as Active Directory objects, files, and registry settings are assigned to security principals. In a domain environment, security principals should be identified in the form: "domain\trustee name". For local security principals use: "computer name\trustee name". For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in security principals should be all caps as that is how the Windows APIs return them. If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the Local Security Authority database. The scope is limited here to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the security_principle entity of an accesstoken_object should be 'string'
The accesstoken_state element defines the different information that can be used to evaluate the specified access tokens. This includes the multitude of user rights and permissions that can be granted. Please refer to the individual elements in the schema for more details about what each represents.
The security_principle element identifies an access token to test for. Security principals include users or groups with either local or domain accounts, and computer accounts created when a computer joins a domain. User rights and permissions to access objects such as Active Directory objects, files, and registry settings are assigned to security principals. In a domain environment, security principals should be identified in the form: "domain\trustee name" For local security principals use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in security principals should be all caps as that is how the Windows APIs return them.
- datatype attribute for the security_principle entity of an accesstoken_state should be 'string'
If the seassignprimarytokenprivilege privilege is enabled, it allows a parent process to replace the access token that is associated with a child process.
- datatype attribute for the seassignprimarytokenprivilege entity of an accesstoken_state should be 'boolean'
If the seauditprivilege privilege is enabled, it allows a process to generate audit records in the security log. The security log can be used to trace unauthorized system access.
- datatype attribute for the seauditprivilege entity of an accesstoken_state should be 'boolean'
If the sebackupprivilege privilege is enabled, it allows the user to circumvent file and directory permissions to back up the system. The privilege is selected only when an application attempts access by using the NTFS backup application programming interface (API). Otherwise, normal file and directory permissions apply.
- datatype attribute for the sebackupprivilege entity of an accesstoken_state should be 'boolean'
If the sechangenotifyprivilege privilege is enabled, it allows the user to pass through folders to which the user otherwise has no access while navigating an object path in the NTFS file system or in the registry. This privilege does not allow the user to list the contents of a folder; it allows the user only to traverse its directories.
- datatype attribute for the sechangenotifyprivilege entity of an accesstoken_state should be 'boolean'
If the secreateglobalprivilege privilege is enabled, it allows the user to create named file mapping objects in the global namespace during Terminal Services sessions.
- datatype attribute for the secreateglobalprivilege entity of an accesstoken_state should be 'boolean'
If the secreatepagefileprivilege privilege is enabled, it allows the user to create and change the size of a pagefile.
- datatype attribute for the secreatepagefileprivilege entity of an accesstoken_state should be 'boolean'
If the secreatepermanentprivilege privilege is enabled, it allows a process to create a directory object in the object manager. It is useful to kernel-mode components that extend the object namespace. Components that are running in kernel mode have this privilege inherently.
- datatype attribute for the secreatepermanentprivilege entity of an accesstoken_state should be 'boolean'
If the secreatesymboliclinkprivilege privilege is enabled, it allows users to create symbolic links.
- datatype attribute for the secreatesymboliclinkprivilege entity of an accesstoken_state should be 'boolean'
If the secreatetokenprivilege privilege is enabled, it allows a process to create an access token by calling NtCreateToken() or other token-creating APIs.
- datatype attribute for the secreatetokenprivilege entity of an accesstoken_state should be 'boolean'
If the sedebugprivilege privilege is enabled, it allows the user to attach a debugger to any process. It provides access to sensitive and critical operating system components.
- datatype attribute for the sedebugprivilege entity of an accesstoken_state should be 'boolean'
If the seenabledelegationprivilege privilege is enabled, it allows the user to change the Trusted for Delegation setting on a user or computer object in Active Directory. The user or computer that is granted this privilege must also have write access to the account control flags on the object.
- datatype attribute for the seenabledelegationprivilege entity of an accesstoken_state should be 'boolean'
If the seimpersonateprivilege privilege is enabled, it allows the user to impersonate a client after authentication.
- datatype attribute for the seimpersonateprivilege entity of an accesstoken_state should be 'boolean'
If the seincreasebasepriorityprivilege privilege is enabled, it allows a user to increase the base priority class of a process.
- datatype attribute for the seincreasebasepriorityprivilege entity of an accesstoken_state should be 'boolean'
If the seincreasequotaprivilege privilege is enabled, it allows a process that has access to a second process to increase the processor quota assigned to the second process.
- datatype attribute for the seincreasequotaprivilege entity of an accesstoken_state should be 'boolean'
If the seincreaseworkingsetprivilege privilege is enabled, it allows a user to increase a process working set.
- datatype attribute for the seincreaseworkingsetprivilege entity of an accesstoken_state should be 'boolean'
If the seloaddriverprivilege privilege is enabled, it allows a user to install and remove drivers for Plug and Play devices.
- datatype attribute for the seloaddriverprivilege entity of an accesstoken_state should be 'boolean'
If the selockmemoryprivilege privilege is enabled, it allows a process to keep data in physical memory, which prevents the system from paging the data to virtual memory on disk.
- datatype attribute for the selockmemoryprivilege entity of an accesstoken_state should be 'boolean'
If the semachineaccountprivilege privilege is enabled, it allows the user to add a computer to a specific domain.
- datatype attribute for the semachineaccountprivilege entity of an accesstoken_state should be 'boolean'
If the semanagevolumeprivilege privilege is enabled, it allows a non-administrative or remote user to manage volumes or disks.
- datatype attribute for the semanagevolumeprivilege entity of an accesstoken_state should be 'boolean'
If the seprofilesingleprocessprivilege privilege is enabled, it allows a user to sample the performance of an application process.
- datatype attribute for the seprofilesingleprocessprivilege entity of an accesstoken_state should be 'boolean'
If the serelabelprivilege privilege is enabled, it allows a user to modify an object label.
- datatype attribute for the serelabelprivilege entity of an accesstoken_state should be 'boolean'
If the seremoteshutdownprivilege privilege is enabled, it allows a user to shut down a computer from a remote location on the network.
- datatype attribute for the seremoteshutdownprivilege entity of an accesstoken_state should be 'boolean'
If the serestoreprivilege privilege is enabled, it allows a user to circumvent file and directory permissions when restoring backed-up files and directories and to set any valid security principal as the owner of an object.
- datatype attribute for the serestoreprivilege entity of an accesstoken_state should be 'boolean'
If the sesecurityprivilege privilege is enabled, it allows a user to specify object access auditing options for individual resources such as files, Active Directory objects, and registry keys. A user who has this privilege can also view and clear the security log from Event Viewer.
- datatype attribute for the sesecurityprivilege entity of an accesstoken_state should be 'boolean'
If the seshutdownprivilege privilege is enabled, it allows a user to shut down the local computer.
- datatype attribute for the seshutdownprivilege entity of an accesstoken_state should be 'boolean'
If the sesyncagentprivilege privilege is enabled, it allows a process to read all objects and properties in the directory, regardless of the protection on the objects and properties. It is required in order to use Lightweight Directory Access Protocol (LDAP) directory synchronization (Dirsync) services.
- datatype attribute for the sesyncagentprivilege entity of an accesstoken_state should be 'boolean'
If the sesystemenvironmentprivilege privilege is enabled, it allows modification of system environment variables either by a process through an API or by a user through System Properties.
- datatype attribute for the sesystemenvironmentprivilege entity of an accesstoken_state should be 'boolean'
If the sesystemprofileprivilege privilege is enabled, it allows a user to sample the performance of system processes.
- datatype attribute for the sesystemprofileprivilege entity of an accesstoken_state should be 'boolean'
If the sesystemtimeprivilege privilege is enabled, it allows the user to adjust the time on the computer's internal clock. It is not required to change the time zone or other display characteristics of the system time.
- datatype attribute for the sesystemtimeprivilege entity of an accesstoken_state should be 'boolean'
If the setakeownershipprivilege privilege is enabled, it allows a user to take ownership of any securable object in the system, including Active Directory objects, NTFS files and folders, printers, registry keys, services, processes, and threads.
- datatype attribute for the setakeownershipprivilege entity of an accesstoken_state should be 'boolean'
If the setcbprivilege privilege is enabled, it allows a process to assume the identity of any user and thus gain access to the resources that the user is authorized to access.
- datatype attribute for the setcbprivilege entity of an accesstoken_state should be 'boolean'
If the setimezoneprivilege privilege is enabled, it allows the user to change the time zone.
- datatype attribute for the setimezoneprivilege entity of an accesstoken_state should be 'boolean'
If the seundockprivilege privilege is enabled, it allows the user of a portable computer to undock the computer by clicking Eject PC on the Start menu.
- datatype attribute for the seundockprivilege entity of an accesstoken_state should be 'boolean'
If the seunsolicitedinputprivilege privilege is enabled, it allows the user to read unsolicited data from a terminal device.
- datatype attribute for the seunsolicitedinputprivilege entity of an accesstoken_state should be 'boolean'
If an account is assigned the sebatchlogonright right, it can log on using the batch logon type.
- datatype attribute for the sebatchlogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the seinteractivelogonright right, it can log on using the interactive logon type.
- datatype attribute for the seinteractivelogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the senetworklogonright right, it can log on using the network logon type.
- datatype attribute for the senetworklogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the seremoteinteractivelogonright right, it can log on to the computer by using a Remote Desktop connection.
- datatype attribute for the seremoteinteractivelogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the seservicelogonright right, it can log on using the service logon type.
- datatype attribute for the seservicelogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the sedenybatchLogonright right, it is explicitly denied the ability to log on using the batch logon type.
- datatype attribute for the sedenybatchLogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the sedenyinteractivelogonright right, it is explicitly denied the ability to log on using the interactive logon type.
- datatype attribute for the sedenyinteractivelogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the sedenynetworklogonright right, it is explicitly denied the ability to log on using the network logon type.
- datatype attribute for the sedenynetworklogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the sedenyremoteInteractivelogonright right, it is explicitly denied the ability to log on through Terminal Services.
- datatype attribute for the sedenyremoteInteractivelogonright entity of an accesstoken_state should be 'boolean'
If an account is assigned the sedenyservicelogonright right, it is explicitly denied the ability to log on using the service logon type.
- datatype attribute for the sedenyservicelogonright entity of an accesstoken_state should be 'boolean'
The AccesstokenBehaviors complex type defines a number of behaviors that allow a more detailed definition of the accesstoken_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
If a group security principal is specified, this behavior specifies whether to include the group or not. For example, maybe you want to check the access tokens associated with every user within a group, but not the group itself. In this case, you would set the include_group behavior to 'false'. If the security_principle is not a group, then this behavior should be ignored.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved and any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: win-def:accesstoken_object
The active directory test is used to check information about specific entries in active directory. 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 activedirectory_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.7
Replaced by the activedirectory57_test. This test allows for single fields to be selected from active directory. A new test was created to allow more than one field to be selected in one statement. See the activedirectory57_test.
This object has been deprecated and may be removed in a future version of the language.
DEPRECATED TEST: ID:
- the object child element of an activedirectory_test must reference an activedirectory_object
- the state child element of an activedirectory_test must reference an activedirectory_state
The activedirectory_object element is used by an active directory test to define those objects to evaluated based on a specified state. Each object extends the standard ObjectType as definied 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.
An active directory object consists of three pieces of information, a naming context, a relative distinguished name, and an attribute. Each piece helps identify a specific active directory entry.
5.7
Replaced by the activedirectory57_object. This object allows for single fields to be selected from active directory. A new object was created to allow more than one field to be selected in one statement. See the activedirectory57_object.
This object has been deprecated and may be removed in a future version of the language.
DEPRECATED OBJECT: ID:
Each object in active directory exists under a certain naming context (also known as a partition). A naming context is defined as a single object in the Directory Information Tree (DIT) along with every object in the tree subordinate to it. There are three default naming contexts in Active Directory: domain, configuration, and schema.
- datatype attribute for the naming_context entity of an activedirectory_object should be 'string'
The relative_dn field is used to uniquely identify an object inside the specified naming context. It contains all the parts of the object's distinguished name except those outlined by the naming context. If the xsi:nil attribute is set to true, then the object being specified is the higher level naming context. In this case, the relative_dn element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every relative dn under a given naming context.
- datatype attribute for the relative_dn entity of an activedirectory_object should be 'string'
Specifies a named value contained by the object. If the xsi:nil attribute is set to true, the attribute element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every attribute under a given relative dn.
- datatype attribute for the attribute entity of an activedirectory_object should be 'string'
The activedirectory_state element defines the different information that can be used to evaluate the specified entries in active directory. An active directory test will reference a specific instance of this state that defines the exact settings that need to be evaluated. Please refer to the individual elements in the schema for more details about what each represents.
5.7
Replaced by the activedirectory57_state. This state allows for single fields to be selected from active directory. A new state was created to allow more than one field to be selected in one statement. See the activedirectory57_state.
This object has been deprecated and may be removed in a future version of the language.
DEPRECATED STATE: ID:
Each object in active directory exists under a certain naming context (also known as a partition). A naming context is defined as a single object in the Directory Information Tree (DIT) along with every object in the tree subordinate to it. There are three default naming contexts in Active Directory: domain, configuration, and schema.
- datatype attribute for the naming_context entity of an activedirectory_state should be 'string'
The relative_dn field is used to uniquely identify an object inside the specified naming context. It contains all the parts of the objects distinguished name except those outlined by the naming context.
- datatype attribute for the relative_dn entity of an activedirectory_state should be 'string'
Specifies a named value contained by the object.
- datatype attribute for the attribute entity of an activedirectory_state should be 'string'
The name of the class of which the object is an instance.
- datatype attribute for the object_class entity of an activedirectory_state should be 'string'
Specifies the type of information that the specified attribute represents.
- datatype attribute for the adstype entity of an activedirectory_state should be 'string'
The actual value of the specified active directory attribute.
- datatype attribute for the entity of an should not be 'record'
The active directory test is used to check information about specific entries in active directory. 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 activedirectory57_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of an activedirectory57_test must reference an activedirectory57_object
- the state child element of an activedirectory57_test must reference an activedirectory57_state
The activedirectory57_object element is used by an active directory test to define those objects to evaluated based on a specified state. Each object extends the standard ObjectType as definied 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.
An active directory object consists of three pieces of information, a naming context, a relative distinguished name, and an attribute. Each piece helps identify a specific active directory entry.
Each object in active directory exists under a certain naming context (also known as a partition). A naming context is defined as a single object in the Directory Information Tree (DIT) along with every object in the tree subordinate to it. There are three default naming contexts in Active Directory: domain, configuration, and schema.
- datatype attribute for the naming_context entity of an activedirectory57_object should be 'string'
The relative_dn field is used to uniquely identify an object inside the specified naming context. It contains all the parts of the object's distinguished name except those outlined by the naming context. If the xsi:nil attribute is set to true, then the object being specified is the higher level naming context. In this case, the relative_dn element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every relative dn under a given naming context.
- datatype attribute for the relative_dn entity of an activedirectory57_object should be 'string'
Specifies a named value contained by the object. If the xsi:nil attribute is set to true, the attribute element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every attribute under a given relative dn.
- datatype attribute for the attribute entity of an activedirectory57_object should be 'string'
The activedirectory57_state element defines the different information that can be used to evaluate the specified entries in active directory. An active directory test will reference a specific instance of this state that defines the exact settings that need to be evaluated. Please refer to the individual elements in the schema for more details about what each represents.
Each object in active directory exists under a certain naming context (also known as a partition). A naming context is defined as a single object in the Directory Information Tree (DIT) along with every object in the tree subordinate to it. There are three default naming contexts in Active Directory: domain, configuration, and schema.
- datatype attribute for the naming_context entity of an activedirectory57_state should be 'string'
The relative_dn field is used to uniquely identify an object inside the specified naming context. It contains all the parts of the objects distinguished name except those outlined by the naming context.
- datatype attribute for the relative_dn entity of an activedirectory57_state should be 'string'
Specifies a named value contained by the object.
- datatype attribute for the attribute entity of an activedirectory57_state should be 'string'
The name of the class of which the object is an instance.
- datatype attribute for the object_class entity of an activedirectory57_state should be 'string'
The type of information that the specified attribute represents.
- datatype attribute for the adstype entity of an activedirectory57_state should be 'string'
The value of the specified active directory attribute.
- datatype attribute for the entity of an should be 'record'
The auditeventpolicy_test is used to check different types of events the system should audit. 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 auditeventpolicy_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of an auditeventpolicy_test must reference an auditeventpolicy_object
- the state child element of an auditeventpolicy_test must reference an auditeventpolicy_state
The auditeventpolicy_object element is used by an audit event policy test to define those objects to evaluate based on a specified state. There is actually only one object relating to audit event policy and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check audit event policy will reference the same auditeventpolicy_object which is basically an empty object element.
The auditeventpolicy_state element specifies the different system activities that can be audited. An audit event policy test will reference a specific instance of this state that defines the exact settings that need to be evaluated. The defined values are found in window's POLICY_AUDIT_EVENT_TYPE enumeration and accessed through the LsaQueryInformationPolicy when the InformationClass parameters are set to PolicyAuditEventsInformation. Please refer to the individual elements in the schema for more details about what each represents.
Audit attempts to log on to or log off of the system. Also, audit attempts to make a network connection.
- datatype attribute for the account_logon entity of an auditeventpolicy_state should be 'string'
Audit attempts to create, delete, or change user or group accounts. Also, audit password changes.
- datatype attribute for the account_management entity of an auditeventpolicy_state should be 'string'
Audit specific events, such as program activation, some forms of handle duplication, indirect access to an object, and process exit. Note that this activitiy is also known as process tracking.
- datatype attribute for the detailed_tracking entity of an auditeventpolicy_state should be 'string'
Audit attempts to access the directory service.
- datatype attribute for the directory_service_access entity of an auditeventpolicy_state should be 'string'
Audit attempts to log on to or log off of the system. Also, audit attempts to make a network connection.
- datatype attribute for the logon entity of an auditeventpolicy_state should be 'string'
Audit attempts to access securable objects, such as files.
- datatype attribute for the object_access entity of an auditeventpolicy_state should be 'string'
Audit attempts to change Policy object rules.
- datatype attribute for the policy_change entity of an auditeventpolicy_state should be 'string'
Audit attempts to use privileges.
- datatype attribute for the privilege_use entity of an auditeventpolicy_state should be 'string'
Audit attempts to shut down or restart the computer. Also, audit events that affect system security or the security log.
- datatype attribute for the system entity of an auditeventpolicy_state should be 'string'
The auditeventpolicysubcategories_test is used to check the audit event policy settings on a Windows system. These settings are used to specify which system and network events are monitored. For example, if the credential_validation element has a value of AUDIT_FAILURE, it means that the system is configured to log all unsuccessful attempts to validate a user account on a system. It is important to note that these audit event policy settings are specific to certain versions of Windows. As a result, the documentation for that version of Windows should be consulted for more information on each setting. The test 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 auditeventpolicy_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of an auditeventpolicysubcategories_test must reference an auditeventpolicysubcategories_object
- the state child element of an auditeventpolicysubcategories_test must reference an auditeventpolicysubcategories_state
The auditeventpolicysubcategories_object element is used by an audit event policy subcategories test to define those objects to evaluate based on a specified state. There is actually only one object relating to audit event policy subcategories and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check audit event policy subcategories will reference the same auditeventpolicysubcategories_object which is basically an empty object element.
The auditeventpolicysubcategories_state element specifies the different system activities that can be audited. An audit event policy subcategories test will reference a specific instance of this state that defines the exact subcategories that need to be evaluated. Please refer to the individual elements in the schema for more details about what each represents.
Audit the events produced during the validation of a user's logon credentials.
- datatype attribute for the credential_validation entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by Kerberos authentication ticket-granting requests.
- datatype attribute for the kerberos_authentication_service entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by Kerberos service ticket requests.
- datatype attribute for the kerberos_service_ticket_operations entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced during the validation of Kerberos tickets provided for a user account logon request.
- datatype attribute for the kerberos_ticket_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to user accounts that are not covered by other events in the Account Logon category.
- datatype attribute for the other_account_logon_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to application groups.
- datatype attribute for the application_group_management entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to computer accounts.
- datatype attribute for the computer_account_management entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to distribution groups.
- datatype attribute for the distribution_group_management entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by other user account changes that are not covered by other events in the Account Management category.
- datatype attribute for the other_account_management_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to security groups.
- datatype attribute for the security_group_management entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to user accounts.
- datatype attribute for the user_account_management entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when requests are made to the Data Protection application interface.
- datatype attribute for the dpapi_activity entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when a process is created or starts.
- datatype attribute for the process_creation entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when a process ends.
- datatype attribute for the process_termination entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by inbound remote procedure call connections.
- datatype attribute for the rpc_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when a Active Directory Domain Services object is accessed.
- datatype attribute for the directory_service_access entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when changes are made to Active Directory Domain Services objects.
- datatype attribute for the directory_service_changes entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when two Active Directory Domain Services domain controllers are replicated.
- datatype attribute for the directory_service_replication entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by detailed Active Directory Domain Services replication between domain controllers.
- datatype attribute for the detailed_directory_service_replication entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by a failed attempt to log onto a locked out account.
- datatype attribute for the account_lockout entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by Internet Key Exchange and Authenticated Internet protocol during Extended Mode negotiations.
- datatype attribute for the ipsec_extended_mode entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by Internet Key Exchange and Authenticated Internet protocol during Main Mode negotiations.
- datatype attribute for the ipsec_main_mode entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by Internet Key Exchange and Authenticated Internet protocol during Quick Mode negotiations.
- datatype attribute for the ipsec_quick_mode entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by closing a logon session.
- datatype attribute for the logoff entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by attempts to log onto a user account.
- datatype attribute for the logon entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by RADIUS and Network Access Protection user access requests.
- datatype attribute for the network_policy_server entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by other logon/logoff based events that are not covered in the Logon/Logoff category.
- datatype attribute for the other_logon_logoff_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by special logons.
- datatype attribute for the special_logon entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by applications that use the Windows Auditing API.
- datatype attribute for the application_generated entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by operations on Active Directory Certificate Services.
- datatype attribute for the certification_services entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by attempts to access files and folders on a shared folder.
- datatype attribute for the detailed_file_share entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by attempts to access a shared folder.
- datatype attribute for the file_share entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced user attempts to access file system objects.
- datatype attribute for the file_system entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by connections that are allowed or blocked by Windows Filtering Platform.
- datatype attribute for the filtering_platform_connection entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by packets that are dropped by Windows Filtering Platform.
- datatype attribute for the filtering_platform_packet_drop entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced when a handle is opened or closed.
- datatype attribute for the handle_manipulation entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by attempts to access the system kernel.
- datatype attribute for the kernel_object entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by the management of Task Scheduler jobs or COM+ objects.
- datatype attribute for the other_object_access_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by attempts to access registry objects.
- datatype attribute for the registry entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by attempts to access Security Accounts Manager objects.
- datatype attribute for the sam entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes in security audit policy settings.
- datatype attribute for the audit_policy_change entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to the authentication policy.
- datatype attribute for the authentication_policy_change entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to the authorization policy.
- datatype attribute for the authorization_policy_change entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to the Windows Filtering Platform.
- datatype attribute for the filtering_platform_policy_change entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes to policy rules used by the Windows Firewall.
- datatype attribute for the mpssvc_rule_level_policy_change entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by other security policy changes that are not covered other events in the Policy Change category.
- datatype attribute for the other_policy_change_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by the use of non-sensitive privileges.
- datatype attribute for the non_sensitive_privilege_use entity of an auditeventpolicysubcategories_state should be 'string'
This is currently not used and has been reserved by Microsoft for use in the future.
- datatype attribute for the other_privilege_use_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by the use of sensitive privileges.
- datatype attribute for the sensitive_privilege_use entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by the IPsec filter driver.
- datatype attribute for the ipsec_driver entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by the startup and shutdown, security policy processing, and cryptography key file and migration operations of the Windows Firewall.
- datatype attribute for the other_system_events entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by changes in the security state.
- datatype attribute for the security_state_change entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events produced by the security system extensions or services.
- datatype attribute for the security_system_extension entity of an auditeventpolicysubcategories_state should be 'string'
Audit the events that indicate that the integrity security subsystem has been violated.
- datatype attribute for the system_integrity entity of an auditeventpolicysubcategories_state should be 'string'
The dnscache_test is used to check the time to live and IP addresses associated with a domain name. The time to live and IP addresses for a particular domain name are retrieved from the DNS cache on the local system. The entries in the DNS cache can be collected using Microsoft's DnsGetCacheDataTable() and DnsQuery() API calls. 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 dnscache_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a dnscache_test must reference a dnscache_object
- the state child element of a dnscache_test must reference a dnscache_state
The dnscache_object is used by the dnscache_test to specify the domain name(s) that should be collected from the DNS cache on the local system. Each object extends the standard ObjectType as definied 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.
The domain_name element specifies the domain name(s) that should be collected from the DNS cache on the local system.
- datatype attribute for the domain_name entity of a dnscache_object should be 'string'
The dnscache_state contains three entities that are used to check the domain name, time to live, and IP addresses associated with the DNS cache entry.
The domain_name element contains a string that represents a domain name that was collected from the DNS cache on the local system.
- datatype attribute for the domain_name entity of a dnscache_state should be 'string'
The ttl element contains an integer that represents the time to live in seconds of the DNS cache entry.
- datatype attribute for the ttl entity of a dnscache_state should be 'int'
The ip_address element contains a string that represents an IP address associated with the specified domain name that was collected from the DNS cache on the local system. Note that the IP address can be IPv4 or IPv6.
- datatype attribute for the ip_address entity of a dnscache_state should be 'string'
The file test is used to check metadata associated with Windows files. 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 file_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a file_test must reference a file_object
- the state child element of a file_test must reference a file_state
The file_object element is used by a file test to define the specific file(s) to be evaluated. The file_object will collect directories and all Windows file types (FILE_TYPE_CHAR, FILE_TYPE_DISK, FILE_TYPE_PIPE, FILE_TYPE_REMOTE, and FILE_TYPE_UNKNOWN). Each object extends the standard ObjectType as definied 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.
A file object defines the path and filename or complete filepath of the file(s). In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FileBehaviors complex type for more information about specific behaviors.
The set of files to be evaluated may be identified with either a complete filepath or a path and filename. Only one of these options may be selected.
It is important to note that the 'max_depth' and 'recurse_direction' attributes of the 'behaviors' element do not apply to the 'filepath' element, only to the 'path' and 'filename' elements. This is because the 'filepath' element represents an absolute path to a particular file and it is not possible to recurse over a file.
The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.
- datatype attribute for the filepath entity of a file_object should be 'string'
- the max_depth and recurse_direction behaviors are not allowed with a filepath entity
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a file_object should be 'string'
The filename element specifies the name of a file to evaluate. If the xsi:nil attribute is set to true, then the object being specified is the higher level directory object (not all the files in the directory). In this case, the filename element should not be used during collection and would result in the unique set of collected objects being the directories themselves. For example, one would set xsi:nil to true if the desire was to test the attributes or permissions associated with a directory. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every file under a given path.
- datatype attribute for the filename entity of a file_object should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The file_state element defines the different metadata associate with a Windows file. This includes the path, filename, owner, size, last modified time, version, etc. Please refer to the individual elements in the schema for more details about what each represents.
The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.
- datatype attribute for the filepath entity of a file_state should be 'string'
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a file_state should be 'string'
The filename element specifies the name of the file.
- datatype attribute for the filename entity of a file_state should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The owner element is a string that contains the name of the owner. The name should be specified in the DOMAIN\username format.
- datatype attribute for the owner entity of a file_state should be 'string'
The size element is the size of the file in bytes.
- datatype attribute for the size entity of a file_state should be 'int'
Time of last access of file. Valid on NTFS but not on FAT formatted disk drives. The string should represent the FILETIME structure which is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC).
- datatype attribute for the a_time entity of a file_state should be 'int'
Time of creation of file. Valid on NTFS but not on FAT formatted disk drives. The string should represent the FILETIME structure which is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC).
- datatype attribute for the c_time entity of a file_state should be 'int'
Time of last modification of file. The string should represent the FILETIME structure which is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC).
- datatype attribute for the m_time entity of a file_state should be 'int'
The checksum of the file as supplied by Microsoft's MapFileAndCheckSum function.
- datatype attribute for the ms_checksum entity of a file_state should be 'string'
The version element is the delimited version string of the file.
- datatype attribute for the version entity of a file_state should be 'version'
The type element marks whether the file is a directory, named pipe, standard file, etc. These types are the return values for GetFileType, with the exception of FILE_ATTRIBUTE_DIRECTORY which is obtained by looking at GetFileAttributesEx. NOTE: Should this entity be split into two in future versions of the language as there are other values associated with GetFileAttributesEx that are not represented here?
- datatype attribute for the type entity of a file_state should be 'string'
The development_class element allows the distinction to be made between the GDR development environment and the QFE development environment. This field holds the text found in front of the mmmmmm-nnnn version, for example srv03_gdr.
- datatype attribute for the development_class entity of a file_state should be 'string'
This entity defines a company name to be found within the version-information structure.
- datatype attribute for the company entity of a file_state should be 'string'
This entity defines an internal name to be found within the version-information structure.
- datatype attribute for the internal_name entity of a file_state should be 'string'
This entity defines a language to be found within the version-information structure.
- datatype attribute for the language entity of a file_state should be 'string'
This entity defines an original filename to be found within the version-information structure.
- datatype attribute for the original_filename entity of a file_state should be 'string'
This entity defines a product name to be found within the version-information structure.
- datatype attribute for the product_name entity of a file_state should be 'string'
This entity defines a product version to be found within the version-information structure.
- datatype attribute for the product_version entity of a file_state should be 'string'
The FileBehaviors complex type defines a number of behaviors that allow a more detailed definition of the file_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
It is important to note that the 'max_depth' and 'recurse_direction' attributes of the 'behaviors' element do not apply to the 'filepath' element, only to the 'path' and 'filename' elements. This is because the 'filepath' element represents an absolute path to a particular file and it is not possible to recurse over a file.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent directories, or 'down' into child directories to recursively search for files. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'recurse_file_system' defines the file system limitation of any recursion, either 'local' limiting data collection to local file systems (as opposed to file systems mounted from an external system), or 'defined' to keep any recursion within the file system that the file_object (path+filename) has specified. The default value is 'all' meaning to use all available file systems for data collection.
The file audit permissions test is used to check the audit permissions associated with Windows files. 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 fileauditedpermissions_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a fileauditedpermissions53_test must reference a fileauditedpermissions53_object
- the state child element of a fileauditedpermissions53_test must reference a fileauditedpermissions53_state
The fileauditedpermissions53_object element is used by a file audited permissions test to define the objects used to evalutate against the specified state. The fileauditedpermissions53_object will collect directories and all Windows file types (FILE_TYPE_CHAR, FILE_TYPE_DISK, FILE_TYPE_PIPE, FILE_TYPE_REMOTE, and FILE_TYPE_UNKNOWN). Each object extends the standard ObjectType as definied 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.
A fileauditedpermissions53_object is defined as a combination of a Windows file and trustee sid. The file represents the file to be evaluated while the trustee sid represents the account (sid) to check audited permissions of. If multiple files or sids are matched by either reference, then each possible combination of file and sid is a matching file audited permissions object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FileAuditPermissions53Behaviors complex type for more information about specific behaviors.
The set of files to be evaluated may be identified with either a complete filepath or a path and filename. Only one of these options may be selected.
It is important to note that the 'max_depth' and 'recurse_direction' attributes of the 'behaviors' element do not apply to the 'filepath' element, only to the 'path' and 'filename' elements. This is because the 'filepath' element represents an absolute path to a particular file and it is not possible to recurse over a file.
The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.
- datatype attribute for the filepath entity of a fileauditedpermissions53_object should be 'string'
- the max_depth and recurse_direction behaviors are not allowed with a filepath entity
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileauditedpermissions53_object should be 'string'
The filename element specifies the name of a file to evaluate. If the xsi:nil attribute is set to true, then the object being specified is the higher level directory object (not all the files in the directory). In this case, the filename element should not be used during collection and would result in the unique set of collected objects being the directories themselves. For example, one would set xsi:nil to true if the desire was to test the attributes or permissions associated with a directory. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every file under a given path.
- datatype attribute for the filename entity of a fileauditedpermissions53_object should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_sid entity identifies a unique sid associated with a user, group, system, or program (such as a Windows service). If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the file's Security Descriptor. The scope is limited here to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the trustee_sid entity of a fileauditedpermissions53_object should be 'string'
The fileauditedpermissions53_state element defines the different audit permissions that can be associated with a given fileauditedpermissions53_object. Please refer to the individual elements in the schema for more details about what each represents.
The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.
- datatype attribute for the filepath entity of a fileauditedpermissions53_state should be 'string'
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileauditedpermissions53_state should be 'string'
The filename element specifies the name of a file to test for.
- datatype attribute for the filename entity of a fileauditedpermissions53_state should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_sid element is the unique sid that associated a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a fileauditedpermissions53_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a fileauditedpermissions53_state should be 'string'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a fileauditedpermissions53_state should be 'string'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a fileauditedpermissions53_state should be 'string'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a fileauditedpermissions53_state should be 'string'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a fileauditedpermissions53_state should be 'string'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a fileauditedpermissions53_state should be 'string'
Read access.
- datatype attribute for the generic_read entity of a fileauditedpermissions53_state should be 'string'
Write access.
- datatype attribute for the generic_write entity of a fileauditedpermissions53_state should be 'string'
Execute access.
- datatype attribute for the generic_execute entity of a fileauditedpermissions53_state should be 'string'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a fileauditedpermissions53_state should be 'string'
Grants the right to read data from the file.
- datatype attribute for the file_read_data entity of a fileauditedpermissions53_state should be 'string'
Grants the right to write data to the file.
- datatype attribute for the file_write_data entity of a fileauditedpermissions53_state should be 'string'
Grants the right to append data to the file.
- datatype attribute for the file_append_data entity of a fileauditedpermissions53_state should be 'string'
Grants the right to read extended attributes.
- datatype attribute for the file_read_ea entity of a fileauditedpermissions53_state should be 'string'
Grants the right to write extended attributes.
- datatype attribute for the file_write_ea entity of a fileauditedpermissions53_state should be 'string'
Grants the right to execute a file.
- datatype attribute for the file_execute entity of a fileauditedpermissions53_state should be 'string'
Right to delete a directory and all the files it contains (its children), even if the files are read-only.
- datatype attribute for the file_delete_child entity of a fileauditedpermissions53_state should be 'string'
Grants the right to read file attributes.
- datatype attribute for the file_read_attributes entity of a fileauditedpermissions53_state should be 'string'
Grants the right to change file attributes.
- datatype attribute for the file_write_attributes entity of a fileauditedpermissions53_state should be 'string'
The FileAuditPermissions53Behaviors complex type defines a number of behaviors that allow a more detailed definition of the fileauditpermissions53_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
It is important to note that the 'max_depth' and 'recurse_direction' attributes of the 'behaviors' element do not apply to the 'filepath' element, only to the 'path' and 'filename' elements. This is because the 'filepath' element represents an absolute path to a particular file and it is not possible to recurse over a file.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent directories, or 'down' into child directories to recursively search for files. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'recurse_file_system' defines the file system limitation of any recursion, either 'local' limiting data collection to local file systems (as opposed to file systems mounted from an external system), or 'defined' to keep any recursion within the file system that the file_object (path+filename) has specified. The default value is 'all' meaning to use all available file systems for data collection.
'include_group' defines whether the group sid should be included in the object when the object is defined by a group sid. For example, the intent of an object defined by a group sid might be to retrieve all the user sids that are a member of the group, but not the group sid itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: fileauditedpermissions53_object
The file audited permissions test is used to check the audit permissions associated with Windows files. 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 fileauditedpermissions_object, and the optional state element references a fileauditedpermissions_state that specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.3
Replaced by the fileauditedpermissions53_test. This test uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. See the fileauditedpermissions53_test.
This test has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED TEST: ID:
- the object child element of a fileauditedpermissions_test must reference a fileauditedpermissions_object
- the state child element of a fileauditedpermissions_test must reference a fileauditedpermissions_state
The fileauditedpermissions_object element is used by a file audited permissions test to define the objects used to evalutate against the specified state. The fileauditedpermissions_object will collect directories and all Windows file types (FILE_TYPE_CHAR, FILE_TYPE_DISK, FILE_TYPE_PIPE, FILE_TYPE_REMOTE, and FILE_TYPE_UNKNOWN). Each object extends the standard ObjectType as definied 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.
A fileauditedpermissions_object is defined as a combination of a Windows file and trustee name. The file represents the file to be evaluated while the trustee name represents the account (sid) to check audited permissions of. If multiple files or sids are matched by either reference, then each possible combination of file and sid is a matching file audited permissions object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FileAuditPermissionsBehaviors complex type for more information about specific behaviors.
5.3
Replaced by the fileauditedpermissions53_object. This object uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new object was created to use trustee SIDs, which are unique. See the fileauditedpermissions53_object.
This object has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED OBJECT: ID:
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileauditedpermissions_object should be 'string'
The filename element specifies the name of a file to evaluate. If the xsi:nil attribute is set to true, then the object being specified is the higher level directory object (not all the files in the directory). In this case, the filename element should not be used during collection and would result in the unique set of collected objects being the directories themselves. For example, one would set xsi:nil to true if the desire was to test the attributes or permissions associated with a directory. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every file under a given path.
- datatype attribute for the filename entity of a fileauditedpermissions_object should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_name element is the unique name that associated a particular SID. A SID can be associated with a user, group, or program (such as a Windows service). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a fileauditedpermissions_object should be 'string'
The fileauditedpermissions_state element defines the different audit permissions that can be associated with a given fileauditedpermissions_object. Please refer to the individual elements in the schema for more details about what each represents.
5.3
Replaced by the fileauditedpermissions53_state. This state uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new state was created to use trustee SIDs, which are unique. See the fileauditedpermissions53_state.
This state has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED STATE: ID:
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileauditedpermissions_state should be 'string'
The filename element specifies the name of a file to test for.
- datatype attribute for the filename entity of a fileauditedpermissions_state should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_name is the unique name associated with a particular security identifier (SID). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a fileauditedpermissions_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a fileauditedpermissions_state should be 'string'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a fileauditedpermissions_state should be 'string'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a fileauditedpermissions_state should be 'string'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a fileauditedpermissions_state should be 'string'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a fileauditedpermissions_state should be 'string'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a fileauditedpermissions_state should be 'string'
Read access.
- datatype attribute for the generic_read entity of a fileauditedpermissions_state should be 'string'
Write access.
- datatype attribute for the generic_write entity of a fileauditedpermissions_state should be 'string'
Execute access.
- datatype attribute for the generic_execute entity of a fileauditedpermissions_state should be 'string'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a fileauditedpermissions_state should be 'string'
Grants the right to read data from the file.
- datatype attribute for the file_read_data entity of a fileauditedpermissions_state should be 'string'
Grants the right to write data to the file.
- datatype attribute for the file_write_data entity of a fileauditedpermissions_state should be 'string'
Grants the right to append data to the file.
- datatype attribute for the file_append_data entity of a fileauditedpermissions_state should be 'string'
Grants the right to read extended attributes.
- datatype attribute for the file_read_ea entity of a fileauditedpermissions_state should be 'string'
Grants the right to write extended attributes.
- datatype attribute for the file_write_ea entity of a fileauditedpermissions_state should be 'string'
Grants the right to execute a file.
- datatype attribute for the file_execute entity of a fileauditedpermissions_state should be 'string'
Right to delete a directory and all the files it contains (its children), even if the files are read-only.
- datatype attribute for the file_delete_child entity of a fileauditedpermissions_state should be 'string'
Grants the right to read file attributes.
- datatype attribute for the file_read_attributes entity of a fileauditedpermissions_state should be 'string'
Grants the right to change file attributes.
- datatype attribute for the file_write_attributes entity of a fileauditedpermissions_state should be 'string'
The FileAuditPermissionsBehaviors complex type defines a number of behaviors that allow a more detailed definition of the fileauditpermissions_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
5.3
Replaced by the FileAuditPermissionsBehaviors53. The FileAuditPermissionsBehaviors complex type is used by the fileauditedpermissions_test which uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. This new test utilizes the FileAuditPermissionsBehaviors53 complex type, and as a result, the FileAuditPermissionsBehaviors complex type is no longer needed.
This complex type has been deprecated and will be removed in version 6.0 of the language.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent directories, or 'down' into child directories to recursively search for files. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'include_group' defines whether the group trustee name should be included in the object when the object is defined by a group trustee name. For example, the intent of an object defined by a group trustee name might be to retrieve all the user sids that are a member of the group, but not the group trustee name itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: fileauditedpermissions_object
The file effective rights test is used to check the effective rights associated with Windows files. Note that the trustee's effective access rights are the access rights that the ACL grants to the trustee or to any groups of which the trustee is a member. The fileeffectiverights53_test element 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 fileeffectiverights53_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a fileeffectiverights53_test must reference a fileeffectiverights53_object
- the state child element of a fileeffectiverights53_test must reference a fileeffectiverights53_state
The fileeffectiverights53_object element is used by a file effective rights test to define the objects used to evalutate against the specified state. The fileeffectiverights53_object will collect directories and all Windows file types (FILE_TYPE_CHAR, FILE_TYPE_DISK, FILE_TYPE_PIPE, FILE_TYPE_REMOTE, and FILE_TYPE_UNKNOWN). Each object extends the standard ObjectType as definied 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.
A fileeffectiverights53_object is defined as a combination of a Windows file and trustee sid. The file represents the file to be evaluated while the trustee sid represents the account (sid) to check effective rights of. If multiple files or sids are matched by either reference, then each possible combination of file and sid is a matching file effective rights object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FileEffectiveRights53Behaviors complex type for more information about specific behaviors.
The set of files to be evaluated may be identified with either a complete filepath or a path and filename. Only one of these options may be selected.
It is important to note that the 'max_depth' and 'recurse_direction' attributes of the 'behaviors' element do not apply to the 'filepath' element, only to the 'path' and 'filename' elements. This is because the 'filepath' element represents an absolute path to a particular file and it is not possible to recurse over a file.
The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.
- datatype attribute for the filepath entity of a fileeffectiverights53_object should be 'string'
- the max_depth and recurse_direction behaviors are not allowed with a filepath entity
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileeffectiverights53_object should be 'string'
The filename element specifies the name of a file to evaluate. If the xsi:nil attribute is set to true, then the object being specified is the higher level directory object (not all the files in the directory). In this case, the filename element should not be used during collection and would result in the unique set of collected objects being the directories themselves. For example, one would set xsi:nil to true if the desire was to test the attributes or permissions associated with a directory. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every file under a given path..
- datatype attribute for the filename entity of a fileeffectiverights53_object should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_sid entity identifies a unique sid associated with a user, group, system, or program (such as a Windows service). If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the file's Security Descriptor. The scope is limited here to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the trustee_sid entity of a fileeffectiverights53_object should be 'string'
The fileeffectiverights53_state element defines the different rights that can be associated with a given fileeffectiverights53_object. Please refer to the individual elements in the schema for more details about what each represents.
The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.
- datatype attribute for the filepath entity of a fileeffectiverights53_state should be 'string'
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileeffectiverights53_state should be 'string'
The filename element specifies the name of the file.
- datatype attribute for the filename entity of a fileeffectiverights53_state should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_sid element is the unique sid that associated a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a fileeffectiverights53_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a fileeffectiverights53_state should be 'boolean'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a fileeffectiverights53_state should be 'boolean'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a fileeffectiverights53_state should be 'boolean'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a fileeffectiverights53_state should be 'boolean'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a fileeffectiverights53_state should be 'boolean'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a fileeffectiverights53_state should be 'boolean'
Read access.
- datatype attribute for the generic_read entity of a fileeffectiverights53_state should be 'boolean'
Write access.
- datatype attribute for the generic_write entity of a fileeffectiverights53_state should be 'boolean'
Execute access.
- datatype attribute for the generic_execute entity of a fileeffectiverights53_state should be 'boolean'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to read data from the file, or if a directory, grants the right to list the contents of the directory.
- datatype attribute for the file_read_data entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to write data to the file, or if a directory, grants the right to add a file to the directory.
- datatype attribute for the file_write_data entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to append data to the file, or if a directory, grants the right to add a sub-directory to the directory.
- datatype attribute for the file_append_data entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to read extended attributes.
- datatype attribute for the file_read_ea entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to write extended attributes.
- datatype attribute for the file_write_ea entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to execute a file, or if a directory, the right to traverse the directory.
- datatype attribute for the file_execute entity of a fileeffectiverights53_state should be 'boolean'
Right to delete a directory and all the files it contains (its children), even if the files are read-only.
- datatype attribute for the file_delete_child entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to read file, or directory, attributes.
- datatype attribute for the file_read_attributes entity of a fileeffectiverights53_state should be 'boolean'
Grants the right to change file, or directory, attributes.
- datatype attribute for the file_write_attributes entity of a fileeffectiverights53_state should be 'boolean'
The FileEffectiveRights53Behaviors complex type defines a number of behaviors that allow a more detailed definition of the fileeffectiverights53_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
It is important to note that the 'max_depth' and 'recurse_direction' attributes of the 'behaviors' element do not apply to the 'filepath' element, only to the 'path' and 'filename' elements. This is because the 'filepath' element represents an absolute path to a particular file and it is not possible to recurse over a file.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent directories, or 'down' into child directories to recursively search for files. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'recurse_file_system' defines the file system limitation of any recursion, either 'local' limiting data collection to local file systems (as opposed to file systems mounted from an external system), or 'defined' to keep any recursion within the file system that the file_object (path+filename) has specified. The default value is 'all' meaning to use all available file systems for data collection.
'include_group' defines whether the group sid should be included in the object when the object is defined by a group sid. For example, the intent of an object defined by a group sid might be to retrieve all the user sids that are a member of the group, but not the group sid itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: fileeffectiverights53_object
The file effective rights test is used to check the effective rights associated with Windows files. Note that the trustee's effective access rights are the access rights that the ACL grants to the trustee or to any groups of which the trustee is a member. The fileeffectiverights_test element 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 fileeffectiverights_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.3
Replaced by the fileeffectiverights53_test. This test uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. See the fileeffectiverights53_test.
This test has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED TEST: ID:
- the object child element of a fileeffectiverights_test must reference a fileeffectiverights_object
- the state child element of a fileeffectiverights_test must reference a fileeffectiverights_state
The fileeffectiverights_object element is used by a file effective rights test to define the objects used to evalutate against the specified state. The fileeffectiverights_object will collect directories and all Windows file types (FILE_TYPE_CHAR, FILE_TYPE_DISK, FILE_TYPE_PIPE, FILE_TYPE_REMOTE, and FILE_TYPE_UNKNOWN). Each object extends the standard ObjectType as definied 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.
A fileeffectiverights_object is defined as a combination of a Windows file and trustee name. The file represents the file to be evaluated while the trustee name represents the account (sid) to check effective rights of. If multiple files or sids are matched by either reference, then each possible combination of file and sid is a matching file effective rights object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FileEffectiveRightsBehaviors complex type for more information about specific behaviors.
5.3
Replaced by the fileeffectiverights_object. This object uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new object was created to use trustee SIDs, which are unique. See the fileeffectiverights53_object.
This object has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED OBJECT: ID:
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileeffectiverights_object should be 'string'
The filename element specifies the name of a file to evaluate. If the xsi:nil attribute is set to true, then the object being specified is the higher level directory object (not all the files in the directory). In this case, the filename element should not be used during collection and would result in the unique set of collected objects being the directories themselves. For example, one would set xsi:nil to true if the desire was to test the attributes or permissions associated with a directory. Setting xsi:nil equal to true is different than using a .* pattern match, which says to collect every file under a given path.
- datatype attribute for the filename entity of a fileeffectiverights_object should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The trustee_name element is the unique name that associated a particular SID. A SID can be associated with a user, group, or program (such as a Windows service). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a fileeffectiverights_object should be 'string'
The fileeffectiverights_state element defines the different rights that can be associated with a given fileeffectiverights_object. Please refer to the individual elements in the schema for more details about what each represents.
5.3
Replaced by the fileeffectiverights53_state. This state uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new state was created to use trustee SIDs, which are unique. See the fileeffectiverights53_state.
This state has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED STATE: ID:
The path element specifies the directory component of the absolute path to a file on the machine.
- datatype attribute for the path entity of a fileeffectiverights_state should be 'string'
The filename element specifies the name of the file.
- datatype attribute for the filename entity of a fileeffectiverights_state should be 'string'
- filename entity cannot contain the characters / \ : * ? > |
The unique name associated with a particular security identifier (SID). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a fileeffectiverights_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a fileeffectiverights_state should be 'boolean'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a fileeffectiverights_state should be 'boolean'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a fileeffectiverights_state should be 'boolean'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a fileeffectiverights_state should be 'boolean'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a fileeffectiverights_state should be 'boolean'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a fileeffectiverights_state should be 'boolean'
Read access.
- datatype attribute for the generic_read entity of a fileeffectiverights_state should be 'boolean'
Write access.
- datatype attribute for the generic_write entity of a fileeffectiverights_state should be 'boolean'
Execute access.
- datatype attribute for the generic_execute entity of a fileeffectiverights_state should be 'boolean'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a fileeffectiverights_state should be 'boolean'
Grants the right to read data from the file, or if a directory, grants the right to list the contents of the directory.
- datatype attribute for the file_read_data entity of a fileeffectiverights_state should be 'boolean'
Grants the right to write data to the file, or if a directory, grants the right to add a file to the directory.
- datatype attribute for the file_write_data entity of a fileeffectiverights_state should be 'boolean'
Grants the right to append data to the file, or if a directory, grants the right to add a sub-directory to the directory.
- datatype attribute for the file_append_data entity of a fileeffectiverights_state should be 'boolean'
Grants the right to read extended attributes.
- datatype attribute for the file_read_ea entity of a fileeffectiverights_state should be 'boolean'
Grants the right to write extended attributes.
- datatype attribute for the file_write_ea entity of a fileeffectiverights_state should be 'boolean'
Grants the right to execute a file, or if a directory, the right to traverse the directory.
- datatype attribute for the file_execute entity of a fileeffectiverights_state should be 'boolean'
Right to delete a directory and all the files it contains (its children), even if the files are read-only.
- datatype attribute for the file_delete_child entity of a fileeffectiverights_state should be 'boolean'
Grants the right to read file, or directory, attributes.
- datatype attribute for the file_read_attributes entity of a fileeffectiverights_state should be 'boolean'
Grants the right to change file, or directory, attributes.
- datatype attribute for the file_write_attributes entity of a fileeffectiverights_state should be 'boolean'
The FileEffectiveRightsBehaviors complex type defines a number of behaviors that allow a more detailed definition of the fileeffectiverights_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
5.3
Replaced by the FileEffectiveRightsBehaviors53. The FileEffectiveRightsBehaviors complex type is used by the fileeffectiverights_test which uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. This new test utilizes the FileEffectiveRightsBehaviors53 complex type, and as a result, the FileEffectiveRightsBehaviors complex type is no longer needed.
This complex type has been deprecated and will be removed in version 6.0 of the language.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent directories, or 'down' into child directories to recursively search for files. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'include_group' defines whether the group trustee name should be included in the object when the object is defined by a group trustee name. For example, the intent of an object defined by a group sid might be to retrieve all the user trustee names that are members of the group, but not the group trustee name itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: fileeffectiverights_object
The group_test allows the different users and subgroups, that directly belong to specific groups (identified by name), to be tested. When the group_test collects the groups on the system, it should only include the local and built-in group accounts and not domain group accounts. However, it is important to note that domain group accounts can still be looked up. Also, note that the subgroups of the group will not be resolved to find indirect user and group members. If the subgroups need to be resolved, it should be done using the sid_object. 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 group_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a group_test must reference a group_object
- the state child element of a group_test must reference a group_state
The group_object element is used by a group test to define the specific group(s) (identified by name) to be evaluated. Each object extends the standard ObjectType as definied 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.
The group element holds a string that represents the name of a particular group. In Windows, group names are case-insensitive and thus case does not matter for this entity. In a domain environment, the group should be identified in the form: "domain\group name". In a local environment, the group should be identified in the form: "computer name\group name". If the group is a built-in group, the group should be identified in the form: "group name" without a domain component. Note that the built-in group names should be all caps to help improve readability as that is how the Windows APIs return them. Of course, techincally it does not matter since the names are case-insensitive.
- datatype attribute for the group entity of a group_object should be 'string'
The group_state element enumerates the different users and subgroups directly associated with a Windows group. Please refer to the individual elements in the schema for more details about what each represents.
The group element holds a string that represents the name of a particular group. In a domain environment, groups should be identified in the form: "domain\group name" For local groups use: "computer name\group name" For built-in accounts on the system, use the group name without a domain. For example: ADMINISTRATORS, etc. Note that the built-in group names should be all caps to help improve readability as that is how the Windows APIs return them. Of course techincally it does not matter since the names are case-insensitive.
- datatype attribute for the group entity of a group_state should be 'string'
The user element holds a string that represents the name of a particular user. In a domain environment, users should be identified in the form: "domain\user name" For local users use: "computer name\user name" For built-in accounts on the system, use the user name without a domain. For example: ADMINISTRATOR, SYSTEM, etc. Note that the built-in user names should be all caps to help improve readability as that is how the Windows APIs return them. Of course techincally it does not matter since the names are case-insensitive.
The user element can be included multiple times in a system characteristic item in order to record that a group contains a number of different users. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like user that refer to items that can occur an unbounded number of times.
- datatype attribute for the user entity of a group_state should be 'string'
A string that represents the name of a particular subgroup in the specified group. In a domain environment, the subgroups should be identified in the form: "domain\group name". In a local environment, the subgroups should be identified in the form: "computer name\group name". If the subgroups are built-in groups, the subgroups should be identified in the form: "group name" without a domain component. Note that the built-in group names should be all caps as that is how the Windows APIs return them.
The subgroup element can be included multiple times in a system characteristic item in order to record that a group contains a number of different subgroups. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like the subgroup entity that refer to items that can occur an unbounded number of times.
- datatype attribute for the subgroup entity of a group_state should be 'string'
The group_sid_test allows the different users and subgroups, that directly belong to specific groups (identified by SID), to be tested. When the group_sid_test collects the group SIDs on the system, it should only include the local and built-in group SIDs and not domain group SIDs. However, it is important to note that domain group SIDs can still be looked up. Also, note that the subgroups of the group will not be resolved to find indirect user and group members. If the subgroups need to be resolved, it should be done using the sid_sid_object. 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 group_sid_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a group_sid_test must reference a group_sid_object
- the state child element of a group_sid_test must reference a group_sid_state
The group_sid_object element is used by a group_test to define the specific group(s) (identified by SID) to be evaluated. Each object extends the standard ObjectType as definied 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.
The group_sid entity holds a string that represents the SID of a particular group.
- datatype attribute for the group_sid entity of a group_sid_object should be 'string'
The group_state element enumerates the different users and subgroups directly associated with a Windows group. Please refer to the individual elements in the schema for more details about what each represents.
The group_sid entity holds a string that represents the SID of a particular group.
- datatype attribute for the group_sid entity of a group_sid_state should be 'string'
The user_sid entity holds a string that represents the SID of a particular user. This entity can be included multiple times in a system characteristic item in order to record that a group contains a number of different users. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like user that refer to items that can occur an unbounded number of times.
- datatype attribute for the user_sid entity of a group_sid_state should be 'string'
The subgroup_sid entity holds a string that represents the SID of particular subgroup in the specified group. This entity can be included multiple times in a system characteristic item in order to record that a group contains a number of different subgroups. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like subgroup_sid that refer to items that can occur an unbounded number of times.
- datatype attribute for the subgroup_sid entity of a group_sid_state should be 'string'
The interface test enumerate various attributes about the interfaces on a 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 interface_object and the optional state element specifies the interface information to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of an interface_test must reference an interface_object
- the state child element of an interface_test must reference an interface_state
The interface_object element is used by an interface test to define the specific interfaces(s) to be evaluated. Each object extends the standard ObjectType as definied 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.
An interface object consists of a single name entity that identifies which interface is being specified. For help understanding this object, see the MIB_IFROW and MIB_IPADDRROW structures.
The name element specifies the name of an interface.
- datatype attribute for the name entity of a interface_object should be 'string'
The interface_state element enumerates the different properties associate with a Windows interface. Please refer to the individual elements in the schema for more details about what each represents.
The name element specifies the name of an interface.
- datatype attribute for the name entity of an interface_state should be 'string'
The index element specifies index that identifies the interface.
- datatype attribute for the index entity of an interface_state should be 'int'
The type element specifies the type of interface which is limited to certain set of values.
- datatype attribute for the type entity of an interface_state should be 'string'
The hardware_addr entity is the hardware or MAC address of the physical network card. MAC addresses should be formatted according to the IEEE 802-2001 standard which states that a MAC address is a sequence of six octet values, separated by hyphens, where each octet is represented by two hexadecimal digits. Uppercase letters should also be used to represent the hexadecimal digits A through F.
- datatype attribute for the hardware_addr entity of an interface_state should be 'string'
The inet_addr element specifies the IP address. Note that the IP address can be IPv4 or IPv6.
- datatype attribute for the inet_addr entity of an interface_state should be 'string'
The broadcast_addr element specifies the broadcast address. A broadcast address is typically the IP address with the host portion set to either all zeros or all ones. Note that the IP address can be IPv4 or IPv6.
- datatype attribute for the broadcast_addr entity of an interface_state should be 'string'
The netmask element specifies the subnet mask for the IP address. Note that the IP address can be IPv4 or IPv6.
- datatype attribute for the netmask entity of an interface_state should be 'string'
The addr_type element specifies the address type or state of a specific interface. Each interface can be associated with more than one value meaning the addr_type element can occur multiple times in a system characteristic item. Note that the entity_check attribute associated with EntityStateAddrTypeType guides the evaluation of unbounded entities like addr_type.
- datatype attribute for the addr_type entity of an interface_state should be 'string'
The lockout policy test enumerates various attributes associated with lockout information for users and global groups in the security database. 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 lockoutpolicy_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a lockoutpolicy_test must reference a lockoutpolicy_object
- the state child element of a lockoutpolicy_test must reference a lockoutpolicy_state
The lockoutpolicy_object element is used by a lockout policy test to define those objects to evaluated based on a specified state. There is actually only one object relating to lockout policy and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check lockout policy will reference the same lockoutpolicy_object which is basically an empty object element.
The lockoutpolicy_state element specifies the various attributes associated with lockout information for users and global groups in the security database. A lockout policy test will reference a specific instance of this state that defines the exact settings that need to be evaluated. Please refer to the individual elements in the schema for more details about what each represents.
Specifies, in seconds, the amount of time between the end of the valid logon time and the time when the user is forced to log off the network. A value of TIMEQ_FOREVER (-1) indicates that the user is never forced to log off. A value of zero indicates that the user will be forced to log off immediately when the valid logon time expires. See the USER_MODALS_INFO_0 structure returned by a call to NetUserModalsGet().
- datatype attribute for the force_logoff entity of a lockoutpolicy_state should be 'int'
Specifies, in seconds, how long a locked account remains locked before it is automatically unlocked. See the USER_MODALS_INFO_3 structure returned by a call to NetUserModalsGet().
- datatype attribute for the lockout_duration entity of a lockoutpolicy_state should be 'int'
Specifies the maximum time, in seconds, that can elapse between any two failed logon attempts before lockout occurs. See the USER_MODALS_INFO_3 structure returned by a call to NetUserModalsGet().
- datatype attribute for the lockout_observation_window entity of a lockoutpolicy_state should be 'int'
Specifies the number of invalid password authentications that can occur before an account is marked "locked out." See the USER_MODALS_INFO_3 structure returned by a call to NetUserModalsGet().
- datatype attribute for the lockout_threshold entity of a lockoutpolicy_state should be 'int'
The metabase test is used to check information found in the Windows metabase. 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 metabase_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a metabase_test must reference a metabase_object
- the state child element of a metabase_test must reference a metabase_state
The metabase_object element is used by a metabase test to define the specific metabase item(s) to be evaluated. Each object extends the standard ObjectType as definied 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.
A metabase object defines the key and id of the item(s).
The key element specifies a metabase key.
- datatype attribute for the key entity of a metabase_object should be 'string'
The id element specifies a particular object under the metabase key. If the xsi:nil attribute is set to true, then the object being specified is the higher level key. In this case, the id 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 id under a given key. The most likely use for xsi:nil within a metabase object is when checking for the existence of a particular key, without regards to the different ids associated with it.
- datatype attribute for the id entity of a metabase_object should be 'int'
The metabase_state element defines the different metadata associate with a metabase item. This includes the name, user type, data type, and the actual data. Please refer to the individual elements in the schema for more details about what each represents.
The key element specifies a metabase key.
- datatype attribute for the key entity of a metabase_state should be 'string'
The id element specifies a particular object under the metabase key.
- datatype attribute for the id entity of a metabase_state should be 'int'
The name element describes the name of the specified metabase object.
- datatype attribute for the name entity of a metabase_state should be 'string'
The user_type element is a DWORD that specifies the user type of the data. See the METADATA_RECORD structure.
- datatype attribute for the user_type entity of a metabase_state should be 'string'
The data_type element identifies the type of data in the metabase entry. See the METADATA_RECORD structure.
- datatype attribute for the data_type entity of a metabase_state should be 'string'
The actual data of the named item under the specified metabase key
- datatype attribute for the entity of an should not be 'record'
The password policy test is used to check specific policy associated with passwords. It is important to note that these policies are specific to certain versions of Windows. As a result, the documentation for that version of Windows should be consulted for more information. 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 passwordpolicy_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
NOTE: This information is stored in the SAM or Active Directory but is encrypted or hidden so the registry_test and activedirectory57_test are of no use. If this can be figured out, then the password_policy test is not needed.
- the object child element of a passwordpolicy_test must reference a passwordpolicy_object
- the state child element of a passwordpolicy_test must reference a passwordpolicy_state
The passwordpolicy_object element is used by a password policy test to define those objects to evaluated based on a specified state. There is actually only one object relating to password policy and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check password policy will reference the same passwordpolicy_object which is basically an empty object element.
The passwordpolicy_state element specifies the various policies associated with passwords. A password policy test will reference a specific instance of this state that defines the exact settings that need to be evaluated.
Specifies, in seconds, the maximum allowable password age. A value of TIMEQ_FOREVER (-1) indicates that the password never expires. The minimum valid value for this element is ONE_DAY (86400).
- datatype attribute for the max_passwd_age entity of a passwordpolicy_state should be 'int'
Specifies the minimum number of seconds that can elapse between the time a password changes and when it can be changed again. A value of zero indicates that no delay is required between password updates.
- datatype attribute for the min_passwd_age entity of a passwordpolicy_state should be 'int'
Specifies the minimum allowable password length. Valid values for this element are zero through PWLEN.
- datatype attribute for the min_passwd_len entity of a passwordpolicy_state should be 'int'
Specifies the length of password history maintained. A new password cannot match any of the previous usrmod0_password_hist_len passwords. Valid values for this element are zero through DEF_MAX_PWHIST.
- datatype attribute for the password_hist_len entity of a passwordpolicy_state should be 'int'
A boolean value that signifies whether passwords must meet the complexity requirements put forth by the operating system.
- datatype attribute for the password_complexity entity of an passwordpolicy_state should be 'boolean'
Determines whether or not passwords are stored using reversible encryption.
- datatype attribute for the reversible_encryption entity of an passwordpolicy_state should be 'boolean'
The port test is used to check information about the available ports on a Windows 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 port_object and the optional state element specifies the port information to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a port_test must reference a port_object
- the state child element of a port_test must reference a port_state
The port_object element is used by a port test to define the specific port(s) to be evaluated. Each object extends the standard ObjectType as definied 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.
A port object defines the local address, port number, and protocol of the port(s).
This element specifies the local IP address the listening port is bound to. Note that the IP address can be IPv4 or IPv6.
- datatype attribute for the local_address entity of a port_object should be 'string'
This element specifies the number assigned to the local listening port.
- datatype attribute for the local_port entity of a port_object should be 'int'
This element specifies the type of listening port. It is restricted to either TCP or UDP.
- datatype attribute for the protocol entity of a port_object should be 'string'
The port_state element defines the different metadata associate with a Windows port. This includes the local address, port number, protocol, and pid. Please refer to the individual elements in the schema for more details about what each represents.
This element specifies the local IP address the listening port is bound to. Note that the IP address can be IPv4 or IPv6.
- datatype attribute for the local_address entity of a port_state should be 'string'
This element specifies the number assigned to the local listening port.
- datatype attribute for the local_port entity of a port_state should be 'int'
This element specifies the type of listening port. It is restricted to either TCP or UDP.
- datatype attribute for the protocol entity of a port_state should be 'string'
The id given to the process that is associated with the specified listening port.
- datatype attribute for the pid entity of a port_state should be 'int'
The printer effective rights test is used to check the effective rights associated with Windows printers. The printereffectiverights_test element 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 printereffectiverights_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a printereffectiverights_test must reference a printereffectiverights_object
- the state child element of a printereffectiverights_test must reference a printereffectiverights_state
The printer_name element describes a printer that a user may have rights on.
- datatype attribute for the kprinter_nameey entity of a printereffectiverights_object should be 'string'
The trustee_sid entity identifies a unique sid associated with a user, group, system, or program (such as a Windows service). If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the printer's Security Descriptor. The scope is limited here to ensure that it is possible to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the trustee_sid entity of a printereffectiverights_object should be 'string'
The printereffectiverights_state element defines the different rights that can be associated with a given printereffectiverights_object. Please refer to the individual elements in the schema for more details about what each represents.
This element specifies the name of the printer.
- datatype attribute for the printer_name entity of a printereffectiverights_state should be 'string'
The trustee_sid element is the unique sid that associated a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a printereffectiverights_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a printereffectiverights_state should be 'boolean'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a printereffectiverights_state should be 'boolean'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a printereffectiverights_state should be 'boolean'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a printereffectiverights_state should be 'boolean'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a printereffectiverights_state should be 'boolean'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a printereffectiverights_state should be 'boolean'
Read access.
- datatype attribute for the generic_read entity of a printereffectiverights_state should be 'boolean'
Write access.
- datatype attribute for the generic_write entity of a printereffectiverights_state should be 'boolean'
Execute access.
- datatype attribute for the generic_execute entity of a printereffectiverights_state should be 'boolean'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a printereffectiverights_state should be 'boolean'
- datatype attribute for the printer_access_administer entity of a printereffectiverights_state should be 'boolean'
- datatype attribute for the printer_access_use entity of a printereffectiverights_state should be 'boolean'
- datatype attribute for the job_access_administer entity of a printereffectiverights_state should be 'boolean'
- datatype attribute for the job_access_read entity of a printereffectiverights_state should be 'boolean'
The PrinterEffectiveRightsBehaviors complex type defines a number of behaviors that allow a more detailed definition of the pritnereffectiverights_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'include_group' defines whether the group trustee name should be included in the object when the object is defined by a group trustee name. For example, the intent of an object defined by a group trustee name might be to retrieve all the user trustee names that are members of the group, but not the group trustee name itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: printereffectiverights_object
The process test is used to check information found in the Windows processes. 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 process_object and the optional state element specifies the process information to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a process_test must reference a process_object
- the state child element of a process_test must reference a process_state
The process_object element is used by a process test to define the specific process(es) to be evaluated. Each object extends the standard ObjectType as definied 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.
A process object defines the command line used to start the process(s).
The command_line entity is the string used to start the process. This includes any parameters that are part of the command line.
- datatype attribute for the command_line entity of a process_object should be 'string'
The process_state element defines the different metadata associate with a Windows process. This includes the command line, pid, ppid, image path, and current directory. Please refer to the individual elements in the schema for more details about what each represents.
The command_line entity is the string used to start the process. This includes any parameters that are part of the command line.
- datatype attribute for the command_line entity of a process_state should be 'string'
The id given to the process that is created for a specified command line.
- datatype attribute for the pid entity of a port_state should be 'int'
The id given to the parent of the process that is created for the specified command line
- datatype attribute for the ppid entity of a port_state should be 'int'
The base priority of the process.
- datatype attribute for the priority entity of a process_state should be 'string'
The image_path entity contains the name of the executable file in question.
- datatype attribute for the image_path entity of a process_state should be 'string'
The current_directory entity represents the current path to the executable.
- datatype attribute for the current_dir entity of a process_state should be 'string'
The registry test is used to check metadata associated with Windows registry key. 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 registry_object and the optional state element specifies the registry data to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a registry_test must reference a registry_object
- the state child element of a registry_test must reference a registry_state
The hive that the registry key belongs to. This is restricted to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.
- datatype attribute for the hive entity of a registry_object should be 'string'
The key element describes a registry key to be collected. Note that the hive portion of the string should not be included, as this data should be found under the hive element. If the xsi:nil attribute is set to true, then the object being specified is the higher level hive. In this case, the key element should not be collected or used in analysis. Setting xsi:nil equal to true is different than using a .* pattern match. A .* pattern match says to collect every key under a given hive. Note that when xsi:nil is used for the key element, the name element should also be nilled.
- datatype attribute for the key entity of a registry_object should be 'string'
- name entity must be nil when key is nil
The name element describes the name assigned to a value associated with a specific registry key. If an empty string is specified for the name element, the registry key's default value should be collected. If the xsi:nil attribute is set to true, then the object being specified is the higher level hive/key. In this case, the name element should not be collected or used in analysis. Setting xsi:nil equal to true on an element is different than using a .* pattern match. A .* pattern match says to collect every name under a given hive/key. The most likely use for xsi:nil within a registry object is when checking for the existence of a particular key, without regards to the different names associated with it.
- datatype attribute for the name entity of a registry_object should be 'string'
The registry_state element defines the different metadata associate with a Windows registry key. This includes the hive, key, name, type, and value. Please refer to the individual elements in the schema for more details about what each represents.
The hive that the registry key belongs to. This is restricted to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.
- datatype attribute for the hive entity of a registry_state should be 'string'
This element describes a registry key to be tested. Note that the hive portion of the string should not be inclueded, as this data should be found under the hive element.
- datatype attribute for the key entity of a registry_state should be 'string'
This element describes the name of a value of a registry key. If the xsi:nil attribute is set to true, then the name element should not be used in analysis.
- datatype attribute for the name entity of a registry_state should be 'string'
The type entity allows a test to be written against the registy type associated with the specified registry key(s). Please refer to the documentation on the EntityStateRegistryTypeType for more information about the different valid individual types.
- datatype attribute for the type entity of a registry_state should be 'string'
The value entity allows a test to be written against the value held within the specified registry key(s). If the value being tested is of type REG_BINARY, then the datatype attribute should be set to 'binary' and the data represented by the value entity should follow the xsd:hexBinary form. (each binary octet is encoded as two hex digits) If the value being tested is of type REG_DWORD or REG_QWORD, then the datatype attribute should be set to 'int' and the value entity should represent the data as an integer. If the value being tested is of type REG_EXPAND_SZ, then the datatype attribute should be set to 'string' and the pre-expanded string should be represented by the value entity. If the value being tested is of type REG_MULTI_SZ, then only a single string (one of the multiple strings) should be tested using the value entity with the datatype attribute set to 'string'. In order to test multiple values, multiple OVAL registry tests should be used. If the specified registry key is of type REG_SZ, then the datatype should be 'string' and the value entity should be a copy of the string.
Note that if the intent is to test a version number held in the registry (as a reg_sz) then instead of setting the datatype to 'string', the datatype can be set to 'version'. This allows tools performing the evaluation to know how to perform less than and greater than operations correctly.
- datatype attribute for the entity of an should not be 'record'
The RegistryBehaviors complex type defines a number of behaviors that allow a more detailed definition of the registry_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent keys, or 'down' into child keys to recursively search for registry keys. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
The registry key audited permissions test is used to check the audit permissions associated with Windows registry keys. 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 regkeyauditedpermissions53_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a regkeyauditedpermissions53_test must reference a regkeyauditedpermissions53_object
- the state child element of a regkeyauditedpermissions53_test must reference a regkeyauditedpermissions53_state
The regkeyauditedpermissions53_object element is used by a registry key audited permissions test to define the objects used to evalutate against the specified state. Each object extends the standard ObjectType as definied 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.
A regkeyauditedpermissions53_object is defined as a combination of a Windows registry key and trustee name. The hive and key elements represents the registry key to be evaluated while the trustee name represents the account (sid) to check audited permissions of. If multiple keys or sids are matched by either reference, then each possible combination of registry key and sid is a matching registry key audited permissions object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the RegkeyAuditPermissions53Behaviors complex type for more information about specific behaviors.
The hive that the registry key belongs to. This is restricted to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.
- datatype attribute for the hive entity of a regkeyauditedpermissions53_object should be 'string'
The key element describes a registry key to be collected. Note that the hive portion of the string should not be included, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyauditedpermissions53_object should be 'string'
The trustee_sid entity identifies a unique sid associated with a user, group, system, or program (such as a Windows service). If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the registry key's Security Descriptor. The scope is limited here to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the trustee_sid entity of a regkeyauditedpermissions53_object should be 'string'
The regkeyauditedpermissions53_state element defines the different audit permissions that can be associated with a given regkeyauditedpermissions53_object. Please refer to the individual elements in the schema for more details about what each represents.
This element specifies the hive of a registry key on the machine from which to retrieve the SACL.
- datatype attribute for the hive entity of a regkeyauditedpermissions53_state should be 'string'
This element specifies a registry key on the machine from which to retrieve the SACL. Note that the hive portion of the string should not be inclueded, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyauditedpermissions53_state should be 'string'
The trustee_sid element is the unique sid that associated a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a regkeyauditedpermissions53_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a regkeyauditedpermissions53_state should be 'string'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a regkeyauditedpermissions53_state should be 'string'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a regkeyauditedpermissions53_state should be 'string'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a regkeyauditedpermissions53_state should be 'string'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
5.6
This entity has been deprecated because registry keys do not support the SYNCHRONIZE standard access right.
DEPRECATED ELEMENT: ID:
item - datatype attribute for the standard_synchronize entity of a regkeyauditedpermissions53_state should be 'string'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a regkeyauditedpermissions53_state should be 'string'
Read access.
- datatype attribute for the generic_read entity of a regkeyauditedpermissions53_state should be 'string'
Write access.
- datatype attribute for the generic_write entity of a regkeyauditedpermissions53_state should be 'string'
Execute access.
- datatype attribute for the generic_execute entity of a regkeyauditedpermissions53_state should be 'string'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_query_value entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_set_value entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_create_sub_key entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_enumerate_sub_keys entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_notify entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_create_link entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_wow64_64key entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_wow64_32key entity of a regkeyauditedpermissions53_state should be 'string'
- datatype attribute for the key_wow64_res entity of a regkeyauditedpermissions53_state should be 'string'
The RegkeyAuditPermissions53Behaviors complex type defines a number of behaviors that allow a more detailed definition of the registrykeyauditedpermissions53_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent keys, or 'down' into child keys to recursively search for registry keys. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'include_group' defines whether the group sid should be included in the object when the object is defined by a group sid. For example, the intent of an object defined by a group sid might be to retrieve all the user sids that are a member of the group, but not the group sid itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: regkeyauditedpermissions53_object
The registry key audited permissions test is used to check the audit permissions associated with Windows registry keys. 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 regkeyauditedpermissions_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.3
Replaced by the regkeyauditedpermissions53_test. This test uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. See the regkeyauditedpermissions53_test.
This test has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED TEST: ID:
- the object child element of a regkeyauditedpermissions_test must reference a regkeyauditedpermissions_object
- the state child element of a regkeyauditedpermissions_test must reference a regkeyauditedpermissions_state
The regkeyauditedpermissions_object element is used by a registry key audited permissions test to define the objects used to evalutate against the specified state. Each object extends the standard ObjectType as definied 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.
A regkeyauditedpermissions_object is defined as a combination of a Windows registry key and trustee name. The hive and key elements represents the registry key to be evaluated while the trustee name represents the account (sid) to check audited permissions of. If multiple keys or sids are matched by either reference, then each possible combination of file and sid is a matching file audited permissions object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the RegkeyAuditPermissionsBehaviors complex type for more information about specific behaviors.
5.3
Replaced by the regkeyauditedpermissions53_object. This object uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new object was created to use trustee SIDs, which are unique. See the regkeyauditedpermissions53_object.
This object has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED OBJECT: ID:
The hive that the registry key belongs to. This is restricted to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.
- datatype attribute for the hive entity of a regkeyauditedpermissions_object should be 'string'
The key element describes a registry key to be collected. Note that the hive portion of the string should not be included, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyauditedpermissions_object should be 'string'
The trustee_name element is the unique name that associated a particular SID. A SID can be associated with a user, group, or program (such as a Windows service). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a regkeyauditedpermissions_object should be 'string'
The regkeyauditedpermissions_state element defines the different audit permissions that can be associated with a given regkeyauditedpermissions_object. Please refer to the individual elements in the schema for more details about what each represents.
5.3
Replaced by the regkeyauditedpermissions53_state. This state uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new state was created to use trustee SIDs, which are unique. See the regkeyauditedpermissions53_state.
This state has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED STATE: ID:
This element specifies the hive of a registry key on the machine from which to retrieve the SACL.
- datatype attribute for the hive entity of a regkeyauditedpermissions_state should be 'string'
This element specifies a registry key on the machine from which to retrieve the SACL. Note that the hive portion of the string should not be inclueded, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyauditedpermissions_state should be 'string'
The unique name associated with a particular security identifier (SID). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a regkeyauditedpermissions_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a regkeyauditedpermissions_state should be 'string'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a regkeyauditedpermissions_state should be 'string'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a regkeyauditedpermissions_state should be 'string'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a regkeyauditedpermissions_state should be 'string'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a regkeyauditedpermissions_state should be 'string'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a regkeyauditedpermissions_state should be 'string'
Read access.
- datatype attribute for the generic_read entity of a regkeyauditedpermissions_state should be 'string'
Write access.
- datatype attribute for the generic_write entity of a regkeyauditedpermissions_state should be 'string'
Execute access.
- datatype attribute for the generic_execute entity of a regkeyauditedpermissions_state should be 'string'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_query_value entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_set_value entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_create_sub_key entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_enumerate_sub_keys entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_notify entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_create_link entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_wow64_64key entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_wow64_32key entity of a regkeyauditedpermissions_state should be 'string'
- datatype attribute for the key_wow64_res entity of a regkeyauditedpermissions_state should be 'string'
The RegkeyAuditPermissionsBehaviors complex type defines a number of behaviors that allow a more detailed definition of the registrykeyauditedpermissions_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
5.3
Replaced by the RegkeyAuditPermissionsBehaviors53. The RegkeyAuditPermissionsBehaviors complex type is used by the regkeyauditedpermissions_test which uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. This new test utilizes the RegkeyAuditPermissionsBehaviors53 complex type, and as a result, the RegkeyAuditPermissionsBehaviors complex type is no longer needed.
This complex type has been deprecated and will be removed in version 6.0 of the language.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent keys, or 'down' into child keys to recursively search for registry keys. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'include_group' defines whether the group trustee name should be included in the object when the object is defined by a group trustee name. For example, the intent of an object defined by a group trustee name might be to retrieve all the user trustee names that are members of the group, but not the group trustee name itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: regkeyauditedpermissions_object
The registry key effective rights test is used to check the effective rights associated with Windows files. Note that the trustee's effective access rights are the access rights that the ACL grants to the trustee or to any groups of which the trustee is a member. The regkeyeffectiverights53_test element 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 regkeyeffectiverights53_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a regkeyeffectiverights53_test must reference a regkeyeffectiverights53_object
- the state child element of a regkeyeffectiverights53_test must reference a regkeyeffectiverights53_state
The regkeyeffectiverights53_object element is used by a registry key effective rights test to define the objects used to evalutate against the specified state. Each object extends the standard ObjectType as definied 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.
A regkeyeffectiverights53_object is defined as a combination of a Windows registry and trustee sid. The key entity represents the registry key to be evaluated while the trustee sid represents the account (sid) to check effective rights of. If multiple files or sids are matched by either reference, then each possible combination of registry key and sid is a matching registry key effective rights object. In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the RegkeyEffectiveRights53Behaviors complex type for more information about specific behaviors.
The hive that the registry key belongs to. This is restricted to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.
- datatype attribute for the hive entity of a regkeyeffectiverights53_object should be 'string'
The key element describes a registry key to be collected. Note that the hive portion of the string should not be included, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyeffectiverights53_object should be 'string'
The trustee_sid entity identifies a unique sid associated with a user, group, system, or program (such as a Windows service). If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the registry key's Security Descriptor. The scope is limited here to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the trustee_sid entity of a regkeyeffectiverights53_object should be 'string'
The regkeyeffectiverights53_state element defines the different rights that can be associated with a given regkeyeffectiverights53_object. Please refer to the individual elements in the schema for more details about what each represents.
This element specifies the hive of a registry key on the machine from which to retrieve the SACL.
- datatype attribute for the hive entity of a regkeyeffectiverights53_state should be 'string'
This element specifies a registry key on the machine from which to retrieve the SACL. Note that the hive portion of the string should not be inclueded, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyeffectiverights53_state should be 'string'
The trustee_sid element is the unique sid that associated a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a regkeyeffectiverights53_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a regkeyeffectiverights53_state should be 'boolean'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a regkeyeffectiverights53_state should be 'boolean'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a regkeyeffectiverights53_state should be 'boolean'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a regkeyeffectiverights53_state should be 'boolean'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
5.6
This entity has been deprecated because registry keys do not support the SYNCHRONIZE standard access right.
DEPRECATED ELEMENT: ID:
- datatype attribute for the standard_synchronize entity of a regkeyeffectiverights53_state should be 'boolean'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a regkeyeffectiverights53_state should be 'boolean'
Read access.
- datatype attribute for the generic_read entity of a regkeyeffectiverights53_state should be 'boolean'
Write access.
- datatype attribute for the generic_write entity of a regkeyeffectiverights53_state should be 'boolean'
Execute access.
- datatype attribute for the generic_execute entity of a regkeyeffectiverights53_state should be 'boolean'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_query_value entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_set_value entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_create_sub_key entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_enumerate_sub_keys entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_notify entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_create_link entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_wow64_64key entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_wow64_32key entity of a regkeyeffectiverights53_state should be 'boolean'
- datatype attribute for the key_wow64_res entity of a regkeyeffectiverights53_state should be 'boolean'
The RegkeyEffectiveRights53Behaviors complex type defines a number of behaviors that allow a more detailed definition of the registrykeyeffectiverights53_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent keys, or 'down' into child keys to recursively search for registry keys. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'include_group' defines whether the group sid should be included in the object when the object is defined by a group sid. For example, the intent of an object defined by a group sid might be to retrieve all the user sids that are a member of the group, but not the group sid itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: regkeyeffectiverights53_object
The registry key effective rights test is used to check the effective rights associated with Windows files. Note that the trustee's effective access rights are the access rights that the ACL grants to the trustee or to any groups of which the trustee is a member. The regkeyeffectiverights_test element 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 regkeyeffectiverights_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.3
Replaced by the regkeyeffectiverights53_test. This test uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. See the regkeyeffectiverights53_test.
This test has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED TEST: ID:
- the object child element of a regkeyeffectiverights_test must reference a regkeyeffectiverights_object
- the state child element of a regkeyeffectiverights_test must reference a regkeyeffectiverights_state
5.3
Replaced by the fileauditedpermissions53_object. This object uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new object was created to use trustee SIDs, which are unique. See the regkeyeffectiverights53_object.
This object has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED OBJECT: ID:
The hive that the registry key belongs to. This is restricted to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.
- datatype attribute for the hive entity of a regkeyeffectiverights_object should be 'string'
The key element describes a registry key to be collected. Note that the hive portion of the string should not be included, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyeffectiverights_object should be 'string'
The trustee_name element is the unique name that associated a particular SID. A SID can be associated with a user, group, or program (such as a Windows service). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a regkeyeffectiverights_object should be 'string'
The regkeyeffectiverights_state element defines the different rights that can be associated with a given regkeyeffectiverights_object. Please refer to the individual elements in the schema for more details about what each represents.
5.3
Replaced by the regkeyeffectiverights53_state. This state uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new state was created to use trustee SIDs, which are unique. See the regkeyeffectiverights53_state.
This state has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED STATE: ID:
This element specifies the hive of a registry key on the machine from which to retrieve the SACL.
- datatype attribute for the hive entity of a regkeyeffectiverights_state should be 'string'
This element specifies a registry key on the machine from which to retrieve the SACL. Note that the hive portion of the string should not be inclueded, as this data should be found under the hive element.
- datatype attribute for the key entity of a regkeyeffectiverights_state should be 'string'
The unique name associated with a particular security identifier (SID). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a regkeyeffectiverights_state should be 'string'
The right to delete the object.
- datatype attribute for the standard_delete entity of a regkeyeffectiverights_state should be 'boolean'
The right to read the information in the object's Security Descriptor, not including the information in the SACL.
- datatype attribute for the standard_read_control entity of a regkeyeffectiverights_state should be 'boolean'
The right to modify the DACL in the object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a regkeyeffectiverights_state should be 'boolean'
The right to change the owner in the object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a regkeyeffectiverights_state should be 'boolean'
The right to use the object for synchronization. This enables a thread to wait until the object is in the signaled state. Some object types do not support this access right.
- datatype attribute for the standard_synchronize entity of a regkeyeffectiverights_state should be 'boolean'
Indicates access to a system access control list (SACL).
- datatype attribute for the access_system_security entity of a regkeyeffectiverights_state should be 'boolean'
Read access.
- datatype attribute for the generic_read entity of a regkeyeffectiverights_state should be 'boolean'
Write access.
- datatype attribute for the generic_write entity of a regkeyeffectiverights_state should be 'boolean'
Execute access.
- datatype attribute for the generic_execute entity of a regkeyeffectiverights_state should be 'boolean'
Read, write, and execute access.
- datatype attribute for the generic_all entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_query_value entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_set_value entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_create_sub_key entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_enumerate_sub_keys entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_notify entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_create_link entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_wow64_64key entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_wow64_32key entity of a regkeyeffectiverights_state should be 'boolean'
- datatype attribute for the key_wow64_res entity of a regkeyeffectiverights_state should be 'boolean'
The RegkeyEffectiveRightsBehaviors complex type defines a number of behaviors that allow a more detailed definition of the registrykeyeffectiverights_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
5.3
Replaced by the RegkeyEffectiveRightsBehaviors53. The RegkeyEffectiveRightsBehaviors complex type is used by the regkeyeffectiverights_test which uses a trustee_name element for identifying trustees. Trustee names are not unique, and a new test was created to use trustee SIDs, which are unique. This new test utilizes the RegkeyEffectiveRightsBehaviors53 complex type, and as a result, the RegkeyEffectiveRightsBehaviors complex type is no longer needed.
This complex type has been deprecated and will be removed in version 6.0 of the language.
'max_depth' defines the maximum depth of recursion to perform when a recurse_direction is specified. A value of '0' is equivalent to no recursion, '1' means to step only one directory level up/down, and so on. The default value is '-1' meaning no limitation. Note that the default recurse_direction behavior is 'none' so even though max_depth specifies no limitation by default, the recurse_direction behavior turns recursion off.
'recurse_direction' defines the direction, either 'up' to parent keys, or 'down' into child keys to recursively search for registry keys. When recursing up or down, one is limited by the max_depth behavior. Note that it is not an error if max_depth specifies a certain level of recursion and that level does not exist. Recursing should only go as deep as available. The default value is 'none' for no recursion.
'include_group' defines whether the group trustee name should be included in the object when the object is defined by a group trustee name. For example, the intent of an object defined by a group trustee name might be to retrieve all the user trustee names that are members of the group, but not the group trustee name itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
5.6
The 'resolve_group' behavior has been deprecated in favor of using variables to reference more efficient objects for expanding groups.
Consider using a sid_sid_object or similar to resolve the members of a group.
DEPRECATED BEHAVIOR IN: regkeyeffectiverights_object
The service effective rights test is used to check the effective rights associated with Windows services. Note that the trustee's effective access rights are the access rights that the ACL grants to the trustee or to any groups of which the trustee is a member. The serviceeffectiverights_test element 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 serviceeffectiverights_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a serviceeffectiverights_test must reference a serviceeffectiverights_object
- the state child element of a serviceeffectiverights_test must reference a serviceeffectiverights_state
The serviceeffectiverights_object element is used by the serviceeffectiverights_test to define the objects used to evalutate against the specified state. Each object extends the standard ObjectType as definied 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.
A serviceeffectiverights_object is defined as a combination of a Windows service_name and trustee_sid. The service_name entity represents the service to be evaluated while the trustee_sid entity represents the account (sid) to check the effective rights of. If multiple services or sids are matched by either reference, then each possible combination of service and sid is a matching service effective rights object.
The service_name element describes a service to be collected. Note that the service_name element should contain the actual name of the service and not its display name that is found in Control Panel->Administrative Tools->Services. For example, if you wanted to check the effective rights of the Automatic Updates service you would specify 'wuauserv' for the service_name element not 'Automatic Updates'.
- datatype attribute for the service_name entity of a serviceeffectiverights_object should be 'string'
The trustee_sid entity identifies a set of sids associated with a user, group, system, or program (such as a Windows service). If an operation other than equals is used to identify matching trustees (i.e. not equal, or a pattern match) then the resulting matches shall be limited to only the trustees referenced in the service's Security Descriptor. The scope is limited here to avoid unnecessarily resource intensive searches for trustees. Note that the larger scope of all known trustees may be obtained through the use of variables.
- datatype attribute for the trustee_sid entity of a serviceeffectiverights_object should be 'string'
The serviceeffectiverights_state element defines the different rights that can be associated with a given serviceeffectiverights_object. Please refer to the individual elements in the schema for more details about what each represents.
See http://support.microsoft.com/kb/914392 for more information.
The service_name element specifies a service on the machine from which to retrieve the DACL. Note that the service_name element should contain the actual name of the service and not its display name that is found in Control Panel->Administrative Tools->Services. For example, if you wanted to check the effective rights of the Automatic Updates service you would specify 'wuauserv' for the service_name element not 'Automatic Updates'.
- datatype attribute for the service_name entity of a serviceeffectiverights_state should be 'string'
The trustee_sid element is the unique sid that is associated with a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a serviceeffectiverights_state should be 'string'
This permission is required to call the DeleteService function to delete the service.
- datatype attribute for the standard_delete entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the QueryServiceObjectSecurity function to query the Security Descriptor of the service object.
- datatype attribute for the standard_read_control entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the SetServiceObjectSecurity function to modify the DACL member of the service object's Security Descriptor.
- datatype attribute for the standard_write_dac entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the SetServiceObjectSecurity function to modify the Owner and Group members of the service object's Security Descriptor.
- datatype attribute for the standard_write_owner entity of a serviceeffectiverights_state should be 'boolean'
Read access (STANDARD_RIGHTS_READ, SERVICE_QUERY_CONFIG, SERVICE_QUERY_STATUS, SERVICE_INTERROGATE, SERVICE_ENUMERATE_DEPENDENTS).
- datatype attribute for the generic_read entity of a serviceeffectiverights_state should be 'boolean'
Write access (STANDARD_RIGHTS_WRITE, SERVICE_CHANGE_CONFIG).
- datatype attribute for the generic_write entity of a serviceeffectiverights_state should be 'boolean'
Execute access (STANDARD_RIGHTS_EXECUTE, SERVICE_START, SERVICE_STOP, SERVICE_PAUSE_CONTINUE, SERVICE_USER_DEFINED_CONTROL).
- datatype attribute for the generic_execute entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the QueryServiceConfig and QueryServiceConfig2 functions to query the service configuration.
- datatype attribute for the service_query_conf entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the ChangeServiceConfig or ChangeServiceConfig2 function to change the service configuration.
- datatype attribute for the service_change_conf entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the QueryServiceStatusEx function to ask the service control manager about the status of the service.
- datatype attribute for the service_query_stat entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the EnumDependentServices function to enumerate all the services dependent on the service.
- datatype attribute for the service_enum_dependents entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the StartService function to start the service.
- datatype attribute for the service_start entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the ControlService function to stop the service.
- datatype attribute for the service_stop entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the ControlService function to pause or continue the service.
- datatype attribute for the service_pause entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the ControlService function to ask the service to report its status immediately.
- datatype attribute for the service_interrogate entity of a serviceeffectiverights_state should be 'boolean'
This permission is required to call the ControlService function to specify a user-defined control code.
- datatype attribute for the service_user_defined entity of a serviceeffectiverights_state should be 'boolean'
The shared resource test is used to check properties associated with any shared resource on the 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 sid_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a sharedresource_test must reference a sharedresource_object
- the state child element of a sharedresource_test must reference a sharedresource_state
The sharedresource_object element is used by a shared resource test to define the object, in this case a shared resource, to be evaluated. Each object extends the standard ObjectType as definied 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.
An shared resource object consists of a single netname entity that identifies a specific shared resource.
The netname element is the unique name that is associated with a specific shared resource.
- datatype attribute for the netname entity of a sharedresource_object should be 'string'
The sharedresource_state element defines the different metadata associate with a Windows shared resource. This includes the share type, permissions, and max uses. This state mirror the SHARE_INFO_2 structure. Please refer to the individual elements in the schema for more details about what each represents.
This element specifies the name associated with a particular shared resource.
- datatype attribute for the netname entity of a sharedresource_state should be 'string'
The type of the shared resource.
- datatype attribute for the shared_type entity of a sharedresource_state should be 'string'
The maximum number of concurrent connections that the shared resource can accommodate.
- datatype attribute for the max_uses entity of a sharedresource_state should be 'int'
The number of current connections to the resource.
- datatype attribute for the current_uses entity of a sharedresource_state should be 'int'
The local path for the shared resource.
- datatype attribute for the local_path entity of a sharedresource_state should be 'string'
Permission to read data from a resource and, by default, to execute the resource.
- datatype attribute for the access_read_permission entity of a sharedresource_state should be 'boolean'
Permission to write data to the resource.
- datatype attribute for the access_write_permission entity of a sharedresource_state should be 'boolean'
Permission to create an instance of the resource (such as a file); data can be written to the resource as the resource is created.
- datatype attribute for the access_create_permission entity of a sharedresource_state should be 'boolean'
Permission to execute the resource.
- datatype attribute for the access_exec_permission entity of a sharedresource_state should be 'boolean'
Permission to delete the resource.
- datatype attribute for the access_delete_permission entity of a sharedresource_state should be 'boolean'
Permission to modify the resource's attributes (such as the date and time when a file was last modified).
- datatype attribute for the access_atrib_permission entity of a sharedresource_state should be 'boolean'
Permission to modify the permissions (read, write, create, execute, and delete) assigned to a resource for a user or application.
- datatype attribute for the access_perm_permission entity of a sharedresource_state should be 'boolean'
Permission to read, write, create, execute, and delete resources, and to modify their attributes and permissions.
- datatype attribute for the access_all_permission entity of a sharedresource_state should be 'boolean'
The sid test is used to check properties associated with the specified sid. 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 sid_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a sid_test must reference a sid_object
- the state child element of a sid_test must reference a sid_state
The sid_object element is used by a sid_test to define the object set, in this case a set of sids (identified by name), to be evaluated. Each object extends the standard ObjectType as definied 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.
The trustee_name element is the unique name that associated a particular SID. A SID can be associated with a user, group, or program (such as a Windows service). In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a sid_object should be 'string'
The sid_state element defines the different metadata associate with a Windows trustee (identified by name). Please refer to the individual elements in the schema for more details about what each represents.
This element specifies the trustee name associated with a particular SID. In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a sid_state should be 'string'
The security identifier (SID) of the specified trustee name.
- datatype attribute for the trustee_sid entity of a sid_state should be 'string'
The domain of the specified trustee name.
- datatype attribute for the trustee_domain entity of a sid_state should be 'string'
The SidBehaviors complex type defines a number of behaviors that allow a more detailed definition of the sid_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'include_group' defines whether the group sid should be included in the object when the object is defined by a group sid. For example, the intent of an object defined by a group sid might be to retrieve all the user sids that are a member of the group, but not the group sid itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
The sid_sid_test is used to check properties associated with the specified sid. 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 sid_sid_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
Note that this sid_sid test was added in version 5.4 as a temporary fix. There is a need within the community to identify things like users and groups by both the name and the sid. For version 6 of OVAL, work is underway for a better solution to the problem, but for now, a second test was added to satisfy the need.
- the object child element of a sid_sid_test must reference a sid_sid_object
- the state child element of a sid_sid_test must reference a sid_sid_state
The sid_sid_object element is used by a sid_sid_test to define the object set, in this case a set of sids, to be evaluated. Each object extends the standard ObjectType as definied 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.
The trustee_sid entity identifies a unique sid associated with a user, group, system, or program (such as a Windows service).
- datatype attribute for the trustee_sid entity of a sid_sid_object should be 'string'
The sid_state element defines the different metadata associate with a Windows trustee (identified by SID). Please refer to the individual elements in the schema for more details about what each represents.
The security identifier (SID) of the specified trustee name.
- datatype attribute for the trustee_sid entity of a sid_sid_state should be 'string'
This element specifies the trustee name associated with a particular SID. In a domain environment, trustee names should be identified in the form: "domain\trustee name" For local trustee names use: "computer name\trustee name" For built-in accounts on the system, use the trustee name without a domain. For example: ADMINISTRATOR, SYSTEM, NETWORK_SERVICES, ADMINISTRATORS (group), etc. Note that the built-in trustee names should be all caps as that is how the Windows APIs return them.
- datatype attribute for the trustee_name entity of a sid_sid_state should be 'string'
The domain of the specified trustee name.
- datatype attribute for the trustee_domain entity of a sid_sid_state should be 'string'
The SidSidBehaviors complex type defines a number of behaviors that allow a more detailed definition of the sid_sid_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'include_group' defines whether the group sid should be included in the object when the object is defined by a group sid. For example, the intent of an object defined by a group sid might be to retrieve all the user sids that are a member of the group, but not the group sid itself.
The 'resolve_group' behavior defines whether an object set defined by a group sid should be resolved to return a set that contains all the user sids that are a member of that group. Note that all child groups should also be resolved any valid domain users that are members of the group should also be included. The intent of this behavior is to end up with a list of all individual users from that system that make up the group once everything has been resolved.
The user access control test is used to check setting related to User Access Control within Windows. 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 uaac_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a uac_test must reference a uac_object
- the state child element of a uac_test must reference a uac_state
The uac_object element is used by a user access control test to define those objects to evaluate based on a specified state. There is actually only one object relating to user access control and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check user access control settings will reference the same uac_object which is basically an empty object element.
The uac_state element specifies the different settings that are available under User Access Control. A user access control test will reference a specific instance of this state that defines the exact settings that need to be evaluated. Please refer to the individual elements in the schema for more details about what each represents.
Admin Approval Mode for the Built-in Administrator account.
- datatype attribute for the admin_approval_mode entity of a uac_state should be 'boolean'
Behavior of the elevation prompt for administrators in Admin Approval Mode.
- datatype attribute for the elevation_prompt_admin entity of a uac_state should be 'string'
Behavior of the elevation prompt for standard users.
- datatype attribute for the elevation_prompt_standard entity of a uac_state should be 'string'
Detect application installations and prompt for elevation.
- datatype attribute for the detect_installations entity of a uac_state should be 'boolean'
Only elevate executables that are signed and validated.
- datatype attribute for the elevate_signed_executables entity of a uac_state should be 'boolean'
Only elevate UIAccess applications that are installed in secure locations.
- datatype attribute for the elevate_uiaccess entity of a uac_state should be 'boolean'
Run all administrators in Admin Approval Mode.
- datatype attribute for the run_admins_aam entity of a uac_state should be 'boolean'
Switch to the secure desktop when prompting for elevation.
- datatype attribute for the secure_desktop entity of a uac_state should be 'boolean'
Virtualize file and registry write failures to per-user locations.
- datatype attribute for the virtualize_write_failures entity of a uac_state should be 'boolean'
The user_test is used to check information about Windows users. When the user_test collects the users on the system, it should only include the local and built-in user accounts and not domain user accounts. However, it is important to note that domain user accounts can still be looked up. Also, note that the collection of groups, for which a user is a member, is not recursive. The only groups that will be collected are those for which the user is a direct member. For example, if a user is a member of group A, and group A is a member of group B, the only group that will be collected is group A. 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 user_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a user_test must reference a user_object
- the state child element of a user_test must reference a user_state
The user entity holds a string that represents the name of a particular user. In Windows, user names are case-insensitive and thus case does not matter for this entity. In a domain environment, users should be identified in the form: "domain\user name" For local users use: "computer name\user name" For built-in accounts on the system, use the user name without a domain. For example: ADMINISTRATOR, SYSTEM, etc. Note that the built-in user names should be all caps to help improve readability as that is how the Windows APIs return them. Of course techincally it does not matter since the names are case-insensitive.
- datatype attribute for the user entity of a user_object should be 'string'
The user_state element enumerates the different groups (identified by name) that a Windows user might belong to. Please refer to the individual elements in the schema for more details about what each represents.
The user entity holds a string that represents the name of a particular user. In Windows, user names are case-insensitive and thus case does not matter for this entity. In a domain environment, users should be identified in the form: "domain\user name" For local users use: "computer name\user name" For built-in accounts on the system, use the user name without a domain. For example: ADMINISTRATOR, SYSTEM, etc. Note that the built-in user names should be all caps to help improve readability as that is how the Windows APIs return them. Of course techincally it does not matter since the names are case-insensitive.
- datatype attribute for the user entity of a user_state should be 'string'
This element holds a boolean value that specifies whether the particular user account is enabled or not.
- datatype attribute for the enabled entity of a user_state should be 'boolean'
A string that represents the name of a particular group. In Windows, group names are case-insensitive and thus case does not matter for this entity. In a domain environment, groups should be identified in the form: "domain\group name" For local groups use: "computer name\group name" For built-in accounts on the system, use the group name without a domain. For example: ADMINISTRATORS, etc. Note that the built-in group names should be all caps as that is how the Windows APIs return them. Of course, techincally it does not matter since the names are case-insensitive.
The group element can be included multiple times in a system characteristic item in order to record that a user can be a member of a number of different groups. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like group that refer to items that can occur an unbounded number of times.
- datatype attribute for the group entity of a user_state should be 'string'
The user_sid55_test is used to check information about Windows users. When the user_sid55_test collects the user SIDs on the system, it should only include the local and built-in user SIDs and not domain user SIDs. However, it is important to note that domain user SIDs can still be looked up. Also, note that the collection of groups, for which a user is a member, is not recursive. The only groups that will be collected are those for which the user is a direct member. For example, if a user is a member of group A, and group A is a member of group B, the only group that will be collected is group A. 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 user_sid55_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a user_sid55_test must reference a user_sid55_object
- the state child element of a user_sid55_test must reference a user_sid55_state
The user_sid55_object represents a set of users on a Windows system. This set (which might contain only one user) is identified by a SID.
The user_sid entity holds a string that represents the SID of a particular user.
- datatype attribute for the user_sid entity of a user_sid55_object should be 'string'
The user_sid55_state element enumerates the different groups (identified by SID) that a Windows user might belong to. Please refer to the individual elements in the schema for more details about what each represents.
The user_sid entity holds a string that represents the SID of a particular user.
- datatype attribute for the user_sid entity of a user_sid55_state should be 'string'
This element holds a boolean value that specifies whether the particular user account is enabled or not.
- datatype attribute for the enabled entity of a user_sid55_state should be 'boolean'
A string the represents the SID of a particular group. The group_sid element can be included multiple times in a system characteristic item in order to record that a user can be a member of a number of different groups. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like group that refer to items that can occur an unbounded number of times.
- datatype attribute for the group_sid entity of a user_sid55_state should be 'string'
The user_sid_test is used to check information about Windows users. When the user_sid_test collects the user SIDs on the system, it should only include the local and built-in user SIDs and not domain user SIDs. However, it is important to note that domain user SIDs can still be looked up. Also, note that the collection of groups, for which a user is a member, is not recursive. The only groups that will be collected are those for which the user is a direct member. For example, if a user is a member of group A, and group A is a member of group B, the only group that will be collected is group A. 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 user_sid_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.5
Replaced by the user_sid55_test. This test uses user and group elements that are incorrectly named. A new test was created to change the element names to their correct values which are user_sid and group_sid. See the user_sid55_test.
This test has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED TEST: ID:
- the object child element of a user_sid_test must reference a user_sid_object
- the state child element of a user_sid_test must reference a user_sid_state
The user_sid_object represents a set of users on a Windows system. This set (which might contain only one user) is identified by a SID.
5.5
Replaced by the user_sid55_object. This object uses a user element that is incorrectly named. A new object was created to change the element name to its correct value which is user_sid. See the user_sid55_object.
This object has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED OBJECT: ID:
The user_sid entity holds a string that represents the SID of a particular user.
- datatype attribute for the user_sid entity of a user_sid_object should be 'string'
The user_sid_state element enumerates the different groups (identified by SID) that a Windows user might belong to. Please refer to the individual elements in the schema for more details about what each represents.
5.5
Replaced by the user_sid55_state. This state uses user and group elements that are incorrectly named. A new state was created to change the element names to their correct values which are user_sid and group_sid. See the user_sid55_state.
This state has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED STATE: ID:
The user_sid entity holds a string that represents the SID of a particular user.
- datatype attribute for the user_sid entity of a user_sid_state should be 'string'
This element holds a boolean value that specifies whether the particular user account is enabled or not.
- datatype attribute for the enabled entity of a user_state should be 'boolean'
A string the represents the SID of a particular group. The group_sid element can be included multiple times in a system characteristic item in order to record that a user can be a member of a number of different groups. Note that the entity_check attribute associated with EntityStateStringType guides the evaluation of entities like group that refer to items that can occur an unbounded number of times.
- datatype attribute for the group_sid entity of a user_sid_state should be 'string'
The volume_test is used to check information about different storage volumes found on a Windows system. This includes the various system flags returned by GetVolumeInformation(). It is important to note that these system flags are specific to certain versions of Windows. As a result, the documentation for that version of Windows should be consulted for more information. 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 volume_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a volume_test must reference a volume_object
- the state child element of a volume_test must reference a volume_state
The volume_object element is used by a volume test to define the specific volume(s) to be evaluated. Each object extends the standard ObjectType as definied 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.
A volume object defines the rootpath of the volume(s).
A string that contains the root directory of the volume to be described. A trailing backslash is required. For example, you would specify \\MyServer\MyShare as "\\MyServer\MyShare\", or the C drive as "C:\".
- datatype attribute for the rootpath entity of a volume_object should be 'string'
The volume_state element defines the different metadata associate with a storage volume in Windows. This includes the rootpath, the file system type, name, and serial number, as well as any associated flags. Please refer to the individual elements in the schema for more details about what each represents. The GetVolumeInformation function as defined by Microsoft is also a good place to look for information.
A string that contains the root directory of the volume to be described. A trailing backslash is required. For example, you would specify \\MyServer\MyShare as "\\MyServer\MyShare\", or the C drive as "C:\".
- datatype attribute for the rootpath entity of a volume_state should be 'string'
The type of filesystem. For example FAT or NTFS.
- datatype attribute for the file_system entity of a volume_state should be 'string'
The name of the volume.
- datatype attribute for the name entity of a volume_state should be 'string'
The volume_max_component_length element specifies the maximum length, in TCHARs, of a file name component that a specified file system supports. A file name component is the portion of a file name between backslashes. The value that is stored in the variable that *lpMaximumComponentLength points to is used to indicate that a specified file system supports long names. For example, for a FAT file system that supports long names, the function stores the value 255, rather than the previous 8.3 indicator. Long names can also be supported on systems that use the NTFS file system.
- datatype attribute for the volume_max_component_length entity of a volume_state should be 'int'
The volume serial number.
- datatype attribute for the serial_number entity of a volume_state should be 'int'
The file system supports case-sensitive file names.
- datatype attribute for the file_case_sensitive_search entity of a volume_state should be 'boolean'
The file system preserves the case of file names when it places a name on disk.
- datatype attribute for the file_case_preserved_names entity of a volume_state should be 'boolean'
The file system supports Unicode in file names as they appear on disk.
- datatype attribute for the file_unicode_on_disk entity of a volume_state should be 'boolean'
The file system preserves and enforces ACLs. For example, NTFS preserves and enforces ACLs, and FAT does not.
- datatype attribute for the file_persistent_acls entity of a volume_state should be 'boolean'
The file system supports file-based compression.
- datatype attribute for the file_file_compression entity of a volume_state should be 'boolean'
The file system supports disk quotas.
- datatype attribute for the file_volume_quotas entity of a volume_state should be 'boolean'
The file system supports sparse files.
- datatype attribute for the file_supports_sparse_files entity of a volume_state should be 'boolean'
The file system supports reparse points.
- datatype attribute for the file_supports_reparse_points entity of a volume_state should be 'boolean'
The specified volume is a compressed volume; for example, a DoubleSpace volume.
- datatype attribute for the file_supports_remote_storage entity of a volume_state should be 'boolean'
The specified volume is a compressed volume; for example, a DoubleSpace volume.
- datatype attribute for the file_volume_is_compressed entity of a volume_state should be 'boolean'
The file system supports object identifiers.
- datatype attribute for the file_supports_object_ids entity of a volume_state should be 'boolean'
The file system supports the Encrypted File System (EFS).
- datatype attribute for the file_supports_encryption entity of a volume_state should be 'boolean'
The file system supports named streams.
- datatype attribute for the file_named_streams entity of a volume_state should be 'boolean'
The specified volume is read-only.
- datatype attribute for the file_read_only_volume entity of a volume_state should be 'boolean'
The wmi test is used to check information accessed by WMI. 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 wmi_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
5.7
Replaced by the wmi57_test. This test only allows for single fields to be selected from WMI. A new test was created to allow more than one field to be selected in one statement. See the wmi57_test.
This test has been deprecated and may be removed in a future version of the language.
DEPRECATED TEST: ID:
- the object child element of a wmi_test must reference a wmi_object
- the state child element of a wmi_test must reference a wmi_state
5.7
Replaced by the wmi57_object. This object allows for single fields to be selected from WMI. A new object was created to allow more than one field to be selected in one statement. See the wmi57_object.
This object has been deprecated and may be removed in a future version of the language.
DEPRECATED OBJECT: ID:
Specifies which WMI namespace to look under. Each WMI provider normally registers its own WMI namespace and then all its classes within that namespace. For example, all Win32 WMI classes can be found in the namespace "root\cimv2", all IIS WMI classes can be found at "root\microsoftiisv2", and all LDAP WMI classes can be found at "root\directory\ldap".
- datatype attribute for the namespace entity of a wmi_object should be 'string'
- operation attribute for the namespace entity of a wmi_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one)
A WQL query used to identify the object(s) to test against. Any valid WQL query is usable with one exception, at most one field is allowed in the SELECT portion of the query. For example SELECT name FROM ... is valid, as is SELECT 'true' FROM ..., but SELECT name, number FROM ... is not valid. This is because the result element in the data section is only designed to work against a single field.
- datatype attribute for the wql entity of a wmi_object should be 'string'
- operation attribute for the wql entity of a wmi_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one)
5.7
Replaced by the wmi57_state. This object allows for single fields to be selected from WMI. A new state was created to allow more than one field to be selected in one statement. See the wmi57_state.
This state has been deprecated and may be removed in a future version of the language.
DEPRECATED STATE: ID:
Specifies which WMI namespace to look under. Each WMI provider normally registers its own WMI namespace and then all its classes within that namespace. For example, all Win32 WMI classes can be found in the namespace "root\cimv2", all IIS WMI classes can be found at "root\microsoftiisv2", and all LDAP WMI classes can be found at "root\directory\ldap".
- datatype attribute for the namespace entity of a wmi_state should be 'string'
A WQL query used to identify the object(s) to test against. Any valid WQL query is usable with one exception, at most one field is allowed in the SELECT portion of the query. For example SELECT name FROM ... is valid, as is SELECT 'true' FROM ..., but SELECT name, number FROM ... is not valid. This is because the result element in the data section is only designed to work against a single field.
- datatype attribute for the wql entity of a wmi_state should be 'string'
The result element specifies how to test objects in the result set of the specified WQL statement. Only one comparable field is allowed. So if the WQL statement look like 'SELECT name FROM ...', then a result element with a value of 'Fred' would test that value against the names returned by the WQL statement.
- datatype attribute for the entity of an should not be 'record'
The wmi57 test is used to check information accessed by WMI. 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 wmi57_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
- the object child element of a wmi57_test must reference a wmi57_object
- the state child element of a wmi57_test must reference a wmi57_state
Specifies which WMI namespace to look under. Each WMI provider normally registers its own WMI namespace and then all its classes within that namespace. For example, all Win32 WMI classes can be found in the namespace "root\cimv2", all IIS WMI classes can be found at "root\microsoftiisv2", and all LDAP WMI classes can be found at "root\directory\ldap".
- datatype attribute for the namespace entity of a wmi57_object should be 'string'
- operation attribute for the namespace entity of a wmi57_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one)
A WQL query used to identify the object(s) to test against. Any valid WQL query is usable with one exception, all fields must be named in the SELECT portion of the query. For example SELECT name, age FROM ... is valid. However, SELECT * FROM ... is not valid. This is because the record element in the state and item require a unique field name value to ensure that any query results can be evaluated consistantly.
- datatype attribute for the wql entity of a wmi57_object should be 'string'
- operation attribute for the wql entity of a wmi57_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one)
Specifies which WMI namespace to look under. Each WMI provider normally registers its own WMI namespace and then all its classes within that namespace. For example, all Win32 WMI classes can be found in the namespace "root\cimv2", all IIS WMI classes can be found at "root\microsoftiisv2", and all LDAP WMI classes can be found at "root\directory\ldap".
- datatype attribute for the namespace entity of a wmi57_state should be 'string'
A WQL query used to identify the object(s) to test against. Any valid WQL query is usable with one exception, all fields must be named in the SELECT portion of the query. For example SELECT name, age FROM ... is valid. However, SELECT * FROM ... is not valid. This is because the record element in the state and item require a unique field name value to ensure that any query results can be evaluated consistantly.
- datatype attribute for the wql entity of a wmi57_state should be 'string'
The result element specifies how to test items in the result set of the specified WQL statement.
- datatype attribute for the entity of an should be 'record'
The wuaupdatesearcher_test is used to evaluate patch level in a Windows environment utilizing the WUA (Windows Update Agent) interface. It is based on the Search method of the IUpdateSearcher interface found in the WUA API. 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 wuaupdatesearcher_object and the optional state element specifies the metadata to check. The evaluation of the test is guided by the check attribute that is inherited from the TestType.
Note that WUA can work off of many different sources including WSUS, update.microsoft.com, and a local cab file. The content source is specific to a given system evaluating a wuaupdatesearcher_test and thus is not defined by this test. The tool being used for evaluation should determine what content source is best for the system being assessed and then evaluate this test based on that selection.
- the object child element of a wuaupdatesearcher_test must reference a wuaupdatesearcher_object
- the state child element of a wuaupdatesearcher_test must reference a wuaupdatesearcher_state
The wuaupdatesearcher_object element is used by a wuaupdatesearcher_test to define the specific search criteria to be evaluated. Each object extends the standard ObjectType as definied 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.
The search_criteria entity specifies a search criteria to use when generating a search result. The string used for the search criteria entity must match the custom search language for Search method of the IUpdateSearcher interface. The string consists of criteria that are evaluated to determine which updates to return. The Search method performs a synchronous search for updates by using the current configured search options. For more information about possible search criteria, please see the Search method of the IUpdateSearcher interface.
- datatype attribute for the search_criteria entity of a wuaupdatesearcher_object should be 'string'
- operation attribute for the search_criteria entity of a wuaupdatesearcher_object should be 'equals'
The wuaupdatesearcher_state element defines entities that can be tested related to a uaupdatesearcher_object. This includes the search criteria and updated id. Please refer to the individual elements in the schema for more details about what each represents.
The search_criteria entity specifies a string to examine the search criteria that was used to generate the object set. Note that since this entity is part of the state, it is not used to determine the object set, but rather is used to test the search criteria that was actually used.
- datatype attribute for the entity of a should be 'string'
The update_id enity specifies a string that represents a revision-independent identifier of an update. This information is part of the IUpdateIdentity interface that is part of the result of the IUpdateSearcher interface's Search method.
- datatype attribute for the entity of a should be 'string'
The WuaUpdateSearcherBehaviors complex type defines behaviors that allow a more detailed definition of the wuaupdatesearcher_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
'include_superseded_updates' is a boolean flag that when set to true indicates that the search results should include updates that are superseded by other updates in the search results. When set to 'false' superseded updates should be excluded from the set of matching update items. The default value is 'true'.
The EntityStateAddrTypeType complex type restricts a string value to a specific set of values that describe address types associated with an interface. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The stated IP address is being deleted. The unsigned short value that this corresponds to is 0x0040
The stated IP address is on a disconnected interface. The unsigned short value that this corresponds to is 0x0008.
The stated IP address is a dynamic IP address. The unsigned short value that this corresponds to is 0x0004.
The stated IP address is a primary IP address. The unsigned short value that this corresponds to is 0x0001.
The stated IP address is a transient IP address. The unsigned short value that this corresponds to is 0x0080
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateAdstypeType complex type restricts a string value to a specific set of values that specify the different types of information that an active directory attribute can represents. For more information look at the ADSTYPEENUM enumeration defined by Microsoft. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The data type is invalid.
The string is of Distinguished Name (path) of a directory service object.
The string is of the case-sensitive type.
The string is of the case-insensitive type.
The string is displayable on the screen or in print.
The string is of a numeric value to be interpreted as text.
The data is of a Boolean value.
The data is of an integer value.
The string is of a byte array.
The data is of the universal time as expressed in Universal Time Coordinate (UTC).
The data is of a long integer value.
The string is of a provider-specific string.
Not used.
The data is of a list of case insensitive strings.
The data is of a list of octet strings.
The string is of a directory path.
The string is of the postal address type.
The data is of a time stamp in seconds.
The string is of a back link.
The string is of a typed name.
The data is of the Hold data structure.
The string is of a net address.
The data is of a replica pointer.
The string is of a fax number.
The data is of an e-mail message.
The data is of Windows NT/Windows 2000 Security Descriptor as represented by a byte array.
The data is of an undefined type.
The data is of ADS_DN_WITH_BINARY used for mapping a distinguished name to a non varying GUID.
The data is of ADS_DN_WITH_STRING used for mapping a distinguished name to a non-varying string value.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateAuditType complex type restricts a string value to a specific set of values: AUDIT_NONE, AUDIT_SUCCESS, AUDIT_FAILURE, and AUDIT_SUCCESS_FAILURE. These values describe which audit records should be generated. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The audit type AUDIT_FAILURE is used to perform audits on all unsuccessful occurrences of specified events when auditing is enabled.
The audit type AUDIT_NONE is used to cancel all auditing options for the specified events.
The audit type AUDIT_SUCCESS is used to perform audits on all successful occurrences of the specified events when auditing is enabled.
The audit type AUDIT_SUCCESS_FAILURE is used to perform audits on all successful and unsuccessful occurrences of the specified events when auditing is enabled.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateInterfaceTypeType complex type restricts a string value to a specific set of values. These values describe the different interface types. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The MIB_IF_TYPE_ETHERNET type is used to describe ethernet interfaces.
The MIB_IF_TYPE_FDDI type is used to describe fiber distributed data interfaces (FDDI).
The MIB_IF_TYPE_LOOPBACK type is used to describe loopback interfaces.
The MIB_IF_TYPE_OTHER type is used to describe unknown interfaces.
The MIB_IF_TYPE_PPP type is used to describe point-to-point protocol interfaces (PPP).
The MIB_IF_TYPE_SLIP type is used to describe serial line internet protocol interfaces (SLIP).
The MIB_IF_TYPE_TOKENRING type is used to describe token ring interfaces..
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateFileTypeType complex type restricts a string value to a specific set of values. These values describe the type of file being represented. For more information see the GetFileType and GetFileAttributesEx functions as defined by Microsoft. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The handle identifies a directory.
The specified file is a character file, typically an LPT device or a console.
The specified file is a disk file.
The specified file is a socket, a named pipe, or an anonymous pipe.
Unused.
Either the type of the specified file is unknown, or the function failed.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityObjectNamingContextType restricts a string value to a specific set of values: domain, configuration, and schema. These values describe the different default naming context found in active directory. A naming context is defined as a single object in the Directory Information Tree (DIT) along with every object in the tree subordinate to it. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The domain naming context contains Active Directory objects present in the specified domain (e.g. users, computers, groups, and other objects).
The configuration naming context contains configuration data that is required for the Active Directory to operate as a directory service.
The schema naming context contains all of the Active Directory object definitions.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateNamingContextType restricts a string value to a specific set of values: domain, configuration, and schema. These values describe the different default naming context found in active directory. A naming context is defined as a single object in the Directory Information Tree (DIT) along with every object in the tree subordinate to it. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The domain naming context contains Active Directory objects present in the specified domain (e.g. users, computers, groups, and other objects).
The configuration naming context contains configuration data that is required for the Active Directory to operate as a directory service.
The schema naming context contains all of the Active Directory object definitions.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityObjectProtocolType restricts a string value to a specific set of values: TCP and UDP. These values describe the different protocols available to a port. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The port uses the Transmission Control Protocol (TCP).
The port uses the User Datagram Protocol (UDP).
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateProtocolType restricts a string value to a specific set of values: TCP and UDP. These values describe the different protocols available to a port. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
The port uses the Transmission Control Protocol (TCP).
The port uses the User Datagram Protocol (UDP).
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityObjectRegistryHiveType restricts a string value to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS. These values describe the possible hives in the registry. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
This registry subtree contains information that associates file types with programs and configuration data for automation (e.g. COM objects and Visual Basic Programs).
This registry subtree contains configuration data for the current hardware profile.
This registry subtree contains the user profile of the user that is currently logged into the system.
This registry subtree contains information about the local system.
This registry subtree contains user-specific data.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateRegistryHiveType restricts a string value to a specific set of values: HKEY_CLASSES_ROOT, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS. These values describe the possible hives in the registry. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
This registry subtree contains information that associates file types with programs and configuration data for automation (e.g. COM objects and Visual Basic Programs).
This registry subtree contains configuration data for the current hardware profile.
This registry subtree contains the user profile of the user that is currently logged into the system.
This registry subtree contains information about the local system.
This registry subtree contains user-specific data.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateRegistryTypeType complex type defines the different values that are valid for the type entity of a registry state. These values describe the possible types of data stored in a registry key. The empty string is also allowed as a valid value to support an empty element that is found when a variable reference is used within the type entity. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values. Please note that the values identified are for the type entity and are not valid values for the datatype attribute. For information about how to encode registry data in OVAL for each of the different types, please visit the registry_state documentation.
The reg_binary type is used by registry keys that specify binary data in any form.
The reg_dword type is used by registry keys that specify a 32-bit number.
The reg_expand_sz type is used by registry keys to specify a null-terminated string that contains unexpanded references to environment variables (for example, "%PATH%").
The reg_multi_sz type is used by registry keys that specify an array of null-terminated strings, terminated by two null characters.
The reg_none type is used by registry keys that have no defined value type.
The reg_qword type is used by registry keys that specify a 64-bit number.
The reg_sz type is used by registry keys that specify a single null-terminated string.
The empty string value is permitted here to allow for empty elements associated with variable references.
The EntityStateSharedResourceTypeType complex type defines the different values that are valid for the type entity of a shared resource state. Note that the Windows API returns a DWORD value and OVAL uses the constant name that is normally defined for these return values. This is done to increase readability and maintainability of OVAL Definitions. The empty string is also allowed as a valid value to support an empty element that is found when a variable reference is used within the type entity. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
It is also important to note that special shared resources are those reserved for remote administration, interprocess communication, and administrative shares.
The STYPE_DISKTREE type means that the shared resource is a disk drive. The DWORD value that this corresponds to is 0x00000000.
The STYPE_DISKTREE_SPECIAL type means that the shared resource is a special disk drive. The DWORD value that this corresponds to is 0x80000000.
The STYPE_DISKTREE_TEMPORARY type means that the shared resource is a temporary disk drive. The DWORD value that this corresponds to is 0x40000000.
The STYPE_DISKTREE_SPECIAL_TEMPORARY type means that the shared resource is a temporary, special disk drive. The DWORD value that this corresponds to is 0xC0000000.
The STYPE_PRINTQ type means that the shared resource is a print queue. The DWORD value that this corresponds to is 0x00000001.
The STYPE_PRINTQ_SPECIAL type means that the shared resource is a special print queue. The DWORD value that this corresponds to is 0x80000001.
The STYPE_PRINTQ_TEMPORARY type means that the shared resource is a temporary print queue. The DWORD value that this corresponds to is 0x40000001.
The STYPE_PRINTQ_SPECIAL_TEMPORARY type means that the shared resource is a temporary, special print queue. The DWORD value that this corresponds to is 0xC0000001.
The STYPE_DEVICE type means that the shared resource is a communication device. The DWORD value that this corresponds to is 0x00000002.
The STYPE_DEVICE_SPECIAL type means that the shared resource is a special communication device. The DWORD value that this corresponds to is 0x80000002.
The STYPE_DEVICE_TEMPORARY type means that the shared resource is a temporary communication device. The DWORD value that this corresponds to is 0x40000002.
The STYPE_DEVICE_SPECIAL_TEMPORARY type means that the shared resource is a temporary, special communication device. The DWORD value that this corresponds to is 0xC0000002.
The STYPE_IPC type means that the shared resource is a interprocess communication. The DWORD value that this corresponds to is 0x00000003.
The STYPE_IPC_SPECIAL type means that the shared resource is a special interprocess communication. The DWORD value that this corresponds to is 0x80000003.
The STYPE_IPC_TEMPORARY type means that the shared resource is a temporary interprocess communication. The DWORD value that this corresponds to is 0x40000003.
The STYPE_IPC_SPECIAL_TEMPORARY type means that the shared resource is a temporary, special interprocess communication. The DWORD value that this corresponds to is 0xC0000003.
The STYPE_SPECIAL type means that this is a special share reserved for interprocess communication (IPC$) or remote administration of the server (ADMIN$). Can also refer to administrative shares such as C$, D$, E$, and so forth. The DWORD value that this corresponds to is 0x40000000.
5.6
In version 5.6 of the OVAL Language, the EntityStateSharedResourceTypeType was changed to include all of the different shared resource types as specified in Microsoft's documentation of the shi2_type member of the SHARE_INFO_2 structure. As a result, the STYPE_SPECIAL value by itself is no longer valid because it would actually be equal to the value STYPE_DISKTREE_SPECIAL (0x80000000) which is STYPE_DISKTREE (0x00000000) OR'd with STYPE_SPECIAL (0x80000000).
This value has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED ELEMENT VALUE IN: sharedresource_state ELEMENT VALUE:
The STYPE_TEMPORARY type means that the shared resource is a temporary share. The DWORD value that this corresponds to is 0x80000000.
5.6
In version 5.6 of the OVAL Language, the EntityStateSharedResourceTypeType was changed to include all of the different shared resource types as specified in Microsoft's documentation of the shi2_type member of the SHARE_INFO_2 structure. As a result, the STYPE_TEMPORARY value by itself is no longer valid because it would actually be equal to the value STYPE_DISKTREE_TEMPORARY (0x40000000) which is STYPE_DISKTREE (0x00000000) OR'd with STYPE_TEMPORARY (0x40000000).
This value has been deprecated and will be removed in version 6.0 of the language.
DEPRECATED ELEMENT VALUE IN: sharedresource_state ELEMENT VALUE:
The empty string value is permitted here to allow for empty elements associated with variable references.