schemas.v1.1.1.cybox.objects.Account_Object.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of stix Show documentation
Show all versions of stix Show documentation
The Java bindings for STIX v.1.2.0.2
This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.
Account_Object
2.1
01/22/2014
The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML.
Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.
The Account object is intended to characterize generic accounts.
The AccountObjectType type is intended to characterize generic accounts.
The Description field is used for providing a description of the account, if applicable.
The Domain field is used for specifying the domain that the account belongs to.
The Authentication field specifies authentication information associated with this account.
The Creation_Date field specifies the date and time that the account was created.
The Modified_Date field specifies the date and time that the account was last modified.
The Last_Accessed_Time field specifies the date and time that the account was last accessed.
The disabled field specifies whether or not the account is disabled.
The locked_out field specifies whether or not the account is locked out.
The AuthenticationType type specifies authentication information for an account.
The Authentication_Type field specifies the type of authentication required by this Account.
This field is implemented through the xsi:type controlled vocabulary extension mechanism. The default vocabulary type is AuthenticationTypeVocab-1.0 in the http://cybox.mitre.org/objects#AccountObject-2 namespace.
Users may also define their own vocabulary using the type extension mechanism, specify a vocabulary name and reference using the attributes, or simply use this as a string field.
The Authentication_Data field specifies the data used for the authentication type specified by the Authentication_Type field. For example, if Authentication_Type is set to "Password", this would be the actual password value.
The Authentication_Token_Protection_Mechanism field specifies the method (typically algorithm) of protecting authentication tokens for this account.
This field is implemented through the xsi:type controlled vocabulary extension mechanism. The default vocabulary type is AuthenticationTokenProtectionMechanismTypeVocab-1.0 in the http://cybox.mitre.org/objects#AccountObject-2 namespace.
Users may also define their own vocabulary using the type extension mechanism, specify a vocabulary name and reference using the attributes, or simply use this as a string field.
The Structured_Authentication_Mechanism field provides authors a field for describing authentication mechanism information in a structured language defined outside of CybOX.
Characterizes the description of an authentication mechanism, such as biometrics-based authentication.
In addition to capturing basic information, this type is intended to be extended to enable the structured description of an authentication mechanism using the XML Schema extension feature. No extension is provided by CybOX to support this, however those wishing to represent structured authentication mechanism information may develop such an extension.
The Description field provides an unstructured description of an individual StructuredAuthenticationMechanismType instance.
The AuthenticationTypeVocab is the default CybOX vocabulary for authentication types, used in the AuthenticationType/Authentication_Type found in the Account Object schema.
The AuthenticationTypeEnum is a (non-exhaustive) enumeration of authentication types for accounts. This is leveraged by the Account Object.
The No Authentication value specifies that there is no authentication mechanism in place.
The Password value specifies password based authentication.
The Cryptographic Key value specifies cryptographic key based authentication.
The Biometrics value specifies biometrics based authentication. Examples include fingerprint or retina readers.
The Hardware Token value specifies authentication requiring physical or hardware tokens. Examples include smart cards, bluetooth tokens, and usb tokens.
The Software Token value specifies an authentication device stored in software form.
The Multifactor authentication value specifies multifactor authentication.
The AuthenticationTokenProtectionMechanismTypeVocab is the default CybOX vocabulary for authentication token protection mechanisms, used in the AuthenticationType/Authentication_Token_Protection_Mechanism found in the Account Object schema.
The AuthenticationTokenProtectionMechanismTypeEnum is a (non-exhaustive) enumeration of methods for the protection of authentication tokens.
The authentication tokens are stored in plaintext.
The authentication tokens have been salted and hashed with the GOST hash algorithm.
The authentication tokens have been hashed with the GOST hash algorithm, without salting.
The authentication tokens have been salted and hashed with the HAVAL hash algorithm.
The authentication tokens have been hashed with the HAVAL hash algorithm, without salting.
The authentication tokens have been salted and hashed with the MD2 hash algorithm.
The authentication tokens have been hashed with the MD2 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the MD4 hash algorithm.
The authentication tokens have been hashed with the MD4 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the MD5 hash algorithm.
The authentication tokens have been hashed with the MD5 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the PANAMA hash algorithm.
The authentication tokens have been hashed with the PANAMA hash algorithm, without salting.
The authentication tokens have been salted and hashed with the RadioGatun hash algorithm.
The authentication tokens have been hashed with the RadioGatun hash algorithm, without salting.
The authentication tokens have been salted and hashed with the RIPEMD hash algorithm.
The authentication tokens have been hashed with the RIPEMD hash algorithm, without salting.
The authentication tokens have been salted and hashed with the RIPEMD-128/256 hash algorithm.
The authentication tokens have been hashed with the RIPEMD-128/256 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the RIPEMD-160 hash algorithm.
The authentication tokens have been hashed with the RIPEMD-160 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the RIPEMD-320 hash algorithm.
The authentication tokens have been hashed with the RIPEMD-320 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-0 hash algorithm.
The authentication tokens have been hashed with the SHA-0 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-1 hash algorithm.
The authentication tokens have been hashed with the SHA-1 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-256/224 hash algorithm.
The authentication tokens have been hashed with the SHA-256/224 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-512/384 hash algorithm.
The authentication tokens have been hashed with the SHA-512/384 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-3 hash algorithm.
The authentication tokens have been hashed with the SHA-3 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-3-224 hash algorithm.
The authentication tokens have been hashed with the SHA-3-224 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-3-256 hash algorithm.
The authentication tokens have been hashed with the SHA-3-256 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-3-384 hash algorithm.
The authentication tokens have been hashed with the SHA-3-384 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the SHA-3-512 hash algorithm.
The authentication tokens have been hashed with the SHA-3-512 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the Tiger(2)-192/160/128 hash algorithm.
The authentication tokens have been hashed with the Tiger(2)-192/160/128 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the WHIRLPOOL hash algorithm.
The authentication tokens have been hashed with the WHIRLPOOL hash algorithm, without salting.
The authentication tokens have been salted and hashed with the Skein-256 hash algorithm.
The authentication tokens have been hashed with the Skein-256 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the Skein-512 hash algorithm.
The authentication tokens have been hashed with the Skein-512 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the Skein-1024 hash algorithm.
The authentication tokens have been hashed with the Skein-1024 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the Snefru-128 hash algorithm.
The authentication tokens have been hashed with the Snefru-128 hash algorithm, without salting.
The authentication tokens have been salted and hashed with the Snefru-256 hash algorithm.
The authentication tokens have been hashed with the Snefru-256 hash algorithm, without salting.
The authentication tokens have been hashed using an iterative hashing algorithm.
The authentication tokens have been encrypted with the AES algorithm.
The authentication tokens have been encrypted with the Blowfish algorithm.
The authentication tokens have been encrypted with the DES algorithm.
The authentication tokens have been encrypted with the IDEA algorithm.
The authentication tokens have been encrypted with the RC4 algorithm.
The authentication tokens have been encrypted with the Tiny Encryption Algorithm (TEA).