Documentation for Open Vulnerability and Assessment Language (OVAL®)
Definition Type: Element
Name: user
Namespace: http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#windows
Type: oval-sc:EntityItemStringType
Containing Schema: windows-system-characteristics-schema.xsd
MinOccurs 0
MaxOccurs unbounded
Abstract
Documentation:
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 as that is how the windows apis return them. If the specified group has more than one user as a member, then multiple user elements should exist. If the specified group does not contain a single user, then a single user element should exist with a status of 'does not exist'. If there is an error determining the userss that are members of the group, then a single user element should be included with a status of 'error'.
Collapse XSD Schema Diagram:
Drilldown into status in schema oval-system-characteristics-schema_xsd Drilldown into mask in schema oval-system-characteristics-schema_xsd Drilldown into datatype in schema oval-system-characteristics-schema_xsd Drilldown into EntityItemStringType in schema oval-system-characteristics-schema_xsdXSD Diagram of user in schema windows-system-characteristics-schema_xsd (Open Vulnerability and Assessment Language (OVAL®))
Collapse XSD Schema Code: 
<xsd:element name="user" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
        <xsd:documentation>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 as that is how the windows apis return them.</xsd:documentation>
        <xsd:documentation>If the specified group has more than one user as a member, then multiple user elements should exist. If the specified group does not contain a single user, then a single user element should exist with a status of 'does not exist'. If there is an error determining the userss that are members of the group, then a single user element should be included with a status of 'error'.</xsd:documentation>
        <xsd:appinfo>
            <sch:pattern id="groupitemuser" xmlns:sch="http://purl.oclc.org/dsdl/schematron">
                <sch:rule context="win-sc:group_item/win-sc:user">
                    <sch:assert test="not(@datatype) or @datatype='string'">item <sch:value-of select="../@id" /> - datatype attribute for the user entity of a group_item should be 'string'</sch:assert>
                </sch:rule>
            </sch:pattern>
        </xsd:appinfo>
    </xsd:annotation>
</xsd:element>
Collapse Child Attributes:
Name Type Default Value Use
datatype oval-sc:datatype string Optional
mask oval-sc:mask false Optional
status oval-sc:status exists Optional
Collapse Derivation Tree:
Documentation for Open Vulnerability and Assessment Language (OVAL®)

Generated using Liquid Studio - Developer Bundle 21.0.0.0