***Targeting data**: Targeting information to include recipient email, infected machines, department, and or locations.
***Antivirus detection**: List of anti-virus vendors detecting the malware or information on detection performance (e.g. 13/43 or 67%). Attachment with list of detection or link to VirusTotal could be placed here as well.
***Payload delivery**: Information about the way the malware payload is initially delivered, for example information about the email or web-site, vulnerability used, originating IP etc. Malware sample itself should be attached here.
***Artifacts dropped**: Any artifact (files, registry keys etc.) dropped by the malware or other modifications to the system
***Payload installation**: Location where the payload was placed in the system and the way it was installed. For example, a filename|md5 type attribute can be added here like this: c:\windows\system32\malicious.exe|41d8cd98f00b204e9800998ecf8427e.
***Persistence mechanism**: Mechanisms used by the malware to start at boot. This could be a registry key, legitimate driver modification, LNK file in startup
***Payload type**: Information about the final payload(s). Can contain a function of the payload, e.g. keylogger, RAT, or a name if identified, such as Poison Ivy.
***Attribution**: Identification of the group, organisation, or country behind the attack
***External analysis**: Any other result from additional analysis of the malware like tools output Examples: pdf-parser output, automated sandbox analysis, reverse engineering report.
***Financial fraud**: Financial Fraud indicators, for example: IBAN Numbers, BIC codes, Credit card numbers, etc.
***md5**: You are encouraged to use filename|md5 instead. A checksum in md5 format, only use this if you don't know the correct filename
***sha1**: You are encouraged to use filename|sha1 instead. A checksum in sha1 format, only use this if you don't know the correct filename
***sha256**: You are encouraged to use filename|sha256 instead. A checksum in sha256 format, only use this if you don't know the correct filename
***filename**: Filename
***pdb**: Microsoft Program database (PDB) path information
***filename|md5**: A filename and an md5 hash separated by a | (no spaces)
***filename|sha1**: A filename and an sha1 hash separated by a | (no spaces)
***filename|sha256**: A filename and an sha256 hash separated by a | (no spaces)
***ip-src**: A source IP address of the attacker
***ip-dst**: A destination IP address of the attacker or C&C server. Also set the IDS flag on when this IP is hardcoded in malware
***hostname**: A full host/dnsname of an attacker. Also set the IDS flag on when this hostname is hardcoded in malware
***domain**: A domain name used in the malware. Use this instead of hostname when the upper domain is important or can be used to create links between events.
***domain|ip**: A domain name and its IP address (as found in DNS lookup) separated by a | (no spaces)
***ja3-fingerprint-md5**: JA3 is a method for creating SSL/TLS client fingerprints that should be easy to produce on any platform and can be easily shared for threat intelligence.
***hassh-md5**: hassh is a network fingerprinting standard which can be used to identify specific Client SSH implementations. The fingerprints can be easily stored, searched and shared in the form of an MD5 fingerprint.
***hasshserver-md5**: hasshServer is a network fingerprinting standard which can be used to identify specific Server SSH implementations. The fingerprints can be easily stored, searched and shared in the form of an MD5 fingerprint.
***regkey**: Registry key or value
***regkey|value**: Registry value + data separated by |
***AS**: Autonomous system
***snort**: An IDS rule in Snort rule-format. This rule will be automatically rewritten in the NIDS exports.
***bro**: An NIDS rule in the Bro rule-format.
***zeek**: An NIDS rule in the Zeek rule-format.
***community-id**: a community ID flow hashing algorithm to map multiple traffic monitors into common flow id
***sigma**: Sigma - Generic Signature Format for SIEM Systems
***gene**: GENE - Go Evtx sigNature Engine
***mime-type**: A media type (also MIME type and content type) is a two-part identifier for file formats and format contents transmitted on the Internet
***identity-card-number**: Identity card number
***cookie**: HTTP cookie as often stored on the user web client. This can include authentication cookie or session cookie.
***vulnerability**: A reference to the vulnerability used in the exploit
***attachment**: Please upload files using the <em>Upload Attachment</em> button.
***malware-sample**: Please upload files using the <em>Upload Attachment</em> button.
***link**: Link to an external information
***comment**: Comment or description in a human language. This will not be correlated with other attributes
***text**: Name, ID or a reference
***hex**: A value in hexadecimal format
***other**: Other attribute
***named pipe**: Named pipe, use the format \.\pipe\<PipeName>
***mutex**: Mutex, use the format \BaseNamedObjects\<Mutex>
***authentihash**: You are encouraged to use filename|authentihash instead. Authenticode executable signature hash, only use this if you don't know the correct filename
***ssdeep**: You are encouraged to use filename|ssdeep instead. A checksum in the SSDeep format, only use this if you don't know the correct filename
***imphash**: You are encouraged to use filename|imphash instead. A hash created based on the imports in the sample, only use this if you don't know the correct filename
***pehash**: PEhash - a hash calculated based of certain pieces of a PE executable file
***impfuzzy**: You are encouraged to use filename|impfuzzy instead. A fuzzy hash created based on the imports in the sample, only use this if you don't know the correct filename
***sha224**: You are encouraged to use filename|sha224 instead. A checksum in sha224 format, only use this if you don't know the correct filename
***sha384**: You are encouraged to use filename|sha384 instead. A checksum in sha384 format, only use this if you don't know the correct filename
***sha512**: You are encouraged to use filename|sha512 instead. A checksum in sha512 format, only use this if you don't know the correct filename
***sha512/224**: You are encouraged to use filename|sha512/224 instead. A checksum in sha512/224 format, only use this if you don't know the correct filename
***sha512/256**: You are encouraged to use filename|sha512/256 instead. A checksum in sha512/256 format, only use this if you don't know the correct filename
***tlsh**: You are encouraged to use filename|tlsh instead. A checksum in the Trend Micro Locality Sensitive Hash format, only use this if you don't know the correct filename
***cdhash**: An Apple Code Directory Hash, identifying a code-signed Mach-O executable file
***filename|authentihash**: A checksum in md5 format
***filename|ssdeep**: A checksum in ssdeep format
***filename|imphash**: Import hash - a hash created based on the imports in the sample.
***filename|impfuzzy**: Import fuzzy hash - a fuzzy hash created based on the imports in the sample.
***filename|pehash**: A filename and a PEhash separated by a |
***filename|sha224**: A filename and a sha-224 hash separated by a |
***filename|sha384**: A filename and a sha-384 hash separated by a |
***filename|sha512**: A filename and a sha-512 hash separated by a |
***filename|sha512/224**: A filename and a sha-512/224 hash separated by a |
***filename|sha512/256**: A filename and a sha-512/256 hash separated by a |
***filename|tlsh**: A filename and a Trend Micro Locality Sensitive Hash separated by a |
***windows-scheduled-task**: A scheduled task in windows
***windows-service-name**: A windows service name. This is the name used internally by windows. Not to be confused with the windows-service-displayname.
***windows-service-displayname**: A windows service's displayname, not to be confused with the windows-service-name. This is the name that applications will generally display as the service's name in applications.
***dns-soa-email**: RFC1035 mandates that DNS zones should have a SOA (Statement Of Authority) record that contains an email address where a PoC for the domain could be contacted. This can sometimes be used for attribution/linkage between different domains even if protected by whois privacy
***size-in-bytes**: Size expressed in bytes
***counter**: An integer counter, generally to be used in objects
***datetime**: Datetime in the ISO 8601 format
***cpe**: Common platform enumeration
***port**: Port number
***ip-dst|port**: IP destination and port number seperated by a |
***ip-src|port**: IP source and port number seperated by a |
***hostname|port**: Hostname and port number seperated by a |
***mac-address**: Mac address
***mac-eui-64**: Mac EUI-64 address
***email-dst-display-name**: Email destination display name
***email-src-display-name**: Email source display name
***email-header**: Email header
***email-reply-to**: Email reply to header
***email-x-mailer**: Email x-mailer header
***email-mime-boundary**: The email mime boundary separating parts in a multipart email
***email-thread-index**: The email thread index header
***email-message-id**: The email message ID
***github-username**: A github user name
***github-repository**: A github repository
***github-organisation**: A github organisation
***jabber-id**: Jabber ID
***twitter-id**: Twitter ID
***first-name**: First name of a natural person
***middle-name**: Middle name of a natural person
***last-name**: Last name of a natural person
***date-of-birth**: Date of birth of a natural person (in YYYY-MM-DD format)
***place-of-birth**: Place of birth of a natural person
***gender**: The gender of a natural person (Male, Female, Other, Prefer not to say)
***passport-number**: The passport number of a natural person
***passport-country**: The country in which the passport was issued
***passport-expiration**: The expiration date of a passport
***redress-number**: The Redress Control Number is the record identifier for people who apply for redress through the DHS Travel Redress Inquiry Program (DHS TRIP). DHS TRIP is for travelers who have been repeatedly identified for additional screening and who want to file an inquiry to have erroneous information corrected in DHS systems
***nationality**: The nationality of a natural person
***visa-number**: Visa number
***issue-date-of-the-visa**: The date on which the visa was issued
***primary-residence**: The primary residence of a natural person
***country-of-residence**: The country of residence of a natural person
***special-service-request**: A Special Service Request is a function to an airline to provide a particular facility for A Passenger or passengers.
***frequent-flyer-number**: The frequent flyer number of a passenger
***travel-details**: Travel details
***payment-details**: Payment details
***place-port-of-original-embarkation**: The orignal port of embarkation
***place-port-of-clearance**: The port of clearance
***place-port-of-onward-foreign-destination**: A Port where the passenger is transiting to
***passenger-name-record-locator-number**: The Passenger Name Record Locator is a key under which the reservation for a trip is stored in the system. The PNR contains, among other data, the name, flight segments and address of the passenger. It is defined by a combination of five or six letters and numbers.
***mobile-application-id**: The application id of a mobile application
***cortex**: Cortex analysis result
***boolean**: Boolean value - to be used in objects
***anonymised**: Anonymised value - described with the anonymisation object via a relationship.
