The following is a description of the elements, types, and attributes that compose the MacOS 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 MacOS Definition Schema was initially developed by The Center for Internet Security. Many thanks to their contributions to OVAL and the security community. The OVAL Schema is maintained by the OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.cisecurity.org. MacOS Definition 5.11.1:1.2 11/30/2016 09:00:00 AM Copyright (c) 2016, Center for Internet Security. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at https://oval.cisecurity.org/terms. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included. User account information (username, uid, gid, etc.) See netinfo(5) for field information, niutil(1) for retrieving it. As of Mac OS 10.5, niutil(1) is no longer available, however, the same functionality can be obtained using dscl(1). Specifically, the command 'dscl . -list /Users' can be used to list all users and the command 'dscl . -read /Users/some_user passwd uid gid realname home shell' can be used to retrieve the attributes associated with an account. accountinfo_test accountinfo_object accountinfo_state accountinfo_item - the object child element of an accountinfo_test must reference an accountinfo_object - the state child element of an accountinfo_test must reference an accountinfo_state The accountinfo_object element is used by an accountinfo_test to define the object(s) to be evaluated. This object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. An accountinfo_object consists of a single username that identifies the account from which to gather information. State referenced in filter for '' is of the wrong type. Specifies the user of the account to gather information from. The accountinfo_state element defines the different information that can be used to evaluate the specified accounts. Please refer to the individual elements in the schema for more details about what each represents. Specifies the user of the account to gather information from. Obfuscated (*****) or encrypted password for this user. The numeric user id, or uid, is the third column of each user's entry in /etc/passwd. This element represents the owner of the file. Group ID of this account. User's real name, aka gecos field of /etc/passwd. The home directory for this user account. The login shell for this user account. The authorizationdb_test is used to check the properties of the plist-style XML output from the "security authorizationdb read >right-name<" command, for reading information about rights authorizations on MacOSX. 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 authorizationdb_object and the optional state element specifies the data to check. authorizationdb_test authorizationdb_object authorizationdb_state authorizationdb_item - the object child element of a authorizationdb_test must reference an authorizationdb_object - the state child element of a authorizationdb_test must reference an authorizationdb_state The authorizationdb_object element is used by an authorizationdb_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. An authorizationdb_object consists of a right_name entity that contains the name of the right to be read from the authorization dabatase. The resulting plist data can be queried using the xpath entity. State referenced in filter for '' is of the wrong type. Specifies the right name to be queried (read) from the authorization database. Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. Any valid Xpath 1.0 statement is usable with one exception, at most one field may be identified in the Xpath. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible. - operation attribute for the xpath entity of an authorizationdb_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) The authorizationdb_state element defines a value used to evaluate the result of a specific authorizationdb_object item. Specifies the right_name used to create the object. Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. The value_of element checks the value(s) of the text node(s) or attribute(s) found. The corestorage_test is used to check the properties of the plist-style XML output from the "diskutil cs list -plist" command, for reading information about the CoreStorage setup on MacOSX. 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 corestorage_object and the optional state element specifies the data to check. corestorage_test corestorage_object corestorage_state corestorage_item - the object child element of a corestorage_test must reference an corestorage_object - the state child element of a corestorage_test must reference an corestorage_state The corestorage_object element is used by an corestorage_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. An corestorage_object consists of a uuid entity that contains the UUID of the volume whose information should be read (i.e., 'diskutil cs info -plist [UUID]'). The resulting plist data can be queried using the xpath entity. State referenced in filter for '' is of the wrong type. Specifies the UUID of the volume about which the plist information should be retrieved. Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. Any valid Xpath 1.0 statement is usable with one exception, at most one field may be identified in the Xpath. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible. - operation attribute for the xpath entity of an corestorage_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) The corestorage_state element defines a value used to evaluate the result of a specific corestorage_object item. Specifies the UUID of the volume about which the plist information was retrieved. Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. The value_of element checks the value(s) of the text node(s) or attribute(s) found. The diskutil_test is used to verify packages on a Mac OS system. The information used by this test is modeled after the diskutil command's verifyPermissions option. On MacOS X 10.11 and later, this option was replaced by the repair_packages command. For more information, see diskutil(8) or repair_packages(8). 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 diskutil_object and the optional diskutil_state element specifies the data to check. diskutil_test diskutil_object diskutil_state diskutil_item - the object child element of a diskutil_test must reference a diskutil_object - the state child element of a diskutil_test must reference a diskutil_state The diskutil_object element is used by a diskutil_test to define the volumes containing packages to be verified on a Mac OS system. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. State referenced in filter for '' is of the wrong type. The device entity is a string that represents the name of a volume containing system packages that is mounted on a Mac OS system to verify. Please see diskutil(8) or repair_packages(8) for instructions on how to specify the volume. The filepath element specifies the absolute path for a file or directory in the specified package. The diskutil_state element defines the different verification information associated with a disk on a Mac OS system. Please refer to the individual elements in the schema for more details about what each represents. The device entity is a string that represents the volume on a Mac OS system to verify. Please see diskutil(8) or repair_packages(8) for instructions on how to specify the device. The filepath element specifies the absolute path for a file or directory on the specified device. Has the actual user read permission changed from the expected user read permission? Has the actual user write permission changed from the expected user write permission? Has the actual user exec permission changed from the expected user exec permission? Has the actual group read permission changed from the expected group read permission? Has the actual group write permission changed from the expected group write permission? Has the actual group exec permission changed from the expected group exec permission? Has the actual others read permission changed from the expected others read permission? Has the actual others write permission changed from the expected others write permission? Has the actual others exec permission changed from the expected others exec permission? Has the actual user changed from the expected user? The actual user of the file/directory. The expected user of the file/directory. Has the actual group changed from the expected group? The actual group of the file/directory. The expected group of the file/directory. Has the actual symlink changed from the expected symlink? The actual symlink of the file/directory. The expected symlink of the file/directory. The gatekeeper_test is used to check the status of Gatekeeper and any unsigned applications that have been granted execute permission. gatekeeper_test gatekeeper_object gatekeeper_state gatekeeper_item - the object child element of a gatekeeper_test must reference an gatekeeper_object - the state child element of a gatekeeper_test must reference an gatekeeper_state The gatekeeper_object is a singleton used to access information about Gatekeeper. The gatekeeper_state element makes it possible to make assertions about Gatekeeper's operational status and unsigned applications that have been granted execute permission. The status of Gatekeeper assessments. The path to an unsigned application folder to which Gatekeeper has granted execute permission. This test's purpose is generally used to check if an application is listening on the network, either for a new connection or as part of an ongoing connection. This is limited to applications that are listening for connections that use the TCP or UDP protocols and have addresses represented as IPv4 or IPv6 addresses (AF_INET or AF_INET6). It is generally speaking the parsed output of running the command netstat -tuwlnpe with root privilege. inetlisteningservers_test inetlisteningservers_object inetlisteningservers_state inetlisteningserver_item 5.10 The inetlisteningservers_test has been deprecated and replaced by the inetlisteningserver510_test. The name of an application cannot be used to uniquely identify an application that is listening on the network. As a result, the inetlisteningserver510_object utilizes the protocol, local_address, and local_port entities to uniquely identify an application listening on the network. Please see the inetlisteningserver510_test for additional information. DEPRECATED TEST: ID: - the object child element of an inetlisteningservers_test must reference an inetlisteningservers_object - the state child element of an inetlisteningservers_test must reference an inetlisteningservers_state The inetlisteningservers_object element is used by an inetlisteningserver test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. 5.10 The inetlisteningservers_object has been deprecated and replaced by the inetlisteningserver510_object. The name of an application cannot be used to uniquely identify an application that is listening on the network. As a result, the inetlisteningserver510_object utilizes the protocol, local_address, and local_port entities to uniquely identify an application listening on the network. Please see the inetlisteningserver510_object for additional information. DEPRECATED OBJECT: ID: State referenced in filter for '' is of the wrong type. The inetlisteningservers_state element defines the different information that can be used to evaluate the specified inet listening server. This includes the local address, foreign address, port information, and process id. Please refer to the individual elements in the schema for more details about what each represents. 5.10 The inetlisteningservers_state has been deprecated and replaced by the inetlisteningserver510_state. The name of an application cannot be used to uniquely identify an application that is listening on the network. As a result, the inetlisteningserver510_object utilizes the protocol, local_address, and local_port entities to uniquely identify an application listening on the network. Please see the inetlisteningserver510_state for additional information. DEPRECATED STATE: ID: This is the name of the communicating program. This is the IP address of the network interface on which the program listens. Note that the IP address can be IPv4 or IPv6. This is the IP address and network port on which the program listens, equivalent to local_address:local_port. Note that the IP address can be IPv4 or IPv6. This is the TCP or UDP port on which the program listens. Note that this is not a list -- if a program listens on multiple ports, or on a combination of TCP and UDP, each will have its own entry in the table data stored by this test. This is the IP address with which the program is communicating, or with which it will communicate, in the case of a listening server. Note that the IP address can be IPv4 or IPv6. This is the IP address and network port to which the program is communicating or will accept communications from, equivalent to foreign_address:foreign_port. Note that the IP address can be IPv4 or IPv6. This is the TCP or UDP port to which the program communicates. In the case of a listening program accepting new connections, this is usually '0'. This is the process ID of the process. The process in question is that of the program communicating on the network. This is the transport-layer protocol, in lowercase: tcp or udp. The numeric user id, or uid, is the third column of each user's entry in /etc/passwd. It represents the owner, and thus privilege level, of the specified program. The inetlisteningserver510_test is used to check if an application is listening on the network, either for a new connection or as part of an ongoing connection. This is limited to applications that are listening for connections that use the TCP or UDP protocols and have addresses represented as IPv4 or IPv6 addresses (AF_INET or AF_INET6). One method for retrieving the required information is by parsing the output of the command 'lsof -i -P -n -l' with root privileges. inetlisteningserver510_test inetlisteningserver510_object inetlisteningserver510_state inetlisteningserver510_item - the object child element of an inetlisteningserver510_test must reference an inetlisteningserver510_object - the state child element of an inetlisteningserver510_test must reference an inetlisteningserver510_state The inetlisteningserver510_object element is used by an inetlisteningserver510_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. State referenced in filter for '' is of the wrong type. The protocol entity defines a certain transport-layer protocol, in lowercase: tcp or udp. This is the IP address of the network interface on which an application listens. Note that the IP address can be IPv4 or IPv6. This is the TCP or UDP port on which an application would listen. Note that this is not a list -- if a program listens on multiple ports, or on a combination of TCP and UDP, each will be represented by its own object. The inetlisteningserver510_state element defines the different information that can be used to evaluate the specified inet listening server. This includes the local address, foreign address, port information, and process id. Please refer to the individual elements in the schema for more details about what each represents. This is the transport-layer protocol, in lowercase: tcp or udp. This is the IP address of the network interface on which the program listens. Note that the IP address can be IPv4 or IPv6. This is the TCP or UDP port on which the program listens. Note that this is not a list -- if a program listens on multiple ports, or on a combination of TCP and UDP, each will have its own entry in the table data stored by this test. This is the IP address and network port on which the program listens, equivalent to local_address:local_port. Note that the IP address can be IPv4 or IPv6. This is the name of the communicating program. This is the IP address with which the program is communicating, or with which it will communicate, in the case of a listening server. Note that the IP address can be IPv4 or IPv6. This is the TCP or UDP port to which the program communicates. In the case of a listening program accepting new connections, this is usually '0'. This is the IP address and network port to which the program is communicating or will accept communications from, equivalent to foreign_address:foreign_port. Note that the IP address can be IPv4 or IPv6. This is the process ID of the process. The process in question is that of the program communicating on the network. The numeric user id, or uid, is the third column of each user's entry in /etc/passwd. It represents the owner, and thus privilege level, of the specified program. The keychain_test is used to check the properties of the plist-style XML output from the "security show-keychain-info >keychain<" command, for reading information about keychain settings on MacOSX. 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 keychain_object and the optional state element specifies the data to check. keychain_test keychain_object keychain_state keychain_item - the object child element of a keychain_test must reference an keychain_object - the state child element of a keychain_test must reference an keychain_state The keychain_object element is used by an corestorage_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. A keychain_object consists of a keychain (name) entity that contains the name of the keychain whose settings will be queried. State referenced in filter for '' is of the wrong type. Specifies the filepath of the keychain to be queried. The default keychain for a user is normally located at ~/Library/Keychains/login.keychain. The keychain_state element defines a value used to evaluate the result of a specific keychain_object item. Specifies the filepath of the keychain used to create the object. Specifies whether the keychain is configured to lock when the computer sleeps. Specifies the inactivity timeout (in seconds) for the keychain, or 0 if there is no timeout. The launchd_test is used to check the status of daemons/agents loaded via the launchd service. 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 launchd_object and the optional state element specifies the data to check. launchd_test launchd_object launchd_state launchd_item - the object child element of a launchd_test must reference an launchd_object - the state child element of a launchd_test must reference an launchd_state The launchd_object element is used by a launchd_test to define the daemon/agent to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. A launchd_object consists of a label (name) entity that contains the name of the agent/daemon whose attributes will be queried. State referenced in filter for '' is of the wrong type. Specifies the deamon to be queried. The launchd_state element defines a value used to evaluate the result of a specific launchd_object item. Specifies the name of the agent/daemon used to create the object. Specifies the process ID of the daemon (if any). Specifies the last exit code of the daemon (if any), or if $lt; 0, indicates the negative of the signal that interrupted processing. For example, a value of -15 would indicate that the job was terminated via a SIGTERM. This test pulls data from the 'nvram -p' output. nvram_test nvram_object nvram_state nvram_item - the object child element of an nvram_test must reference an nvram_object - the state child element of an nvram_test must reference an nvram_state The nvram_object element is used by a nvram test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. State referenced in filter for '' is of the wrong type. This test pulls data from the 'nvram -p' output. This specifies the nvram variable to check. This is the value of the associated nvram variable. The plist_test is used to check the value(s) associated with property list preference 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 plist_object and the optional plist_state element specifies the data to check. plist_test plist_object plist_state plist_item 5.10 Replaced by the plist510_test. This test references the plist_object which does not contain an instance entity. As a result, it is not possible to differentiate between two preference keys that have the same name using the plist_object. The plist510_test was added to address this deficiency. See the plist510_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 plist_test must reference a plist_object - the state child element of a plist_test must reference a plist_state The plist_object element is used by a plist_test to define the preference keys to collect and where to look for them. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. 5.10 Replaced by the plist510_object. This object does not contain an instance entity. As a result, it is not possible to differentiate between two preference keys that have the same name using this object. The plist510_object was added to address this deficiency. See the plist510_object. This object has been deprecated and may be removed in a future version of the language. DEPRECATED OBJECT: ID: State referenced in filter for '' is of the wrong type. The preference key to check. If the xsi:nil attribute is set to 'true', the plist does not have any keys associated with it (i.e. it is not a CFDictionary) and the default value of the plist will be collected. The unique application identifier that specifies the application to use when looking up the preference key (e.g. com.apple.Safari). The absolute path to a plist file (e.g. ~/Library/Preferences/com.apple.Safari.plist). A directory cannot be specified as a filepath. - operation attribute for the filepath entity of a plist_object should be 'equals' The plist_state element defines the different information that can be used to evaluate the specified property list preference key. This includes the preference key, application identifier, filepath, type, as well as the preference key's value. Please refer to the individual elements in the schema for more details about what each represents. 5.10 Replaced by the plist510_state. This state is used in conjunction with the plist_object which does not contain an instance entity. As a result, it is not possible to differentiate between two preference keys that have the same name using the plist_object. The plist510_state was added to address this deficiency. See the plist510_state. This object has been deprecated and may be removed in a future version of the language. DEPRECATED STATE: ID: The preference key to check. The unique application identifier that specifies the application to use when looking up the preference key (e.g. com.apple.Safari). The absolute path to a plist file (e.g. ~/Library/Preferences/com.apple.Safari.plist). The instance of the preference key found in the plist. The first instance of a matching preference key is given the instance value of 1, the second instance of a matching preference key is given the instance value of 2, and so on. Note that the main purpose of this entity is to provide uniqueness for the different plist_items that result from multiple instances of a given preference key in the same plist file. The type of the preference key. The value of the preference key. The plist510_test is used to check the value(s) associated with property list preference 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 plist510_object and the optional plist510_state element specifies the data to check. plist510_test plist510_object plist510_state plist_item 5.11.2:1.0 Replaced by the plist511_test. This test references the plist_object which cannot express the context hierarchy required to differentiate between nodes with identical names. As a result, it is not possible to address a particular node when the order of their parent nodes is indeterminate. The plist511_test was added to address this deficiency. See the plist511_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 plist510_test must reference a plist510_object - the state child element of a plist510_test must reference a plist510_state The plist510_object element is used by a plist510_test to define the preference keys to collect and where to look for them. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. 5.11.2:1.0 Replaced by the plist511_object. This object cannot express the context hierarchy required to differentiate between nodes with identical names. As a result, it is not possible to address a particular node when the order of their parent nodes is indeterminate. The plist511_object was added to address this deficiency. See the plist511_object. This object has been deprecated and may be removed in a future version of the language. DEPRECATED OBJECT: ID: State referenced in filter for '' is of the wrong type. The preference key to check. If the xsi:nil attribute is set to 'true', the plist does not have any keys associated with it (i.e. it is not a CFDictionary) and the default value of the plist will be collected. The unique application identifier that specifies the application to use when looking up the preference key (e.g. com.apple.Safari). - key entity must not be nil when the app_id entity is used because preferences require a key. The absolute path to a plist file (e.g. ~/Library/Preferences/com.apple.Safari.plist). A directory cannot be specified as a filepath. - operation attribute for the filepath entity of a plist510_object should be 'equals' The instance of the preference key found in the plist. The first instance of a matching preference key is given the instance value of 1, the second instance of a matching preference key is given the instance value of 2, and so on. Instance values must be assigned using a depth-first approach. Note that the main purpose of this entity is to provide uniqueness for the different plist_items that result from multiple instances of a given preference key in the same plist file. The plist510_state element defines the different information that can be used to evaluate the specified property list preference key. This includes the preference key, application identifier, filepath, type, as well as the preference key's value. Please refer to the individual elements in the schema for more details about what each represents. 5.11.2:1.0 Replaced by the plist511_state. This state is used in conjunction with the plist510_object which cannot express the context hierarchy required to differentiate between nodes with identical names. As a result, it is not possible to address a particular node when the order of their parent nodes is indeterminate. The plist511_state was added to address this deficiency. See the plist511_state. This object has been deprecated and may be removed in a future version of the language. DEPRECATED STATE: ID: The preference key to check. The unique application identifier that specifies the application to use when looking up the preference key (e.g. com.apple.Safari). The absolute path to a plist file (e.g. ~/Library/Preferences/com.apple.Safari.plist). The instance of the preference key found in the plist. The first instance of a matching preference key is given the instance value of 1, the second instance of a matching preference key is given the instance value of 2, and so on. Instance values must be assigned using a depth-first approach. Note that the main purpose of this entity is to provide uniqueness for the different plist_items that result from multiple instances of a given preference key in the same plist file. The type of the preference key. The value of the preference key. The plist511_test is used to check the value(s) associated with property list preference keys. It can be used to represent any plist file in XML form (whether its native format is ASCII text, binary, or XML), permitting the use of the XPATH query language to explore its contents. 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 plist511_object and the optional plist511_state element specifies the data to check. plist511_test plist511_object plist511_state plist_item - the object child element of a plist511_test must reference a plist511_object - the state child element of a plist511_test must reference a plist511_state The plist511_object element is used by a plist511_test to define the preference keys to collect and where to look for them. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. State referenced in filter for '' is of the wrong type. The unique application identifier that specifies the application to use when looking up the preference key (e.g. com.apple.Safari). The absolute path to a plist file (e.g. /Library/Preferences/com.apple.TimeMachine.plist). A directory cannot be specified as a filepath. - operation attribute for the filepath entity of a plist511_object should be 'equals' Specifies an XPath 1.0 expression to evaluate against the XML representation of the plist file specified by the filename or app_id entity. This XPath 1.0 expression must evaluate to a list of zero or more text values which will be accessible in OVAL via instances of the value_of item entity. Any results from evaluating the XPath 1.0 expression other than a list of text strings (e.g., a nodes set) is considered an error. The intention is that the text values be drawn from instances of a single, uniquely named element or attribute. However, an OVAL interpreter is not required to verify this, so the author should define the XPath expression carefully. Note that "equals" is the only valid operator for the xpath entity. - operation attribute for the xpath entity of a plist_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) The plist511_state element defines the different information that can be used to evaluate the specified property list preference key. This includes the preference key, application identifier, filepath, type, as well as the preference key's value. Please refer to the individual elements in the schema for more details about what each represents. The unique application identifier that specifies the application to use when looking up the preference key (e.g. com.apple.Safari). The absolute path to a plist file (e.g. ~/Library/Preferences/com.apple.Safari.plist). Specifies an XPath expression describing the text node(s) or attribute(s) to look at. The value of the preference key. This test pulls data from the 'pwpolicy -getpolicy' output. The actual values get stored under /var/db/netinfo/local.nidb/ in a Store.# file. Is this test actually needed, or can the text file content test be used instead? pwpolicy_test pwpolicy_object pwpolicy_state pwpolicy_item 5.9 Replaced by the pwpolicy59_test. The username, userpass, and directory_node entities in the pwpolicy_object, pwpolicy_state, and pwpolicy_item were underspecified and as a result their meaning was uncertain. A new test was created to resolve this issue. See the pwpolicy59_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 an pwpolicy_test must reference an pwpolicy_object - the state child element of an pwpolicy_test must reference an pwpolicy_state The pwpolicy_object element is used by a pwpolicy_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. 5.9 Replaced by the pwpolicy59_object. The username, userpass, and directory_node entities in the pwpolicy_object were underspecified and as a result their meaning was uncertain. A new object was created to resolve this issue. See the pwpolicy59_object. This object has been deprecated and may be removed in a future version of the language. DEPRECATED OBJECT: ID: State referenced in filter for '' is of the wrong type. - operation attribute for the username entity of a pwpolicy_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) - operation attribute for the userpass entity of a pwpolicy_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) - operation attribute for the directory_node entity of a pwpolicy_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) 5.9 Replaced by the pwpolicy59_state. The username, userpass, and directory_node entities in the pwpolicy_state were underspecified and as a result their meaning was uncertain. A new state was created to resolve this issue. See the pwpolicy59_state. This state has been deprecated and may be removed in a future version of the language. DEPRECATED STATE: ID: Maximum number of characters allowed in a password. Maximum number of failed logins before the account is locked. Minimum number of characters allowed in a password. Defines if the password is allowed to be the same as the username or not. Defines if the password must contain an alphabetical character or not. Defines if the password must contain an numeric character or not. This test retrieves password policy data from the 'pwpolicy -getpolicy -u target_user [-a username] [-p userpass] [-n directory_node]' output where username, userpass, and directory_node are optional. Please see the 'pwpolicy' man page for additional information. pwpolicy59_test pwpolicy59_object pwpolicy59_state pwpolicy59_item - the object child element of an pwpolicy59_test must reference an pwpolicy59_object - the state child element of an pwpolicy59_test must reference an pwpolicy59_state The pwpolicy59_object element is used by a pwpolicy59_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. State referenced in filter for '' is of the wrong type. The target_user element specifies the user whose password policy information should be collected. If an operation other than equals is specified, the users on the system should be enumerated and the 'pwpolicy' command should be issued for each user that matches the target_user element. If the xsi:nil attribute is set to true, the global policy should be retrieved. The username element specifies the username of the authenticator. If the xsi:nil attribute is set to true, authentication to the directory node will not be performed (i.e. the '-a' and '-p' command line options will not be specified when issuing the 'pwpolicy' command) and the xsi:nil attribute of the userpass element should also be set to true. - userpass entity must be nil when username entity is nil The userpass element specifies the password of the authenticator as specified by the username element. If the xsi:nil attribute is set to true, authentication to the directory node will not be performed (i.e. the '-a' and '-p' command line options will not be specified when issuing the 'pwpolicy' command) and the xsi:nil attribute of the username element should also be set to true. - operation attribute for the userpass entity of a pwpolicy59_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) - username entity must be nil when userpass entity is nil The directory_node element specifies the directory node that you would like to retrieve the password policy information from. If the xsi:nil attribute is set to true, the default directory node is used (i.e. the '-n' command line option will not be specified when issuing the 'pwpolicy' command). - operation attribute for the directory_node entity of a pwpolicy59_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) The pwpolicy59_state element defines the different information that can be used to evaluate the password policy for the target user in the specified directory node. Please refer to the individual elements in the schema for more details about what each represents. The target_user element specifies the user whose password policy information should be collected. The username element specifies the username of the authenticator. The userpass element specifies the password of the authenticator as specified by the username element. The directory_node element specifies the directory node that you would like to retrieve the password policy information from. Maximum number of characters allowed in a password. Maximum number of failed logins before the account is locked. Minimum number of characters allowed in a password. Defines if the password is allowed to be the same as the username or not. Defines if the password must contain an alphabetical character or not. Defines if the password must contain an numeric character or not. Maximum number of minutes until the password must be changed. Minimum number of minutes between password changes. Defines if the password must contain upper and lower case characters or not. Defines if the password must contain a symbol character or not. Number of minutes after login has been disabled due to too many failed login attempts to wait before reenabling login. 0 = user can reuse the current pass-word, 1 = user cannot reuse the current password, 2-15 = user cannot reuse the last n passwords. If true, the user can change the password. If true, user is required to change password on the date in expirationDateGMT If true, user's account is disabled on the date in hardExpireDateGMT Date for the password to expire, format is: mm/dd/yyyy. NOTE: The pwpolicy command returns the year as a two digit value, but OVAL uses four digit years; the pwpolicy value is converted to an OVAL compatible value. Date for the user's account to be disabled, format is: mm/dd/yyyy. NOTE: The pwpolicy command returns the year as a two digit value, but OVAL uses four digit years; the pwpolicy value is converted to an OVAL compatible value. User's account is disabled after this interval User's account is disabled if it is not accessed by this interval If true, the user will be prompted for a new password at the next authentication. The rlimit_test is used to check system resource limits for launchd. It is a singleton 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 state element specifies the system setup elements to check. rlimit_test rlimit_object rlimit_state rlimit_item - the object child element of a rlimit_test must reference an rlimit_object - the state child element of a rlimit_test must reference an rlimit_state The rlimit_object is a singleton used to access resource limit information. The rlimit_state element makes it possible to make assertions about the resource limits for launchd. A resource limit is specified as a soft (current) limit and a hard (max) limit. When a soft limit is exceeded a process may receive a signal (for example, if the cpu time or file size is exceeded), but it will be allowed to con-tinue continue tinue execution until it reaches the hard limit (or modifies its resource limit). For any 'unlimited' resource, the entity will have the status of 'does not exist'. The maximum amount of cpu time (in seconds) to be used by each process. cpu hard limit. The largest size (in bytes) file that may be created. filesize hard limit. The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call. data hard limit. The maximum size (in bytes) of the stack segment for a process; this defines how far a program's stack segment may be extended. Stack extension is performed automatically by the system. stack hard limit. The largest size (in bytes) core file that may be created. core hard limit. The maximum size (in bytes) to which a process's resident set size may grow. This imposes a limit on the amount of physical memory to be given to a process; if memory is tight, the system will prefer to take memory from processes that are exceeding their declared resident set size. rss hard limit. The maximum size (in bytes) which a process may lock into memory using the mlock(2) function. memlock hard limit. The maximum number of simultaneous processes for this user id. maxproc hard limit. The maximum number of open files for this process. maxfiles hard limit. The softwareupdate_test is used to check the status of automatic software updates on MacOSX. It is a singleton 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 state element specifies the softwareupdate elements to check. softwareupdate_test softwareupdate_object softwareupdate_state softwareupdate_item - the object child element of a softwareupdate_test must reference an softwareupdate_object - the state child element of a softwareupdate_test must reference an softwareupdate_state The softwareupdate_object is a singleton used to access automatic software update information. The softwareupdate_state element makes it possible to make assertions about the state of automatic software updates. Specifies whether automatic checking is enabled (true). Specifies the title string for an available (not installed) software update. The systemprofiler_test is used to check the properties of the plist-style XML output from the "system_profiler -xml <data type>" command, for reading information about system inventory data on MacOSX. 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 systemprofiler_object and the optional state element specifies the data to check. systemprofiler_test systemprofiler_object systemprofiler_state systemprofiler_item - the object child element of a systemprofiler_test must reference an systemprofiler_object - the state child element of a systemprofiler_test must reference an systemprofiler_state The systemprofiler_object element is used by an systemprofiler_test to define the object to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema. An systemprofiler_object consists of a data_type entity that contains the name of the datatype that was probed by the system_profiler utility. The resulting plist data can be queried using the xpath entity. State referenced in filter for '' is of the wrong type. The data_type entity provides the datatype value that is desired. Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. Any valid Xpath 1.0 statement is usable with one exception, at most one field may be identified in the Xpath. This is because the value_of element in the data section is only designed to work against a single field. The only valid operator for xpath is equals since there is an infinite number of possible xpaths and determinining all those that do not equal a given xpath would be impossible. - operation attribute for the xpath entity of an systemprofiler_object should be 'equals', note that this overrules the general operation attribute validation (i.e. follow this one) The systemprofiler_state element defines a value used to evaluate the result of a specific systemprofiler_object item. The data_type entity provides the datatype value that is desired. Specifies an Xpath expression describing the text node(s) or attribute(s) to look at. The value_of element checks the value(s) of the text node(s) or attribute(s) found. The systemsetup_test is used to check systemsetup properties. It is a singleton 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 state element specifies the system setup elements to check. systemsetup_test systemsetup_object systemsetup_state systemsetup_item - the object child element of a systemsetup_test must reference an systemsetup_object - the state child element of a systemsetup_test must reference an systemsetup_state The systemsetup_object is a singleton used to access system setup information. The systemsetup_state element makes it possible to make assertions about system setup settings. Specifies the name of the time zone. Specifies weather the machine is using network time. Specifies the network time server. Specifies the computer sleep inactivity timer, or 0 for never. Specifies the display sleep inactivity timer, or 0 for never. Specifies the hard disk sleep inactivity timer, or 0 for never. Specifies whether the computer will wake up if the modem is accessed. Specifies whether the computer will wake up if the network is accessed. Specifies whether the computer will restart after freezing. Specifies whether the power button can be used to cause the computer to sleep. Specifies whether remote logins are allowed. Specifies whether remote Apple events are enabled. Specifies the computer's name. Specifies the startup disk. Specifies the number of seconds the computer waits to start up after a power failure. Specifies whether the keyboard is locked when the closure lock is engaged. Specifies the kernel boot architecture setting. The EntityObjectDataTypeType complex type defines the different values that are valid for the data_type entity of a system_profiler object. These values describe the system_profiler XML data to be retrieved. 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 index 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 data_type entity and are not valid values for the datatype attribute. The empty string value is permitted here to allow for empty elements associated with variable references. The EntityStateDataTypeType complex type defines the different values that are valid for the data_type entity of a system_profiler state. These values describe the system_profiler XML data to be retrieved. 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 index 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 data_type entity and are not valid values for the datatype attribute. The empty string value is permitted here to allow for empty elements associated with variable references. The EntityStatePermissionCompareType complex type restricts a string value to more, less, or same which specifies if an actual permission is different than the expected permission (more or less restrictive) or if the permission is the same. The empty string is also allowed to support empty elements 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 actual permission is more restrictive than the expected permission. The actual permission is less restrictive than the expected permission. The actual permission is the same as the expected permission. The empty string value is permitted here to allow for empty elements associated with variable references. The EntityStatePlistTypeType complex type restricts a string value to the seven values CFString, CFNumber, CFBoolean, CFDate, CFData, CFArray, and CFDictionary that specify the datatype of the value associated with a property list preference key. The empty string is also allowed to support empty elements 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. 5.11.2:1.0 Used only by the deprecated plist_state and plist510_state. This enumeration has been deprecated and may be removed in a future version of the language. The CFString type is used to describe a preference key that has a string value. The OVAL string datatype should be used to represent CFString values. The CFNumber type is used to describe a preference key that has a integer or float value. The OVAL int and float datatypes should be used, as appropriate, to represent CFNumber values. The CFBoolean type is used to describe a preference key that has a boolean value. The OVAL boolean datatype should be used to represent CFBoolean values. The CFDate type is used to describe a preference key that has a date value. The OVAL string datatype should be used to represent CFDate values. The CFData type is used to describe a preference that has a base64-encoded binary value. The OVAL string datatype should be used to represent CFData values. The CFArray type is used to describe a preference key that has a collection of values. This is represented as multiple value entities. The CFDictionary type is used to describe a preference key that has a collection of key-value pairs. Note that the collection of CFDictionary values is not supported. If an attempt is made to collect a CFDictionary value, an error should be reported. The empty string value is permitted here to allow for empty elements associated with variable references.