Examples { ... "distance": 8.321, ... } Hashes Type Name: hashes The Hashes type represents 1 or more cryptographic hashes, as a special set of key/value pairs. Accordingly, the name of each hashing algorithm MUST be specified as a key in the dictionary and MUST identify the name of the hashing algorithm used to generate the corresponding value. This name either be one of the values defined in the hash-algorithm-ov OR a custom value prepended SHOULD with (e.g., “x_” “x_custom_hash”). Keys MUST be unique in each hashes property, MUST be in ASCII, and are limited to the characters a-z (lowercase ASCII), A-Z (uppercase ASCII), numerals 0-9, hyphen (-), and underscore (_). Keys SHOULD be no longer than 30 ASCII characters in length, MUST have a minimum length of 3 ASCII characters, MUST be no longer than 256 ASCII characters in length. Examples SHA-256 and Custom Hash { "SHA-256": "6db12788c37247f2316052e142f42f4b259d6561751e5f401a1ae2a6df9c674b", "x_foo_hash": "aaaabbbbccccddddeeeeffff0123457890" } Identifier Type Name: identifier An identifier universally and uniquely identifies a SDO, SRO, Bundle, or Marking Definition. Identifiers MUST follow the form where is the exact value (all type names are object-type--UUIDv4, object-type lowercase strings, by definition) from the type property of the object being identified or referenced and where the is an RFC 4122-compliant Version 4 UUID. The UUID MUST be generated according to UUIDv4 the algorithm(s) defined in RFC 4122, section 4.4 (Version 4 UUID) []. The JSON MTI serialization uses the JSON string type [] when representing identifier. Examples { ... "type": "indicator",
Examples { ... "distance": 8.321, ... } Hashes Type Name: hashes The Hashes type represents 1 or more cryptographic hashes, as a special set of key/value pairs. Accordingly, the name of each hashing algorithm MUST be specified as a key in the dictionary and MUST identify the name of the hashing algorithm used to generate the corresponding value. This name SHOULD either be one of the values defined in the hash-algorithm-ov OR a custom value prepended with “x_” (e.g., “x_custom_hash”). Keys MUST be unique in each hashes property, MUST be in ASCII, and are limited to the characters a-z (lowercase ASCII), A-Z (uppercase ASCII), numerals 0-9, hyphen (-), and underscore (_). Keys SHOULD be no longer than 30 ASCII characters in length, MUST have a minimum length of 3 ASCII characters, MUST be no longer than 256 ASCII characters in length. Examples SHA-256 and Custom Hash { "SHA-256": "6db12788c37247f2316052e142f42f4b259d6561751e5f401a1ae2a6df9c674b", "x_foo_hash": "aaaabbbbccccddddeeeeffff0123457890" } Identifier Type Name: identifier An identifier universally and uniquely identifies a SDO, SRO, Bundle, or Marking Definition. Identifiers MUST follow the form object-type--UUIDv4, where object-type is the exact value (all type names are lowercase strings, by definition) from the type property of the object being identified or referenced and where the UUIDv4 is an RFC 4122-compliant Version 4 UUID. The UUID MUST be generated according to the algorithm(s) defined in RFC 4122, section 4.4 (Version 4 UUID) []. The JSON MTI serialization uses the JSON string type [] when representing identifier. Examples { ... "type": "indicator",
stix-v2.0-csprd02-part1-stix-core.docx