MISP
/
misp-objects
mirror of https://github.com/MISP/misp-objects
2
0
Fork 0
Code Issues Releases Wiki Activity
misp-objects/objects/intelmq_event/definition.json

420 lines
18 KiB
JSON
Raw Blame History

{
"attributes": {
"classification.identifier": {
"description": "The lowercase identifier defines the actual software or service (e.g. 'heartbleed' or 'ntp_version') or standardized malware name (e.g. 'zeus'). Note that you MAY overwrite this field during processing for your individual setup. This field is not standardized across IntelMQ setups/users.",
"misp-attribute": "text",
"ui-priority": 1
},
"classification.taxonomy": {
"description": "We recognize the need for the CSIRT teams to apply a static (incident) taxonomy to abuse data. With this goal in mind the type IOC will serve as a basis for this activity. Each value of the dynamic type mapping translates to a an element in the static taxonomy. The European CSIRT teams for example have decided to apply the eCSIRT.net incident classification. The value of the taxonomy key is thus a derivative of the dynamic type above. For more information about check [ENISA taxonomies](http://www.enisa.europa.eu/activities/cert/support/incident-management/browsable/incident-handling-process/incident-taxonomy/existing-taxonomies).",
"misp-attribute": "text",
"ui-priority": 1
},
"classification.type": {
"description": "The abuse type IOC is one of the most crucial pieces of information for any given abuse event. The main idea of dynamic typing is to keep our ontology flexible, since we need to evolve with the evolving threatscape of abuse data. In contrast with the static taxonomy below, the dynamic typing is used to perform business decisions in the abuse handling pipeline. Furthermore, the value data set should be kept as minimal as possible to avoid “type explosion”, which in turn dilutes the business value of the dynamic typing. In general, we normally have two types of abuse type IOC: ones referring to a compromised resource or ones referring to pieces of the criminal infrastructure, such as a command and control servers for example.",
"misp-attribute": "text",
"ui-priority": 1
},
"comment": {
"description": "Free text commentary about the abuse event inserted by an analyst.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.abuse_contact": {
"description": "Abuse contact for destination address. A comma separated list.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.account": {
"description": "An account name or email address, which has been identified to relate to the destination of an abuse event.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.allocated": {
"description": "Allocation date corresponding to BGP prefix.",
"misp-attribute": "datetime",
"ui-priority": 1
},
"destination.as_name": {
"description": "The autonomous system name to which the connection headed.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.asn": {
"description": "The autonomous system number to which the connection headed.",
"misp-attribute": "AS",
"ui-priority": 1
},
"destination.domain_suffix": {
"description": "The suffix of the domain from the public suffix list.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.fqdn": {
"description": "A DNS name related to the host from which the connection originated. DNS allows even binary data in DNS, so we have to allow everything. A final point is stripped, string is converted to lower case characters.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.geolocation.cc": {
"description": "Country-Code according to ISO3166-1 alpha-2 for the destination IP.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.geolocation.city": {
"description": "Some geolocation services refer to city-level geolocation.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.geolocation.country": {
"description": "The country name derived from the ISO3166 country code (assigned to cc field).",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.geolocation.latitude": {
"description": "Latitude coordinates derived from a geolocation service, such as MaxMind geoip db.",
"misp-attribute": "float",
"ui-priority": 1
},
"destination.geolocation.longitude": {
"description": "Longitude coordinates derived from a geolocation service, such as MaxMind geoip db.",
"misp-attribute": "float",
"ui-priority": 1
},
"destination.geolocation.region": {
"description": "Some geolocation services refer to region-level geolocation.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.geolocation.state": {
"description": "Some geolocation services refer to state-level geolocation.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.ip": {
"description": "The IP which is the target of the observed connections.",
"misp-attribute": "ip-dst",
"ui-priority": 1
},
"destination.local_hostname": {
"description": "Some sources report a internal hostname within a NAT related to the name configured for a compromized system",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.local_ip": {
"description": "Some sources report a internal (NATed) IP address related a compromized system. N.B. RFC1918 IPs are OK here.",
"misp-attribute": "ip-dst",
"ui-priority": 1
},
"destination.network": {
"description": "CIDR for an autonomous system. Also known as BGP prefix. If multiple values are possible, select the most specific.",
"misp-attribute": "ip-dst",
"ui-priority": 1
},
"destination.port": {
"description": "The port to which the connection headed.",
"misp-attribute": "counter",
"ui-priority": 1
},
"destination.registry": {
"description": "The IP registry a given ip address is allocated by.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.reverse_dns": {
"description": "Reverse DNS name acquired through a reverse DNS query on an IP address. N.B. Record types other than PTR records may also appear in the reverse DNS tree. Furthermore, unfortunately, there is no rule prohibiting people from writing anything in a PTR record. Even JavaScript will work. A final point is stripped, string is converted to lower case characters.",
"misp-attribute": "text",
"ui-priority": 1
},
"destination.tor_node": {
"description": "If the destination IP was a known tor node.",
"misp-attribute": "boolean",
"ui-priority": 1
},
"destination.url": {
"description": "A URL denotes on IOC, which refers to a malicious resource, whose interpretation is defined by the abuse type. A URL with the abuse type phishing refers to a phishing resource.",
"misp-attribute": "url",
"ui-priority": 1
},
"destination.urlpath": {
"description": "The path portion of an HTTP or related network request.",
"misp-attribute": "text",
"ui-priority": 1
},
"event_description.target": {
"description": "Some sources denominate the target (organization) of a an attack.",
"misp-attribute": "text",
"ui-priority": 1
},
"event_description.text": {
"description": "A free-form textual description of an abuse event.",
"misp-attribute": "text",
"ui-priority": 1
},
"event_description.url": {
"description": "A description URL is a link to a further description of the the abuse event in question.",
"misp-attribute": "url",
"ui-priority": 1
},
"event_hash": {
"description": "Computed event hash with specific keys and values that identify a unique event. At present, the hash should default to using the SHA1 function. Please note that for an event hash to be able to match more than one event (deduplication) the receiver of an event should calculate it based on a minimal set of keys and values present in the event. Using for example the observation time in the calculation will most likely render the checksum useless for deduplication purposes.",
"misp-attribute": "text",
"ui-priority": 1
},
"extra": {
"description": "All anecdotal information, which cannot be parsed into the data harmonization elements. E.g. os.name, os.version, etc. **Note**: this is only intended for mapping any fields which can not map naturally into the data harmonization. It is not intended for extending the data harmonization with your own fields.",
"misp-attribute": "text",
"ui-priority": 1
},
"feed.accuracy": {
"description": "A float between 0 and 100 that represents how accurate the data in the feed is",
"misp-attribute": "float",
"ui-priority": 1
},
"feed.code": {
"description": "Code name for the feed, e.g. DFGS, HSDAG etc.",
"misp-attribute": "text",
"ui-priority": 1
},
"feed.documentation": {
"description": "A URL or hint where to find the documentation of this feed.",
"misp-attribute": "text",
"ui-priority": 1
},
"feed.name": {
"description": "Name for the feed, usually found in collector bot configuration.",
"misp-attribute": "text",
"ui-priority": 1
},
"feed.provider": {
"description": "Name for the provider of the feed, usually found in collector bot configuration.",
"misp-attribute": "text",
"ui-priority": 1
},
"feed.url": {
"description": "The URL of a given abuse feed, where applicable",
"misp-attribute": "url",
"ui-priority": 1
},
"malware.hash.md5": {
"description": "A string depicting an MD5 checksum for a file, be it a malware sample for example.",
"misp-attribute": "text",
"ui-priority": 1
},
"malware.hash.sha1": {
"description": "A string depicting a SHA1 checksum for a file, be it a malware sample for example.",
"misp-attribute": "text",
"ui-priority": 1
},
"malware.hash.sha256": {
"description": "A string depicting a SHA256 checksum for a file, be it a malware sample for example.",
"misp-attribute": "text",
"ui-priority": 1
},
"malware.name": {
"description": "The malware name in lower case.",
"misp-attribute": "text",
"ui-priority": 1
},
"malware.version": {
"description": "A version string for an identified artifact generation, e.g. a crime-ware kit.",
"misp-attribute": "text",
"ui-priority": 1
},
"misp.attribute_uuid": {
"description": "MISP - Malware Information Sharing Platform & Threat Sharing UUID of an attribute.",
"misp-attribute": "text",
"ui-priority": 1
},
"misp.event_uuid": {
"description": "MISP - Malware Information Sharing Platform & Threat Sharing UUID.",
"misp-attribute": "text",
"ui-priority": 1
},
"output": {
"description": "Event data converted into foreign format, intended to be exported by output plugin.",
"misp-attribute": "text",
"ui-priority": 1
},
"protocol.application": {
"description": "e.g. vnc, ssh, sip, irc, http or smtp.",
"misp-attribute": "text",
"ui-priority": 1
},
"protocol.transport": {
"description": "e.g. tcp, udp, icmp.",
"misp-attribute": "text",
"ui-priority": 1
},
"raw": {
"description": "The original line of the event from encoded in base64.",
"misp-attribute": "text",
"ui-priority": 1
},
"rtir_id": {
"description": "Request Tracker Incident Response ticket id.",
"misp-attribute": "counter",
"ui-priority": 1
},
"screenshot_url": {
"description": "Some source may report URLs related to a an image generated of a resource without any metadata. Or an URL pointing to resource, which has been rendered into a webshot, e.g. a PNG image and the relevant metadata related to its retrieval/generation.",
"misp-attribute": "url",
"ui-priority": 1
},
"source.abuse_contact": {
"description": "Abuse contact for source address. A comma separated list.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.account": {
"description": "An account name or email address, which has been identified to relate to the source of an abuse event.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.allocated": {
"description": "Allocation date corresponding to BGP prefix.",
"misp-attribute": "datetime",
"ui-priority": 1
},
"source.as_name": {
"description": "The autonomous system name from which the connection originated.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.asn": {
"description": "The autonomous system number from which originated the connection.",
"misp-attribute": "AS",
"ui-priority": 1
},
"source.domain_suffix": {
"description": "The suffix of the domain from the public suffix list.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.fqdn": {
"description": "A DNS name related to the host from which the connection originated. DNS allows even binary data in DNS, so we have to allow everything. A final point is stripped, string is converted to lower case characters.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.cc": {
"description": "Country-Code according to ISO3166-1 alpha-2 for the source IP.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.city": {
"description": "Some geolocation services refer to city-level geolocation.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.country": {
"description": "The country name derived from the ISO3166 country code (assigned to cc field).",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.cymru_cc": {
"description": "The country code denoted for the ip by the Team Cymru asn to ip mapping service.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.geoip_cc": {
"description": "MaxMind Country Code (ISO3166-1 alpha-2).",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.latitude": {
"description": "Latitude coordinates derived from a geolocation service, such as MaxMind geoip db.",
"misp-attribute": "float",
"ui-priority": 1
},
"source.geolocation.longitude": {
"description": "Longitude coordinates derived from a geolocation service, such as MaxMind geoip db.",
"misp-attribute": "float",
"ui-priority": 1
},
"source.geolocation.region": {
"description": "Some geolocation services refer to region-level geolocation.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.geolocation.state": {
"description": "Some geolocation services refer to state-level geolocation.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.ip": {
"description": "The ip observed to initiate the connection",
"misp-attribute": "ip-src",
"ui-priority": 1
},
"source.local_hostname": {
"description": "Some sources report a internal hostname within a NAT related to the name configured for a compromised system",
"misp-attribute": "text",
"ui-priority": 1
},
"source.local_ip": {
"description": "Some sources report a internal (NATed) IP address related a compromised system. N.B. RFC1918 IPs are OK here.",
"misp-attribute": "ip-src",
"ui-priority": 1
},
"source.network": {
"description": "CIDR for an autonomous system. Also known as BGP prefix. If multiple values are possible, select the most specific.",
"misp-attribute": "ip-src",
"ui-priority": 1
},
"source.port": {
"description": "The port from which the connection originated.",
"misp-attribute": "counter",
"ui-priority": 1
},
"source.registry": {
"description": "The IP registry a given ip address is allocated by.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.reverse_dns": {
"description": "Reverse DNS name acquired through a reverse DNS query on an IP address. N.B. Record types other than PTR records may also appear in the reverse DNS tree. Furthermore, unfortunately, there is no rule prohibiting people from writing anything in a PTR record. Even JavaScript will work. A final point is stripped, string is converted to lower case characters.",
"misp-attribute": "text",
"ui-priority": 1
},
"source.tor_node": {
"description": "If the source IP was a known tor node.",
"misp-attribute": "boolean",
"ui-priority": 1
},
"source.url": {
"description": "A URL denotes an IOC, which refers to a malicious resource, whose interpretation is defined by the abuse type. A URL with the abuse type phishing refers to a phishing resource.",
"misp-attribute": "url",
"ui-priority": 1
},
"source.urlpath": {
"description": "The path portion of an HTTP or related network request.",
"misp-attribute": "text",
"ui-priority": 1
},
"status": {
"description": "Status of the malicious resource (phishing, dropzone, etc), e.g. online, offline.",
"misp-attribute": "text",
"ui-priority": 1
},
"time.observation": {
"description": "The time the collector of the local instance processed (observed) the event.",
"misp-attribute": "datetime",
"ui-priority": 1
},
"time.source": {
"description": "The time of occurence of the event as reported the feed (source).",
"misp-attribute": "datetime",
"ui-priority": 1
},
"tlp": {
"description": "Traffic Light Protocol level of the event.",
"misp-attribute": "text",
"ui-priority": 1
}
},
"description": "IntelMQ Event",
"meta-category": "network",
"name": "intelmq_event",
"uuid": "491ac7d2-25a1-4078-8246-b04a132d003d",
"version": 3
}
Reference in New Issue View Git Blame Copy Permalink